Develop Bugs

Strange problem

Dear friends,
I have problem with my Nexus. Sometimes it vibrates by itself, without any reason. I don't mind it but it is little bit annoying. What can it be? I am on JB + franco's kernel.
Thanks.

mcipovic said:
Dear friends,
I have problem with my Nexus. Sometimes it vibrates by itself, without any reason. I don't mind it but it is little bit annoying. What can it be? I am on JB + franco's kernel.
Thanks.
Click to expand...
Click to collapse
Check all software that issues notifications and make sure none is set to vibrate. Like Yahoo, Facebook, etc.

Also happening to me. I rebooted and it's ok for another few days then vibrate itself again... I don't care now XD

Checked all options and I am thinking that settings are good. I don't use any of social apps except Instagram and twicca. This is very strange and happens randomly.

Do you ever get asked to choose an app to open 'something' with? like email apps etc?
Also do you have a folder in your gallery with a load of screen shots?
This is usually cause by the automated bug report system.
you may have to wipe data and re-flash rom/kernel.

Yes, happens all the time. So this is rom fault? Should I just use rooted stock?
Sent from my Galaxy Nexus using Tapatalk 2

This was happening all the time to me, on stock ICS and when I went to JB.. I am running my own build of CM10 and the issue has subsided.
Personally I Think a bad flash is to blame.
just try reflashing.. like i say i had this problem consistently and flashed many different roms with no resolution.. but now its fine very odd..
Like i say do a wipe and full flash/reinstall.

I found solution to my problem. You have to disable bug mailer. Just rename /system/bin/bugmailer.sh to bugmailer.sh.bak and you are good to go.

(Thread Closed)

Thread Closed !!

New Google's Android 4.2.1 Features
-> Photo Sphere
-> Gesture Typing
-> Multi-User Support (Tablets Only)
-> Miracast Wireless Display Support
-> Daydream
-> Notification Power Controls
-> Google Now Improvements
For More Information on Which of the above features available in CyanogenMod, Come to My New Thread T989 Official CM10.1 4.2.1 Discussion (Coming Soon)
Enjoy !!! :good:

This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.

theandroidrooter88 said:
This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.
Click to expand...
Click to collapse
This is why i started this Thread, So we can discuss Bugs in the latest versions. :highfive:
I heard AOKP JB is stll having SODs and RRs. Do u find anything like these?

Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2

algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
First we have to fix our flashing methods and recoveries used. I for one haven't experienced one single RR or SoD since I started flashing official nightlies. People are probably causing these issues themselves to begin with. Expecting a fix for an issue that has no identifiable cause.. I wonder if any other phones outside the t989 forums are experiencing RR and SoDs with Jelly Bean..
Sent from my SAMSUNG-SGH-T989 using xda premium

algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates

algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.

garth719 said:
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates
Click to expand...
Click to collapse
Great to hear that your running latest 10-Oct Nightly. A Simple advice to you & all other users, is to restore app without data if your are using any backup tools such as TitaniumBackup etc., Restore Apps with data cause Problems.

srikanth.t989 said:
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.
Click to expand...
Click to collapse
Sorry, I don't mean to crap on the thread but unless you can confidently say that SODs and RRs have been fixed (changelogs, yourself writing the code, etc.), going by your own experience shouldn't be the end-all-be-all to say whether something is fixed or not. Just like with call echo, some devices are worse than others.

I see that supposedly the issue with audio and docking has been addressed. However, the docking option is still grayed out for me when docked. Just looking for audio pass-through while docked...

Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet

SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

eight_heads said:
Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet
Click to expand...
Click to collapse
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.

I'm on recent CM10 Oct10 nightly and the BLN lights stay on, even with the Oct 7 nightly.
Update: fixed my own problems. This post helped: go to menu - systems - advanced settings - sensor and uncheck and check enable keys notifications and then send yourself a text or email. It actually should work out the box mine always has. Make sure you have notifications checked off in the apps like sms and gmail.
Also check display - notification light to make sure it enabled and you can add the apps you want to have the light enabled to work
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app

on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.

garth719 said:
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.
EDIT:
Just ran the music player for 45min on a run. no skips, nothing.. ran a 90 mb mp3 file too which usually gives my ipod trouble.. good sign
Click to expand...
Click to collapse
So is that how we're saying we don't get random reboots anymore? We just call them something else??

algorhythm said:
So is that how we're saying we don't get random reboots anymore? We just call them something else??
Click to expand...
Click to collapse
well there was a difference in this reboot because my phone didnt actually fully shut off. the "cyanogenmod" boot animation came up and the phone was ready to go in about 20 seconds. there was no usual vibration indicating that the phone has shut off and no "samsung" boot image as a regular reboot would do. call it what you will

Quote:
[email protected]: on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.
Try updating it on the market
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Laazyboy said:
SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Run only One ROM. Do a clean reflash. We are not experiencing any SODs or RRs. Use only one ROM because Flashing different ROMs one after the Other will Make your device weak. The data left by the AOKP causes some errors to CM10. Thats why i said that don't restore the apps with data.

Proximity Sensor Mmuzzy JB 4.2

On this particular Rom, has anyone had any issues with proximity sensor not recognizing the phone to your ear, therefore pressing buttons with your face instead of shutting off? I don't use phone for calls often, but seems every call I've taken I've run across that issue. Thanks!

I am on the latest MMuzzy Toro plus 4.2 and haven't noticed anything like this so far. I don't do a lot of calling but when I take a call it seems to work normally.

I'm running the 11/21 build and have no issue. I have made a few calls and no problems.

OP may try a fresh flash

Thanks I'll try fresh flash see what happens. Just wanted to see if anyone else had similar issues.
Sent from my Galaxy Nexus using xda app-developers app

I've problems with the Proximity sensor too.
Ok.. I am noob. But here is what I've.
I got the new 4.2 takju image from google and followed a very good thread here about how to install it and it worked perfectly. The only thing that is not working is Proximity sensor during Skype calls and Google Talk calls. I really can't understand this but this is the problem I've.
I flashed it twice with takju and it didn't work and installed yajku too and still not working. I am noticing minimal amount of reports about this but over the internet. But no solutions yet.
Hope someone would help us

I have been on his ROM from the day 4.2 dropped and it has been great. Few problems (googles not mmuzy's)but they have been fixed berry quickly
Sent from my Galaxy Nexus using Tapatalk 2

Yes, please check out my thread: http://forum.xda-developers.com/showthread.php?t=2006783
Fresh install, factory resets, the works. Still have the problem. Proximity sensor turns the screen off but the dial pad or even the end call button are active and are pressed by my cheek. It pretty much kills 4.2 for me and I am just about to go back to 4.1.2.
EDIT: Just to clarify, I am running completely stock 4.2 tajku

Just an FYI, appears to be a PGM issue in relation to 4.2. Even checked the PGM app thread and author released an update for the paid version, with the free version being updated soon.

[Q] CM10 on Bell Galaxy S III (d2att)

I know CM10 has been made "stable" on this device but I just have a few questions regarding it. My wife has been using the nightlies since the first previews were available and I'm not sure if our issues are common or something I am doing wrong.
She is currently on a nightly from a few days ago but these issues have persisted for about a month. I have done a full wipe and flash multiple times and we still have the same issues.
Skype: She can't barely here the other user and the other user hears nothing but static. I have tested with multiple other users. I have wiped data for Skype and reinstalled it, still has the same issue.
Force Close - Many apps. Happens randomly and it's not the same apps every time. I feel it is an OS issue and not an app issue.
Speakerphone is randomly activated by default. She usually has to tap the mic button a few times (deactivate, reactivate, deactivate) in order to get it switched to the handset.
Depending on what nightly she flashes the caller on the other end gets echo. It hasn't been happening with recent flashes but every couple weeks it pops up again for a nightly and then disappears.
I understand there are many issues due to Samsung not releasing sources, etc, just want to verify I am not alone. I have looked through the forums and see some people have some of the issues from time to time but I am hoping for some verification.
Thanks for everything.

I noticed the same thing a few days ago on Skype but didn't think much of it at the time.
Just checked again and sure enough I'm having the same experience you are with static.
Flashed back to stock and the problem disappears.
Must be a problem with CM10.

Ever try flashing the Stable version? Or a different rom for that matter? Maybe AOKP?

The issue existed before Stable and it exists in Stable. I just tried [ROM] AOKP(Jellybean 4.1.2)Task & Ktoonsez (11/18) and the issue with Skype exists there as well. If anybody knows of a AOKP or CM build that doesn't have any issues I would swap over. I have been wiping and flashing roms like crazy lately and I we really can't stand stock samsung rom. I may end up selling the phone and picking up something different, it's quite frustrating. Last time I buy a Samsung phone, that's for sure. They basically **** on devs.

DarthDerron said:
Ever try flashing the Stable version? Or a different rom for that matter? Maybe AOKP?
Click to expand...
Click to collapse
I see you have the same phone as my wife. Any chance you have time to test Skype on your current rom? If so thanks in advance, I appreciate it.
Sent from my LG-E973 using xda app-developers app

Thanks guys. Just going to return her to stock and sell it. Going to find a device with better support from manufacturer.
Sent from my LG-E973 using xda premium

[Q] Problem in keyboard and dialing

Ok, straight to the point..
I have an issue in making a call exactly
When I am trying to call somebody, sometimes the dialing window won't appear.
Ok, it finnaly appear, but it takes a long time
Also, when typing, sometimes it wont type anything
I think there is an issue with the keyboard, but with different keyboard, the issue still exists
Clearing app data wont help, because those issue happen sometimes and it working again a couple minutes later
Those issues happen almost in all ROM i've installed.
I wonder what the problem is ?
Is there anyone having exactly the same issue with me ?
Any suggestion would be highly appreciated :beer:
Sent from my GT-S5660 using xda app-developers app

Hey!
I've been having the same problem on stock rom and the only way that seems to fix it is just rebooting your device. When I run cyanogenmod for example the problem doesn't occur anymore

Yea man, I have followed your suggestion and now I am on GingerDX ported by oldDroid, looking if the problems occur again
what is your daily ROM anyway ?

I mainly use maclaw's cyanogenmod for my gio
And does the problem still occur?

not for now..
is that CM 9 RC3 by maclaw ?
I used that rom a year ago, before i realised there is a problem with netd process taking high cpu usage when not connected to a wifi
I prefer to use gingerbread ROM

I've been using Jellybean 4.2.2 (CyanogenMod 10.1) from maclaw since it came out and I haven't had alot of problems with it!