[Q] build.prop tweak problems - Atrix 4G Q&A, Help & Troubleshooting

I changed the Wi-Fi checking interval from 45 to 90 and then rebooted my phone to find that I had no connection to Bell and my widgets all said "problem loading widget". Could simply changing the interval really cause that many problems?

The Widgets not showing sounds like a launcher issue. Changing the interval shouldn't have messed anything up. What are you running for a rom? Stock, cm7?
Sent from my MB860 using XDA App

I'm on Gobstopper 2.3.4 Build 4.5.2A. I did have the proximity sensor settings changed too, but I don't see how that would affect my connection to Bell either.

Try putting it back to 90 and see if it fixes it. Are you running a custom launcher or stock launcher
Check your apns as well, may have just been a fluke that you can't connect
Sent from my MB860 using XDA App

Well the default was 45 and I set it back to that and rebooted a couple times to make sure it was fixed and it seems to be Ok now. I'm using LauncherPro. Maybe the new settings conflicted with the LauncherPro settings which messed things up? And I only have one APN, "Bell-Internet", which seemed fine.

Hmm, I put the build.prop back to how it was and just rebooted again and my widgets aren't loading, but I can connect to Bell. Should I try uninstalling LauncherPro and reinstalling? I've been doing a lot of modding and I recently flashed faux123's OC kernel so maybe even wiping my cache would help my widgets load again?

I think you need the ram fix too, let me refresh my memory real quick.
Sent from my MB860 using XDA Premium App

Related

Half of screen not working

I have CM 6.1.3 v06 running on my phone. Occasionally I an unable to touch anything on the top half of my screen but the bottom half works fine. I never had this problem before I had a custom rom installed. When I had the previous CM version I had this problem. Wiping and reinstalling did not fix it. It only happens once in a while but I have to restart my phone so it goes away and that's kind of annoying.
Sent from my X10i using XDA App
Yep.I've the same issue.
I got it fixed by dragging down the notification bar and everything works normally later
Sent from my X10i using XDA App
i find that if you go to the dialler, dial anything eg. 0000 and cut the call off straight away. then voila top of screen works again bit quicker than reboot.
hope this helps
rojdag
What BaseBand are you guys using... I'm wondering if that has anything to do with it... I've had it happen in the past and now with TW V07... I'm on BB52

[Q] Lost Lockscreen(Cannot Unlock or use phone)

Soo heres my setup:
Rom: Das BAMF 2.0-5
Radio: MR2
So I was using my phone just fine and then decided to restart it after doing abunch of updates to apps etc.
Then all of a sudden once it boots back up there is no lockscreen what so ever, so I cannot unlock my phone in order to use it, I didn't have the pattern/pin/password lockscreen just the basic slide to unlock one.
I can see the notification bar at the top of the screen but I am unable to pull it down due to the phone basically being locked... I also cannot turn off/restart the phone because I cannot get it unlocked..
I tried a battery pull or two and everytime I boot it up the same thing happens..
can you get into recovery? if so it may be a good idea to go to a backup. I have never heard of that issue before:S
you need a car dock to unlock it and change the lockscreen,what happened is the default wallpaper lockscreen vanished, or reinstall the rom over the top again,i have asked many times can never get an answer as to why or how to fix it any other way.
Sent from my ADR6400L using XDA Premium App
I have the bamf rom on my SD card, but I also have the stupid radio update on there so I cannot get to the recovery until I get home otherwise I could fix it..
But thank you for your help, hopefully that will fix it. How does the car dock work? I had a moto droid previously and that car dock had a magnet in it that would some how put the phone into car dock mode. What does the thunderbolt's do?
basically the same thing,you out it in the dock and it starts the car dock app,when you remove it the phone is unlocked,then go to tje settings customize and change the lock screen,you will see only five and should be six
Sent from my ADR6400L using XDA Premium App
thanx for reminding me just deleted the radio file from the sd
Sent from my ADR6400L using XDA Premium App
Well I don't have a car dock, so I ended up flashing the bamf rom back over it and that did not help.. Just ended up doing a factory reset and re-flashing the rom again..
thank you for your help guys
satseaker said:
thanx for reminding me just deleted the radio file from the sd
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
exactly why u need to delete the PG50IMG.zip file as soon as possbile....
would still like one if the devs to take a look and see whats causing it,has happened to me on all the gb bamfs i have installed. really like the wallpaper lockscreen but its gone,hoped it would come back with the bamf prev 3 but no go
Sent from my ADR6400L using XDA Premium App
Hence the reason I love the feature of menu to unlock also
-Dubsky
I just had the lock screen issue. That sucked. I freaked for a bit, but I was able to save it in recovery. Now to get my phone back to the way I like it... x_x
Best thing is to change the lockscreen,it has happened to me on every th band so far most of the time right after a back up
sent from a screamin' bamfed out tbolt
how do you get menu to unlock
You can try reflashing in recovery,I used my car dock to unlock the phone then change to the weather lock screen
sent from a screamin' bamfed out tbolt
Having this issue too...hopefully someone can figure out what is causing it.
To get around it, I installed a new lockscreen from the android market website, did cache & dalvic wipe, then reboot. Not sure which of those actually fixed the issue, but I'll probably be re-flashing today anyway.
I have experienced the same bug on Liquid roms. I had to wipe/factory reset and reinstall everything.
Someone in the Liquid thread told me it was due to the underclock while idle being too low. Thoughts?
I tried the car dock to unlock and the phone did not unlock. The notification bar showed it was in car mode, but it did not unlock the phone. Any ideas besides reflashing?

Go Launcher kept my phone from sleeping

It took me a while to figure it out, but that was the problem. Anyone else have this issue? I'm s-off and rooted and that is it. Maybe I missed something in setup? Anyways it is gone now and I'm back to sense.
Ive had no issues with go launcher.
Are you sure that was it?
I'm almost certain. Narrowed it down by deleting apps. After I uninstalled it, my phone showed a time diff immediately.
I'm running Go Launcher and my phone sleeps without issue.
My phone stays awake too. Still trying to determine the culprit. I too have go installed
I had the same problem but with Go sms
Sent from my PG86100 using XDA Premium App

text notifications do not sound after switching from silent

Hey ladies and gentlemen,
I am using stock ics rooted and am having sound issue. When I switch to silent mode everything goes silent as intended but when I switch back all sounds work minus text notifications. I usually have to restart phone to get it working. Any ideas? Thanks
Out of curiosity are you using a system notification tone or one that you downloaded? Does the vibration still work?
Yes. I am using pixie dust. And other programs like gmail and group me do not sound. It makes no sense. Thinking about going back to cm9 anyways.
Try wiping cache and dalvik cache. Also try fixing permissions
Sent from my SGH-I777 using xda premium
I have the same problem. I find a soft reset fixes the issue. Oh I am on stock ATT ics 4.0.3
Glad I am not the only one. Even soft tests aren't working anymore. I will wipe cache now and give status update.
you realize there is a separate setting in the messaging app for notification sounds I hope. I'm assuming you've already tried changing this.
Sent from my SGH-I777 using Tapatalk 2
Yes I do realize that. It works randomly. As of now sounds are back after wiping cache but I have not switched to silent mode yet. Will update once I switch to that mode and back to normal.
are you using a seperate launcher? if so its probably that needs update. i had same issue on go launcher but when i switched back to stock launcher the issue went away. wow i said launcher alot.
I was using stock tw launcher but just now switched to ported sgs3 launcher. Wiping the cache worked for a couple hours but back to the same problem.
You may have to wipe and start over to clear it up :-( I hate to say that, but sometimes it's the easiest fix. Orr....is there maybe a market app that could do what you want ? I know it sucks reinstalling everything when you've got a bunch of apps. Or try just wiping/system and flash over top of your current set up?
Sent from my SGH-I777 using Tapatalk 2
I have the same problem, reboot solves the problem only temporarily. I spoke with AT&T support and they had no record if this. If you Google this problem, you will see it is not only happening with AT&T, but with T Mobile Galaxy S 2 phones that have updated to ICS. I will have a conversation with Samsung this coming week and will post results of my conversation here.

S Voice Network Error

I just noticed that my S voice no longer works. I'm on stock rooted ROM (LE8 Bell) with KT747 kernel....is it because I'm not using a stock kernel? I tried uninstalling S Voice and installing some of the other APKs i found kicking around and am still getting network error.
Help?
Thanks in advance
Don't think so it didn't worn in mine either I'm stock I opened a thread last Friday n others also reported as similar
I just noticed mine was doing the same today. I am on Telus with root and stock rom, stock kernel.
Tried it again later on and it worked. Weird.
Sent from my SGH-I747M using xda app-developers app
If happens again try this:
Clear S-voice app data then soft reset.
Settings> Application Manager> All> Svoice> clear data.
Then
Power off device> remove battery for at least 30 seconds> replace battery> power on> should be all fixed up.
Sent from my SAMSUNG-SGH-I747 using xda premium
My experience is the thing is just spotty and I attribute it to a few million users coming online with it at once giving it a test spin.

Categories

Resources