Related
Hello,
Today is my 14th day with the device and this device seems to be hot rebooting itself. Its not a complete reboot but a hot reboot that take 1/3rd the time to start up. Attached is the Alogcat. Anyone have any ideas? Should I swap the device out?
There is no reason for a reboot. I am not running any applications at time of reboot. And it happens randomly.
I didn't see anything in the logcat showing what the problem was. It looked like alogcat didn't pull everything, or maybe something got lost when it hot booted. Could you try to get a logcat via adb if it happens again?
Code:
adb logcat > logcat.txt
Run the above and wait a little bit (10-15 sec) and then press ctrl+c to stop as it will just keep outputting the log to the file.
now i notice that only 3 apps are showing in my downloads in the market and i have around 20 downloaded applications. what can cause this?
do you use any app2sd+ technique (script, application, ...) ?
this happened to me in one ROM it was app2sd+, specially when i install/uninstall any app
or if i mount the sdcard as drive.
i do not all apps are installed on the phone internal memory.
after installing a new app all my apps showed back up in the market.
Its your setcpu. No profiles
Sent from my SCH-I510 using XDA Premium App
papi92 said:
Its your setcpu. No profiles
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
i dont have setcpu installed on this device. have not done that yet
Hi everyone! My first post!
After almost 2 years with my Nexus S, I finally got around to trying a custom rom after it started being ridiculously laggy.
All went well with the update, except now my "Easy Battery Saver" app keeps crashing. (every time I leave my phone a bit and turn it on I get an error message saying the application has crashed.)
When I read the error message, it seems like the reason is "Permission denial: broadcast from android asks to run as user - 1 but is calling from user 0", whatever that means.
I've tried stopping the app, clearing the cache and data, but to no avail. Any ideas on what I can do to stop the Easy Battery Saver app from crashing and making it unusable?
(FYI the ROM I've updated to is Slim Bean build 5 4.2.2 in case that matters.)
Just guessing but fix permissions in recovery or the clockwork mod app. That should help.
Sent from my Nexus S using xda premium
Hello
I found many bugs in my Moto G Android Kitkat , and I wonder if this is a problem of Android or if my phone is having trouble manufacturing , I updated 2 days ago and have had problems in the transitions of the keyboard or spinning when they are not serious but I doubt that .
30 minutes ago if I had a serious problem with the interface, all the icons have gone blank and it was impossible to use , I had to restart my phone so that it can return to normal , I have taken a screenshot because that has alarmed me much happened when downloading an app from the store play enclose your image so they can appreciate.
All bugs I've found so far were generally graphics, transitions keyboard when was returning to the home , etc. .
Errors in operation for now none .
We do not probe reinstalling and I have not unlocked your bootloader , nothing, only actualize the Android , just took 4 days with the phone!
This is the new Kitkat bugs ?
Anyone have a problem like this?
Please can anyone help me with a tips ?
the only bugs i encountered is the same with u,but the icon is there but the description or title is blank like yours.
Sent from my XT1034 using XDA Premium 4 mobile app
Got 2 moto g. None of them ever had that neither on kk nor on jb.
Faulty unit or software installation. Try to factory reset, if that doesn't help I would send it back if you do not want to try it for yourself (unlocking, flashing old firmware, flashing new firmware etc...)
creambyemute said:
Got 2 moto g. None of them ever had that neither on kk nor on jb.
Faulty unit or software installation. Try to factory reset, if that doesn't help I would send it back if you do not want to try it for yourself (unlocking, flashing old firmware, flashing new firmware etc...)
Click to expand...
Click to collapse
i just flashed my phone 2 times and so far never encounter any problem anymore. thanks
Sent from my XT1034 using XDA Premium 4 mobile app
racchi said:
Hello
I found many bugs in my Moto G Android Kitkat , and I wonder if this is a problem of Android or if my phone is having trouble manufacturing , I updated 2 days ago and have had problems in the transitions of the keyboard or spinning when they are not serious but I doubt that .
30 minutes ago if I had a serious problem with the interface, all the icons have gone blank and it was impossible to use , I had to restart my phone so that it can return to normal , I have taken a screenshot because that has alarmed me much happened when downloading an app from the store play enclose your image so they can appreciate.
All bugs I've found so far were generally graphics, transitions keyboard when was returning to the home , etc. .
Errors in operation for now none .
We do not probe reinstalling and I have not unlocked your bootloader , nothing, only actualize the Android , just took 4 days with the phone!
This is the new Kitkat bugs ?
Anyone have a problem like this?
Please can anyone help me with a tips ?
Click to expand...
Click to collapse
I never had this blank icon screen issue so far and have the phone for 6 weeks now. I`am using Nova Launcher Prime with various icon packs.
Glad it's fixed and I hope the problem doesn't return. Otherwise return the device
same with me,too.
don't know why.
This may tie into your post, ive had the phone for maybe 3 weeks. I have weird transition stutter happening. I dont think i noticed it before kitkat. But I took the kitkat update, and then after that the phone does it whenever. Inside apps or home screen, txt messaging whatever. Once it finishes the stutter the phone is fine. Since ive been seeing this more and more, I went ahead and reset the phone and started over, thinking it may be from an app or so. But even right after a reset it will still do it. Also what ive noticed after the kitkat update was a volume problem. I usually would just put the phone on speaker phone right after i dial someone and the speaker volume was real low. Even though you press volume up and the volume is already set to max. It still sounds low. What i would have to do is click the volume button down Once, then back up to high to have the volume go actually high. This happens on speaker or not. If this all makes sense, any help? I see you say you reflashed the phone again, was that reflashed to kitkat? if so how would i do that if I already took the kitkat update. Any help, Thanks.
---------- Post added at 12:18 AM ---------- Previous post was at 12:10 AM ----------
Sorry also back on your post with the pictures of the black icons, i have had that also happen before and after the reset.
Lost all the saved game data after upadte
racchi said:
Hello
I found many bugs in my Moto G Android Kitkat , and I wonder if this is a problem of Android or if my phone is having trouble manufacturing , I updated 2 days ago and have had problems in the transitions of the keyboard or spinning when they are not serious but I doubt that .
30 minutes ago if I had a serious problem with the interface, all the icons have gone blank and it was impossible to use , I had to restart my phone so that it can return to normal , I have taken a screenshot because that has alarmed me much happened when downloading an app from the store play enclose your image so they can appreciate.
All bugs I've found so far were generally graphics, transitions keyboard when was returning to the home , etc. .
Errors in operation for now none .
We do not probe reinstalling and I have not unlocked your bootloader , nothing, only actualize the Android , just took 4 days with the phone!
This is the new Kitkat bugs ?
Anyone have a problem like this?
Please can anyone help me with a tips ? [/QUOTE
The only issue after upadting to kitkat is I lost all the saved data on temple run 2. I was on ninth level and had to start from scratch. This is my first android phone and first upgrade ( obviously ) but I suppose this doesn't happen or shouldn't happen with everyone.
Click to expand...
Click to collapse
racchi said:
Hello
I found many bugs in my Moto G Android Kitkat....
Click to expand...
Click to collapse
Do you post your found bugs also on Motorola forum?
I am just asking, because complaining here at XDA would not solve these.
mokkami said:
Do you post your found bugs also on Motorola forum?
I am just asking, because complaining here at XDA would not solve these.
Click to expand...
Click to collapse
I think this is the according thread in the Motorola Forum
Wait you are the same Nicole as in the Motorola Forum?
So Motorola is also reading here ^^ ? :good:
Not really wondering....but somehow yes.
Feels so to be observed by Motorola........and they are reading how ppl are abusing their device
Hehe people can do whatever they want with their device, I'm not judging
Motorola decided to up their social media presence to gather feedback about bugs and issues this way and I occasionally ask to do troubleshooting steps and to provide logs on unmodified devices. It really helps - little bugs got fixed which otherwise might not have been noted and sometimes design changes are implemented as well.
I'll try my best to keep up with XDA but it's quite lively. If you think you found a bug feel free to send me a message to draw my attention to the according thread.
Cheers,
Nicole
So Nicole, i would like to use this opportunity for a request.
It is not about a bug but a, i think basic, feature.
I am verry happy with this device.
But i was truly disappointed when i realized that i had to download a third party app to share a contact via SMS.
That is the way Motorola is going though. If the stock ROM doesn't provide it you need an app for it. Motorola will change clearly annoying or broken stuff, but not too much else - updates are faster this way and that is what most people are looking for nowadays.
The LED light not flashing after a missed call is a good example: It's not flashing by design because the stock ROM does not provide this since ca 2008 or so I have been told
But it annoyed enough users so Motorola decided to change it.
Hope that helps.
Cheers,
Nicole
Anybody had any networking errors/drops
I Recently bought a XT1033 and it was working very fine with the Jelly Bean 4.3 OS .. but after upgrading to KitKat (4.4.2) I face network problems frequently. Network automatically drops... returns after a reboot/ toggling airplane mode. The symbol it shows on the top is a RED TRIANGLE WITH A CROSS ( + ) IN IT... Did anyone of you face any problems..like what I'm facing... Please suggest a solution/workaround if possible
Regards,
Jayesh
bugs i found after 2 week usage
1. serious one: the no sound when making call or attending one. have to restart the phone. happens 2 or 3 times a day
2. one mentioned in thread: icons vanishes aftr some usage
3. sudden battery drop while connecting to pc- phone shut downs
4. the dialer wont display on first click, have to click 'back' and then again click to see dialer
rahublathur said:
1. serious one: the no sound when making call or attending one. have to restart the phone. happens 2 or 3 times a day
2. one mentioned in thread: icons vanishes aftr some usage
3. sudden battery drop while connecting to pc- phone shut downs
4. the dialer wont display on first click, have to click 'back' and then again click to see dialer
Click to expand...
Click to collapse
I never had first your 3 bugs... Try a clean restore.
For the fourth one, I had this when I had the animations set to 0 in developer options.
After setting them to 0.5x the problem was gone.
Sent from my GT-P3110 using xda app-developers app
Hi,Racchi, i m also facing same problem..........
Hey guys, lately I've been having the eventx-xxxx wakelocks that *seem* to keep my phone awake and drain my battery. These wakelocks are usually event0 ones and followed by a four digit number which I believe to be the Process ID.
The current wake lock I am having is event0-2012 shown by BBS. It changes on every so the PIDs are rarely the same. It also happens that the 4 digit number happens to be the process ID of system_server. So there's something that's keeping it awake.
Lastly, the event0 is the synaptics touchscreen. So I'm guessing that this event0 wakelock keeps track of all the touches you make on the screen. This problem only appeared after the new touchscreen firmware updates so that may be the cause. Anyone have any thoughts on this matter?
Screenshots for proof below
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Alright guys I'm back to share what I have found after doing some research.
Right now I'm using ark kernel with liquid smooth 3.2 milestone
So back to these wakelocks, as it turns out, even though event0 was the most prevalent, most of the time it was on was while the screen was on, so basically you can ignore it.
However, there were two other events that I still had to investigate, event2 and event3. For me event2 is gpio_keys which are the button inputs. event3 is s2w_pwrkey.
First I deleted the event2 file under /dev/input. These files are restored on boot but I would still make a backup before trying this. After deleting this, my volume buttons stopped working, as expected. But my power button still worked. I used it for a couple hours but there was something that was keeping my phone awake still.
Then I rebooted and deleted event3. This is related to the sweep2wake that's implemented in alucard's kernel. I never use it anyway so I went ahead and deleted it. And what do you know, now my phone is sleeping like a baby and even the other events have gone down as well. But the problem is you have to delete the file on every boot. The solution? An init.d script with the following line. Where X is the number of the event you want to remove. You can also just add it to any existing scripts you might have in /system/etc/init.d
rm /dev/input/eventX
How to find out what's causing yours?
1.Download wake lock detector from the
play store and use it for a day
2.check under kernel wakelocks to see if
your phone is being kept awake by an
alarmingly high number of event
wakelocks, if so proceed.
3. Open terminal emulator and type the
following: "su" press enter after each
line
"ps | grep xxxx" where xxxx
is the number
following the event
wakelocks.
4. If system_server doesn't show up,
another app is causing it. Find it and
manage it. Otherwise, proceed.
5. Go back in terminal and type "su" enter
"getevent -c 1" this will give you all
of you events and and what they
are bound to.
6. Make a backup in recovery.
7. Delete one of the problem events and
see if your phone is kept awake, if it.
isn't then congrats! You found the
drain! Else keep testing.
8. Once your are certain which one it is.
Create an init.d or use an existing
one and add the line "rm /dev/input/
eventX" replace X with the event
you want to remove.
You're done.
If you have any problems or questions, I'll be happy to help.
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Thanks alot for this thread, very helpful. :good:
i don't have wakelocks (using @ak kernel and enabled only dt2w) but very useful thread
5 star rated :good:
ak said:
Thanks alot for this thread, very helpful. :good:
Click to expand...
Click to collapse
Cool that means alot coming from you
wizyy said:
i don't have wakelocks (using @ak kernel and enabled only dt2w) but very useful thread
5 star rated :good:
Click to expand...
Click to collapse
Thanks! I've never had a 5 star thread before
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
I am on cm11s and have these same wake locks but all are less than 10 on so far a days worth of battery time. I don't think it's much of a problem for me and probably more for cm12? Anyways thanks for the info now I know where to look if it ever becomes an issue
Cheers
i've been getting these crazy same wakelocks the last week as well, which is weird because i didn't get them the two weeks before that when i got my phone. And I've been flashing ROMs (Mahdi, SlimKat, Lollipop) and kernels (stock and AK) back and forth. Even after settling on Mahdi with a clean flash, they're still showing up. THanks for your investigation, I'm going to check things out when I get home tonight.
tracerit said:
i've been getting these crazy same wakelocks the last week as well, which is weird because i didn't get them the two weeks before that when i got my phone. And I've been flashing ROMs (Mahdi, SlimKat, Lollipop) and kernels (stock and AK) back and forth. Even after settling on Mahdi with a clean flash, they're still showing up. THanks for your investigation, I'm going to check things out when I get home tonight.
Click to expand...
Click to collapse
Agreed, it only started happening recently and I haven't installed any new apps, but newer Roms and kernels. So I really don't know whats causing it
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
tracerit said:
i've been getting these crazy same wakelocks the last week as well, which is weird because i didn't get them the two weeks before that when i got my phone. And I've been flashing ROMs (Mahdi, SlimKat, Lollipop) and kernels (stock and AK) back and forth. Even after settling on Mahdi with a clean flash, they're still showing up. THanks for your investigation, I'm going to check things out when I get home tonight.
Click to expand...
Click to collapse
Update: I flashed AK v30 kernel and the wakelocks seem to be gone now! Prior to this I was on Mahdi with stock kernel which had the wakelocks, and prior to that I was on Mahdi with AK v11 kernel which also had the wakelocks. This is only after an hour of "testing" though, so hopefully no apps I'm going to use will trigger them back :/
Edit: jk, wakelocks returned after a while. Screenshot attached. I rebooted the phone then left it alone for almost two hours.
Getting event0 1585 wakelocks, quite alot , more than 30k wakelocks in 3 hours.
It seems to be related to the synaptics driver, which to my knowledge is the touchscreen so i better not turn that off
Running AK 030 with Paranoid Saber Droid 4.4.4
mumaster20 said:
Getting event0 1585 wakelocks, quite alot , more than 30k wakelocks in 3 hours.
It seems to be related to the synaptics driver, which to my knowledge is the touchscreen so i better not turn that off
Running AK 030 with Paranoid Saber Droid 4.4.4
Click to expand...
Click to collapse
No just ignore that one. Most of the the 30k happens when the screen is on l
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
abhi08638 said:
No just ignore that one. Most of the the 30k happens when the screen is on l
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Click to expand...
Click to collapse
I am getting another quite massive wakelock, ipc0000007b_sensors.qcom, this one hits 143k wakelocks in 6 hours.
Tried searching for it on google but didnt really find any answerd or solutions. Do you know maybe what this wakelock is?
Most likely its a sensor, as seen in the name.
mumaster20 said:
I am getting another quite massive wakelock, ipc0000007b_sensors.qcom, this one hits 143k wakelocks in 6 hours.
Tried searching for it on google but didnt really find any answerd or solutions. Do you know maybe what this wakelock is?
Most likely its a sensor, as seen in the name.
Click to expand...
Click to collapse
I'll look into it
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Nice investigating and bug hunting OP.
mumaster20 said:
I am getting another quite massive wakelock, ipc0000007b_sensors.qcom, this one hits 143k wakelocks in 6 hours.
Tried searching for it on google but didnt really find any answerd or solutions. Do you know maybe what this wakelock is?
Most likely its a sensor, as seen in the name.
Click to expand...
Click to collapse
Alright, unfortunately I couldn't find any information about it. Are you running any auto brightness apps? Autorotation? Accelerator gaming? Magnetic case?
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Flashed the most recent boeffla kernel this morning (had ak 030 yesterday) and this whole day I haven't had any disruptive event wakelocks. Instead of minutes of those wakelocks, they're just St seconds now. Didn't change anything else.
tracerit said:
Flashed the most recent boeffla kernel this morning (had ak 030 yesterday) and this whole day I haven't had any disruptive event wakelocks. Instead of minutes of those wakelocks, they're just St seconds now. Didn't change anything else.
Click to expand...
Click to collapse
That's curious. It might be because of new commits that might have been reverted in the kernels. Right now I'm using Ark kernel
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
abhi08638 said:
Alright guys I'm back to share what I have found after doing some research.
Right now I'm using ark kernel with liquid smooth 3.2 milestone
So back to these wakelocks, as it turns out, even though event0 was the most prevalent, most of the time it was on was while the screen was on, so basically you can ignore it.
However, there were two other events that I still had to investigate, event2 and event3. For me event2 is gpio_keys which are the button inputs. event3 is s2w_pwrkey.
First I deleted the event2 file under /dev/input. These files are restored on boot but I would still make a backup before trying this. After deleting this, my volume buttons stopped working, as expected. But my power button still worked. I used it for a couple hours but there was something that was keeping my phone awake still.
Then I rebooted and deleted event3. This is related to the sweep2wake that's implemented in alucard's kernel. I never use it anyway so I went ahead and deleted it. And what do you know, now my phone is sleeping like a baby and even the other events have gone down as well. But the problem is you have to delete the file on every boot. The solution? An init.d script with the following line. Where X is the number of the event you want to remove. You can also just add it to any existing scripts you might have in /system/etc/init.d
rm /dev/input/eventX
How to find out what's causing yours?
1.Download wake lock detector from the
play store and use it for a day
2.check under kernel wakelocks to see if
your phone is being kept awake by an
alarmingly high number of event
wakelocks, if so proceed.
3. Open terminal emulator and type the
following: "su" press enter after each
line
"ps | grep xxxx" where xxxx
is the number
following the event
wakelocks.
4. If system_server doesn't show up,
another app is causing it. Find it and
manage it. Otherwise, proceed.
5. Go back in terminal and type "su" enter
"getevent -c 1" this will give you all
of you events and and what they
are bound to.
6. Make a backup in recovery.
7. Delete one of the problem events and
see if your phone is kept awake, if it.
isn't then congrats! You found the
drain! Else keep testing.
8. Once your are certain which one it is.
Create an init.d or use an existing
one and add the line "rm /dev/input/
eventX" replace X with the event
you want to remove.
You're done.
If you have any problems or questions, I'll be happy to help.
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Click to expand...
Click to collapse
Really a different way to deal with the problem than any other threads I have gone through. I am facing the same issue. Phone being awake when connected to WIFI only. The problem does not persist with Data connection and WIFI Off. Its very strange. I was working around for the solution but different things seemed liked working at different times.
Though I was having Event wakelocks and not wlan wakelocks I followed some solutions from this thread http://forum.xda-developers.com/galaxy-s2/help/puzzle-wlanrxwake-wakelock-sgsii-t2133176
Disabling netbios worked for me and again after an update the problem came back. Next time I tried changing frequency to 2.4Ghz and it worked. Now again after dalvik cache wipe the problem came back. No solution left to try.
I shall try the methodology u hav provided. Finger crossed. Really frustrated with this issue. Unable to keep the phone connected to WIFI.
But what can be the real issue. How can the volume keys or sweepwake issues persist only on WIFI and not on data connection. Should I ask for am exchange from OPO?
abhi08638 said:
Alright, unfortunately I couldn't find any information about it. Are you running any auto brightness apps? Autorotation? Accelerator gaming? Magnetic case?
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Click to expand...
Click to collapse
Non of that, next to the standard autorotation and auto brightness of android itself. I did see that all the screen off gestures were turned on in synapse so I turned that off but it didn't seem to help. Its not that big of a deal though, probably some necessary stuff happening in the background. Still getting rock solid battery life! 6+ hours sot over 2 days so you don't hear me complain thanks anyways for sharing your info!
Sent from my One using XDA Free mobile app
kandalamv said:
Really a different way to deal with the problem than any other threads I have gone through. I am facing the same issue. Phone being awake when connected to WIFI only. The problem does not persist with Data connection and WIFI Off. Its very strange. I was working around for the solution but different things seemed liked working at different times.
Though I was having Event wakelocks and not wlan wakelocks I followed some solutions from this thread http://forum.xda-developers.com/galaxy-s2/help/puzzle-wlanrxwake-wakelock-sgsii-t2133176
Disabling netbios worked for me and again after an update the problem came back. Next time I tried changing frequency to 2.4Ghz and it worked. Now again after dalvik cache wipe the problem came back. No solution left to try.
I shall try the methodology u hav provided. Finger crossed. Really frustrated with this issue. Unable to keep the phone connected to WIFI.
But what can be the real issue. How can the volume keys or sweepwake issues persist only on WIFI and not on data connection. Should I ask for am exchange from OPO?
Click to expand...
Click to collapse
Yeah I have noticed this wifi issue as well. Iight be related to the new drivers that were implemented but I haven't been keeping up with that so I don't know if it was reverted or not. I usually keep the wifi sleep policy to never. As I said before, I don't really know why they show up, but this "solution" is very dirty. The best way would be to find the cause of it.
I removes the s2w event because whatever triggered it actually uses power by keeping the capacitive keys on. So stopping that process ultimately saved me some battery.
Sent from my LG-P880 using XDA Free mobile app
Hello Everybody
My name is Ilario from Lodi Italia, i have a problem with my nexus 4 16gb
the problem is:
starts will read ANDROID and goes into optimizing applications 104
then finished the optimization app appears starting with the circle of renovation that will continue to rotate endlessly
I have restored the factory, I installed both original ROM that cyanogen mod but the problem remains the same
Have a suggestions?
Many Thanks a lot
Ilario Orlandi
Same Issue
I second this. I am having the same issue. A couple of days ago my phone died. After plugging it in and letting it charge a bit, I tried to power it on but it stayed on the boot screen (rotating light balls) for hours. I rebooted it and then it stated "android is starting...optimizing app x of y." It then stayed on this screen for hours. My phone has never been rooted or even unlocked. It is completely stock, but won't go past the boot screen. I tried clearing the cache, and then did a full factory reset through recovery menu. Still same thing. Downloaded Nexus Root Toolkit and flashed the stock, still same thing. Any advice would be greatly appreciated. Thanks.
i_orlandi said:
Hello Everybody
My name is Ilario from Lodi Italia, i have a problem with my nexus 4 16gb
the problem is:
starts will read ANDROID and goes into optimizing applications 104
then finished the optimization app appears starting with the circle of renovation that will continue to rotate endlessly
I have restored the factory, I installed both original ROM that cyanogen mod but the problem remains the same
Have a suggestions?
Many Thanks a lot
Ilario Orlandi
Click to expand...
Click to collapse
Did this happen after any specific update.
I think you guys should start the device and leave it all over night. Plug the device in charger and leave it onn whole night.
Next day will bring same happiness for you.
Sent from my LG-X160 using XDA Free mobile app