Database Develop

CM7 and lag immediately before an outgoing call

When i make a call (with 3G active and connected) the phone lag for 1 minute and then starts the call.
With 3G closed and WiFi active the call starts immediately.
Can anyone help me?
Milestone 1 with CM7
Compache off No Swap Partition

I have the same issue here. It's not 1 minute for me (about 20 seconds at max) but happens 70% of the time.
I'm almost always starting the call from Favorites tab on Contacts/Phone, through the little phone icon on the right, and I can see it's hanging again when I press and it won't activate/press the button. Then after the hang time it starts 2 calls - one in backgorund (which is actively using the phone and calling) and one at screen, which fires the "error" dialog "Call not Send. [OK]" since the line is busy by backgoound call. Oh well, annoying =\
I can do any tests if anyone is interested, but I'll probably change the ROM in a few days because it's kinda stressing already.
Phone ROM info:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

wirapuru said:
I have the same issue here. It's not 1 minute for me (about 20 seconds at max) but happens 70% of the time.
I'm almost always starting the call from Favorites tab on Contacts/Phone, through the little phone icon on the right, and I can see it's hanging again when I press and it won't activate/press the button. Then after the hang time it starts 2 calls - one in backgorund (which is actively using the phone and calling) and one at screen, which fires the "error" dialog "Call not Send. [OK]" since the line is busy by backgoound call. Oh well, annoying =\
I can do any tests if anyone is interested, but I'll probably change the ROM in a few days because it's kinda stressing already.
Phone ROM info:
Click to expand...
Click to collapse
With WiFi only i don't have any lag...

Even i do have same problem, most of the time, i will be enabled 2G connection, it simply takes huge time to display.

I think that the problem is related to the Facebook App.
Now without this app the phone works great.
Now I use m.facebook.com with opera.

Xperia Z1 issues

Guys I recently got my Xperia Z1. And constantly I am facing issues in my Z1. Here are the issues that i am facing along with the pictures.
1. In one week I have faced this issue twice. The issue is that suddenly all the signals disappear ( I am using BSNL sim ). And when I try to register it on network an error message comes that cannot register on network. Make sure your SIM card is inserted or selected network is available. So is this issue with the SIM card or the phone? The first time when I faced this issue I manually registered it on network and it worked. But second time when I tried to register my SIM manually nothing happened. So I had to restart the phone. And the issue seems to have disappeared.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. I faced this issue yesterday. When I tried opening the camera app (default app) this message popped up. I tried reopening it many times but no success. Only after restarting the mobile I was able to open the camera app successfully.
3. This issue also happened yesterday. I was playing a not so graphic intensive game. Played the game for around 10 min or so. Then I stopped playing it. I checked CPU-Z, about 5 minutes after stopping, for battery and other information and noticed it is showing battery health as overheat. I checked this coz my phone gets quite hot if I play game for sometime. Is it normal for a mobile to get overheated just by playing a simple game for 10 mins?
4. Today I noticed that there is a slight yellow hue present when screen brightness is minimum. I compared it with my Nexus 4, this too with minimum brightness, and the difference was quite evident that there is a yellow tinge. Maybe it is not evident in the pic I am attaching but it is quite noticeable in reality. So wanted to ask whether there is really an issue or not.
Hoping to get my doubts cleared as I never faced such issue in a week old mobile.
Thank you

Are you on a rooted phone using a custom rom?
Sent from my C6903 using xda app-developers app

No I am not rooted. I am on stock ROM.

pranjaldixit said:
No I am not rooted. I am on stock ROM.
Click to expand...
Click to collapse
I suggest you to reflash your phone with Sony Update Service, that will fully reinstall your Stock ROM, save anything u need because that will wipe all of your datas.

Note 3 on Android 4.3 won't enter deep sleep!

Odd bug I found on my note 3 is that the phone will sit at 300 Mhz with the screen off all day without entering deep sleep
It will only do this on WiFi though as soon as I turn it off Deep Sleep will function as it should.
I have the NB4 firmware and Bootloader, Android 4.3.
I am rooted and I have Xposed Firmware installed, anyone else have this issue?

Install wakelock detector.
https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector
It will tell you what's waking your device. But I'm going to guess you have location services on.

I have the exact same problem. It's a month now and I didn't change my wifi router or anything.
There are no apps directly causing this. I will inspect kernel wakelocks and report back. But I bet that some app is doind something that causes "android system" to wakelock the cpu. I have many apps so it will be very hard since none of them have any battery drain out of the normal usage.

Zibri said:
I have the exact same problem. It's a month now and I didn't change my wifi router or anything.
There are no apps directly causing this. I will inspect kernel wakelocks and report back. But I bet that some app is doind something that causes "android system" to wakelock the cpu. I have many apps so it will be very hard since none of them have any battery drain out of the normal usage.
Click to expand...
Click to collapse
Turn off "Always allow scanning" in wifi. (Menu/Advanced.) Scanning wakes the phone, and the normal scan interval is 5 minutes. (It'll still be scanning when you're in the page showing the available connections. You are in there to look for a connection, right? No one would ever be in there for any other reason. (No, Bill Gates didn't say that no one will ever need more than 640K of memory.) IOW, it's going to scan whether you need it to or not if you're on that page, but it stops as soon as you close the page. (Even though there's a Scan Now button. Come on, Google - next time, try thinking. Just a little.)

Hmm nope.. I think something else was corrupted somewhere.
I tried this:
Code:
adb shell pm clear com.android.providers.settings
adb reboot
After setting the main settings again, the phone is now much faster and as of now the problem didn't show up.
I'll keep you posted if it happens again. If not, this could help many many people.

Confirmed: the problem was totally solved.
I suggest anyone with the same problem to give this a try and do not restore the main settings from a backup.. but just set again the home and lockscreen or any of the main settings you need.
I think something gets messed up with intensive use or tests. This apparently cleans it.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

A friend of mine had his Note3 very slow and draining battery very quickly after the last OTA update. With my "method" his note3 is now back to normal.

I had the same problem, the phone was at 300 Mhz with the screen off all day without entering deep sleep mode.
All I did was changing the wallpaper to the default one !!!!
Ploblem solved.
Very strange ....
I tried it 3-4 times (switching wallpapers from default to another one downloaded from the internet) to make sure that this was the problem.
At all times the problem came back and disappearing.
Note3 n9005, stock android 4.3, No Root.
Thanks Zibri !!!
ps
How can I try this without root ?
Code:
adb shell pm clear com.android.providers.settings
adb reboot

Xt1056's signal got bad, always lower than -85 dBm

Hi, since yesterday, my Xt1056's signal got very bad, most of time was under -85dBm. three bars.
And I had another phone MB865, using same carrier, the signal was -75dBm.But they are in the same place.
I want to know it's the hardware problem or software problem? Is there any ways to examin the problem?
I used to had a signal problem with my photon MB855, and It's the antenna inside the phone.
English is not my native language; please excuse typing errors.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

myarms said:
Hi, since yesterday, my Xt1056's signal got very bad, most of time was under -85dBm. three bars.
And I had another phone MB865, using same carrier, the signal was -75dBm.But they are in the same place.
I want to know it's the hardware problem or software problem? Is there any ways to examin the problem?
I used to had a signal problem with my photon MB855, and It's the antenna inside the phone.
English is not my native language; please excuse typing errors.
Click to expand...
Click to collapse
Signal is not your issue here. Wakelocks are. Your device barely slept.
As far as signal goes, the lower number the better. And yours isn't bad. Those yellow and red areas on your signal bar in the chart aren't good... But if you are on wifi, it won't hurt you. It will on data though.
If you're rooted, you need to try gsam and Gsam root companion to see your app held awake time and times waking device to see why your device is being held awake.
If you're not rooted, wakelock detectors pc version can show app wakelocks on an unrooted device, through adb.
Your battery life will not get much better until you stop that held awake time.
You can see the battery life help thread in my signature too. Posts 1 to 4. If you want, post the recommended screen shots from post 4 in that thread for help. Or, wakelock detectors pc version if you can. ?

Active Edge stopped working randomly

Hello everyone, I'm having issues with active edge. You can squeeze for assistant or silent stuff. But it stopped working for me whenever the phone is locked. And it'll start working again when it's charging. It stops working again when it's off the charger...
Steps to reproduce:
1. Ensure your phone is not charging
2. Try squeezing for assistant, if it works then let your phone go to sleep and lock (5 sec default)
3. Unlock your phone and try squeezing again
4. If it stops working, put your phone into charging state (wireless or wired), and it should start working again until next sleep
Let me know if you have the same issue too? I'm on the Feb update btw.

Can't replicate it here. Still on the January update but about to install February.
Sent from my Pixel 4 XL using Tapatalk

Update:
I found out that "allow when screen is off" is causing the issue. Turning it off and active edge is working now (when screen is on). Perhaps Google can fix this soon

JellyPuddie said:
Update:
I found out that "allow when screen is off" is causing the issue. Turning it off and active edge is working now (when screen is on). Perhaps Google can fix this soon
Click to expand...
Click to collapse
Mine is on and still working. Just saying.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel 4 XL using Tapatalk

EeZeEpEe said:
Mine is on and still working. Just saying. View attachment 4942653
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
Thanks for replying. Hopefully a factory reset would fix the issue.

I just factory reset and the issue still persists. Just so anyone else having the same issue know this.

Mike does something similar. I sometimes unlock the phone and the active edge does not work. Then I push the power button to lock the device, then unlock and it works fine. Can't really figure out as it's random...it doesn't happen every single time.

mkouk said:
Mike does something similar. I sometimes unlock the phone and the active edge does not work. Then I push the power button to lock the device, then unlock and it works fine. Can't really figure out as it's random...it doesn't happen every single time.
Click to expand...
Click to collapse
Exactly the same issue! It works fine after I turned off "allow when the screen is off". I never used it with screen off, since the screen turns on whenever you lift the phone, or when it detects movement.

JellyPuddie said:
I just factory reset and the issue still persists. Just so anyone else having the same issue know this.
Click to expand...
Click to collapse
Hey guys just a last update: I managed to get it working by reflashing the factory image (not OTA)