O2 Froyo 2.2 Update Today - Desire General

For anybody who's interested

Has anyone had a successful update, there are a couple of guys on the o2 Forums that are having trouble.
o2 Forum

yes, mines went with no problems
stock O2 desire

bjproc said:
yes, mines went with no problems
stock O2 desire
Click to expand...
Click to collapse
Oh ok, and was there anything special you did? How much free space? which screen SLCD or AMOLED?
Sorry for all the questions, don't need a shiny new paper weight

Can someone confirm the software number and baseband? I'd like to see if it's the same release as before.

teppic74 said:
Can someone confirm the software number and baseband? I'd like to see if it's the same release as before.
Click to expand...
Click to collapse
kernal version 2.6.32.15-gd96f2c0
software version 2.
14.207.1
build number 2.14.207.1 cl233777
This is the info from the o2 Forums

Looks like it's the same release then. Cheers.

matt.tumber said:
Oh ok, and was there anything special you did? How much free space? which screen SLCD or AMOLED?
Sorry for all the questions, don't need a shiny new paper weight
Click to expand...
Click to collapse
no, nothing special, just seen the update today and updated it, as i've said, mines was a stock phone with nothing done to it.
it's an AMOLED
sorry, not sure how much free space i had, but i don't have a lot on it, if this helps

Installed ok here too had to remove some apps as it needed about 28 meg free.
Sent from my HTC Desire using XDA App

Finally! Updated to 2.2 without any problems (have an AMOLED display).
Arite.
Sent from my HTC Desire using XDA App

I'm not touching this update until O2 confirm what the problem is. Apparently, it's exactly the same build released a few weeks ago. You know, the one that bricked about 1/3 to 1/2 of the phones it was applied to. Knowing O2, they'll probably just pull the update again, sulk for a few weeks, then give it another go.
I rely on my phone pretty heavily, and I'm not risking losing all of my data just because O2 can't get their crap together and release a stable ROM. With the popularity of this phone, it's surprising there's not more of an uproar about it. Would really like to know just what the hell's in this ROM that's causing so much hassle.
Will keep an eye on the O2 forum for the next couple of days, see if there's anything resembling some official feedback. This is a joke.

Just update... no problems!!!
Sent from my HTC Desire using XDA App

Please could someone explain step by step how to do the update as i have downloaded the exe. file. Much help needed.

If you're willing to risk it, the standard update procedure should run as follows.
1) Free at least 88MB of space on your phone memory.
You can check your phone memory by pressing the Menu button, going to Settings, then SD & Phone Storage. The value at the bottom (Internal phone storage) is the one you're looking for. The reason for needing such a large amount of space is to accommodate the 87.21MB update file.
If you don't have enough free space, you can start deleting applications from your phone to clear some room. You can do this by going to the Applications section of the Settings menu, then to Manage Applications. Bear in mind that you can also clear the cache / stored data of some applications without having to delete them, but that some applications cannot be deleted at all.
2) Charge your battery.
The update procedure is best done with a full battery, so make sure it's freshly charged if you don't plan to keep it plugged in for the duration.
3) Restart your phone.
Having a load of applications running in the background is never advisable when doing upgrades. The phone will have to restart during the update procedure, so the less it has to shut down, the less can go wrong.
4) Recommended: Plug your phone in to charge.
The update can take a while. If you're fully charged, it shouldn't matter, but it can't do any harm.
5) Check for updates.
This is a simple matter of pressing the Menu button, going to Settings, About Phone, System Software Updates, then hitting "Check Now". The phone will say that a new update is available. It is highly recommended that, if you're in an area that allows it, you use WiFi only. It reduces the risk of the update being split over two different data connections during the download. Once you're happy with the setting, hit OK.
6) Wait.
For a good while. Don't touch your phone unless it asks you to. Don't interrupt the update unless the world is falling apart and/or someone offers you a great deal of money to do so.
If anyone wants to correct me on any of these steps, go right ahead. But assuming that the update file isn't broken entirely, this should allow for a pretty smooth update process. Good luck.

Updated my wife's phone last night - broke all the rules - but it went off without a hitch. Battery at about 70% , didn't reboot first - though she had not installed any apps. Took about 20 mins - never touched it during that time.
Installed the updated gmail afterwards and that worked fine too.
Don't know the screen type.
Good luck everyone else, hope your updates go well - it's well worth it.
Cheers

mine went yesterday, cleared out some apps as it requested more memory and after install the phone went into the sense force close loop that happened the 1st time it was released
online support told me to take it to a o2 retail shop and they would fix it quickly in shop
o2 retail told me they offered no such service and it would be sent away for repair
ended up using this solution found on the o2 forum
1. Shut down the handset.
2. Press the "Volume down" button and (whilst keeping it pressed) press on the power button.
3. You will see some boot up text.
4. Go to the "Clear Storage" option using the "Volume down" button, then select that option by pressing the power button.
5. Press the "Volume up" button to start the process.
6. After clearing the storage, it will restart - hopefully the Sense reload issue should have resolved (mine did!).
PLEASE NOTE: SELECTING THE "CLEAR STORAGE" OPTION CLEARED OUT EVERYTHING ON MY PHONE, set up the active sync and touchdown and it all came back and most other stuff is backed up anyway
R

Did the update OTA successfully. But i noticed that i can browse on my phone unlike before when running 2.1. I took it to my service provider Etisalat for manual configuration, but all to no avail. At Etisalat, they told me that there network can't provide internet service for HTC desire running on android 2.2. I don't know if what they told me is true or not. could someone please help me out. I have an O2 branded desire and updated it to O2 froyo update.

Related

Why is my O2 Orbit soooo sllllooowww?

I've had an O2 XDA Orbit for about a month. It's my first Windows mobile product. I love the range of functions. I like being able to use CoPilot with the GPS. I really like being able to sync my Outlook address book.
BUT... the thing hangs ALL THE TIME. Sometimes it hangs for a few seconds. Other times, it locks up completely and I've got to take the battery out to reboot because even the power button doesn' work.
Last week, it hung during a re-boot, I tried the PIN number a few times and it locked me out for a full day. O2 tech support didn't have a clue what was going on. I sorted it myself. (I've now disabled the PIN).
It's really annoying when you have to wait a full minute before you can make a phone call because it is hanging whilst opening up your contact list.
How do I make the thing stop hanging?
Tolkien said:
I've had an O2 XDA Orbit for about a month. It's my first Windows mobile product. I love the range of functions. I like being able to use CoPilot with the GPS. I really like being able to sync my Outlook address book.
BUT... the thing hangs ALL THE TIME. Sometimes it hangs for a few seconds. Other times, it locks up completely and I've got to take the battery out to reboot because even the power button doesn' work.
Last week, it hung during a re-boot, I tried the PIN number a few times and it locked me out for a full day. O2 tech support didn't have a clue what was going on. I sorted it myself. (I've now disabled the PIN).
It's really annoying when you have to wait a full minute before you can make a phone call because it is hanging whilst opening up your contact list.
How do I make the thing stop hanging?
Click to expand...
Click to collapse
Put either the HTC or DOPOD rom on it, the O2 one is crap.
Tolkien said:
It's really annoying when you have to wait a full minute before you can make a phone call because it is hanging whilst opening up your contact list.
How do I make the thing stop hanging?
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showthread.php?t=297793
for a start overclock it and you will a great difference in speed
http://www.trancreative.com/mb.aspx
Longhair said:
http://www.trancreative.com/mb.aspx
Click to expand...
Click to collapse
I don't know about the O2 model but I believe the HTC model already has such a function, it just needs to be turned on. It should be in settings and titled Task Manager.
Download "Audacity" and it comes with a free sd card speed test.
See it it's the speed of the sd card.
If it is then read through the "corrupt card" thread >> you will see the recommendation -- set the power turnoff time to say 2 minutes and never use the on/off switch.
You will need a soft reset in between to reset the speed of the card.
kennyidaho said:
I don't know about the O2 model but I believe the HTC model already has such a function, it just needs to be turned on. It should be in settings and titled Task Manager.
Click to expand...
Click to collapse
Here is my personal experience on the link I gave you:
Before I installed it - I would click the OK button in the upper right hand corner. The application would only be MINIMIZED. After a while, all the minimized programs eat up so many resources that it bogs down the phone.
After I installed it, the OK button was replaced with an X and it would actually CLOSE the applications freeing up the resources.
It is a small free program that can be uninstalled if you do not like it - so there is nothing to lose.
Now what I don't understand is why didn't WM5 give the choice to either minimize or close applications like they do with PCs
Longhair said:
Here is my personal experience on the link I gave you:
Before I installed it - I would click the OK button in the upper right hand corner. The application would only be MINIMIZED. After a while, all the minimized programs eat up so many resources that it bogs down the phone.
After I installed it, the OK button was replaced with an X and it would actually CLOSE the applications freeing up the resources.
It is a small free program that can be uninstalled if you do not like it - so there is nothing to lose.
Now what I don't understand is why didn't WM5 give the choice to either minimize or close applications like they do with PCs
Click to expand...
Click to collapse
I reckon the reasoning is that if people minimize applications (which they will do to avoid launch lag) and forget to close applications (which they will do ) the device will definitely crash.
For an insight into WM5 memory management read this:
http://blogs.msdn.com/windowsmobile/archive/2006/08/16/702746.aspx
Incidentally, the O2 Custom Today plugin included with the O2 UK Orbit rom allows you to actually close an application.
in the bottom right of my o2 device is a little o2 logo that allows me to close programs manually, works a treat
Thank you
Thanks so much to everyone who has responded to my (desparate sounding) post.
I use the O2 button to close applications routinely. I don't leave them open because I know this slows things down and (presumably) increases battery usage. I don't think that is the cause of the problem.
I've already been through the routine with the SD card. I don't think that it the problem either.
The only suggestion here I haven't tried is overclocking it. How do I do it? Does it invalidate my warranty?
amino said:
in the bottom right of my o2 device is a little o2 logo that allows me to close programs manually, works a treat
Click to expand...
Click to collapse
Same as mine. It's pretty good.
yup, it will invalidate the warranty so just hope you can take it off before it goes back if it has to, I work for o2, the people in the shop wont know that youve overclocked it and I wouldnt tell them, the repairers on the other hand might spot it so be careful
tou can get the overclocking program here: http://www.chi-tai.info/cs_BatteryStatus_XDA_Neo_WM5_iM_cs.htm
theres full instructions, read before you start tweaking it on your own. I have mine overclocked to 260mhz and I noticed the difference immediatley, it reverts back to 201mhz in sleep mode and jumps to 260 when I power it up.
hth
Do you have a skin? I downloaded a nice AppleMac style skin and everything slowed down - took me 2 days to realise the cause.
Also, the o2 icon does not always close programs. Use it then go to Settings/System/Memory , have a look in the Running Programs tab and you sometimes see something still in there that should have closed with the o2 icon!!
Michael

Anyones phone freezing after sleep mode?

I noticed this after I set up direct push email. Wondering if anyone else is having the same issue.
BTW I'm using the Premier Plus Rom and Mail 2 Web free push service
mine is, dont know why but just started recently after re flashing to artemies love rom 4.1.
Sometimes it shuts down when it wants to, freezes when it wants to and received sms notification dont work even after you have set it in the phone settings.
I reckon didnt flash properly so i am going to do it again. I hate flashing.
illusion786 said:
mine is, dont know why but just started recently after re flashing to artemies love rom 4.1.
Sometimes it shuts down when it wants to, freezes when it wants to and received sms notification dont work even after you have set it in the phone settings.
I reckon didnt flash properly so i am going to do it again. I hate flashing.
Click to expand...
Click to collapse
Thanx for replying but I think I've narrowed it down to a storage card issue. i noticed that it woud freeze for abouta full minute when I had a particular program open that I run from the storage card. I moved it to the Device memory and today it still froze, but I could at least turn the device on and off.
Now that I think about it, I noticed this freezing after i reflashed to the Premium Plus ROM with SDHC support. I upgraded from a 2GB Card to a 4GB Card. So it could be the SDHC drivers or just the card itself. I'm going to switch back to the 2GB card for a few days to see if it happens again.
That's as far as I'll gotten. These observations were made after a hard reset.
And I know what you mean about reflashing. You hare to reinstall everything. But it's good to do at least once a year.
illusion786 said:
mine is, dont know why but just started recently after re flashing to artemies love rom 4.1.
Sometimes it shuts down when it wants to, freezes when it wants to and received sms notification dont work even after you have set it in the phone settings.
I reckon didnt flash properly so i am going to do it again. I hate flashing.
Click to expand...
Click to collapse
I have very similar issues on mine.
I had the Oops v1.0 on it, then thought it had been a while since I last flashed, and perhaps that was the reason it froze often no logical reason to think this ! I KNOW).
So I flashed it with another ROM, and it does exactly the same. I have searched on this forum and seen some HTC do this as well.
UPDATE:
I have now narrowed it down to this:
I discovered that if I restart my Atremis and use it as normal or leave it on a stable table or side bed, it works OK, but if I slip it into my pocket for a minute it freezes....or if I place it in the same space/place/pocket/bag with my BB Pearl it just freezes....AMAZING !
I will be very stunned...yes stunned if their any solution to this...
Feel free to stun me !
I dont have any input on the issues you guys are having but I think i solved my own problem. I moved two programs from the storage card to the main memory and it hasnt come back. Actually, I think it was just the 2nd program.
I'm using an older ROM though: O2 Premium Plus by Meschle (now retired). I've stuck with this ROM because it's been the most stable for me.
UPDATE
I have very similar issues on mine.
I had the Oops v1.0 on it, then thought it had been a while since I last flashed, and perhaps that was the reason it froze often no logical reason to think this ! I KNOW).
So I flashed it with another ROM, and it does exactly the same. I have searched on this forum and seen some HTC do this as well.
UPDATE:
I have now narrowed it down to this:
I discovered that if I restart my Atremis and use it as normal or leave it on a stable table or side bed, it works OK, but if I slip it into my pocket for a minute it freezes....or if I place it in the same space/place/pocket/bag with my BB Pearl it just freezes....AMAZING !
I will be very stunned...yes stunned if their any solution to this...
Feel free to stun me !
Possible solution
Hello,
first of all when you experience any kind of freezing, run a full scandisk in Pocket Mechanic, then Check Notification queue in the same app.
Also check Start - settings - system - Key lock , make sure that you select "Lock all buttons except power" (first option). Restart your Artemis and try if the problem happens again.
Well it's been a week and I haven't had the freeze come back after I moved a couple programs from my storage card to my device. Both were programs with an application (small) and a huge database on the storage card (Oxford Spanish Dictionary & iSilo data base). I noticed that I always got the freeze when one or both of these applications was running.
So, of course, the data base info is still on the storage card but the applications are saved under Windows/Programs. No more freezes. And when I mentioned freeze, I ment that the phone would be extremely slow to respond to inputs. I would wait about 30 to 60 seconds for it to respond. If I pushed the power button 3 or 4 times, like a minute later I would get the screen flashing on and off so it's registering the commands. I wasn't sure if this was the same type of freezing that others were experiencing.
I'm thinking it has something to do with the card or the drivers for the SDHC. I never had this problem without the SDHC support and my 2GB card. Just FYI
nik3r said:
Hello,
first of all when you experience any kind of freezing, run a full scandisk in Pocket Mechanic, then Check Notification queue in the same app.
Also check Start - settings - system - Key lock , make sure that you select "Lock all buttons except power" (first option). Restart your Artemis and try if the problem happens again.
Click to expand...
Click to collapse
As funny as it may sound.
I did the above and noticed a few days after, that the freezing is now reduced....still happens from time to time, though not as frequently as it used to...
What is the logic?
I assumed it was due to my frequent ROMing of my Atremis....guess patience has now paid off, but seriously and technically, I would want to be able to explain what is happening !
I had the Standby of Death SOD this is when the phone fails to come out of standby with a power button press. This issue only affects some people on some networks. I'm not sure if its a network problem or a software problem but as only a minority of people have it, I suspect its mainly a network problem there is a software solution.
The solution is to change the phone settings band option from auto 3G/2G to either 3G Only (WCDMA + UTMS 2100 in Europe) or 2G Only (GSM + AUTO) depending on your requirements.
Also read this thread http://forum.xda-developers.com/showthread.php?t=540943&highlight=standby&page=2where the resolution was to get a new SIM.
Obviously this only solves the problem when the crash is because of the sim and/or settings which impact the sim. To rule out a software cause its best to start with a hard reset.

[Q] Accidental Reset... wtf

I had a strange reset of my phone last night, through what I think was no real action on my part, but I wanted to defer to the experts and see if anyone can help me make sense of this...
Also, as you'll see at the end of my post—if you make it through my rambling—I could find some of the info I seek elsewhere on this, and other forums, but the combination of data would be a difficult scavenger hunt and I thought this thread may help other lite (or lazy) power users with similar issues or info searches in the future...
So I was changing my battery out last night and when I was pulling the dead one out I had accidentally turned the phone on, but was talking to someone at the time and, being distracted, continued pulling the battery.
I got the new one in and turned the phone on to be greeted by what I think is called, and excuse my ignorance on terms as I have had no real interest in rooting to date, the debug screen—white background, cute little android rascals on the bottom, several restart options, etc. I believe I selected 'fast boot', as I think I have done when some random serious of events have greeted me with the 'debug' screen in the past.
All seemed fine and the device started up but it lagged on a black screen with an icon I interpreted as an 'update' icon and a progress bar. When I got to the OS, my settings, screens, apps, etc were reverted to stock conditions. My SD card retained all its contents and I used AppBrain so I was able to get things back to some semblance of normalcy rather quickly, but I am left with so many questions...
I've come up with 3 possible explanations...I made an error on the 'debug' screen, my device had a huge and random hiccup, or there was some strange update last night that, despite my best efforts, I cannot find mention of here or on any other forums.
Some additional info...
-on App Brain site, after linking the reset device back up to my E-mail/account, I have a totally new list named, not by the former 'ADR6300', but by 'HTC Droid Incredible'. This leads me to believe either AppBrain has changed its naming convention for this device since I originally set the app/account up, or there was some strange mystery update.
-I have always updated when prompted so I believe I was running the newest OS and am still on 2.2 now.
I'm not really looking for a solution to the reset, more looking for answers/theories and some preventative measures for reducing possible distress should something similar occur in the future.
-back-up methods...I use Launcher Pro Plus - paid, and just realized I can back-up home screens and settings through the launcher but is there anything else I should be doing?
-break down on that 'debug' screen, best option to choose for various issues, etc.
-has anyone heard of a similar story, update last night, or know the reason for AppBrain's new naming convention for my device?
Any other info, tips, or relevant advice would be much appreciated. As a Web/graphic designer and modern woman I am inquisitive and technical by nature but tend to subscribe to the 'if it aint broke, don't fix it' school of thought unless there is some new feature I hear about or want when it comes to my device. So I am not dense but I definitely don't know everything and I am looking to you, the 'experts' for answers
You held vol - and the pwr button when you turned on the phone. That is what made you go to the bootloader (debug). From there i'm guessing you had the phone do a factory reset, that is why everything went back to how it was when you first bought the phone.
2.2 is the "newest" build available without rooting your device.
Rooting and making a backup through Recovery is the best way (imo) to create a backup.
For what it's worth, I think g00s3y is spot-on
When you get to the hboot screen (the white screen with the Android dudes at the bottom), there should be 5 options:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
FACTORY RESET
Seems most likely that you mistakenly hit the last one rather than the first.

[Q] First time smartphone owner, noob question?

Hey everyone!
So I've browsed on XDA forums for a few weeks now whilst deciding on the perfect smartphone for me, and decided on the HTC One X.
I've powered on, created accounts and synced all accounts on my One X, but there are some problems I've been having (NOTE: I bought this phone eBay refurbished and the Vodafone intro comes up every time I reboot the phone, oh and there are two Vodafone apps already installed, which I can't delete as well).
Anyway the problem is that I've heard that Jellybean on the HTC One X is already available in most countries (especially unlocked devices), but I have updated up to Sense 4.1 so far and it says that there are no more software updates?!
I live in Australia and the phone is unlocked (from Vodafone apparently) so why no Jellybean update?
Another problem I'm having is that the device is all around too hot most of the time (not warm, but really hot), but so far I've only used it while it's charging (even if the screen is turned off the phone is still hot whilst charging). Is this normal?
I've also heard of rooting, and was wondering for the HTC One X is it really complicated? (I've jailbroken iOS devices previously).
Last of all sometimes there are some touchscreen problems (e.g. I'm tapping multitask button and I have to swipe really hard to delete an app running in the background).
Thanks guys!
So far the phone is great, beautiful design, the screen makes me drool (a bit creepy I know) and it seems like android so far is awesome!
My HTC One X from Virgin mobile in Australia did an other the air (OTA) update to JB awhile back and just today did another update.
Yes, mine runs hot, not always, but often enough, especially after charging.
Touchscreen problems, can't comment as it's kinda subjective, but haven't heard any complaints about it (try a quick search and see what comes up)
Before you unlock your bootloader and try rooting the phone, please heed all the warning regarding creating backups of everything! Also, consider that your backup might be invaluable to others who are not on jellybean yet, depending on your phone's region, a nandroid backup (backup using Clockworkmod recovery tool) that is not jellybean could be an absolute life saver for someone out there.
I also highly recommend that you find the RUU that currently works with your stock ROM, and then the RUU version that should work with the jellybean update that it sounds like you plan on getting.
1. get the HTC windows drivers (assuming you are using windows)
2. get the fastboot files into a folder of your choice on your computer (lots of "all in one toolkits" out there include them)
3. hold power+vol down until the bootloader screen appears
4. use vol keys to navigate to fastboot and the power button to select it
5. plug into your computer via usb
6. with the windows folder open, hold shift then right click and "open a command window here"
7. type fastboot getvar all
this should give you a long list of variables, copy past them to a notepad file for future reference (saved my butt more than once)
with these variables you should be able to search the forums for the necessary recovery tools and versions that you require
Now go ahead and decide if you want to unlock the bootloader (allows you to use fastboot to push files to the phone manually) and get root access (for example, by pushing SuperSu files to the phone manually), or whatever.
CaptainPrice said:
Hey everyone!
So I've browsed on XDA forums for a few weeks now whilst deciding on the perfect smartphone for me, and decided on the HTC One X.
I've powered on, created accounts and synced all accounts on my One X, but there are some problems I've been having (NOTE: I bought this phone eBay refurbished and the Vodafone intro comes up every time I reboot the phone, oh and there are two Vodafone apps already installed, which I can't delete as well).
Anyway the problem is that I've heard that Jellybean on the HTC One X is already available in most countries (especially unlocked devices), but I have updated up to Sense 4.1 so far and it says that there are no more software updates?!
I live in Australia and the phone is unlocked (from Vodafone apparently) so why no Jellybean update?
Another problem I'm having is that the device is all around too hot most of the time (not warm, but really hot), but so far I've only used it while it's charging (even if the screen is turned off the phone is still hot whilst charging). Is this normal?
I've also heard of rooting, and was wondering for the HTC One X is it really complicated? (I've jailbroken iOS devices previously).
Last of all sometimes there are some touchscreen problems (e.g. I'm tapping multitask button and I have to swipe really hard to delete an app running in the background).
Thanks guys!
So far the phone is great, beautiful design, the screen makes me drool (a bit creepy I know) and it seems like android so far is awesome!
Click to expand...
Click to collapse
There should be an update. My Vodafone HOX was updated a few weeks ago.
I also noticed my hox gets quite warm particularly when gaming or using the camera for extended periods. From what I recall heat is normal with this phone. I just a case and mostly ignored it lol.
I havent rooted my hox in a while but from memory it is very easy. The method I used last using the all in one toolkit to flash clockworkmod recovery then flash the SU.zip. The process may have changed since then, but it was quite easy.
I'm not 100% sure what you mean by swiping hard lol but I wouldnt worry about apps running in the background too much. I never clear mine and the phone runs smooth.
Hi there,
Regarding the touchscreen issues - maybe you could try recalibrating the screen? (settings - display - G-Sensor calibration). I'm not sure whether this would have any effect, but it's worth trying.
My One X also is warm after charging.
After I relocked etc. and got the JB update (then relocked and rooted), my battery life is pretty good - currently at 45% after 1 day, 13 hours using internet a lot (keeping track of the premier league transfers in the UK!), playing games, and standard, SMS/calls.
Re. the updates: did you try manually checking for updates? sometimes a couple of manual updates will make the phone see the small pre-JB update, then the big JB update follows.
As the previous post says, rooting is easy - just get the all in one kit. Once rooted, you can get rid of the Vodafone stock apps either by physically deleting them, or using a rom cleaner app (I made a backup, then moved the apps I figured I didn't want to a folder on my SD card, rebooted to check I hadn't killed my phone, then deleted them from their temporary folder. Then I got rid of the Vodafone splash screens).
I'm still pretty much a n00b though...
@sneesh
G-sensor has nothing to do with the screen.
Sent from my HTC One X using xda app-developers app
TToivanen said:
@sneesh
G-sensor has nothing to do with the screen.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Ah...I did look at it on mine and wasn't too sure...

Phone automatically goes to home screen,

I've been having an issue with my Z2 Force that I've never had with any of my other phones. For some reason, it acts like I'm hitting the home button, even when I'm not touching it. I could be using a web browser, the XBox app, or any other app and it will go back to whatever launcher I have set as default. It doesn't close the app, it just minimizes it. I've tried disabling the home button for navigating & use the touch buttons instead, and when that didn't work I tried doing a factory reset. Well, it's still doing it, and I'm to the point where I'm very tempted to try to use one of the rooting methods I was able to find online, one of which does mention the specific model of my Verizon variant (XT1789-01). I can live without root if needed, but this 'phantom home button pressing' thing is driving me nuts. Any help is appreciated, and thanks.
I have 4 Moto Z2 Force in my house, 2 of them (Android 9, Verizon version) have this same issue.
Eco0901 said:
I have 4 Moto Z2 Force in my house, 2 of them (Android 9, Verizon version) have this same issue.
Click to expand...
Click to collapse
I'm still working on getting myself to go through with trying the root method I found. I think it'd work, but my main issue would be with making sure I can find a rooted ROM for the phone. Assuming the method works and I don't bork my phone, I'd still need a different ROM to install in order to determine if it's a hardware issue or software based. By the way, on the chance you're thinking of trying to remove the screen protector, be aware it is realllllllly stuck on there. I almost pulled my screen off, but I was able to remove it & was rewarded with a bunch of left over residue.
At any rate, if I do actually get myself to do the root thing, I'll be sure to post my results here.
will4958 said:
I'm still working on getting myself to go through with trying the root method I found. I think it'd work, but my main issue would be with making sure I can find a rooted ROM for the phone. Assuming the method works and I don't bork my phone, I'd still need a different ROM to install in order to determine if it's a hardware issue or software based. By the way, on the chance you're thinking of trying to remove the screen protector, be aware it is realllllllly stuck on there. I almost pulled my screen off, but I was able to remove it & was rewarded with a bunch of left over residue.
At any rate, if I do actually get myself to do the root thing, I'll be sure to post my results here.
Click to expand...
Click to collapse
I use the ROM stock so isn't the root that cause the problem, but I hope you find the way, my only hope is on you, actually ):
Eco0901 said:
I use the ROM stock so isn't the root that cause the problem, but I hope you find the way, my only hope is on you, actually ):
Click to expand...
Click to collapse
My concern is whether the root method I found is legit or not. The only reason why I want to attempt it is because the description mentions the specific model of my phone. All variants of the Z2 Force start with XT789-, but it's the number after the '-' you have to look for, and for Verizon users is '01'. Rooting the phone will let me install a different version of Android that should help me narrow down the cause of the glitch. Since your phone is doing the same thing mine is, it's more-than-likely not due to an app, so it has to be either the OS or a hardware thing.
Maybe a downgrade to 8.0 will make it, this bug is so annoying
Eco0901 said:
Maybe a downgrade to 8.0 will make it, this bug is so annoying
Click to expand...
Click to collapse
It's possible that might work, but either way I still need to be able to root the thing and find a ROM made for the Verizon model. My phone has only been doing this for a couple weeks or so, but before that it would actually fully close certain apps (gsam Battery Monitor, RadioU, Taskbar, and some others). However, I more than less fixed that by setting the timers for those apps to 23 hrs.
How did you set the timers? That fixed the problem of minimizing the apps?
Eco0901 said:
How did you set the timers? That fixed the problem of minimizing the apps?
Click to expand...
Click to collapse
The reason why I tried setting timers on certain apps was because they were being killed automatically, this was before the 'phantom' home button thing. The following steps may/may not resolve your current issue, but you can try them if you'd like:
1. Go to Settings
2. Apps & notifications
3. Screen time
4. At the bottom, you'll see a few apps listed, and a an option to show all of your apps. Select 'Show all apps', then the app you want to set the timer for.
5. Next to each app you'll see a little hour glass. If it's empty, then there is currently not timer set. If you'd like to set a timer, tap the hour glass, then set your desired time.
Again, I did all this well before my phone started acting like I was hitting the home button in an effort to get it to stop closing my favorite apps. For the most part, it worked, but the automatic closing thing only started after the upgrade to Android 9. I did find a site where I could download a previous stock ROM, but without root it may/will re-update again. There's an app that let's you prevent updates, but the phone has to be rooted in order for the app to work. I can't really remember the name app right now, but I used to use it on my Note 4. I think there was also a way to do it through the command line in Windows (might've worked in Linux, too), or it might've been a combination of an app and the command line.
In any case, the root method I thought I'd found wasn't really all that instructive, and I need to make sure I can actually fully unlock the boot loader before attempting root. If I can't unlock it, then whatever root method I try won't stick. The auto home button thing, at least on my phone, seems to be random, though. Sometimes it'll be fairly soon after opening an app, other times the app will stay open for a good while before going back to the home screen.
Well, like I said, I have other 2 Moto Z2 Force but they are Sprint or whatever the carrier are. They don't have the phantom home button problem. But they are in Android 8. I actually don't have a problem on click the multitasking button to go back to the app but the problem is on the games and that stuff. So if I go back to Android 8 the system will update automatically to 9? I didn't know that, I thought that it was volunteer hahaha. Btw I don't even know how to downgrade since I'm not a moto user of all life. This is my first experience with a moto phone and it sucks. . Hahaha actually the home button problem happen.
Eco0901 said:
Well, like I said, I have other 2 Moto Z2 Force but they are Sprint or whatever the carrier are. They don't have the phantom home button problem. But they are in Android 8. I actually don't have a problem on click the multitasking button to go back to the app but the problem is on the games and that stuff. So if I go back to Android 8 the system will update automatically to 9? I didn't know that, I thought that it was volunteer hahaha. Btw I don't even know how to downgrade since I'm not a moto user of all life. This is my first experience with a moto phone and it sucks. . Hahaha actually the home button problem happen.
Click to expand...
Click to collapse
It may not immediately update the OS after a downgrade, but you would get a notice there's an update available, even on a rooted phone. Since root only removes the barriers that're usually there to keep the less knowledgeable from hurting their phones, you'd still get any update notices a non-rooted phone would usually get. There is an app called NoBloat Free, and with it there are two files you'd be able to block that'd keep your phone from updating when you don't want it to. I'm not sure if the app is still in the Play Store or not, but I did use it on my Note 4, and it worked pretty well.
On a side note, I've had Opera open on my phone for a while now, and so far it hasn't gone back to the home screen yet. As for the phone itself, Moto phones are pretty good phones, my Z2 Force is my fourth phone from Moto (the other three being the RAZOR smartphone, Bionic, and the original RAZOR, which I sometimes miss). For all we know, our issue could be caused by a software glitch, hence my desire to root and test a different ROM.
Do you know how to downgrade to 8.0? I'll try it, it's a good phone and I didn't pay so much por this, that's why I'm not that angry. I won't root the phone since the games I play would kick me from the game. So just for make me sure I understand, do you reestablished the phone with a computer or from the same phone?
will4958 said:
My concern is whether the root method I found is legit or not. The only reason why I want to attempt it is because the description mentions the specific model of my phone. All variants of the Z2 Force start with XT789-, but it's the number after the '-' you have to look for, and for Verizon users is '01'. Rooting the phone will let me install a different version of Android that should help me narrow down the cause of the glitch. Since your phone is doing the same thing mine is, it's more-than-likely not due to an app, so it has to be either the OS or a hardware thing.
Click to expand...
Click to collapse
My man, I found something, I think it's a Verizon app's problem, there is a post in Reddit with more people having this problem, one of them leading to the conclusion that two apps of Verizon update recently. I don't know if that work. Btw I leave the link to that post. https://www.reddit.com/r/Moto_Z/com..._source=amp&utm_medium=&utm_content=post_body
Eco0901 said:
My man, I found something, I think it's a Verizon app's problem, there is a post in Reddit with more people having this problem, one of them leading to the conclusion that two apps of Verizon update recently. I don't know if that work. Btw I leave the link to that post. https://www.reddit.com/r/Moto_Z/com..._source=amp&utm_medium=&utm_content=post_body
Click to expand...
Click to collapse
I think I may have finally given my phone the smack in the pants it needed to start behaving itself again. I followed the link you provided, and one of the comments suggested installing any updates for a couple Verizon apps and disabling them. Not sure if this would work on a non-Verizon phone or not, but I've had the XBox app open on my phone for over 20 minutes now, and so far it hasn't minimized yet. To be accurate, I even closed & reopened the app. The apps mentioned were Verizon App Manager & My Verizon Services. I was able to disable the first app, but not the second, and rebooted my phone after doing so.
If your phone isn't from Verizon, there may be a similar pair of apps you could try disabling, though I'd probably look it up first to be on the safe side.
Update: It's been almost two hours now and the app still hasn't closed. Now, to get the screen protector residue off my phone.

Categories

Resources