[Q] First time smartphone owner, noob question? - HTC One X

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...

Related

O2 Froyo 2.2 Update Today

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.

[Q] HTC Desire Z Freeze During Standby Mode

Hi,
I just got a new HTC Desire Z Bell Branded (A7275) for my AT&T service. I "debrand" it using the debrand guide. I just noticed twice yesterday that when I put it in standby mode, I try to press the power button to turn off standby mode so I can get the screen to slide down to unlock the screen for usage. Well, it did not....no matter what I do...I cannot get the screen to get unlock. The screen is black as if it isn't on. I hold the power button, still nothing. Only way is for me to pull the battery out, put it back in and power it up. Is this common? What is the problem that causes this? Any help would be nice. Thank you in advance.
have you oc your phone at all? have you flashed a kernel? custom rom? and what guide did you use?
I used this guide to debrand my phone.
have you oc your phone at all?
Not a single bit, everything is bone stock regarding CPU.
have you flashed a kernel? custom rom?
I only flashed the one from the guide.
[ROM] RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e _26.03.02.26_M
what guide did you use?
http://forum.xda-developers.com/showthread.php?t=835777
Thanks for the fast reply and help, bahmanxda.
Tbh I am not sure what is the problem I got nothing ,the only thing that I can think of is if you are already rooted and s/off do a full wipe and flash the Rom again or try different roms if u like sense try virtuous 9.0 its really good.
Sent from my HTC Vision using XDA App
There are some others with this issue. Unfortunately, the cause has not been found, or whether it is hardware or software related:
http://forum.xda-developers.com/showthread.php?t=857584&highlight=pulling+battery
I've had this crop up myself a few times. I can say this:
Several times my Desire Z has powered off and could only be powered on after pulling the battery and re-installing. It did this twice within the first few days I owned it. Then it didn't happen anymore.
Maybe a week later I tried the Godspeed kernal (1 GHz) and SetCPU. No issues for about 2 weeks.
Then I tried CPU Tuner based on claims made by some users here that it is easier on battery life. Used a screen-off profile to underclock. The phone had the power off problem, 3 times in 2 days. Every time when the screen was off. But the random poweroffs did not start immediately after installing CPU Tuner, maybe 2 days later.
I uninstalled CPU Tuner to see if it would help (and it didn't seem to be improving battery life). Went back to Set CPU (have messed around with and without screen-off profiles). Its been more than 2 weeks, and no random power-offs.
None of this is conclusive, of course. Maybe the problem in my case was CPU Tuner, or a combination of the kernal and CPU Tuner. Maybe the things I've described are complete coincidence, and its some other factor altogether. But just thought I'd throw my experiences out there. Some claim Google Maps is the problem, but I have not found this to be the case. Or possibly some issue with the battery contacts, or the battery itself. Who knows?
Same thing happens to my Bell Desire Z. Every now and then it just decides to freeze and Only solution seems to be to take out the battery and then put it back.
Very frustrating.
Thanks for the reply, everyone. Strange it has not happen for the past 2 days now. I've read the other thread and still no exact detail on the cause of this. This is not good...especially it is my first Android phone and first HTC (bought it due to their reputation of quality made phones).
It happened twice within the first week of using the phone. Decided NOT to return the phone to observe it for a full month. During that month it happened every 3-4 days, always happens when the phone is not charging, and at the hour mark. Decided enough is enough and returned for a warranty claim 2 days ago.
During the one month, I rooted the phone after 2 weeks and flashed a custom ROM, but the problem did not go away.
There're people who aren't affected by this problem though.
I've the exact same problem here. CM 6.1.1 will just randomly black screen on standby. No response to charge when plugged in. The only way to reset is to pull the battery.
I don't think it happened on stock firmware. I'm now highly debating switching ROMs. It's getting annoying to remove the back cover every time I need to do a hard reset.
I think there is a thread in regards to CM and overclocking causing a screen on issue. But I think in those cases, the phone has power (LED and front buttons light up), just the screen can't power on. But adjusting any overclocking/underclocking profiles is worth a try.
Do you have SetCPU or CPU Tuner setup, and any profiles under those, such as underclock when the screen is off? I tried CPU Tuner for a few days, due to claims by XDA users of better battery life than SetCPU. I got 3 instances in 3 days of the phone not being able to power on (had to pull battery). I un-installed CPU Tuner, switched back to SetCPU, and haven't had the power on issue crop back up for almost a month now.
Given, I had the power on issue 2 times before using CPU Tuner, so it can't be the sole culprit. My only theory is that some combination of switching the kernel and SetCPU has solved the issue. Or it has nothing to do with those at all, just a coincidence, and is something else completely. Who knows.
It happened to me many time already. I still use stock htc desire rom and never rooted..
I've had it happen about 6 times, always requiring a battery pull. Totally stock other than being unlocked, not-rooted. But it hasn't happened for the last 3 weeks or ever since I stopped using juicedefender. Coincidence?
Desire Z freezes
Hi,
I also have some random freezes of my Stock Desire Z, I didn't do a thing on software or hardware side.
I run Android 2.2.1 Build 1.72.405.2 CL296256, provider KPN (Rabo Mobiel)
I got rid of the hangs after the upgrade from 2.2.0 then after several weeks it came back, only solvable by removing the battery.
I tried to figure out what's wrong and I think I have several clues:
- mostly some time after using Google Maps
- mostly when Wifi was on (it might be that the Wifi has limited connection and it screws up the data)
- after the reset I allways have updates from Market available
I can't remeber the Memory widget I ran, which I felt was having a good influence on the hangs.
I'm not happy with this behavioure, but cannot determine if it is hardware or software, it's not helping much that the phone just stalls , a reboot is irritating but less then a complete hangup when you don't know how long it has been in that status.
P.S. I don't run juicedefender
Cheers, Edward
I have STOCK G2 ROM.
S-off, CID, unlock via http://forum.xda-developers.com/showthread.php?t=855764
NO Cputuner or SetCpu (well I uninstalled them before these problems cropped up)
Used G2 for about a month and a bit no problems. Installed launcher pro then started to experience this problem. Coincidence? Not sure. Uninstalled and it did not help. Uninstalled several more apps that I recently loaded (skype, minimalistic text, Gtab Simi clock...) didn't help.
Wiped phone, nandroid backup to original ROM, restored using TB. Worked for a few days then just started happening again.
I also was using 2 chinese batteries I bought from eBay. Not sure if this has anything to do with it either.
// Just reflashed, HTC stock battery. Froze up within an hour. Too bad I bought this off of ebay, no warranty
// Factory Reset, restored apps and data with TB, still freezing
Hi all
I'm new to this forum (sorry, a newbie about to make a whole load of gaffs, no doubt), but I am at least fairly tech-savvy. I've had HTCs for years, right from the days of the 2000 vintage Compaq Ipaq!!
My wife & I bought two Desire Zs at Christmas, and it was therefore 50:50 which box was opened by whom. It appears I picked the dud, as I'm suffering from the issue described by all you guys, and in the other thread:
http://forum.xda-developers.com/showthread.php?t=857584
For the sake of adding more evidence to this otherwise confusing issue, I thought I'd join the forum:
So:
1) The device is not modded in any way. Standard ROM from HTC, being used on the UK T-mobile network. Currently at Android 2.2.1, Kernel 2.6.32.21-g540976a, Build 1.72.405.2 CL296256 "release-keys". This was installed on Christmas day, over the air.
2) There has been no playing with processor speeds or memory management.
3) The first crash of this nature was either on Christmas Day or Boxing day (ie the day-after-christmas-in-England); can't quite remember now, but certainly after the ROM update.
4) I have had this occur irregularly, but in increasing frequency, since that date. I think I'm probably into double figures by now, but I've only started to log them recently.
5) I was starting to think that there was some correllation with GPS applications. The phone would die after using Google Earth, for example, but not immediately. It may be after two or three standby's that it would fail to respond on the fourth, for example.
6) I had a very bad day a few weekends ago where the phone died four times in a single day. I had been using geotagging-photos (in the standard HTC camera app)... plus location-based services such as Yell and Google maps.
7) I tried keeping GPS disabled, and to be fair, there was no evidence of it crashing at that point. But I use GPS too much to make this plausible for a long time.
8) I wondered if it was due to the motion of keeping my phone in my pocket, but it died over night on the bed-side table on Monday-Tuesday, where my last usage had been the Friend-Stream widget/app. GPS was on...
During all of this, my wife's phone has not shown any of these symptoms. Whilst she uses Google Maps, Google Navigator & HTC Navigator a bit, she generally keeps the GPS turned off except for specific odd occasions. Hers has not crashed in this manner...
About to contact HTC to see what their response is...
This has occurred for me regardless of app usage.
It can occur right after a fresh reboot after being fully charged.
// Wow, I was in the middle of sending a txt and it just shut off on me...
I really wish I had a warranty on this
Hey there.
I can clearly pinpoint the problem with my desire z to the GPS. In the first view weeks I used it regularly and my phone froze, but only when the gps sensor was not active anymore (and the phone had gone to standby once or more). It didn't matter which app I used. For a while now I haven't been using GPS and my phone runs smooth as hell.
@lost800: I suppose your problem has a different kind of nature.
I already contacted HTC (very good support) and they told me to send it in to repair. I need my phone for work at the moment and I haven't found time to do this.
Due to the very small amount of ppl having that problem, I suppose it's an hardware error.
Greetz
Edit: Just out of curiosity, is there any meaning to the kernel version? Or has every mobile phone the same one?
Hello all, here is my input on this problem
My DZ has started freezing while I'm doing stuff:
* playing cards
* writting an email or a text
* using xda app
* ...
I never have GPS on. The frequency has greatly accelerated in the past 2 weeks but the weirder thing is that the last 3 times I remove sdcard and then put it back in to get the phone to boot, but it does not boot... it hangs on HTC logo for a long time (I've left it there for up to 15 minutes to see...) I eventually just remove the battery and from the phone and wait before trying to put it back in and boot...
Wait times required have varried from 5 minutes to several days.
I have observed this behavior on Stock 1.34.405, Virtuous 0.9, Virtuous 1.0.0 and back on stock 1.34.405 Today. I've wiped, flashed stock RUU nothing has helped. This puppy is going back for repair/exchange (it is 3 months old).
dwardo said:
Hello all, here is my input on this problem
My DZ has started freezing while I'm doing stuff:
* playing cards
* writting an email or a text
* using xda app
* ...
I never have GPS on. The frequency has greatly accelerated in the past 2 weeks but the weirder thing is that the last 3 times I remove sdcard and then put it back in to get the phone to boot, but it does not boot... it hangs on HTC logo for a long time (I've left it there for up to 15 minutes to see...) I eventually just remove the battery and from the phone and wait before trying to put it back in and boot...
Wait times required have varried from 5 minutes to several days.
I have observed this behavior on Stock 1.34.405, Virtuous 0.9, Virtuous 1.0.0 and back on stock 1.34.405 Today. I've wiped, flashed stock RUU nothing has helped. This puppy is going back for repair/exchange (it is 3 months old).
Click to expand...
Click to collapse
I called HTC support to see about getting the phone replaced. After explaining to the guy that it was freezing and then not rebooting when I pulled the battery out, the first thing he said was: "Did you install apps from the market ?"
Given that I replied by the affirmative he wanted me to test rebooting in safe mode and seeing if the freezes still occured before moving on to a replacement. He claimed that some market apps are not "properly coded and can mess up the phone"
I asked for and got the instructions how to reboot into "safe mode" (hit keyboard S key at HTC logo and stay on it while it boots)
In "safe mode" you can still install apps but they won't appear in the app drawer so you won't be able to start them (you can start them if they are on your home pages though ). No backgroud apps will run though (bbc, task killer ...)
Well I ran in safemode for 6 days and used the phone as I always do (work email, leisure email, web, video, camera, games, GPS, bluetooth etc...) and the darned thing ran perfectly. No freeze during those 6 days (the last few times it took less than 2 days to get a freeze).
I therefore decided it was time to test it again in "normal mode". Before rebooting I removed my task killer as for me this was "THE APP" that "safe mode" was really blocking from running on my phone...
Well It has been 2 days now and still no freeze. If it stays that way for another week I think I will have a rather good idea of who was the culprit...
Will keep you all updated and keep my fingers crossed.
Hi guys
An update:
HTC over the web-support were very helpful. Immediately they suggested that the device needed to be taken in for repair. In subsequent stages of the dialogue, they stated that the mainboard would be replaced.
A couple of weeks ago, I cleared down my device, packaged it up and waved goodbye to it (sniff...). HTC took it and...
!!DID NOTHING!!
It came back on Monday with an *old* ROM installed (1.35... If I remember correctly), and a statement saying 'no fault found'.
I've built the phone back up to where it used to be, including installing the over-the-air update to 1.72.405.2 (I need this as there's an activesync exchange bug in the old ROM) and within 24 hours, the device was unresponsive again
I have just written back to HTC to find out what the next steps are. I'd be interested to see if they suggest some debugging actions, like the safe-mode option, for example.
I've also asked them directly if their engineers have any clue what is causing this? Fundamentally, I don't see how any app should have the power to kill the device, however badly written it might be. That suggests insufficient controls/barriers in the OS.
Throughout this period, my wife's phone has continued to operate perfectly, even with some extra GPS playing to try to force a failure. So, we are now looking for any differences that could help to pin this down further. One difference is that she has never enabled the HTCSENSE.COM account on her phone, whereas I had. Perhaps there's some problem with the Phone Location functionality (in addition to the fact that I have to be in a yacht off the West coast of Africa for it to accurately show the phone's location). To test this, I've removed my HTCSENSE.COM account this morning.
Dwardo: I think your issue is slightly different, but the safe-mode info is useful.
Thanks
Andy

[Q] Switch-off bug? - (for those, who are planning to install stock gingerbread)

Hi guys!
I wanted to share a quite annoying thing I've noticed since installing the new stock gingerbread.
In short: my phone cannot be turned off. In addition it took me about a week to find it out properly, because it acts like switching off. There are two strange things: 1. it seems quite fast when switching on (it is actually, but it is more like returning from sg. like sllep/stand-by mode), 2. my battery was drained during the nights.
Now I have to enter boot menu, and select power off there.
I tried to search forums (this one and from other sites as well) but I couldn't find anybody else who experienced the same. So be aware of this new software, particularly because your phone cannot be downgraded or rooted yet (I hope someone finds a solution for this too).
Any ideas?
Thanks.
I think it's to do with Fast boot. You could turn it off and try.
Settings/ Applications and it's at the bottom.
Thanks a lot, I tried and it solved my problem immediately.
Actually it is quite embarassing, because it was only one single click. I couldn't remember of this fast boot option from FroYo, now my phone is usable again.
Thank once more!
Lol, that's the fastboot feature, which can be turned off.
Sent from my customized HTC Desire using TTP

[Q] Safe Mode / Optical Trackpad Issue

hi, very new to all this, never had a "Smartphone" of any type, Anyway, I was given a dead Desire to play with, it would not charge, so I got it going by putting 9V across the battery for 30 seconds to kick start, then it charged nicely. But it kept crashing on loading the standard O2 firmware. When it did load the volume down seem to be stuck (it wasn't it seems though). So I rooted it for flashing.
Anyway, tried a few ROMs (BeanStalk 4.4.255, MildWild 8.0JG, MIUI XJ 2.3.7, OxyZM 1.2) - all load but always the Desire runs in Safe Mode. This is shown by the words "Safe Mode" in the bottom left of the screen and a failure to run any downloaded Apps.
Other ROMs (BCM-RC4.1U2 and Carbon KK Unofficial 20140430) run without Safe Mode and only minor glitches (most prominant seems to be an inability to enter 'standby').
Anyway, I'm trying to figure this all out. I now know the Optical Trackpad does not 'track' (ie does not react to swipes). Took me a while to figure as I had no idea what it is supposed to do. It does react to pushing (as some type of 'OK' button).
So, having read loads on the web it seems a failure in the Optical Trackpad makes the Desire run in Safe Mode. Likewise its failure seemed to interfere with the volume down in the original O2 firmware. The failure does not seem to be a problem newer Android versions (I think the BCM and Carbon ROMs use newer versions).
Anyway, anyone got any experience, ideas or suggestions. The phone is a great toy and I love a challenge, been good fun getting this far on a "dead phone". Really impressed with the screen, given I had never used a Smartphone before.
Anyone got an idea why earlier versions of Android cause the HTC Desire (with non-working optical trackpad) to go into safety mode, but later versions (v4 ish) do not? All for interest really, it is working pretty much 95% on 4.0.4 (Nikez Lente). Just minor issues on sleep and occasional volume changes - use "Black Screensaver" and that really helps conserve battery.

[Q] Sim Free and need to root

Hi XDA-Peeps,
Just to give you a bit of background, i'm an ex apple i phone user, so i had never had the freedom of what Android can give you on a device. I live in the UK and bought the LG G3 sim free last month, and for the first few weeks i have been impressed, simply because on iOS i feel like your hands are tied.
However, after the honeymoon period was over i started noticing really bad issues with the phone, which in my eyes, genuinely takes away the every day use of some of the best features of the phone.
First of all i would like to mention that this LG G3 was purchased as a UK Sim Free Unlocked phone with the following build
Model: LG-D855
Software: 4.4.2
BaseBand: MPSS.DI.2.0.1.c1.13-00009-M8974AAAAAANPZM-1.01701338.5067.1
Kernal: 3.4.0
Build: KVT49L.A1412000029
Software: V10l-EUR-XX
Issues i've found so far.
1) the phone is so slow and laggy its painful, i've only got LG and Google software and maybe about 5 other apps, nothing to warrent this sort of speed, i've even restored and booted in safe mode to no avail. the graphics are laggy, the animations are sluggish and the screen refresh rate is slow, my sons iPod Touch games make this thing look silly.
2) The stock camera is not performing as it should because when i take a picture the lag means the subject has moved of i've missed the moment as the software takes ages to load.
3) the stock video camera is misleading as it built into the Camera viewfinder, but the minute you press record, the light from the sensor drops and you are left with a very low light unnatural video, then you press stop, and the sensor apply's the ISO settings and you have a well lit viewfinder again.
there are other things which i can live with but i wanted to shout about the top three...I have seen this phone working at its full potential wow!, thats what made me buy it. LG have said "update the software" which i have according to their software center, but has not done anything noticeable.
before i restored the phone to factory i did try a few setting in the engineer menu to do with temp sensors and animation settings and also enabled ARM which made it worse.
I know a hell of a lot of people have rooted their way out of these issues to make the phone perform at its full potential, and thats what i want to do, but i'm limited as i do not have a PC or Laptop. I've looked into STUMP ROOT but i get an error saying "Deviced Patched" or something like that.
i have found fixes for the camera issues as well but they all require rooting..
can anyone help, i do love this phone but these three things are making it painful.
Without access to a pc or laptop, you will find it hard.
You could use PurpleDrake to root (in the Development section). Or you could flash a .KDZ file in order to be using a firmware which you can root using STUMP or PurpleDrake.
Without such access, you have a problem.
Not much to say. You have somehow get in possession of PC. When you get, root the phone. Use Purple Drake method, you need one minute to do it.
DelBoy said:
Not much to say. You have somehow get in possession of PC. When you get, root the phone. Use Purple Drake method, you need one minute to do it.
Click to expand...
Click to collapse
Great news, so i only need a machine for short time, nothing i have to keep going back to.
So i gather on this forum we have many tutorials for rooting / purple drake.
is there a way to get this to Lollipop in these routes, because i imagine that LG will just GUI the thing up and it will not be as fluid as stock, which is ultimately what i'm after
Lollipop cant be rooted at the moment. If you want Lollipop ROM you will have to flash some prerooted ROM.
All links can be found in link n my signature (FAQ).

Categories

Resources