Database Develop

G1 big problems

Hay i have a rooted G1 with Jf - can't rember what version.
I've been having lots of problems with force closing of various programs but otherwise everything was going fine.
After a few force closes today i decided to restart my phone, turned it off and then back on and stuck it in my pocket.
When i went to check my texts 5 minuets later i took it out and it was just stilling on the 'Android' splash screen - it was moving then freezing for a few seconds then moving (i don't know if that's normal but it wouldnt surprise me).
I took the battery out and restated again and exactly the same thing - it would not boot.
I did a quick search on the problem and remembered how to boot in camera+red mode - which the phone did fine. I then read that pushing green+menu+red would fix it.
I did this and the phone booted, but it lost all my home screen icons and was laid out like when the phone was bought. i then cheked an app or two and they are all still there and seem to have retained their data.
However other strange things are happening - the home button dosnt work, nether does the green, when i hold the red button i only get the 'power off' option not 'power off, silent and airplane' as i used to.
They are the problems i have found so far but there may be more. Basically i want to know what pushing green, menu, red actually does and i want to know what the hell is going on - im totally lost.
Please help
P.S. i did a test on the consol and it seems i still have root assess - just encase that relative

Go to recovery, wipe and reflash. It will solve all your issues.

I can't actually remember how to do that - can you explain more or link me?
and will it have any effect on my apps or settings?

Zippokovich said:
I can't actually remember how to do that - can you explain more or link me?
and will it have any effect on my apps or settings?
Click to expand...
Click to collapse
You're going to need to go into recovery; press the home screen button, then the red (energize, end call, whatever) button. Hold both down until you get into recovery, which will be the text menu with all the selections available in green. Then scroll down to "wipe data/ factory reset" and do that- this simply wipes the phones internal memory. Then load the rom you are using, which I assume is already on the root of your sd card. If not, connect the phone, mount the card, and put the rom there before you get started with the above steps- chris

[Q] Nexus One CM7 power button problem

I have an AT&T unlocked Nexus One that I recently flashed to CM-7.0.3-N1 . I have had a problem unlocking the device with the power button both when I was running stock Gingerbread and now that I have installed CM7.
When the screen is off and my N1 is in standby, I push the power button and the screen turns on and then back off almost immediately. Sometimes there is a half second delay before the screen turns on and then off. This usually goes on 2 or 3 times until the screen will stay on and I can unlock my phone.
Has anyone seen or heard of this problem, and maybe knows of a fix? It could be hardware related, but the button definitely sends a signal to the phone and it works fine to shutdown or turn on the device from completely off. Thanks.

ummm the power button on the nexus one has an incredibly high failure rate, all over the forum here. its a design defect from the factory. that's why it has always been recommended to root the device immediately, and use trackball wake, so you avoid using the power button as much as possible. you have to send the device to HTC for repair, that's your only option...

Thanks for the information. I will have to look into repairs.

You are already running a rooted rom with track all wake. Use it. To reboot the the phone use quickboot. At this stage you really don't need the power button on your phone.

pcflet01 said:
... now that I have installed CM7.
I push the power button and the screen turns on and then back off almost immediate
Click to expand...
Click to collapse
This is a problem with CM7. Most advise turning off the screen off animation if it becomes a big problem for you. Make sure you are using the newest nightly and hope for a fix. I don't know if the RC's have this problem, but I would bet it appears on the 7.0.3 release.

At first glance that seems to have helped. Thanks for the advice!

No problem.

Also you can use widget locker to lock the screen then the trackball to wake, with that and quickboot I don't even touch my power button anymore. Although your problem doesn't sound like a broken power button so in your position I would switch ROMs and see what happens.

pcflet01 said:
I have an AT&T unlocked Nexus One that I recently flashed to CM-7.0.3-N1 . I have had a problem unlocking the device with the power button both when I was running stock Gingerbread and now that I have installed CM7.
When the screen is off and my N1 is in standby, I push the power button and the screen turns on and then back off almost immediately. Sometimes there is a half second delay before the screen turns on and then off. This usually goes on 2 or 3 times until the screen will stay on and I can unlock my phone.
Has anyone seen or heard of this problem, and maybe knows of a fix? It could be hardware related, but the button definitely sends a signal to the phone and it works fine to shutdown or turn on the device from completely off. Thanks.
Click to expand...
Click to collapse
I'm experiencing exactly this too on the latest RC. It doesn't seem to be complete button failure but it's acting like I've pressed it twice sometimes. Disabling the screen-on animation does seem to prevent it from popping back on. But it still sometimes goes on-then-off when I wake it with the power button. So now I'm using trackball wake too.

As others have mentioned, this does not sound like a powerbutton issue, because the powerbutton still turns on the screen. The problem is that the screen turns off immediately after it turns on.
When you flashed 7.0.3, did you come from a previous CM verison? From stock? My first suggestion would probably be to wipe the /system partition (in CWM, it is under mounts and storage -- with Amon_RA, you need to find a flashable zip to do it) and reinstall CM and gapps. This will not cause any data loss. Sometimes, if you install a new ROM over an old one, the upgrade script in CM can get confused and carry over files that aren't supposed to be carried over. The system wipe fixes that.

I've been using this RC since it came out in late June. Only this week did it start flipping out on me.
Sent from my Nook Color!

It still can't hurt anything to do a system wipe, just in case something got screwed up (these things can be so temperamental at times). And, like I said, you won't lose any of your data.

bassmadrigal said:
It still can't hurt anything to do a system wipe, just in case something got screwed up (these things can be so temperamental at times). And, like I said, you won't lose any of your data.
Click to expand...
Click to collapse
I'm currently using S2E for apps2ext and some data2ext. How would a system wipe and reinstall interact with that? I'm a bit nervous on that front.

A system wipe shouldn't change any of that. It is one benefit of using S2E as it is a standard app that is stored in the /data partition without any changes to the /system partition.
Anyway, to be safe, it is a good idea to do a nandroid backup anytime you are doing something that involves the majority of the features in recovery.

It's a hardware problem for me. Failed completely as of today.
Sent from my Nexus One using Tapatalk

CM7 7.1.0
My power button seems to be in the process of completely failing. The new CM7 update to 7.1.0 has made it possible for me to lock the screen without using the power button using the "Notification power widget" -> "Go to sleep". Now the only times I have to use the power button are to shut the phone down or wake it up, which seems to be easier when the phone is plugged in to a wall charger. Are there any simple apps for shutting the phone down and maybe waking it up at a set time?

The only reliable trick I found to turn it back on was to plug into the wall and take the battery out/in a few times till it vibrated.
I ended up getting a replacement phone and then I sent the Nexus to HTC. They quoted a $55 repair cost off warranty which my credit card insurance would've covered, but when I asked for an invoice they offered to just waive the charges. Finally over a month later it came back fixed.
The app Easy Reboot can shut the phone down.
Sent from my Nook Color!

I also use an app called Lock Screen, which just locks the screen. I have it stored in my dock, because I don't like the space being used in the notification widget.

CM7 has an option for one of the items in the notification tray widget to be a lock screen button.

cmstlist said:
I'm experiencing exactly this too on the latest RC. It doesn't seem to be complete button failure but it's acting like I've pressed it twice sometimes. Disabling the screen-on animation does seem to prevent it from popping back on. But it still sometimes goes on-then-off when I wake it with the power button. So now I'm using trackball wake too.
Click to expand...
Click to collapse
THANK YOU!!!! This has been driving me crazy. Turning off the screen-off animations did nothing, but turning off the screen-on animation seems to have fixed the issue. My power button is toast (my new power button ribbon cable just arrived... time for surgery), and I've been using the trackball to wake my phone. Before the power button died, it did the same thing. I'm using CM7.2. I installed it after rooting and went straight to cm7.2 from stock, so obviously the cyanogemnod crew haven't fixed the issue since 7.0.3 when this thread started.

Samsung Captivate Power Button Not Working . FIXED :)

If your phone's power button is in a 'pressed' state, like mine, (turns on automatically when battery is inserted), it is a hardware issue.
Here is a hassle free alternative to turn on the phone when it is in sleep mode, without relying on the power key!! Takes a minute or two only!!
1. Get 'Go launcher' from the app market (play)
2. Get 'Go Locker'
3. Now Enable Go Locker on your device. And you are done!!
When the screen goes black again, Just press the volume button, The screen wakes up!!
Using this method you don't lose the normal functionality of the volume rocker!!
I recalled that I used to have Go Locker on my phone, and that when I pressed the Volume key the screen turned on!!
At that time I found it a little annoying, But now it has turned out to be such a gift!!
* For this method to work, your phone has to be rooted.
The power button is not going to work until the hardware is repaired, I prefer to use this method, because it is a safe and quick method!!
Believe me I looked around the internet and this forum for a fix, The usual method: editing the system files on the phone, and after which the volume button cannot be used to control the volume.
For those looking for a quick fix, just follow my method!
Cheers!

There are also several roms out there that have the volume rocker wake built into the rom without making it completely useless for it intended purpose. As well as several that offer a go to sleep toggle in the notification window so you can lock your phone again.

so this is a hardware issue ? i had been using the go locker i been using but the power button is annoying cus it keep showing the power button options . and killing my battery.
only fix is samsung?

Pretty much every version of cm for cappy has volume rocker wake as an option, because of this common problem. I use app called turn off screen as well.

Natureboyhcg said:
so this is a hardware issue? only fix is samsung?
Click to expand...
Click to collapse
I had the exact same problem with my Epic Touch 4G. Thought it was the ROM, the overclock, etc. I flashed back to (almost) stock, went back to original clock speeds. I couldn't figure out what it the world was causing the issue, until it got worse. Then, I noticed that even brushing past the power button would wake the screen, and about 10 seconds later the phone would reboot.
Long story short, I bought a replacement power switch, soldered it in place, and have had zero problems since!
Several eBay sellers offer the proper replacement switch you'll need.
(They don't include the required skills to properly desolder/solder it, however. It's a tiny switch - about 4mm x 2mm x 1.5mm, and you'll need a good quality fine-tipped soldering iron.)

[Q] Very slow camera launch?

Most of the time when I open the camera I have a 2-4 second wait for the app to open, anyone else? It does open but takes forever. If I have used it recently, within 10-15 minutes it is pretty snappy, 1-2 seconds at most.
I did install the google camera app but the problem predates that. It opens faster, but focuses slower so in usage it isn't any better.
At any given moment I may need 3-5 seconds to take a pic with either app. Certainly a 1st world problem but a nuisance when I want a spontaneous pic.
Anyone heard of this as precursor to the failed camera problem?

No that is not a problem.

delawaredrew said:
Most of the time when I open the camera I have a 2-4 second wait for the app to open, anyone else? It does open but takes forever. If I have used it recently, within 10-15 minutes it is pretty snappy, 1-2 seconds at most.
I did install the google camera app but the problem predates that. It opens faster, but focuses slower so in usage it isn't any better.
At any given moment I may need 3-5 seconds to take a pic with either app. Certainly a 1st world problem but a nuisance when I want a spontaneous pic.
Anyone heard of this as precursor to the failed camera problem?
Click to expand...
Click to collapse
My gf has exactly the same problem. I'm gonna try the following steps:
You might find that a simple restart does the trick. Hold down the Power button and select the Restart option. The problem may return.
Try going to Settings > Application manager and select the camera app. Tap on Force stop, Clear cache, and Clear data.
Try clearing the cache partition. Hold the power button and choose Power off then press and hold the Volume up key, the Home button, and the Power button. When the phone vibrates, release the Power button, but keep holding the other two. When you see the Android System Recovery screen you can let go. Use Volume down to choose wipe cache partition and press Power to select it then, when it’s done, press Power again to Reboot System Now.
There’s a chance that an app is causing the problem. Any app that uses camera functions, including flashlight apps, could be the culprit. The fast way to check this is to reboot in safe mode. Hold down the power button and select Power off then hold down the power button to turn it on again and when you see the Samsung screen come up, release the power button and press and hold the Volume down key. You’ll know it worked if it says Safe mode in the bottom left corner. If the camera works then it’s definitely a problem with an app you installed. Hold down the power button and choose Restart to get back out of Safe mode.
If you’re using a microSD card to save photos try removing it, save them elsewhere, and see if that makes a difference.
Back up anything important and try a factory reset via Settings > Backup and reset > Factory data reset.
Have you solved the problem yet?

It may or may not be related to this...
http://www.informationweek.com/mobi...mera-problem-samsung-eats-crow/d/d-id/1234898
If it continues, exchange it for another S5.

F-energy said:
My gf has exactly the same problem. I'm gonna try the following steps:
You might find that a simple restart does the trick. Hold down the Power button and select the Restart option. The problem may return.
Try going to Settings > Application manager and select the camera app. Tap on Force stop, Clear cache, and Clear data.
Try clearing the cache partition. Hold the power button and choose Power off then press and hold the Volume up key, the Home button, and the Power button. When the phone vibrates, release the Power button, but keep holding the other two. When you see the Android System Recovery screen you can let go. Use Volume down to choose wipe cache partition and press Power to select it then, when it’s done, press Power again to Reboot System Now.
There’s a chance that an app is causing the problem. Any app that uses camera functions, including flashlight apps, could be the culprit. The fast way to check this is to reboot in safe mode. Hold down the power button and select Power off then hold down the power button to turn it on again and when you see the Samsung screen come up, release the power button and press and hold the Volume down key. You’ll know it worked if it says Safe mode in the bottom left corner. If the camera works then it’s definitely a problem with an app you installed. Hold down the power button and choose Restart to get back out of Safe mode.
If you’re using a microSD card to save photos try removing it, save them elsewhere, and see if that makes a difference.
Back up anything important and try a factory reset via Settings > Backup and reset > Factory data reset.
Have you solved the problem yet?
Click to expand...
Click to collapse
I did clear the cache and I switched to internal storage. Also I uninstalled Google' camera app, which I thought would be neat but never used after 1st launch; it seems a little faster but I'll have to use it a few days to see. It may be my SD, as it is pretty old.
Safe Mode didn't effect any change.
I'd never tried to enter recovery on this phone and inadvertently entered Download mode instead. I blame my overly large fingers for it. Gave myself a moment of concern as I only see DL mode when I first root a device, almost 2 years ago for my last phone. I'd forgotten that the "DO NOT TURN OFF TARGET" warning didn't mean much without Odin running.
If this isn't an indicator of a upcoming camera issue I'm not too worried about the lag, if it fails it has a warranty....
scott14719 said:
It may or may not be related to this...
http://www.informationweek.com/mobi...mera-problem-samsung-eats-crow/d/d-id/1234898
If it continues, exchange it for another S5.
Click to expand...
Click to collapse
Yeah.. I mentioned that in OP. That problem usually presents as a "Camera has failed" message according to articles, there is no reference to any symptoms prior to failure.

Try going to Settings > Application manager and select the camera app. Tap on Force stop, Clear cache, and Clear data.

Kael ruch said:
Try going to Settings > Application manager and select the camera app. Tap on Force stop, Clear cache, and Clear data.
Click to expand...
Click to collapse
I'm also having the same issue, doing a restart or clearing cache/data on the camera app just fix the issue temporarily, after couple of days it gets super slow again.

I've also started to run into this issue. The camera will take several seconds to load, then freeze for a second or two. This happens after I haven't used the camera for a while. The gallery, however, always takes several seconds to load when launched from the camera. Both of these still happen whether the camera is set to store on internal memory or my microSD card.
Are there any solutions that anyone has found?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

If I have the image stabilization turned on it makes my camera crawl too. Turning it off seemed to help, at least some.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app

This has really begun to annoy me, as the weather turns nicer here I find that I am using the cam more frequently and the delay is aggravating.
Clearing cache helps a little, and turning off Image Stabilization seems to have helped also. Still a few seconds longer than I like but better. This thing should open a major built-in app faster than it does, I think it did at first.
I may do a factory reset and see if that helps, if not I may seek an exchange from AT&T or Samsung...
Drew

[Q] Upgraded 176CX is very slow

I have upgraded my Asus 176CX to Android 5.0. Although I like the new version, the responses inside the applications (and mainly simple games) is not good. The start time of the applications is 2-3 times slower than the older and slower Asus MemoPad 7 HD!
Any ideas how to fix that?

Mine too. Have you tried factory reset without automatic restore?
I did it and now it's much faster, almost as much as before the update. The game's still stuttering quite a bit but not as laggy as before.
The main problem I have is the screen seems to have lower contrast than in 4.4.2 and sometimes the colour just goes washed out and then return to normal. Especially when switching apps. But sometimes it just does that for no obvious reason.
Also the amount of bloatware just went through the roof and I can't disable or delete them like before.
To anyone passing by: Hold on for a bit. As far as I'm concern the only good thing I can find in this update is native support of USB Audio.

What do you mean by "Automatic Restore"?
Also, after the factory reset, how did you re-installed the apps? I don't want to loose my data, I have some apps (not just games), like for example my Lufthansa app with all my data and Boarding Passes etc that I really need.
The bloatware is a lot. I cannot disable most of it. One of the good things: The backup application.

In Backup & reset you'll have 2 choices called
- Back up my data
- Automatic restore - which will restore your apps along with settings after factory reset. But to be sure that it deletes all files that might cause the device to slow down I'll disable it.
And yes, after factory reset with this option disable you will have to reinstall all your apps and all your data will be gone. So make sure you back up everything you need before doing it.
WARNING: If you have important data like boarding pass in your airliner app then I wouldn't suggest you do the factory reset because even if you enable both "backup my data" and "automatic restore" there's still some risk that data in some apps might not come back.
Back to the issue of device slowing down, another way to fix it is format cache partition. This is the safest way to fix the problem without losing all your data, apps or any settings but I really can't find a way to do it.
Edit: Found it!
Here's how you do it:
- Turn off your device.
- Hold down "volume down" then press power button until it turns on.... at this point continue holding the volume down button.
- After you enter fastboot mode, release the volume down button.
- Use volume up or down to navigate the menu, select "RECOVERY" then press power to choose.
- It will show the belly up droid, don't panic.
- Press volume up and power simultaneously, hold them down for about a second then release them. If this doesn't work try holding down a bit longer. You will get in to recovery menu.
- Use volume up or down to navigate the menu, select "wipe cache partition" then press power to choose.
- Wait until it says "Cache wipe complete." on the bottom of the screen.
- Choose "reboot system now".
Try this first and if it doesn't fix your problem I'm afraid you'll have to factory reset your tablet.