Database Info

Optimus 3d notification led idea

Maybe this belongs in the development area but...
The evo3d got a notification led wich i like...what about if we can make the capacitive button led's blink or something when we have a mail and sms...
Maybe more guys have this idea but well....tell me if its possible and a good idea

It is probably possible and I think developers will have a hand on it if they havent yet.

It will be eventually supported.

this idea is awesome. i think it is possible

joker20 said:
this idea is awesome. i think it is possible
Click to expand...
Click to collapse
Glad someone's liking it

This would be a nice to have for sure. If can light up those "buttons" to use for notification, it will be great.

This is already done with O2X, so it is definitely on the way for us

My previous phone was GalaxyS which had no led aswell.
I used a programmed called NoLed on the Galaxy. Installed on Optimus 3d and seems to work fine.
Link to developer - http://www.devasque.com/noled/index.php

HTCtouchuk said:
My previous phone was GalaxyS which had no led aswell.
I used a programmed called NoLed on the Galaxy. Installed on Optimus 3d and seems to work fine.
Link to developer - http://www.devasque.com/noled/index.php
Click to expand...
Click to collapse
It doesnt support the capacitive button led's.

Sorry i was only suggesting this as a temporary alternative until further developments.

I really like this idea!
But is it possible to expand on it further?
Since there's 4 capacitive buttons on the phone, are we able to make them blink individually?
For example... home button blinks when we have a missed call, menu button blinks when we have a message, back button blinks when we have an email, and etc?

Noled seems to be working fine for me...

gismo918 said:
Noled seems to be working fine for me...
Click to expand...
Click to collapse
Yeah works fine for letting the SCREEN blink?
Were talking about the buttons

HTCtouchuk said:
Sorry i was only suggesting this as a temporary alternative until further developments.
Click to expand...
Click to collapse
Unfortunately not. As the app page states, AMOLED uses no power displaying a fully black pixel so displaying alerts on the screen takes very little power.
Now as the O3D has an old fashioned LCD, it consumes potentially a ton of power just to turn the screen on at all, because it has to light the whole screen just to start. Plus, it uses the MOST power displaying black (least displaying all white), so it would need the opposite behaviour.
[UPDATE]
Ah I see you can make the screen blink, I didn't notice that at first. Might actually be useful then.

i've tested it with the developer of the LG notification app. it seems, that the files which have to be used are'nt writeable. so without root it won't work
perhaps we should send tons of mails to LG, that they make it possible.

Alex Atkin UK said:
[UPDATE]
Ah I see you can make the screen blink, I didn't notice that at first. Might actually be useful then.
Click to expand...
Click to collapse
Also the notifications can have a time limit, i have set at 15mins and haven't noticed any battery drain.

Modified 2X/Black touch led notification app
Hi guys,
I've modified Martin Börjesson's app and now it works on ROOTed O3D and I'll upload it soon.
To-do:
1) fading doesn't work
2) change of brightness doesn't work
What will never work
1) separate LEDs - I don't think there's a way to control each of them, only all 4 LEDs

ztracenyDen said:
Hi guys,
I've modified Martin Börjesson's app and now it works on ROOTed O3D and I'll upload it soon.
To-do:
1) fading doesn't work
2) change of brightness doesn't work
What will never work
1) separate LEDs - I don't think there's a way to control each of them, only all 4 LEDs
Click to expand...
Click to collapse
i am checking every 15 minutes for an update to this

Here it is!
I'm new to android, so I hope the "apk" file is enough for installation:
Fileserve: http://www.fileserve.com/file/qqFjsfS/Optimus3Dnotifications.apk
Mirror: http://home.zcu.cz/~chylek/Optimus3Dnotifications.apk
Source code:
http://www.fileserve.com/file/YvbqKbk/optimus3DnotificationsSRC.zip

Hi
I have a problem with downloading app
Cane you upload to other server
Megaupload or rapid
Thankyou
Sent from my LG-P920 using XDA App

Multitouch problem

Hi!
I recently bought an O3D and I'm getting some multi-touch problems.
As you can see, when you tap 3 times with another finger already tapping, multi-touch goes totally wrong. This happens after unlock/lock screen sometimes, and if you tap 3 times again the problem disappears.
Video from other user.
Kernel problem? Is there any solution? This makes playing multi-touch games (Nova for example) really anoying or zooming in browser with two fingers.

So sad to see the behavior of your touch screen, cause when I do the same test on my O3D it recognize 8 fingers without any problems. Are you rooted? Did you try for example my ROM to see if it makes any difference?
Sent from my amazing LG O3D using ThiaiZO3D V2.4

ThiaiZ said:
So sad to see the behavior of your touch screen, cause when I do the same test on my O3D it recognize 8 fingers without any problems. Are you rooted? Did you try for example my ROM to see if it makes any difference?
Sent from my amazing LG O3D using ThiaiZO3D V2.4
Click to expand...
Click to collapse
Mine recognizes up to 10, but when this happens only recognizes one at time. If you tap three times the problem is gone until you tap 3 times again.
I've tried with custom roms (one of them is yours), rooted, etc.

i confirm the problem...but the games looks not to be affected by it...they works perfectly.Only with touch test i have the problem...very strange and i have your rom thiaiZ...any other experice of it?

I have the same problem...
I'm on CM7 nightly 32 (for the P925 because of the Baseband problems)
but it is a bit strange.. sometimes it works and sometimes it doesnt, i don't know why

I have similar problem.
When I play a game the touch screen with 1 finger is okay but when I play with 2 fingers it stops to recognize the both fingers.
So I have to walk and then stop and then aim and then fire which sucks.

I have the same problem. Is this problem related with hardware?

hi everyone,
i tested this too and i noticed a certain pattern. If i turn off my phone and then turn it on and then run the multitouch tester i will get the issue you described. However if i turn it off and then turn it on and then move my finger from the left of the screen to the right of the screen 3 times(on the homescreen) and then I run the multitouch tester the issue is gone and the touch screen works perfect afterwards. Its a very weird bug. can someone confirm this on their phone also. If a programmer can develop an app that imitates 3 swipes when the phone unlocks then this annoyance is fixed.

Multitouch problem-any permament solution?
Have anyone found a permament solution?The thing is annoying.Has anyone got hardware fixing solution to this problem?Maybe the flat cable (placed at power button)?I've noticed it after 5 months of use.I haven't tried it myself with any other optimus 3d device.Could anyone confirm not having a problem?Btw, I use 2.35 official, without root or any kind of mod.Please, help.

rgunara said:
hi everyone,
(...)However if i turn it off and then turn it on and then move my finger from the left of the screen to the right of the screen 3 times(on the homescreen) and then I run the multitouch tester the issue is gone and the touch screen works perfect afterwards. (...)
Click to expand...
Click to collapse
Yeah, I've noticed this problem too and your three swipe solution seems to work fine. I also realised that I don't need to be on the home screen for this to work. I swiped on the tester screen itself and multitouch resumes working.
Testing with Antutu Tester I can get 10 simultaneous touches. The hard thing is to make 10 fingers fit into the screen
Sent from my LG-P920H using xda app-developers app

[Q] Known bug list with CM11 XT897/Photon Q 4G

Hello,
is there a list of known bugs for the photon q somewhere? I cant find anything related to CM11 for it.
Using the latest CM11 nightly's i am getting some bugs, most important (for me) are:
- Once the phone is booted you get the SIM code screen. I can enter the SIM pin there via touch fine. After that screen is passed
it gets to the phone lock screen. There you can not enter the code via the touch screen, only via physical keyboard.
- Camera button doesnt work (doesnt launch camera app). Inside the camera app the button works (takes pictures).
- Sometimes the data connection "hangs up". It displays 3G/Edge/HSPA+ connected but no data is passed. Only way to get it back to work is to
reset the data connection by turning mobile data off and then back on. I havent been able to find any special situation when this happens, its just random.

Which nightly are you on? Are you using the moto_msm8960 builds?
You are describing some GSM issues, which I cannot recreate but the CM maintainers should be able to.
As for the camera button issue, I think you can map it to anything - although mine seemingly does nothing as well (outside of the cam app itself).
Sent from my PHOTON Q using XDA Free mobile app

The camera button is working in the M5 build. You have to hold it for about a second for it to work, probably a protection against accidental presses.

Solust said:
The camera button is working in the M5 build. You have to hold it for about a second for it to work, probably a protection against accidental presses.
Click to expand...
Click to collapse
I'm on a nightly from June 5th. Holding the button vibes the phone, but nothing actually happens.

The camera button works as expected for me on CM11 M7 from the 9th

Right now i am on today's nightly (15.06.2014).
I've checked the changelog but couldnt see any important changes that could have resolved this issue...will test the next days tho.
Any idea how to map it correctly?
I am not going to use M-builds, they are simply too old and include security bugs (like the openSSL issue).
arrrghhh said:
Which nightly are you on? Are you using the moto_msm8960 builds?
You are describing some GSM issues, which I cannot recreate but the CM maintainers should be able to.
As for the camera button issue, I think you can map it to anything - although mine seemingly does nothing as well (outside of the cam app itself).
Sent from my PHOTON Q using XDA Free mobile app
Click to expand...
Click to collapse

The one bug for the msm8960 builds is the incall volume bug, it goes away after restart, but usually shows up after each phone call for me

Google Play Music not recognising touch properly in lock screen

I am not sure if this problem is exclusive to onePlus one but the google play music lock screen widget doesnt recognise my touch properly. I often have to tap 10 times for my touch to register. I enabled visual feedback for touches and can see that the OS is registering my touch. I dont understand why this is not reaching the widget.
I am adding a short screencast that shows the problem.

I assume you've updated to O5Q then? Mine was fine until I did it and now it never works. The touchscreen is perfect otherwise.

Fwosh said:
I assume you've updated to O5Q then? Mine was fine until I did it and now it never works. The touchscreen is perfect otherwise.
Click to expand...
Click to collapse
Yes I'm running version 11.0-XNPH05Q. Is this a known bug?

As far as I know but there seem to be some that don't have the problem. I certainly do.

a5hwinner said:
Yes I'm running version 11.0-XNPH05Q. Is this a known bug?
Click to expand...
Click to collapse
mate i have gone back to 44s using the toolkit.
i dont do much rooting etc but it was really easy.i can confirm that the lockscreen controls for me on google play music are working fine now.
lets hope i can get back some of that excellent battery life

Fwosh said:
mate i have gone back to 44s using the toolkit.
i dont do much rooting etc but it was really easy.i can confirm that the lockscreen controls for me on google play music are working fine now.
lets hope i can get back some of that excellent battery life
Click to expand...
Click to collapse
I wonder when the next CM update will be released.

Gravity sensor suddenly stopped working

Hi, it appears that recently the gravity sensor in my Nexus 5 stopped working.
At least it is what it seems by using sensor testing apps. And this makes it impossible for the phone to get its orientation (compass is not working).
Screen rotation is still working fine though.
Here is what happened exactly: not long ago I was using Google Maps, but the phone was a bit sluggish so I decided to reboot it.
After rebooting I opened Google Maps again and immediately noticed that the orientation indicator was missing (the blue "beam"), while it was present before the reboot. But I didn't care about it, and just thought that the compass needed re-calibration.
After a few days the orientation indicator was still missing, and the phone never asked me to re-calibrate, as it used to do before instead.
Then one day I launched Google Sky Map, and noticed that the view does not rotate automatically.
So I fired up a sensor test app I had installed (asd.vector.sensor), and no data is displayed for the Gravity sensor. Also orientation is not displayed and the info says that the gravity sensor is used to compute orientation, too.
Other sensors are ok, and as I already wrote screen rotation still works great.
Any clues about this issue? Did anyone ever experience this?
I'm afraid a system restore would not help...
I'm using Resurrection Remix ROM, Android 6.0.1.
Thanks.

If the problem exists on a stock ROM, it could be a hardware fault.

audit13 said:
If the problem exists on a stock ROM, it could be a hardware fault.
Click to expand...
Click to collapse
Ok yes, but I still do not know if it exists on a stock ROM.
Taking it the other way around... Do you think there is real possibility that it is a software fault?
I mean: did it ever occur to anyone? Is there really any hope that resetting my phone to stock will fix this?
I HATE having to reset my phone...
Thank you.

I stopped using custom roms a while ago because of minor problems that would suddenly appear.
I don't think there is a way to really tell if it is software or hardware unless you reset or use a stock ROM.

audit13 said:
I stopped using custom roms a while ago because of minor problems that would suddenly appear..
Click to expand...
Click to collapse
Well, that's a little hope at least.
I will need to find some time to re-stock my Nexus and try.
Thanks .

Ok, I restored the phone to stock and all sensors work again now!
Thanks audit13 for pushing me in that direction .

That's great that it was a software bug in the custom ROM.
Now you get to hunt for a custom ROM that works with a minimal or zero number of issues