I have updated my samsung galaxy ace 2 with the last update version from this thread.
http://forum.xda-developers.com/showthread.php?t=2555021
The previous version had some bugs... sometimes it was necessary to restart the phone. (rarely) Indeed the version was really nice, in 4.4.3 android.
Now, 4.4.4 and I'm having a problem, wich was already present in an other old version, it's about the button, the lights. There is an option to shut down the light of the two tactile button, after some seconds or simply to desactivate the light all the time.
So I still have that bug in the past. I always desactivate the light when it's possible. And there is the bug, I desactivate the light, but when I do that, sometimes for an unknow reason, the light stay ON all the time. (notifications, or ... I don't know)
And that old bug is came back now on this version. I wanted to post in the thread that I mention above here, but I can't reply.
So I don't know if someone know why this bug happens, if you have any solution, it would be great. I'm planning to go back on the previous version if there is no solution. When the light stay always ON and if I don't see that problem, I have problem with my battery consumption.
Thank you for reading, and sorry if my english isn't perfect, I'm french native and I'm still learning and improving my english.
Related
First of all I must give a big THANKS to Albinoman and all who supported him in producing this ROM.
Recently I found one BUG, I have no idea if it is known issue. I tried to search the same but couldn't find any answer.
What I did was pulling down notification bar and switched on Torch, after the time limit Torch goes OFF but in the notification bar it is shown as ON. So far so good. Now if I switched on Camera it gives Camera Error, Can't connect to Camera. This error comes even if the torch is ON.
Build Date
Thu May 9 17:58:04 PDT 2013.
On BADASS
I will try the May 17th version now and POST the error again. I
I just want you to know that this is what I got. Anyways the ROM is good except for the Battery issue. Someone said ROM has nothing to do with any Battery consumption, but I tried with a different ROM earlier and its Battery life was good.
Also tried upgrading to May 17th, I know change log says nothing about Camera, but still I tried first without upgrading to Camera Sphere 4.2 and than with Camera Sphere 4.2 same issue found.
BTW I am S-ON.
Thanks
Love and regards
Prasad
prasad_m said:
First of all I must give a big THANKS to Albinoman and all who supported him in producing this ROM.
Recently I found one BUG, I have no idea if it is known issue. I tried to search the same but couldn't find any answer.
What I did was pulling down notification bar and switched on Torch, after the time limit Torch goes OFF but in the notification bar it is shown as ON. So far so good. Now if I switched on Camera it gives Camera Error, Can't connect to Camera. This error comes even if the torch is ON.
Build Date
Thu May 9 17:58:04 PDT 2013.
On BADASS
I will try the May 17th version now and POST the error again. I
I just want you to know that this is what I got. Anyways the ROM is good except for the Battery issue. Someone said ROM has nothing to do with any Battery consumption, but I tried with a different ROM earlier and its Battery life was good.
Also tried upgrading to May 17th, I know change log says nothing about Camera, but still I tried first without upgrading to Camera Sphere 4.2 and than with Camera Sphere 4.2 same issue found.
BTW I am S-ON.
Thanks
Love and regards
Prasad
Click to expand...
Click to collapse
First off, just for future refference, there are 2 threads for Albino's rom already.
One is in the development section and one specifically for troubleshooting like this post is in teh Q and A Section. In the future please search for an existing thread rather than create a new one. This helps keep XDA a little more organized.
Now onto your problem...
I agree with everything you said. The torch and the camera don't work at the same time. The camera needs access to the LED to work, and obviously so does the torch. When the torch is already on the camera doesn't have access to it. It's like trying to put 2 keys into the same lock at once.
So since the camera app reads the device to see if the hardware it needs is available, when it finds the LED isn't available it shuts down. Even though the torch itself has timed out and has gone off, the torch app is still running and it controls the LED hardware until the app stops. so even though the light is off, the camera still can't control the LED hardware.
This is an overly simplified explanation, but this is what's going on.
We discussed in the dev thread that the camera app can run the led constantly during video so this isn't being done on purpose to prevent a reboot due to extreme battery drain. Its just a conflict for hardware resources. But since the camera can keep the led on there is no reason to have the torch app keep the led on, so there is no reason to really fix this bug.
Again though, the camera still fc's after the led times out because the torch app is still in control of the led hardware. So you have to remember to turn off the torch. That's also why the notification bar says the torch is on, even though the led is off. The torch app is still running in the background, which is what the notification bar is rally indicating.
Thanks I thought I should mention here if it is a Bug, BTW I was not aware how to start a thread within the Albino's ROM.
I can see only option Reply to someones thread. I found new thread here and hence the confusion.
Anyways thanks.
Love and regards
Prasad
Hi All, am a new member to this website. I've been reading all the threads related to my device (Xperia Ion Lt28h) and actually installed a custom ROM for the same for the first time. The ROM i chose was http://forum.xda-developers.com/showthread.php?t=2616450. It is actually cool to use. I have the kitkat feel in my phone but lately I've been experiencing some issues with the ROM. I tried to reply in the same thread but the usual 'New members with less than 10 posts' thing popped up. So i couldn't find any other way to ask someone regarding the issues that am facing. As am new to this , i may know how to contact someone or how to post it in a efficient way, if there are some, please let me know. If not, the below are the problems am facing and am seeking all the seniors help to solve it.
1) Sometimes, when am getting a call, phone rings, vibrates but the screen is still in standby mode and it takes around 5-10 seconds to see the caller info. This happens in 70% cases.
2) Camera doesn't work properly. In JB holding up and down the volume button zooms the camera but here it is taking picture. Also i searched if there is any option to zoom, i couldn't find it.
3) Some of the applications doesn't work. For Ex, Super beam is not working, as soon as i scan the QR code from other mobile to receive a file, my phone gets hang and gets restarted.
4) HDMI is not working, which was working in JB.
All these are the issues am facing. Please help me.
Hello everyone ... on my Nexus 5 once again happened some incredible problem with vibration ... Here's the thing: Last night my Nexus just lay on the bed and when I took it, at this point I found the lack of vibration. First, I turned on Vibrate when pressing the navigation keys, and found no vibration. At first I began to sin on the vibrating motor, but I remembered that I was already have this problem a few months ago, in the same way. When I downloaded from the Market program to test the vibration and turned her to work constantly, I found that the vibration motor that works but is very weak, as if barely barely turns .. As if he did not have enough energy. But! Motor is spinning so bad until not "turn off the screen." After blocking in a few seconds the vibration motor is working again as if nothing had happened! As well and clearly. However, once you unlock it as soon as the problem returns, vibration works very poorly. I have tried different programs for vibration control, no result. Found a video on YouTube of the problem, attach below. If the problem is simply to reiterate, I would like to know the cause .. This problem is very infuriated me yesterday, vibration at all almost no and I missed a few calls. I understand the engine is all right and I think that this is some sort of deep software problem...
I have already booked two motors, then try to replace, but not sure it will help .. Phone never fell or dropped, handle carefully. (but the body have a little small scratches ) A very long time looking for information on this issue on the internet, but found nothing ..
I dont want to go to the service center, I want to understand itself, with your help, of course ..
Factory reset or Reflashing ROM to any other doesn't help too...
Model - D281 16GB white.
ROM - CM11 Snapshot M9
Kernel - ElementalX 1.04cm
Recovery - TWRP 2.7.1.1
Can not listen to what people say on the video, the main thing to hear the vibration motor.
P.S. Sorry for my bad english, I'm from Russia and I write through Google translator... Hope on your help, guys..
Hello everybody,
I've got a problem with a Oneplus One.
First a brief history of the device. I got it on ebay with a shattered display about 1 1/2 years ago and replaced the display. Since then my girlfriend managed to shatter the display 3 times more. So I'm quite used to replace the display on this device.
Since the last display replacement (the 4th) the device developed a partial Screen-of-Death problematic.
Sometimes the display just stays blank, while the backlight is clearly working (you can see the blueish light in dark environments). Also the device reacts to touch and button inputs, like e.g. double-tap-power to start camera. Or double-tap-screen to wake up (you can feel the vibration or display input sounds).
I "just" have to wait about 10-20 seconds, try again and the display turns on without any problems. In other cases I have to try this a couple of times to wake the screen.
A hard reset is not necessary, the device will wake up sooner or later. In this aspect it differs from all SoD descriptions I found online!
An other strange thing is, after the screen replacement the device forgot all wifi networks. The wpa_supplicant.conf was empty. Strangely enough all other apps were OK, I didn't noticed any irregular acting applications.
As the device was sill running on CM13 I decided to give it a fresh nougat installation and assumed the SoD symptomatic would vanish.
Now after flashing back and forth different factory images and custom-rom's the SoD is still there and renders the device almost unusable.
I tried the latest CM13 snapshot and sultans CM13, which I have been using on another OPO without problems for a long time.
I also tried to install different original factory images.
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB.zip
and also another one I got long time ago from Oneplus to fix an annoying Wifi-Reboot-Problem. It contained additional image files like persist.img and reserve4.img.
I tried to turn on and off the setting for the proximity sensor that could interfere with the activation of the screen.
I tried different radio firmware's, as I could remember that there had been some problems in the past with incompatible firmwares, android versions and the proximity sensor.
I enabled and disabled all off-screen-gestures, although they are always working regardless if the display stays blank or not.
Unfortunately I've got no luck.
Literally every single android version I tried suffered from SoD. The only problem free thing is TWRP. Running the latest 3.1.1-0 I never got a blank/black screen on powering up the display.
So now I'm out of ideas and would be happy to hear any additional guesses to fix this problem.
I was also wondering if anybody knows more about the SoD. I couldn't find any information's regarding the causes of this problem. Is it hardware related or software?
thanks!
p.s. another strange thing I noticed now on the latest Slim7 rom (20170526). If I try to take a screenshot with power+vol-down, the screenshot animation happens. But a status bar notification from Android-System tells me, there is not enough free space to save the screenshot. But there is at least 40GB of free space.
I'm not sure if this is related to my problem or just to Slim7. And I'm also a little tired to reflash the device just to test this issue...
Maybe there is a problem with permissions or the flash memory?
p.p.s here a logcat. I couldn't find anything helpful.. https://pastebin.com/UWfwc1VX
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
pesche80 said:
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
pesche80 said:
Hello everybody,
I've got a problem with a Oneplus One.
First a brief history of the device. I got it on ebay with a shattered display about 1 1/2 years ago and replaced the display. Since then my girlfriend managed to shatter the display 3 times more. So I'm quite used to replace the display on this device.
Since the last display replacement (the 4th) the device developed a partial Screen-of-Death problematic.
Sometimes the display just stays blank, while the backlight is clearly working (you can see the blueish light in dark environments). Also the device reacts to touch and button inputs, like e.g. double-tap-power to start camera. Or double-tap-screen to wake up (you can feel the vibration or display input sounds).
I "just" have to wait about 10-20 seconds, try again and the display turns on without any problems. In other cases I have to try this a couple of times to wake the screen.
A hard reset is not necessary, the device will wake up sooner or later. In this aspect it differs from all SoD descriptions I found online!
An other strange thing is, after the screen replacement the device forgot all wifi networks. The wpa_supplicant.conf was empty. Strangely enough all other apps were OK, I didn't noticed any irregular acting applications.
As the device was sill running on CM13 I decided to give it a fresh nougat installation and assumed the SoD symptomatic would vanish.
Now after flashing back and forth different factory images and custom-rom's the SoD is still there and renders the device almost unusable.
I tried the latest CM13 snapshot and sultans CM13, which I have been using on another OPO without problems for a long time.
I also tried to install different original factory images.
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB.zip
and also another one I got long time ago from Oneplus to fix an annoying Wifi-Reboot-Problem. It contained additional image files like persist.img and reserve4.img.
I tried to turn on and off the setting for the proximity sensor that could interfere with the activation of the screen.
I tried different radio firmware's, as I could remember that there had been some problems in the past with incompatible firmwares, android versions and the proximity sensor.
I enabled and disabled all off-screen-gestures, although they are always working regardless if the display stays blank or not.
Unfortunately I've got no luck.
Literally every single android version I tried suffered from SoD. The only problem free thing is TWRP. Running the latest 3.1.1-0 I never got a blank/black screen on powering up the display.
So now I'm out of ideas and would be happy to hear any additional guesses to fix this problem.
I was also wondering if anybody knows more about the SoD. I couldn't find any information's regarding the causes of this problem. Is it hardware related or software?
thanks!
p.s. another strange thing I noticed now on the latest Slim7 rom (20170526). If I try to take a screenshot with power+vol-down, the screenshot animation happens. But a status bar notification from Android-System tells me, there is not enough free space to save the screenshot. But there is at least 40GB of free space.
I'm not sure if this is related to my problem or just to Slim7. And I'm also a little tired to reflash the device just to test this issue...
Maybe there is a problem with permissions or the flash memory?
p.p.s here a logcat. I couldn't find anything helpful.. https://pastebin.com/UWfwc1VX
Click to expand...
Click to collapse
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Click to expand...
Click to collapse
Thanks!
I'm going to consider a new display... but not a new gf
pesche80 said:
Thanks!
I'm going to consider a new display... but not a new gf
Click to expand...
Click to collapse
Don't forget to invite me to your wedding.
Hi all,
I just got the OOS 13 update this evening, and I have an EU version of the Nord 2T. Hopefully all regions should get the update now!
Might as well do a discussion thread to see how people get on with it. Hopefully it's all good, it's been fine for me so far!
First bug on C.24 EU version that I see:
Sometimes the HOME button doesn't work, need to go in multi-task view then home button is back working.
Double tap on multi-task button sometimes doesn't switch to previus app.
After 3 days of use I would say that the battery life has not changed.
As on OxygenOS 12, NO call recording option here in Italy, but with THIS solution is partially working.
Where are you live? In Poland I don't have any update
Edit:
I have used the Oxygen Updated and I have a13
At the moment everything looks fine...
Sometimes the fingerprint scanner does not appear on the AOD.
ivkom said:
Sometimes the fingerprint scanner does not appear on the AOD.
Click to expand...
Click to collapse
Yes bug confirmed
I just installed this update (euro) and think it just made the phone so even worse than (wasnt fan of previous either). The settings are just less accesible, there is an imbalance in font / icon size options, bothering me with even more added 'smart'features. Does anyone know how to downgrade / rollback?
[i came here because even the oneplus forum is a pile of crap ]
xonep said:
I just installed this update (euro) and think it just made the phone so even worse than (wasnt fan of previous either). The settings are just less accesible, there is an imbalance in font / icon size options, bothering me with even more added 'smart'features. Does anyone know how to downgrade / rollback?
[i came here because even the oneplus forum is a pile of crap ]
Click to expand...
Click to collapse
Maybe you should try do wipe?
For me everything works well, so I guess tahat it can resolve a lot of issues after update
I always do it after big update like this.
I appreciate the suggestion but I really want to do a rollback, because I really dont like the UI changes.
With second update C.26 bug always present:
Sometimes the HOME button doesn't work, need to go in multi-task view then home button is back working.
Double tap on multi-task button sometimes doesn't switch to previus app.