Have a nexus 4 running paranoid android 3.6 June 24 release, sometimes when I go to the camera app, it's just a black screen as if lens don't open, this happens at completely random times, like for instance I'm using the camera, I go play a game, come back after like 10 minutes to use the camera again, then it doesn't work. after a minute of that black screen it just says gallery force closed and sometimes just reboots itself, but the reboot is rare. This is such an annoying bug and pisses me off so much cuz it happens so often, I'm pretty much at the point where I always reboot my phone before using the camera because I know it's going crash. It's there any way to fix this?? additional info I've had this phone since like February, running pa3 rom, faux 123 kernel v16tbu, and running that camera mod thing that increases the video bit rate to 20 mbps.
Thanks!!
clear the data for the gallery apk. also, remove the camera mod. does it still happen?
simms22 said:
clear the data for the gallery apk. also, remove the camera mod. does it still happen?
Click to expand...
Click to collapse
Yup I have done that many times. No effect whatsoever
NuckFuggets said:
Yup I have done that many times. No effect whatsoever
Click to expand...
Click to collapse
and you have tried without the custom kernel, and with a different rom?
simms22 said:
and you have tried without the custom kernel, and with a different rom?
Click to expand...
Click to collapse
I've tried using different kernels, same result. As for the rom, no I don't want to switch away from pa as I have grown accustomed to it and really like it, but ever since a few updates ago to pa this problem has happened. I never experienced this problem on stock rom or on aokp
NuckFuggets said:
I've tried using different kernels, same result. As for the rom, no I don't want to switch away from pa as I have grown accustomed to it and really like it, but ever since a few updates ago to pa this problem has happened. I never experienced this problem on stock rom or on aokp
Click to expand...
Click to collapse
sounds like its a PA thing then. if you want to be for sure, nandroid backup your PA and try a stock or aosp rom for a day or two, see if it pops up again. or you can wait until it happens, then run a dmesg, then send someone in PA the log to read/check. maybe they can fix the problem that way.
simms22 said:
sounds like its a PA thing then. if you want to be for sure, nandroid backup your PA and try a stock or aosp rom for a day or two, see if it pops up again. or you can wait until it happens, then run a dmesg, then send someone in PA the log to read/check. maybe they can fix the problem that way.
Click to expand...
Click to collapse
Yeah seems like it! :/ I think I'll go with the second option, it should be faster lol. How do I run a dmesg? What is that anyway?
NuckFuggets said:
Yeah seems like it! :/ I think I'll go with the second option, it should be faster lol. How do I run a dmesg? What is that anyway?
Click to expand...
Click to collapse
open a terminal emulator(i use android terminal emulator, free, play store), type in su then press enter, then type dmesg and press enter. dmesg provide kernel messages/activities, itll show errors as they happen too.
simms22 said:
open a terminal emulator(i use androi d terminal emulator, free, play store), type in su then press enter, then type dmesg and press enter. dmesg provide kernel messages/activities, itll show errors as they happen too.
Click to expand...
Click to collapse
Oh that's cool. So I do that after the camera fails? Then how do I show that to a pa person"
NuckFuggets said:
Oh that's cool. So I do that after the camera fails? Then how do I show that to a pa person"
Click to expand...
Click to collapse
yes, after it fails. copy/paste then email or.. android terminal emulator has a send to option if you press the menu button.
simms22 said:
yes, after it fails. copy/paste then email or.. android terminal emulator has a send to option if you press the menu button.
Click to expand...
Click to collapse
Oh ok cool, I'll do that next time it fails then. Also this is a little off topic, but what about random reboots? Sometimes for example I'm texting, or using the keyboard in general (99% of the time it happens when I use the Swype keyboard or when I'm texting), then all of a sudden it goes straight to the boot animation and reboots. Why? And do I do a dmesg for that too?
NuckFuggets said:
Oh ok cool, I'll do that next time it fails then. Also this is a little off topic, but what about random reboots? Sometimes for example I'm texting, or using the keyboard in general (99% of the time it happens when I use the Swype keyboard or when I'm texting), then all of a sudden it goes straight to the boot animation and reboots. Why? And do I do a dmesg for that too?
Click to expand...
Click to collapse
no, for a random reboot you want to run a last_kmsg afyer booting back up. itll show why you randomly rebooted. last_kmsg is produced when the phone reboots on its own.
simms22 said:
no, for a random reboot you want to run a last_kmsg afyer booting back up. itll show why you randomly rebooted. last_kmsg is produced when the phone reboots on its own.
Click to expand...
Click to collapse
So then how do I show someone that? And where can I find the kmsg :/
in the terminal emulator app..
su(press enter)
cat /proc/last_kmsg > /sdcard/last_kmsg.txt(press enter)
then the file will appear in your storage(main fs).
or grab it from /proc/last_kmsg/
Related
My wifes hero is stock (non-rooted) and she has been losing the audio. It has happened 2-3 times and she has to turn off and turn on the phone to fix.
You might want to root and flash a custom rom then avalaunch's fix
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Hang on -- before you root and flash and try to fix -- having a stock phone with that issue (if it is the same issue) is a big deal. A HUGE deal. A stock phone does not have the .29 kernel, which is where the problem was believed to be.
If this is the same issue showing up on a non-rooted phone, it needs to be known and confirmed. Can you describe a little more please, chfields, about how the phone behaves when the audio fails? Does the phone also become very sluggish before you shut it down and reboot?
askwhy said:
Hang on -- before you root and flash and try to fix -- having a stock phone with that issue (if it is the same issue) is a big deal. A HUGE deal. A stock phone does not have the .29 kernel, which is where the problem was believed to be.
If this is the same issue showing up on a non-rooted phone, it needs to be known and confirmed. Can you describe a little more please, chfields, about how the phone behaves when the audio fails? Does the phone also become very sluggish before you shut it down and reboot?
Click to expand...
Click to collapse
Unfortunately, I don't have any more details at this moment as I'm at work. I will post with details when I get home and get more info from the wife.......Thanks!!
BTW wife is not at all in terested in rooting, but this shouldn't happen on stock phone....Mine is rooted and currently running fresh 2.0d although my normal daily is DC 2.07.2 without issue....
i quit if i did all the work and it happens on stock lol im suing sprint.
Avalaunchmods said:
i quit if i did all the work and it happens on stock lol im suing sprint.
Click to expand...
Click to collapse
My heart goes out to ya man.........I was surprised as well.....
stock audio loss
I would return it to Sprint. My first hero lost all incoming audio. I had it replaced. It was odd because I could call out , send texts etc.
tbuilt said:
I would return it to Sprint. My first hero lost all incoming audio. I had it replaced. It was odd because I could call out , send texts etc.
Click to expand...
Click to collapse
dont return it until you (chfields) can give us details on date bought, in depth software. mainly the pri and prl. those are the only things that could have changed from stock to our roms.
Avalaunchmods said:
dont return it until you (chfields) can give us details on date bought, in depth software. mainly the pri and prl. those are the only things that could have changed from stock to our roms.
Click to expand...
Click to collapse
Ok, We bought these phones 2/7/10. The current PRL is 60663 PRI 1.70.003. This problem started a couple days ago, she will be watching tv/radio whatever, stopping watching and come back later and no audio. Reboots to get audio back.
chfields said:
Ok, We bought these phones 2/7/10. The current PRL is 60663 PRI 1.70.003. This problem started a couple days ago, she will be watching tv/radio whatever, stopping watching and come back later and no audio. Reboots to get audio back.
Click to expand...
Click to collapse
logcat it. even stock phones should have the logcat file in the lib to run debug. do it when you can.
Avalaunchmods said:
logcat it. even stock phones should have the logcat file in the lib to run debug. do it when you can.
Click to expand...
Click to collapse
How do I do that??
chfields said:
How do I do that??
Click to expand...
Click to collapse
do you have adb folder? C:\android-sdk\tools
Avalaunchmods said:
do you have adb folder? C:\android-sdk\tools
Click to expand...
Click to collapse
Yes, what do I do with it?
chfields said:
Yes, but I don't think it will work on stock as its not rooted....
Click to expand...
Click to collapse
yes it should. adb logcat reads from a file in the lib. it shouldnt require root or anything.
adb logcat with the phone plugged in.
Avalaunchmods said:
yes it should. adb logcat reads from a file in the lib. it shouldnt require root or anything.
adb logcat with the phone plugged in.
Click to expand...
Click to collapse
Ok, I plugged in her phone and click on adb, the cmd window came up and a bunch of stuff scrolled and then it shut down......now what?? Sorry.....
chfields said:
Ok, I plugged in her phone and click on adb, the cmd window came up and a bunch of stuff scrolled and then it shut down......now what?? Sorry.....
Click to expand...
Click to collapse
ok when the problems happens. try to make it happen btw. plug the phone in and logcat it. after you logcat it just unplug the phone. then on the cmd prompt
right click the top bar and click properties. then check the insert mode box. the right click the top LEFT PART where you started logcat and click mark. click where its blinking and hold it and scroll all the way right and the bottom. press enter. then ctrl v to copy
Avalaunchmods said:
ok when the problems happens. try to make it happen btw. plug the phone in and logcat it. after you logcat it just unplug the phone. then on the cmd prompt
right click the top bar and click properties. then check the insert mode box. the right click the top LEFT PART where you started logcat and click mark. click where its blinking and hold it and scroll all the way right and the bottom. press enter. then ctrl v to copy
Click to expand...
Click to collapse
I will try, but the cmd box only stays open for a second or so and closes. I tried opening a cmd box and clicking adb but it opens a different one and closes within a second or so....what am I doing wrong?
chfields said:
I will try, but the cmd box only stays open for a second or so and closes. I tried opening a cmd box and clicking adb but it opens a different one and closes within a second or so....what am I doing wrong?
Click to expand...
Click to collapse
First go to a command prompt -- Start>Run>CMD, or in Vista/7 just type cmd into the search box at the bottom of the Start menu. After CMD makes its own window, navigate to folder with adb in it, for example:
cd \android-sdk-windows\tools
Click to expand...
Click to collapse
Then at the C:\android-sdk-windows\tools> prompt, type:
adb logcat
Click to expand...
Click to collapse
(then press enter)
askwhy said:
First go to a command prompt -- Start>Run>CMD, or in Vista/7 just type cmd into the search box at the bottom of the Start menu. After CMD makes its own window, navigate to folder with adb in it, for example:
Then at the C:\android-sdk-windows\tools> prompt, type:
(then press enter)
Click to expand...
Click to collapse
Duh!!!! I swear to god I left my brain somewhere and can't find it......I've been brainfarting all day today...I feel like an idiot...I know better....must've been all that weed I smoked when I was younger......
chfields said:
I will try, but the cmd box only stays open for a second or so and closes. I tried opening a cmd box and clicking adb but it opens a different one and closes within a second or so....what am I doing wrong?
Click to expand...
Click to collapse
it may be the phone. i never tried logcat on stock i was assuming it should work. maybe run as admin.
Hello,
I flashed the 7.0.0-RC1-Glacier last night with no problems. This rom is freakin amazing and I plan on making a donation after writing this.
I noticed some things that might be wrong with the CM7 but am not sure if its cause of me or the rom. I will explain.
*********
The "g" button located at the bottom right side does not work. Meaning, when it was stock and I pressed that button, it would load that app that says you can speak your commands, like text bill or etc.
When it was stock on the keyboard I could choose "speak the message" or use SWYPE...but in CM7 I dont see that option on the keyboard.
Also, when I first flashed the CM7, I went to camera just to check it out...and when I took a picture, the shutter didnt make a sound, which was GREAT! But then the next day I went back to camera and now everytime I take a shot, the shutter makes that noise.
So far thats all I can find for now.
Thanks in advance,
Brian K
fst2011 said:
Hello,
I flashed the 7.0.0-RC1-Glacier last night with no problems. This rom is freakin amazing and I plan on making a donation after writing this.
I noticed some things that might be wrong with the CM7 but am not sure if its cause of me or the rom. I will explain.
*********
1) The "g" button located at the bottom right side does not work. Meaning, when it was stock and I pressed that button, it would load that app that says you can speak your commands, like text bill or etc.
2) When it was stock on the keyboard I could choose "speak the message" or use SWYPE...but in CM7 I dont see that option on the keyboard.
3) Also, when I first flashed the CM7, I went to camera just to check it out...and when I took a picture, the shutter didnt make a sound, which was GREAT! But then the next day I went back to camera and now everytime I take a shot, the shutter makes that noise.
So far thats all I can find for now.
Thanks in advance,
Brian K
Click to expand...
Click to collapse
1) On CM7 the "g" key is used for a search key, if you long press it you should be able to use the native "google speech" application.
2) CM7 only comes loaded with the AOSP keyboard. Swype is closed source and not open for anyone to use on their builds. The MySense Rom that are customized like I/G are modified variants of the current ROM. They didn't build a fresh ROM they just edited T-Mo's.
3) Most phones will have shuttle sound to prevent people from taking pictures that aren't warranted, or taking "certain" pictures that people are unaware of. you can delete the .ogg file for the sound to perm-remove that sound if you should so choose to do so. i believe it's in the /system/media/audio/ui file.
Swype may be available to you, through swype.com's Beta program, if it is still active:
http://beta.swype.com
jggimi...I tried that download and it didnt work. However, I found another app that does the same thing as Swype...this one is called "SlideIT Keyboard" its a app u have to pay or find a beta....but it does work I have it running on CM7
Hope this helps
Brian
Guys, I loaded CM7 yesterday and for some reason my app market is gone. cant install it, dont know how. any ideas? links for install?
shalomhr said:
Guys, I loaded CM7 yesterday and for some reason my app market is gone. cant install it, dont know how. any ideas? links for install?
Click to expand...
Click to collapse
Did you flash the Gapps (Google Apps) with it too?
I wiped the phone so im guessing everything went with it
shalomhr said:
I wiped the phone so im guessing everything went with it
Click to expand...
Click to collapse
download the gapps and then flash it and see what happens.
pinoyz said:
download the gapps and then flash it and see what happens.
Click to expand...
Click to collapse
This guy hit the nail on the head. CM7 is a AOSP project ROM.
I bet your Maps, Email, Google Talk, Market, and some other little ones are missing.
Download the G/apps from Cyanogen and flash them, after a wipe and you should be good to go.
I believe my post was just hijacked....get out and start your own thread....Lol
Anyways...Aside from the swype issue...any ideas on how I can get back the "genius" feature. Please it would be very helpful.
Thanks
Brian K
Please only post on this thread if you are reporting a bug or a bug fix. Thanks!
Please be sure to mention which version you installed AND your install procedure. Be as specific as possible.
Thanks for the wiki _Alex_!!!
Update bug reports & fixes yourself at the "That ROM" Bug Report / Fix wiki!
____________________________________
Checking your tegrapart:
http://forum.xda-developers.com/showpost.php?p=32641715&postcount=132
Don't change web top resolution. Leave it at 720 at 60hz.Otherwise the phone starts glitching bad when you leave web top.
Sometimes there is a green bar on bottom of screen in camera.
Sometimes the phone takes a couple seconds to wake up.
The default CPU governor is pretty jumpy. On demand works better.
That's all I've noticed so far.
Sent from my MB860 using xda app-developers app
Just confirming with others that Ramfix.zip works for non-US models.
I flashed with ICS and Ram fix CWM, install vendor.img with fast boot and now it works very stable i did not get any FC or random reboot
For rooting, simply install SuperSu, if it doesnt work:
1. Download unlock root http://www.mediafire.com/?p2wgclhox6lq218
2. Root using it, very simply, just install, plug phone and run
3. Download SuperSu and any root explorer
4. Delete superuser.apk from /system/app
5. Install superuser from market
6. Uninstall superuser from market
This will get you rooted with SuperSu (better for ICS)
changeofseasons said:
Don't change web top resolution. Leave it at 720 at 60hz.Otherwise the phone starts glitching bad when you leave web top.
Sometimes there is a green bar on bottom of screen in camera.
Sometimes the phone takes a couple seconds to wake up.
The default CPU governor is pretty jumpy. On demand works better.
That's all I've noticed so far.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
ics with webtop???? did you say webtop???
htchd2fix said:
ics with webtop???? did you say webtop???
Click to expand...
Click to collapse
Webtop 3.0 = tablet mode
ticiano_arraes said:
Webtop 3.0 = tablet mode
Click to expand...
Click to collapse
Is this thread for the whole "rebirth atrix" project? Or what exactly is this for?
EDIT just saw other threads. Sorry for the post. Must say though. I CANT WAIT!!!
So is HWA working on this? Can someone confirm that?
And can someone make a thread in general section explaning the rigth steps to flash this and have a stable rom?
Cocolopes said:
So is HWA working on this? Can someone confirm that?
And can someone make a thread in general section explaning the rigth steps to flash this and have a stable rom?
Click to expand...
Click to collapse
HWA, fingerprint and cam corder. See the other threads, let's keep this one for bugs
This thread is for bug reports and fixes ONLY.
jeffreygtab said:
Is this thread for the whole "rebirth atrix" project? Or what exactly is this for?
Click to expand...
Click to collapse
This is for finding issues with the leaked ICS (see other threads in the dev forum).
Cocolopes said:
So is HWA working on this? Can someone confirm that?
And can someone make a thread in general section explaning the rigth steps to flash this and have a stable rom?
Click to expand...
Click to collapse
HWA does appear to be working as per the videos in the install thread showing video camera now working as well as fingerprint reader. I think this thread is a WIP for getting a stable rom installation. The installer thread intro gives you the bare bones.
Bug Report:
While I was updating my apps on Play with Mobile Data, I got a Random Reboot.
Caner092 said:
Bug Report:
While I was updating my apps on Play with Mobile Data, I got a Random Reboot.
Click to expand...
Click to collapse
Thank you for reminding me. My phone locked up and rebooted while downloading a picture in a text. It worked after the reboot though.
changeofseasons said:
Thank you for reminding me. My phone locked up and rebooted while downloading a picture in a text. It worked after the reboot though.
Click to expand...
Click to collapse
i second that, i configure the apn, when i want to use the mobile data the phone reboots, works fine without data, wifi only.
Radio seems Funky
Random reboots and screen scrambling, phone gets hot. Also, screeching noise from bluetooth hands free device at times.
wifi prolem
wifi not working on mi atrix4g at&t
some solution
Phone seems stable until I place it onto the webtop. Once I open up the webtop lid, the picture is of the Android UI, out of phase, but not the webtop interface. Pull the phone out, and the UI is no longer smooth, visible tearing artifacts. After a few minutes, it reboots on its own, and either works or gets stuck in a boot loop (requiring a battery pull).
Google Now for ICS FC's, so don't try.
EDIT: It works, needs a reboot though.
Confirming tearing artifacts (same as corneliusm) on turning screen on by pressing power button while phone is connected to computer (USB cable). Was worried that my phone is dying....
For me to open action memo, I have to open my app folder and go directly to app. Does anyone know how to fix this issue? I'm running cleanrom 1.7 JB 4.3.
Armyrj127 said:
For me to open action memo, I have to open my app folder and go directly to app. Does anyone know how to fix this issue? I'm running cleanrom 1.7 JB 4.3.
Click to expand...
Click to collapse
Check in settings under S Pen. There is an option to choose what happens when you remove the pen. If this doesn't fix the issue try wiping cache/davlik.
kinstre11 said:
Check in settings under S Pen. There is an option to choose what happens when you remove the pen. If this doesn't fix the issue try wiping cache/davlik.
Click to expand...
Click to collapse
Thanks, I tried it and it didn't work. Any other ideas?
Armyrj127 said:
Thanks, I tried it and it didn't work. Any other ideas?
Click to expand...
Click to collapse
Its a longshot but check to see if Air Command is turned off. I don't know if the two processes are integrated but given the amount of integration Samsung has done to its apps (i.e. Samsung keyboard requiring My Magazines) I wouldn't be surprised.
Other than reflashing the rom I don't think there is another way. It seems like a lot to reflash for something seemingly minor.
(Sorry for the late reply).
kinstre11 said:
Its a longshot but check to see if Air Command is turned off. I don't know if the two processes are integrated but given the amount of integration Samsung has done to its apps (i.e. Samsung keyboard requiring My Magazines) I wouldn't be surprised.
Other than reflashing the rom I don't think there is another way. It seems like a lot to reflash for something seemingly minor.
(Sorry for the late reply).
Click to expand...
Click to collapse
Thanks, I really appreciate it. My air command is off and I was planning on reflash ing but I just downloaded NC2 KitKat and waiting til I have some free time and will flash that. Hopefully that fixes my issue.
kinstre11 said:
Its a longshot but check to see if Air Command is turned off. I don't know if the two processes are integrated but given the amount of integration Samsung has done to its apps (i.e. Samsung keyboard requiring My Magazines) I wouldn't be surprised.
Other than reflashing the rom I don't think there is another way. It seems like a lot to reflash for something seemingly minor.
(Sorry for the late reply).
Click to expand...
Click to collapse
Before I reflashed, I tried switching air command on and it worked. Thanks a lot!
Armyrj127 said:
Before I reflashed, I tried switching air command on and it worked. Thanks a lot!
Click to expand...
Click to collapse
Glad we could figure it out.
Hello guys, ever since I got my phone. Everytime the phone trying to do update an app or installing one it froze for a new minutes until the apps is installed. It was like that on stock and it is like that on every custom roms I've tried. I don't know if I'm the only one or not. Please help and thank you.
TheUndertaker21 said:
Hello guys, ever since I got my phone. Everytime the phone trying to do update an app or installing one it froze for a new minutes until the apps is installed. It was like that on stock and it is like that on every custom roms I've tried. I don't know if I'm the only one or not. Please help and thank you.
Click to expand...
Click to collapse
Does it completely freeze up?
Heisenberg said:
Does it completely freeze up?
Click to expand...
Click to collapse
No, just for a few mns until the application is done updating/ installing or un installing Then the screen either hang or locked itself. Like the system did a soft reboot.
TheUndertaker21 said:
No, just for a few mns until the application is done updating/ installing or un installing Then the screen either hang or locked itself. Like the system did a soft reboot.
Click to expand...
Click to collapse
It's normal for a device to slow down or lag a little when installing apps sometimes, the screen locking definitely isn't normal though.
Even my does the same
Like it i update am app or install from play store and use a diff app say I'm on whatsapp then when the app is installing it will be freezed no touch works nothing but screen remains as it is
Cheers ?
Prattham said:
Even my does the same
Like it i update am app or install from play store and use a diff app say I'm on whatsapp then when the app is installing it will be freezed no touch works nothing but screen remains as it is
Cheers ?
Click to expand...
Click to collapse
Even when installing app? That's odd. My note 5 doesn't freeze when installing apps or updating them
It's an issue with aosp package installer. You won't see it on other devices as the oems re-write that code.
It's mostly noticeable on anything FB puts out. As they are known for having the worst coded apps on the market.
zelendel said:
It's an issue with aosp package installer. You won't see it on other devices as the oems re-write that code.
It's mostly noticeable on anything FB puts out. As they are known for having the worst coded apps on the market.
Click to expand...
Click to collapse
Any fix would be nice. I thought my phone was bad
TheUndertaker21 said:
Any fix would be nice. I thought my phone was bad
Click to expand...
Click to collapse
So far I don't think there is a fix. Can't say about official Google. As I have not run a stock rom since I got my first device. If they have fixed it they have not pushed the fix to aosp which is happening more and more with google
zelendel said:
So far I don't think there is a fix. Can't say about official Google. As I have not run a stock rom since I got my first device. If they have fixed it they have not pushed the fix to aosp which is happening more and more with google
Click to expand...
Click to collapse
I'm rooted and running custom rom. It's the same thing.
TheUndertaker21 said:
I'm rooted and running custom rom. It's the same thing.
Click to expand...
Click to collapse
Well as the custom roms sync their source with aosp, then Google has not pushed a fix if there is one. This is happening more and more. Google fixes something but doesn't push it to aosp so it stays broken in 3rd party roms until the devs find a fix
Has this been solved? It's happening to me.
facing same issue. Also my YouTube pause video whenever some app gets updated in background.
Noticed this along with horrible battery life due to system ui restarts or something in all latest may version of Roms. I went back to b29I or whatever "I" version stock rom. No problems since. Goodluck