Database Info

G1 Problem... Not even Tmo Techs can solve

Ok so I called up Tmo because my G1 is acting messed up. I spoke to about 6 different people who had no idea what the problem was, and all offered to send a replacement...
Scenerio:
I had the phone charging and when I unplugged it, I hit the red "Hang Up" button (so I can wake it up). Usually by doing this, the phone would prompt me to hit Menu > My Unlock code.
However, when I hit it, it took me right to the UI, the "Desktop."
So that caught me off guard. I figured I may have changed some setting before, so I went to Settings>Security and Location and made sure my "Require Pattern" was checked. IT WAS!
I even tried to re-do the "shape" i made for the unlock.
From here, I wanted to go back to the main menu (desktop) so I hit the HOME key. NOTHING. Yeah, the home key does nothing. Nor does the Green "Answer" button.
What I've done:
1) Reset the phone numerous times
2) Uninstalled most recent applications + more.
3) Spoke to Tmo who had no idea.
Do YOU guys have any idea? Lool.
Thanks!

I'm living in beijing right now so when i had the same problem with my white us G1 i had to figure out a way myself. what i did was to factory reset my G1 and it went back to normal.

raygun said:
I'm living in beijing right now so when i had the same problem with my white us G1 i had to figure out a way myself. what i did was to factory reset my G1 and it went back to normal.
Click to expand...
Click to collapse
Raygun,
Thanks for the reply.
Just wondering though:
If I backup my apps with MyBackup, would I be able to restore them back on as if I never did a factory restore? In other words, if I restore with the MyBackup Backup, would I receive full functionality of the apps again?
Thanks again

I've had a very similar problem on a development image. If the phone thinks that it isn't activated, then it disables keylock, home, and the call button. The activation flag is stored in a database somewhere, but I forget where. Doing a factory reset and then activating again should fix it (if that's the problem).
The nandroid backup might actually replicate the problem, because the activation flag is stored in the /data partition along with all your apps..
This might not be the problem though!

akapoor said:
Raygun,
Thanks for the reply.
Just wondering though:
If I backup my apps with MyBackup, would I be able to restore them back on as if I never did a factory restore? In other words, if I restore with the MyBackup Backup, would I receive full functionality of the apps again?
Thanks again
Click to expand...
Click to collapse
Yep, minus the settings of each app, and the backing up of home shortcuts, if they are in folders...they won't be in the right place...but the placement of the folder and icons is correct, just not the ones inside of folders on the desktop.

aziwoqpd said:
I've had a very similar problem on a development image. If the phone thinks that it isn't activated, then it disables keylock, home, and the call button. The activation flag is stored in a database somewhere, but I forget where. Doing a factory reset and then activating again should fix it (if that's the problem).
The nandroid backup might actually replicate the problem, because the activation flag is stored in the /data partition along with all your apps..
This might not be the problem though!
Click to expand...
Click to collapse
pychobj2001 said:
Yep, minus the settings of each app, and the backing up of home shortcuts, if they are in folders...they won't be in the right place...but the placement of the folder and icons is correct, just not the ones inside of folders on the desktop.
Click to expand...
Click to collapse
Thank you guys both.
Factory restoring right now. If it comes to the problem aziwopqd said (replicating the issue when restoring) I guess I'm outta luck.
Let's hope for the best.
Side question: (i know its been posted numerous times) If I root my G1, could i re-flash it back to "normal" (as if i bought it... brand new(original OS ))
Thnx
Best wishes,

Had the same problem... I thought mine was water damage though. There was a chance it had gotten wet but wasn't sure. I didn't even think to ask about it here so I sent it in and got a warranty exchange. New one works great, and I rooted it and got jf rc33 1.42 on it without even touching a computer. I thought it was cool lol
Oh ya, and yes you can restore it to factory everything. Just flash the .nbh file. You can even upgrade from there to the ota rc33 if you wanted to...

kindanewbie said:
Had the same problem... I thought mine was water damage though. There was a chance it had gotten wet but wasn't sure. I didn't even think to ask about it here so I sent it in and got a warranty exchange. New one works great, and I rooted it and got jf rc33 1.42 on it without even touching a computer. I thought it was cool lol
Click to expand...
Click to collapse
I was about to get the exchange, but I tried a Factory Reset. It solved the issue.
Haha - nicely done. All without touching a computer? Impressive.

Yup. Going through a divorce and wife took the computer so I didn't have a choice. All you need is linda file manager, and an unzip app. You can do it all with the default browser and those apps. Now I have everything saved on my sd card in different sub folders so I can root any g1 and flash the jf modded rc 33 by just popping my sd card in and putting the files on the root of the card in order. Done it to 2 others already.

kindanewbie said:
Yup. Going through a divorce and wife took the computer so I didn't have a choice. All you need is linda file manager, and an unzip app. You can do it all with the default browser and those apps. Now I have everything saved on my sd card in different sub folders so I can root any g1 and flash the jf modded rc 33 by just popping my sd card in and putting the files on the root of the card in order. Done it to 2 others already.
Click to expand...
Click to collapse
Sorry @ divorce.
Very neatly done. What unzip app did you use? I've tried the 2 (i could find), and they didn't really work. Lol.

Thanks...
I tried usuing linda first (love the app) since it says in supports unzipping. But nowhere could I find anything about how. So I got UnZip. It confused me at first, kept saying blah blah interupted blah force close or wait. So I force closed bout three times. Decided to press wait.... sure enough, sure enough about 1 min latter it prompted me 'unzip complete'. During that time, however, the phone 'acted' frozen. Couldn't scroll or press home or anything. But it worked in the end.

By any chance did those of you that lost your lock screen download the app aviator watch? I had this happen to me and that was the only app that I had installed before losing the lock screen. Also, I lost the option of silencing the phone if you hold down the power button. Under phone options it just said power off, the silent mode option was not avail.

Dharkaron said:
By any chance did those of you that lost your lock screen download the app aviator watch? I had this happen to me and that was the only app that I had installed before losing the lock screen. Also, I lost the option of silencing the phone if you hold down the power button. Under phone options it just said power off, the silent mode option was not avail.
Click to expand...
Click to collapse
Now that you mention it, I too lost the ability to silence with the power button. But no, never downloaded aviator watch...

aziwoqpd said:
I've had a very similar problem on a development image. If the phone thinks that it isn't activated, then it disables keylock, home, and the call button. The activation flag is stored in a database somewhere, but I forget where. Doing a factory reset and then activating again should fix it (if that's the problem).
The nandroid backup might actually replicate the problem, because the activation flag is stored in the /data partition along with all your apps..
This might not be the problem though!
Click to expand...
Click to collapse
Sorry sir, but I think you are right! I had the same exact problem and after reading this post. I thought I would try resetting the google account before a factory reset.
Went to Settings->Applications->Manage applications->Google Apps and cleared the data. Afterwards, it asked me to sign in as if I factory reset the phone. After inputting the credentials, everything started to work. Thanks!
Hope this helps anybody else.

[Q] CM7 Home button opens clock app, calls go direct to speakerphone

It's apparently a semi common problem.
My Wildfire running CM7 will always open up the clock app when I press the home button. Freezing the clock stops this happening.
Similarly, when I answer or make a call, the speakerphone is automatically activated. From what I can tell, the phone thinks it's docked, and indeed, if I set the phone to make a sound when it's docked, you do hear the notification.
If I plug in the power cable and wiggle it around, I can get it to activate/ deactivate this, but I dont have this problem at all if I go back to the Sense backup I have. (Should note, I've cleaned out the power socket with all manner of stuff, to no avail (thought it might be lint etc))
Basically, is there any way I can stop the phone from thinking it's docked/ just remove the dock facility entirely?
I found a thread somewhere that said something about changing the name of a dock related apk somewhere, but I can't for the life of me find it again.
Thanks!

I would start with a fresh install if you haven't tried that already.
Hit that thank button if I helped!

Yup, should've mentioned I've done that numerous times with different versions of stable CM7. Did a full wipe and cleared the dalvik cache each time too.
The problem doesnt happen until the phone has fully loaded i.e. the home button works normally for the first 10 seconds or so of the phone being on. Then I hear the notification to say the phone has been docked, and the problems begin.

Have you thought of uninstalling the docking software, and then rebooting?
Hit that thank button if I helped!

Well that's what I'm asking - how exactly do I do that?

I would download this,
http://www.apkapplications.com/2011/07/root-uninstaller-pro-apk-v121-download.html
Then look for the docking .apk
Hit that thank button if I helped!

Well I used that to freeze the clock before and that worked to stop the home button going to the clock, but the speakerphone issue remained.
There was no docking apk as far as I could tell.

Okay, I've "solved" this, and I feel compelled to share how I did it, since EVERY thread on this on every forum is unresolved.
My problem was something in the USB jack - I thought I had cleaned it properly, but after some WD40 and jamming a paperclip in there, I no longer get the problem...at least for now.
I still find it bizarre that I never had this problem with the stock sense ROM (and didnt have it when I reverted back to my backup of it), but what can you do!?

flamph said:
Okay, I've "solved" this, and I feel compelled to share how I did it, since EVERY thread on this on every forum is unresolved.
My problem was something in the USB jack - I thought I had cleaned it properly, but after some WD40 and jamming a paperclip in there, I no longer get the problem...at least for now.
I still find it bizarre that I never had this problem with the stock sense ROM (and didnt have it when I reverted back to my backup of it), but what can you do!?
Click to expand...
Click to collapse
Glad you got it fixed!
Sent from my DROID3 using XDA App

same problem here, tried everything, reflashing, data wipe, cache wipe.
and same as OP sense based roms do not show this symptoms.
I have this problem with CM7 and almost on every rom based on it.
I searched in many places, but there aren't any positive solutions.
please help.
P.S.- cleaning the USB port also didn't work for me..

I found a way to disable dock mode. there is an app called NoDock which disables the dock mode at OS level.
It requires root permission to disable the dock. so your phone must be rooted.
unlike apps like DockNothing this actually does the job.
no more auto speakerphone modes, no more home button taking to clock app.
m.appszoom.com/android_applications/tools/nodock-free-trialneed-root_ogod.html

[Q] [BUG] - Not waking up from standby and not switching off!

Hi,
I got my Moto G on the weekend (Unlocked from Tesco Mobile for £2.04, thanks ebay)
However, on one occasion, the phone would not turn the screen off until I held the power button for 10 seconds to reboot it.
But more often (a few times every day), the phone will not wake up from standby until I do the same to reboot it. This morning this alarm clock to fail, so this could be an issue.
Does anyone else have the same issue and know of a fix?
Thanks!

Whichs apps do you have installed? Are you rooted? Did you already try a factory reset?
Sent from my LG-P760 using xda app-developers app

I am not rooted. I have tried a factory reset, and with only google account set up the issues still persist! Arghhh, i really like the phone and dont want to send it back

nig060983 said:
I am not rooted. I have tried a factory reset, and with only google account set up the issues still persist! Arghhh, i really like the phone and dont want to send it back
Click to expand...
Click to collapse
Do the issue exist if you don't add a Google account? Have you restored old settings through Google backup?

shaftenberg said:
Do the issue exist if you don't add a Google account? Have you restored old settings through Google backup?
Click to expand...
Click to collapse
I havent restored settings after a reboot, but i have noticed that I get reboots when I am editing google contacts on the phone....

Crappy sleep of death issue .... Seems moto g is having battery issues...

Mm not battery issues its just SW issues.
Simply fixed but will need an update.
Little tweeks like on a phone call when i move the phone away from my ear to open dialer to enter details on an automated service the screen won't come on until I press the power button twice. Once to lock and once to unlock. Then I can bring up dialler
Its due to all the little refinements in power management but it will get fixed.
I personally can live with the little niggles just now for the amazing 3.5-4 hours screen on time I'm getting.
Yest under heavy mobile data use it went a full 14 hours with the 3.5hours screen in time. It was great because I basically done all my Christmas shopping on my phone and checked store prices when out.
If its rebooting often enough I would do a fresh install and start again.
THE BIGGEST thing I found that made a difference in this phone and I think moto should highlight this is:
Do not import previous phone settings on initial start up. This somehow beings weird and wonderful phone settings over and seems to play Havoc with the overall performance of the device be it battery life or connectivity.
I ended up wiping the device in factory reset and on the section on initial set up about backup and restore I unchecked the second option of restore my device settings. Left everything else and since the phone has worked as it should.
My only issue is the power and volume keys location in my car holder means it can be powered off by the holder doh. So I'm looking for a new one which doesn't hug my buttons lol
Sent from my XT1032 using xda app-developers app

Thanks for your help guys, I was still getting random sleeps of death and random reboots so I took the device back to tesco.
They were quick to replace it and I will let you know if I am still getting these issues.

Don't import any old settings, do it manually or you could (if you have the software) do a migrate from My Backup Pro, which I used to migrate pics, contacts, call logs & sms from my old phone with zero issues. My phone hasn't rebooted or had any issues whatsoever. I suspect you just had a faulty unit. Mine is an unlocked tesco16gb too.

rare problem
techguyone said:
Don't import any old settings, do it manually or you could (if you have the software) do a migrate from My Backup Pro, which I used to migrate pics, contacts, call logs & sms from my old phone with zero issues. My phone hasn't rebooted or had any issues whatsoever. I suspect you just had a faulty unit. Mine is an unlocked tesco16gb too.
Click to expand...
Click to collapse
I,
Sorry for broken english
Has the dame problème , i called Motorola and they Say to return it to your cellshop to get new one, very rare hardware deffect,no problem since new phone

Connecting voice call blacks screen, must reboot

The Problem: As soon as I make a call or answer one I'm receiving, the screen goes completely black, although the call is connected and I can speak with them okay. I almost always must reboot the phone by holding power and volume button in order to use my phone again. Very rarely the screen has turned back on, I think after the call disconnects, but this is not reproducible.
I can't say when this started happening, but it may have been after I was fixing a "ERROR: LoadImageAndAuth Failed: Load Error" boot up issue I created when messing around, I think when I restored an old backup made with TWRP. I fixed the problem using this method (a modified Deuce script/.bat file that flashed in the 8.1 OTA to both A/B slots) but I'm not positive. I don't talk on my phone that much so it's hard to say what when.
I'm contemplating putting my phone as far back to storebought-stock-setup as I can before I modified it with Magisk and TWRP, but I wanted to check in here to see if anyone had suggestions on what to look at. My Hope is this will subside when I undo everything and then I can see where the problem was created as I walk the path again, checking as I go.
I tried wiping my data partition in TWRP and setting Android it up from scratch but it looks like the water is still black.

mentalfloss said:
The Problem: As soon as I make a call or answer one I'm receiving, the screen goes completely black, although the call is connected and I can speak with them okay. I almost always must reboot the phone by holding power and volume button in order to use my phone again. Very rarely the screen has turned back on, I think after the call disconnects, but this is not reproducible.
I can't say when this started happening, but it may have been after I was fixing a "ERROR: LoadImageAndAuth Failed: Load Error" boot up issue I created when messing around, I think when I restored an old backup made with TWRP. I fixed the problem using this method (a modified Deuce script/.bat file that flashed in the 8.1 OTA to both A/B slots) but I'm not positive. I don't talk on my phone that much so it's hard to say what when.
I'm contemplating putting my phone as far back to storebought-stock-setup as I can before I modified it with Magisk and TWRP, but I wanted to check in here to see if anyone had suggestions on what to look at. My Hope is this will subside when I undo everything and then I can see where the problem was created as I walk the path again, checking as I go.
I tried wiping my data partition in TWRP and setting Android it up from scratch but it looks like the water is still black.
Click to expand...
Click to collapse
I'm having the same issue but my pixel two is bone stock running 8.1.
Sent from my Pixel 2 using Tapatalk

Screen protectors that do not allow for the light sensor have this issue.

At least I'm not alone, if only for this problem, but my soul is still empty
steve0.adams said:
I'm having the same issue but my pixel two is bone stock running 8.1
Click to expand...
Click to collapse
That's good to know an unmodified version is also affected. Let us know what becomes your fix eventually, even if that means you had it swapped for another phone.
Turns out when the call disconnects I can access my screen again. A temporary fix I figured out is in Android's Accessibility settings you can set the power button to hang up a phone call, so that will let you get back into the system without forcing a reboot.

Doesn't apply to me
teakdamar said:
Screen protectors that do not allow for the light sensor have this issue.
Click to expand...
Click to collapse
I have a screen protector but the phone still functioned okay after it was applied. Just to double-check this I just peeled it back right now and the same behavior still happened. Good point, though.

Google Backup Greyed out OnePlus 7 Pro

Hey guys I received my Oneplus 7 Pro yesterday and its a great phone but I found a problem. If I go to Setting-System-Backup, under Google Backup the Backup Now button is greyed out.
I did some Googling and found a temp fix which worked for another Android Device. If you disable the screen lock by not securing the OnePlus with a code or password then go back to Backup, the Backup Now button is now enabled, but as soon as you put screen lock back on it greys out again.
Also there is a message under each item waiting to be backed up such as App Data, the message is waiting to Backup. Anyone else seen this problem on any other devices and is there a perm fix?
I reset my phone to factory defaults and went through the whole setup process same issue. Don't understand what's going on.

same here in germany

Same thing in Canada.

Hi,
I noticed this was the case a couple of days ago when I first got the phone. I have left it alone for two days and I now have the option to force a backup (ie the button isn't greyed out). I also went into it by Settings, Google, Backup rather than Settings, System, Backup. Not sure if that makes a difference?
I am backing everything up now so I can confirm it works. Maybe the phone needs a couple of days to settle down before it allows the backups to be taken manually?

Mines working fine. Button not greyed out.

rav101 said:
Hi,
I noticed this was the case a couple of days ago when I first got the phone. I have left it alone for two days and I now have the option to force a backup (ie the button isn't greyed out). I also went into it by Settings, Google, Backup rather than Settings, System, Backup. Not sure if that makes a difference?
I am backing everything up now so I can confirm it works. Maybe the phone needs a couple of days to settle down before it allows the backups to be taken manually?
Click to expand...
Click to collapse
Thanks a lot, your way works!

.vermilion said:
Thanks a lot, your way works!
Click to expand...
Click to collapse
I've got the same problem.

Blue button for me.

I had the same issue the only way I was able to fix is the same way the original poster fixed it was was removing the passcode on the device. I was wondering if this was one plus issue? or just carrier modded version issue I currently have the t-mobile version of the device I also tired doing the backup via ADB and that didn't work. But as soon as I removed the password it worked immediately.