[Tutorial] Notification Led for the Moto G3 with Tasker (experimental) - Moto G 2015 General

I've been using this when working in my office with my phone connected to my laptop, and find that it works really well, so I decided to share.
Cons:
- Your phone needs to be connected to a power source
- There is a 10 to 20 seconds delay between when the notification arrives and when the led light turns on
- The led light is white. No other colour is available
- You need to be rooted
- You need to buy Tasker and the AutoNotification plugin which are not cheap.
Pros:
- Your led light turns on whenever you get a notification
- You can choose the apps for which you want the notification led to come on
- The led light switches off when you dismiss your notification
- The led light comes on even if your screen is on
- You don’t have to look at your phone continually to catch sight of the Moto Display screen
You need:
- Tasker and AutoNotification from the PlayStore
_________________________________________
TUTORIAL
1. Install Tasker and AutoNotification on your Moto G3
2. Go to Tasker
Create 1st Task:
1. Click on Tasks and on the + button
2. New Task Name: Led On, then tick
3. Click + to add an Action
4. Choose Code
5. Choose Run Shell
6. In Command, type: echo battery-charging-blink-full-solid >/sys/class/leds/charging/trigger
7. Click Use Root
8. Click your back button
Create 2nd Task:
1. Click on Tasks and on the + button
2. New Task Name: Led Off, then tick
3. Click + to add an Action
4. Choose Code
5. Choose Run Shell
6. In Command, type: echo none >/sys/class/leds/charging/trigger
7. Click Use Root
8. Click your back button
Create a Profile:
3. Click on Profile, click the + button and choose State
4. Click on Plugin
5. Click on AutoNotification
6. Click on Intercept
7. In Configuration, click on the pen icon
8. Tick the Event Behaviour option
9. Click on Apps
10. Select all the apps that you want led notifications for
11. Click OK
12. Click on the tick at the top of the screen
13. Click your back button
14. Choose Task: Led On
15. Long Press on Led On
16. Click Add Exit Task
17. Choose Led Off
18. Click your back button
19. Success!!!
Enjoy! Any questions ask here…

I use tasker and the camera flash.
Sent from my MotoG3 using XDA Free mobile app

krsmit0 said:
I use tasker and the camera flash.
Sent from my MotoG3 using XDA Free mobile app
Click to expand...
Click to collapse
Too bright for me...?

I appreciate the time you put in to this tutorial. For me though having to have the phone plugged in is a deal breaker. If I'm tethered to my desk there are better options like Pushbullet, which is in fact what I use at work. It puts notifications right up on my PC monitor.
I do miss the multi-colored light on my Nexus 4. It is too bad that manufacturers are moving away from them.
Sent from my MotoG3 using XDA Free mobile app

Why am I unable to see LED notification light on my XT1550 when charging?? Where is the led?

skr975 said:
Why am I unable to see LED notification light on my XT1550 when charging?? Where is the led?
Click to expand...
Click to collapse
Hi! That's because it is a hidden led which needs to be implemented using a third party app such as Moto Led or Tasker...

Thank you... but as much as I appreciate you going through the trouble to make this tutorial, this isn't very useful... All this is doing is taking a hard coded charging LED which is disabled in software and toggling the charging state on and off when a notification (or other trigger) is active, not really a notification light, and only if the device is plugged in, which most people don't do, or need to do, during an average day. The fact that the circuit which drives this LED is not powered unless an external charging source is connected makes most of these projects to use it frivolous, but I hope I am wrong to be honest.

May be offtopic but can't a custom kernel make it possible to use led for notifications??
I know that's possible because I have seen such projects.
Even Moto X play got a custom kernel which activates led for notifications.
Y not someone with knowledge of compiling kernels try this with the help of the user who made that kernel for X play.
============================== @squid2 can you help make the kernel for G3??
==============================
Sent from my SM-A800F using XDA Free mobile app

SArnab©® said:
May be offtopic but can't a custom kernel make it possible to use led for notifications??
I know that's possible because I have seen such projects.
Even Moto X play got a custom kernel which activates led for notifications.
Y not someone with knowledge of compiling kernels try this with the help of the user who made that kernel for X play.
============================== @squid2 can you help make the kernel for G3??
==============================
Sent from my SM-A800F using XDA Free mobile app
Click to expand...
Click to collapse
I had spent many hours examining LED notifications on osprey. Unfortunately, we are held back by a hardware difference beteen surnia/lux and osprey. All of the Motorola devices equipped with stml0xx sensor hub were originally equipped with a notification LED that could be controlled by both the sensor hub and the power management IC.
Earlier this year, Motorola decided to drop the LED notification feature and removed the capability from the kernel. This decision was made about a month after the design of the production surnia hardware was completed, and a month before production osprey hardware design was complete. As a result, the hardware for LED notifications controlled by the sensor hub was left in on surnia, but the relevant traces and resistors were removed on osprey. They probably did this to reduce complexity, and it may have saved them a tenth of a cent per device on resistors. They didn't remove the trace on lux, perhaps because it had gone out of mind by the time they were paying attention to production lux hardware, or perhaps because they realized that it was useless to do so, and would only limit the capabilities of the device.
The consequence of this is that the LED can only be controlled through the PMIC on osprey, while it can be controlled by the PMIC or sensor hub on surnia and lux. The sensor hub was designed to support LED notifications, and can run the LED arbitrarily. The PMIC is physically designed to only provide power to the LED driving circuit when a charger is plugged in.
Unfortunately, as a result of this hardware limitation, I don't think it will be possible to have LED notifications with the device unplugged on osprey.

squid2 said:
I had spent many hours examining LED notifications on osprey. Unfortunately, we are held back by a hardware difference beteen surnia/lux and osprey. All of the Motorola devices equipped with stml0xx sensor hub were originally equipped with a notification LED that could be controlled by both the sensor hub and the power management IC.
Earlier this year, Motorola decided to drop the LED notification feature and removed the capability from the kernel. This decision was made about a month after the design of the production surnia hardware was completed, and a month before production osprey hardware design was complete. As a result, the hardware for LED notifications controlled by the sensor hub was left in on surnia, but the relevant traces and resistors were removed on osprey. They probably did this to reduce complexity, and it may have saved them a tenth of a cent per device on resistors. They didn't remove the trace on lux, perhaps because it had gone out of mind by the time they were paying attention to production lux hardware, or perhaps because they realized that it was useless to do so, and would only limit the capabilities of the device.
The consequence of this is that the LED can only be controlled through the PMIC on osprey, while it can be controlled by the PMIC or sensor hub on surnia and lux. The sensor hub was designed to support LED notifications, and can run the LED arbitrarily. The PMIC is physically designed to only provide power to the LED driving circuit when a charger is plugged in.
Unfortunately, as a result of this hardware limitation, I don't think it will be possible to have LED notifications with the device unplugged on osprey.
Click to expand...
Click to collapse
Thanks for clearing the clouds.
Is it possible to fake plugged state?
If yes than may be it will be possible to make it work as expected.
Sent from my SM-A800F using XDA Free mobile app

acejavelin said:
Thank you... but as much as I appreciate you going through the trouble to make this tutorial, this isn't very useful... All this is doing is taking a hard coded charging LED which is disabled in software and toggling the charging state on and off when a notification (or other trigger) is active, not really a notification light, and only if the device is plugged in, which most people don't do, or need to do, during an average day. The fact that the circuit which drives this LED is not powered unless an external charging source is connected makes most of these projects to use it frivolous, but I hope I am wrong to be honest.
Click to expand...
Click to collapse
Hey there, no worries, it only took about 5 minutes to write the tutorial. I said it was "experimental" because it is not a properly functional hack. It's just a bit of fun for people who like messing around with Tasker. I happen to find it useful, but like you, I would much prefer for the led to be fully functional. I really miss this from the Moto G1.

SArnab©® said:
Thanks for clearing the clouds.
Is it possible to fake plugged state?
If yes than may be it will be possible to make it work as expected.
Sent from my SM-A800F using XDA Free mobile app
Click to expand...
Click to collapse
It's possible to fake being plugged in software, but I don't think it's possible to fool the PMIC into thinking it's plugged in software. Even if it were possible, that would result in strange behaviour as the PMIC would try to charge the battery when no charger is plugged in.

He just said it was a hardware limitation. Convincing software its charging won't tell hardware to provide the led power.
Sent from my MotoG3 using XDA Free mobile app

squid2 said:
It's possible to fake being plugged in software, but I don't think it's possible to fool the PMIC into thinking it's plugged in software. Even if it were possible, that would result in strange behaviour as the PMIC would try to charge the battery when no charger is plugged in.
Click to expand...
Click to collapse
Thanks for answering my curiosities.
krsmit0 said:
He just said it was a hardware limitation. Convincing software its charging won't tell hardware to provide the led power.
Sent from my MotoG3 using XDA Free mobile app
Click to expand...
Click to collapse
I read that. What's wrong in asking though if it's possible some other way round?
Sent from my SM-A800F using XDA Free mobile app

squid2 said:
I had spent many hours examining LED notifications on osprey. Unfortunately, we are held back by a hardware difference beteen surnia/lux and osprey. All of the Motorola devices equipped with stml0xx sensor hub were originally equipped with a notification LED that could be controlled by both the sensor hub and the power management IC.
Earlier this year, Motorola decided to drop the LED notification feature and removed the capability from the kernel. This decision was made about a month after the design of the production surnia hardware was completed, and a month before production osprey hardware design was complete. As a result, the hardware for LED notifications controlled by the sensor hub was left in on surnia, but the relevant traces and resistors were removed on osprey. They probably did this to reduce complexity, and it may have saved them a tenth of a cent per device on resistors. They didn't remove the trace on lux, perhaps because it had gone out of mind by the time they were paying attention to production lux hardware, or perhaps because they realized that it was useless to do so, and would only limit the capabilities of the device.
The consequence of this is that the LED can only be controlled through the PMIC on osprey, while it can be controlled by the PMIC or sensor hub on surnia and lux. The sensor hub was designed to support LED notifications, and can run the LED arbitrarily. The PMIC is physically designed to only provide power to the LED driving circuit when a charger is plugged in.
Unfortunately, as a result of this hardware limitation, I don't think it will be possible to have LED notifications with the device unplugged on osprey.
Click to expand...
Click to collapse
Just a doubt did you physically checked the resistor or you are just guessing or you used some method ???
Sent from my MotoG3 using XDA Free mobile app

Need Pictures
Can someone who had followed this procedure, upload a picture of how the Moto G 2015 looks when the notification light is lit up ?

Go on Google Image and type in "moto g3 hidden led"

SArnab©® said:
May be offtopic but can't a custom kernel make it possible to use led for notifications??
I know that's possible because I have seen such projects.
Even Moto X play got a custom kernel which activates led for notifications.
Y not someone with knowledge of compiling kernels try this with the help of the user who made that kernel for X play.
============================== @squid2 can you help make the kernel for G3??
==============================
Sent from my SM-A800F using XDA Free mobile app
Click to expand...
Click to collapse
Awesome ...

How to add flash notifications on kernel instead led light (its impossible..)?

Related

Notification & Power

Hi all,
I have a Snap with the Official WM6.5 ROM.
1 - I want to change the notification settings : for example when you miss a call or a SMS, then the LED should flash until you see the missed call/SMS.
On My HD2 I can do it fairly easily, but on the Snap I do not wee how to do that....
2 - When using Tomtom, the phone go standby, I would like to force the phone to have the display always on... again on my HD2, this is working as expected, but on the Snap, no way... I even change the power settings, but still the screen switch off after a while.
If you have ideas I will be happy to test them.
thanks
Denis
The LED issue has all ready been addressed in this forum: http://forum.xda-developers.com/showthread.php?t=539190
Thanks cswroe,
I will test this LED fix.
Why WM6.5 is different than a touch screen, I mean, why the option are not on both the same....
Br,
Denis
Yahouuuu
it works.
Big thanks.
Denis
cswroe said:
The LED issue has all ready been addressed in this forum: http://forum.xda-developers.com/showthread.php?t=539190
Click to expand...
Click to collapse
Maybe I'm crazy, but I think when my D3G is on the charger and fully charged (solid green LED) that missed calls, messages, etc, won't cause the LED to blink. Have you noticed this?
-GoJ
Ghost of Jaco said:
Maybe I'm crazy, but I think when my D3G is on the charger and fully charged (solid green LED) that missed calls, messages, etc, won't cause the LED to blink. Have you noticed this?
-GoJ
Click to expand...
Click to collapse
It will not flash until I disconnect it from the charger.
cswroe said:
It will not flash until I disconnect it from the charger.
Click to expand...
Click to collapse
The only way to get it to flash when its on the charger is to turn off the charge light via registry edit, but then you wont know when the device is fully charged unless its on and you pick it up... I have not found a way around this... yet

[Q] ctrl calibration problem

Is there another way to calibrate this thing or do I just have a $50 paper weight ?
The left stick on my C.T.R.L. recently went out of whack, it is always moving the pointer down unless I hold a bit of "up" on it.
I tried the calibration steps from the Mad Catz site and it will not work. ie: no flashing purple light. I tried it on my M.O.J.O. and my PC, same problem.
Thank You for any help.
Soooo, paperweight then. Great!
vwtazzman said:
Soooo, paperweight then. Great!
Click to expand...
Click to collapse
Did you put in a support ticket with MadCatz? May be a defunct unit.
christoph80 said:
Did you put in a support ticket with MadCatz? May be a defunct unit.
Click to expand...
Click to collapse
Yup and it looks like the unit went bad. They will warranty it but why bother.
The sad thing is that this whole console has failed in one way or another.
I tried to pair my NYKO to it which pairs with every other android device I own and....will not pair, WTF?
And I am SO tired of seeing "not compatible with M.O.J.O." in the google store!
I have a MK908 and MK802 that will work with everything.
What't the hell MadCatz?
I should have bought a Shield.
By by MOJO
vwtazzman said:
Yup and it looks like the unit went bad. They will warranty it but why bother.
The sad thing is that this whole console has failed in one way or another.
I tried to pair my NYKO to it which pairs with every other android device I own and....will not pair, WTF?
And I am SO tired of seeing "not compatible with M.O.J.O." in the google store!
I have a MK908 and MK802 that will work with everything.
What't the hell MadCatz?
I should have bought a Shield.
By by MOJO
Click to expand...
Click to collapse
Did you update to the latest firmware? Check the MOJO icon on your homescreen, go to the fifth step and get the 205-TS firmware as that will make a huge difference to the "not compatible" incidence rate.
We've had no issues pairing the Nyko or OUYA controller with MOJO though - are you correctly placing the Nyko pad into pairing mode?
Dunno if this is resolved but for future users having an issue
The re-calibrate process for the C.T.R.L.R is as follows
Make sure the C.T.R.L.R is paired and connected to a host
Press and hold A, B, X, Y, L1 and R1 for 3 seconds – the status LED will turn purple
Press the Back button once – the status LED will begin to flash
Move each stick and trigger through their full range of movement 4 times
Press the Start button once – the status LED will return to blue to show the pad is in normal operation
According to madcatz
Edit: Dunno if I even read the first post Jesus,
also stated this before in the correct thread but the update dramatically increased the incompatible message for me, hardly saw it before now its every other app and loads that used to be compatible ain't. Controller is much much better. Just now I've got the choise of laggy controller and loads of apps or brilliant controller and no apps. Lose lose
Ash180287 said:
Dunno if this is resolved but for future users having an issue
The re-calibrate process for the C.T.R.L.R is as follows
Make sure the C.T.R.L.R is paired and connected to a host
Press and hold A, B, X, Y, L1 and R1 for 3 seconds – the status LED will turn purple
Press the Back button once – the status LED will begin to flash
Move each stick and trigger through their full range of movement 4 times
Press the Start button once – the status LED will return to blue to show the pad is in normal operation
According to madcatz
Edit: Dunno if I even read the first post Jesus,
also stated this before in the correct thread but the update dramatically increased the incompatible message for me, hardly saw it before now its every other app and loads that used to be compatible ain't. Controller is much much better. Just now I've got the choise of laggy controller and loads of apps or brilliant controller and no apps. Lose lose
Click to expand...
Click to collapse
interesting instructions.. read more like a finishing move lol
Yeah, sucks google play is stuffed.. I tried going back to the previous firmware update but the rooting doesn't fix it :/
I am having the same issue with my Mac. Tried to recalibrate but its stuck at the bottom left of the screen.

trouble with random light screen variations

Hi
I have a trouble and I wish to test my phone. I have a samsun note 4. Sometimes I stay in the dark or low light in the bedroom, with conditions of constant lights, browsing the web with the browser.
I avoid to cover with the finger the light sensor in front f the phone, but randomly it happens that the screen brightness will rise and fall. This is not a flash but a random chand of display light.
I gave a look to settings and I realized that the cursor is set maximum light (that is no software set light down).
it is possible that there is a defect in the screen? can you suggest a method to test the operation?
The phenomenon is not frequent but since my phone is hot in the upper part I going to consider some electronic defect
Thank you in advance
sareide
Dial *#0*# to open hardware test (screen, sensors,...)
If it doesn't work, you can open it with Samsung Phone Info app on play store. (vndnguyen)
geevh said:
Dial *#0*# to open hardware test (screen, sensors,...)
If it doesn't work, you can open it with Samsung Phone Info app on play store. (vndnguyen)
Click to expand...
Click to collapse
Hi I need to test the sensors on my note 4 the s-pen wont detect when its detached or inserted, but it works for everything else, so I want to test the sensor in the phone, but I need to use the phone info app because I'm running a custom rom and I cant get into service mode using the phone code, any ideas what option i need to choose with phone info app please?
I'm not sure if it will work for you. I'm on a custom rom based on official Samsung firmware. In the phone info app, menu, secret codes, I have the first option 0* (HWmoduletest). I opened it with Launch1
In that program there's a a possibility to do a S-pen test.
Of course, this might not work if you're on CM rom or if your rom developer removed the app to do this test. In that case you can better ask it where you got your rom.
I'm not familiar with CM rom

Led's color problem at first blink

Guys I have a strange beavhiour on my phone. When the LED notification starts "blinking" the first "blink" is always red or blue no matter what color the specific notification what set to.
After the first red or blue "blink" the next "blinks" of the LED looks right as it is setted for the specific notification.
Has anyone come across such weird behaviour? Is this a hardware or software bug?
Sended from my Samsung Galaxy S7 Edge Gold Platinum
It's been happening since the S6. Why is this such a big deal?
Sent from my Pebble Time
Brava27 said:
It's been happening since the S6. Why is this such a big deal?
Sent from my Pebble Time
Click to expand...
Click to collapse
Because it's not normal and because this is an uncommon thing since not everybody has this beavhiour.
Sended from my Samsung Galaxy S7 Edge Gold Platinum
turtuv said:
Because it's not normal and because this is an uncommon thing since not everybody has this beavhiour.
Sended from my Samsung Galaxy S7 Edge Gold Platinum
Click to expand...
Click to collapse
I have it, had it with my note 5, s6. It's not uncommon.
Sent from my Pebble Time
Brava27 said:
I have it, had it with my note 5, s6. It's not uncommon.
Sent from my Pebble Time
Click to expand...
Click to collapse
I first saw that today. I don't understand the meaning of this beavhiour.
Sended from my Samsung Galaxy S7 Edge Gold Platinum
I have this but it's totally not a problem in any way.
dannejanne said:
I have this but it's totally not a problem in any way.
Click to expand...
Click to collapse
I know that is not a problem, but if it is a "design" choice so all S7 must have this, right? In any case I don't understand why the first blink has to be red.
Sended from my Samsung Galaxy S7 Edge Gold Platinum
Rooted with TWRP
Gravity MM (LED Control)
removes what your refering to, I use White as Base LED Colour notification.
Blue for SMS
Purple for some selected Medium Priority Notifications.
Green for Missed SMS
Yellow Voice Mail
Much better than the Blue for all (Whats the point in a LED with Multiple Colours when it never uses them)
dave7802 said:
Rooted with TWRP
Gravity MM (LED Control)
removes what your refering to, I use White as Base LED Colour notification.
Blue for SMS
Purple for some selected Medium Priority Notifications.
Green for Missed SMS
Yellow Voice Mail
Much better than the Blue for all (Whats the point in a LED with Multiple Colours when it never uses them)
Click to expand...
Click to collapse
Light manager app does that, but that's not what i'm talking about. Read the first post, do you experienced that behavior?
turtuv said:
Light manager app does that, but that's not what i'm talking about. Read the first post, do you experienced that behavior?
Click to expand...
Click to collapse
Rooted with TWRP
Gravity MM (LED Control)
removes what your referring to
dave7802 said:
Rooted with TWRP
Gravity MM (LED Control)
removes what your refering to
Click to expand...
Click to collapse
I don't understand, you didn't answered to my question...never mind :good:
turtuv said:
I don't understand, you didn't answered to my question...never mind :good:
Click to expand...
Click to collapse
Okay lets try it another way:
When you get a Notification, The first LED blinks Red.
Then the colour you defined the notification to, then blinks that colour.
I have Rooted with TWRP, I am using Gravity MM
i do not experience this.
"it removes the first blink notification - what your referring to in the OP"
dave7802 said:
Okay lets try it another way:
When you get a Notification, The first LED blinks Red.
Then the colour you defined the notification to, then blinks that colour.
I have Rooted with TWRP, I am using Gravity MM
i do not experience this.
"it removes the first blink notification - what your referring to in the OP"
Click to expand...
Click to collapse
Ok now it's clear, thank you. I don't want to root my device tho. Is there another way?
Sended from my Samsung Galaxy S7 Edge Gold Platinum
turtuv said:
Ok now it's clear, thank you. I don't want to root my device tho. Is there another way?
Sended from my Samsung Galaxy S7 Edge Gold Platinum
Click to expand...
Click to collapse
There used to be a method using Tasker,
Its been a while since i used this, But here is the link:
https://play.google.com/store/apps/details?id=com.tinyroar.galaxys3ledcontroller&hl=en
The App may not be needed and it may be possible to control LED using Tasker alone.
If you setup the rules correct, i believe you should be able to overcome this. i.e. Turn of ALL LED prior to pushing your first LED Custom Colour.
dave7802 said:
There used to be a method using Tasker,
Its been a while since i used this, But here is the link:
https://play.google.com/store/apps/details?id=com.tinyroar.galaxys3ledcontroller&hl=en
The App may not be needed and it may be possible to control LED using Tasker alone.
If you setup the rules correct, i believe you should be able to overcome this. i.e. Turn of ALL LED prior to pushing your first LED Custom Colour.
Click to expand...
Click to collapse
It seems a little bit tricky. What about Light Manager instead?
Ill come back to you in a hour and let you know
There may be a way to do a little bit of a hack, I believe the issue following the Charging LED Notification
Using something like SQlite Editor, you may be able to disable the LED Charging.
Removing the Red LED Notification all together
(This is in theory, Untested, but ill let you know later)
dave7802 said:
Ill come back to you in a hour and let you know
There may be a way to do a little bit of a hack, I believe the issue following the Charging LED Notification
Using something like SQlite Editor, you may be able to disable the LED Charging.
Removing the Red LED Notification all together
(This is in theory, Untested, but ill let you know later)
Click to expand...
Click to collapse
I don't want to remove red led during charging, but thank you for your help. I'm waiting your news
Try this, you may get the Red light gone.
It may replace it with Green.
Try accessibility settings and turn on notification reminders.
Its a odd workaround, But with my Modules disabled, I no longer get the the RED LED
dave7802 said:
Try this, you may get the Red light gone.
It may replace it with Green.
Try accessibility settings and turn on notification reminders.
Its a odd workaround, But with my Modules disabled, I no longer get the the RED LED
Click to expand...
Click to collapse
If it is a replacement so it is not useful, I stick with red. You are rooted so you solved the problem easily..but no big deal, I just wanted to be sure that this is not a problem of my phone, but this is normal [emoji3]
Sended from my Samsung Galaxy S7 Edge Gold Platinum
dave7802 said:
Try this, you may get the Red light gone.
It may replace it with Green.
Try accessibility settings and turn on notification reminders.
Its a odd workaround, But with my Modules disabled, I no longer get the the RED LED
Click to expand...
Click to collapse
I don't want to replace it, you are rooted so you solved the problem easily. Anyway it is not a big deal, I just wanted to be sure that this is not a problem of my phone and that it is normal [emoji3]
Sended from my Samsung Galaxy S7 Edge Gold Platinum

Open Camera bricked Le Pro 3

My phone is a Chinese version Le Pro 3, and it looks like the Open Camera app bricked the phone.
I was taking a picture when the phone suddenly shut down and now does not turn on.
I connected it to charger but there is no led light nor battery progress movement. The phone looks dead. Pressing on power button or power and any volume does not result in anything. The phone is off, non responsive and does not even respond to charging. Is the phone bricked or is there something else I could try?
- This happened 5 days ago as well , also taking picture I think it was Open Camera as well. Plugged the phone to charger and couple of minutes later I was able to revive it
- been on 2 different le eco chargers/USBC cables for the past several hours
- no signs of life
- no charging progress bar
- no vibrations, no Led light
- tried pressing power button for 60 seconds or longer, combination with volume down, up and both volume keys as well.
- the difference between now and 5 days ago is the phone has TWRP, root, and 19s custom USA ROM by Steve Mars.
There are no signs of life, no signs of charging, the phone seems completely dead.
I am doubtful any app can kill the phone just like that. A bad flash of ROM definitely but not app, even system app that could potentially overclock or overvolt the SoC.
It could be a lemon so contact the LeEco and send it back for warranty.
P.S.
I tried Open Camera just weeks ago and it did not kill my phone. I uninstalled it because Google Camera App is still better.
rubiohiguey said:
My phone is a Chinese version Le Pro 3, and it looks like the Open Camera app bricked the phone.
I was taking a picture when the phone suddenly shut down and now does not turn on.
I connected it to charger but there is no led light nor battery progress movement. The phone looks dead. Pressing on power button or power and any volume does not result in anything. The phone is off, non responsive and does not even respond to charging. Is the phone bricked or is there something else I could try?
- This happened 5 days ago as well , also taking picture I think it was Open Camera as well. Plugged the phone to charger and couple of minutes later I was able to revive it
- been on 2 different le eco chargers/USBC cables for the past several hours
- no signs of life
- no charging progress bar
- no vibrations, no Led light
- tried pressing power button for 60 seconds or longer, combination with volume down, up and both volume keys as well.
- the difference between now and 5 days ago is the phone has TWRP, root, and 19s custom USA ROM by Steve Mars.
There are no signs of life, no signs of charging, the phone seems completely dead.
Click to expand...
Click to collapse
Did you try connecting it to a pc? Maybe something in your phone like the motherboard burnt..
1) No sound or any activity when connected to USB on PC. I also installed qualcomm drivers used for brick recovery but there is nothing coming up in the Ports section of device manager either. Though my PC immediately came up with "power overload on USB" or something like that. I connected a different Le Eco phone, another phone, and a portable hard drive to the same USB port, no issue. This happened multiple times on different ports. Makes me think there could be some short circuit inside the phone?
2) I shot 8-10 photos with Open camera before the first issue. Then after reviving it first time, in the 5 days after that, I shot maybe 50+ photos with open camera. This time, it went down when I was changing lighting type within Open Camera app, even without pressing the shutter. But both cases are connected to Open Camera. I also do not believe the app is faulty as I have been using it for a year on Meizu MX5. I am thinking a memory or CPU leak somehow triggered by the app killed the phone?
My Aliexpress seller wants me to make a video for them to authorize a RMA... video of what? of a dead phone? Ok they can have it, as I see this is a standard procedure on many sites. I am just pissed that a superphone with supposedly superior hardware does this.
rubiohiguey said:
1) No sound or any activity when connected to USB on PC. I also installed qualcomm drivers used for brick recovery but there is nothing coming up in the Ports section of device manager either. Though my PC immediately came up with "power overload on USB" or something like that. I connected a different Le Eco phone, another phone, and a portable hard drive to the same USB port, no issue. This happened multiple times on different ports. Makes me think there could be some short circuit inside the phone?
2) I shot 8-10 photos with Open camera before the first issue. Then after reviving it first time, in the 5 days after that, I shot maybe 50+ photos with open camera. This time, it went down when I was changing lighting type within Open Camera app, even without pressing the shutter. But both cases are connected to Open Camera. I also do not believe the app is faulty as I have been using it for a year on Meizu MX5. I am thinking a memory or CPU leak somehow triggered by the app killed the phone?
My Aliexpress seller wants me to make a video for them to authorize a RMA... video of what? of a dead phone? Ok they can have it, as I see this is a standard procedure on many sites. I am just pissed that a superphone with supposedly superior hardware does this.
Click to expand...
Click to collapse
I am sorry to hear this man...i got lex720 and its great....i have it for 2 months now....not even 1 issue. Hope you go well through this. Cheers!
rubiohiguey said:
My Aliexpress seller wants me to make a video for them to authorize a RMA... video of what? of a dead phone? Ok they can have it, as I see this is a standard procedure on many sites. I am just pissed that a superphone with supposedly superior hardware does this.
Click to expand...
Click to collapse
Yes just make a video of u pressing Power button and phone not coming to life. And then make video of u plugging in charger and phone not coming to life. Basically make video of the dead phone while u apply your already failed resuscitation procedures. They have to file RMA on the proof from customer who is in remote place by submitting videos submitted by the owner of the device. This is the rule which applies to every electronic/mechanical device purchased through Ali Express. I RMA'd my Quadcopter Drone this way which was dead out of the box.
I have 3 members in my family who use Le Eco Pro 3 North America version. One member of the family's phone bricked twice! I'm afraid the others wont last.
jyooo said:
I have 3 members in my family who use Le Eco Pro 3 North America version. One member of the family's phone bricked twice! I'm afraid the others wont last.
Click to expand...
Click to collapse
How and how did you save the Phone on first brick
mertsamet said:
How and how did you save the Phone on first brick
Click to expand...
Click to collapse
Sorry about that, wasn't clear on my situation. The first phone bricked, I had to send it in for a replacement and the replacement they sent bricked within a month. I wasn't even doing anything like rooting, just normal app usage. The phone works great when it works though.
[/COLOR]
jyooo said:
Sorry about that, wasn't clear on my situation. The first phone bricked, I had to send it in for a replacement and the replacement they sent bricked within a month. I wasn't even doing anything like rooting, just normal app usage. The phone works great when it works though.
Click to expand...
Click to collapse
In my opinion, I think they sended you the same bricked phone, not a new one
Hi, Have you try turn it on by press: Power button + Volume Up, at the same time.
I flashed Miui 8, I power the phone off and Power butoon didn't work. I use the method above to get it back to life.
All key combinations have been tried for hours and hours, even left overnight several with multiple button combinations pressed while on the charger.

Categories

Resources