Database Info

TouchFlo Crashing

Hi
Only had my Orbit 2 for a few days and already there are quite a few problems with it...most of which got resolved so not too bothered there
However there is one problem that I cant fix. Sometimes when I bring up the TouchFLO it will crash on the screen with the radio, copilot, alarm, etc. The text under the icons does not load and the only way to get out of it is by pressing the end call key.
Soft reset doesnt solve the problem, it did once but only temporarily.
Hard reset has solved it (don't know if the problem will come again), wouldn't mind too much about that except I did a hard reset about 2 days ago for another reason so it is clear the device is just screwing up somehow. I barely installed much software on it.
So i've only hard resetted once to see if I can solve the problem and so far its worked. Hope its not temporary.
If anyone could help me I'd be grateful
(P.S. The button with the end call key and 'OK' is a bit loose, I can jiggle it about slightly left and right...)
Never had this many problems with my Artemis and for a device worth over £300 (over $600) I really think this is unacceptable. First the drivers, and now small problems which screw up the device totally. HTC are messing up big time and I think with all their negative feedback O2 might just cut down on buying their products.

The only time I've ever had Touch Flo, well, the Touch Cube crash was due to my installing City Time Alarms. After uninstalling, everything went back to normal. Maybe a specific app was causing your woes?

I installed an old version of SKTools and did a registry cleanup, maybe that had something to do with it... It did delete a whole lot of stuff..
I remember the problem only occured after I installed SKtools. I did do a hard reset earlier today and that was because the device became slow.. but nothing to do with TouchFlo.
Anyway I have hard reset the device now so I should not be getting any more problems from it..
But I am getting worried about the deivce though, there are so many bugs with it! Like today when the alarm went off to wake me up, the GPRS was turned on for about 56 minutes and I was definately asleep so I couldn't have turned it on!
I am scared to install a program on it incase that likes to mess up my device!
Also, is it normal for the right buttons (end call/OK) to be a BIT wonky? Like you can move it a bit from left to right? They work perfectly fine and I doubt they will suddenly detach or something! If you shake the device you CANNOT hear the slighlty wonky keys or anything, but just got a bit worried cos the other keys opposite it (pickup/windows) is not wonky at all...
This device is not worth £300
At most I would say it is worth £250
It is just so full of bugs and I have never had these kinds of problems with the other 4 PDAs that I have owned in the past. The more higher tech you go, the more unreliable the device becomes. My XDA II which I owned about 2 years ago was the most reliable I've ever had. HTC are really screwing it up and I think they are more interested in their money than their customers. I hope they screw up big time and I mean big time. If it wasn't for XDA-Developers they would have been out of business a long, looong time ago.

With regards to HTC, they didn't screw up. Sounds to me, just like anything you buy, you got a lemon. I would exchange it for another unit, not only for the system instability but also the "defective" (loose) button.

I bought the item off eBay so I cannot return it
The button is fine though, its nothing major it only moves ever so slightly and I dont think theres any problem with it. It works perfectly fine, I shouldn't really have mentioned it in the first place!
The system instability is normal though I am sure, look at what other problems people are having with their devices that get resolved every day.
O2/HTC doesnt expect lots of users to install custom ROMS (well I haven't) or edit the registry so the devices will be more user friendly and if you play about with that it can screw up.
I thought the device is kinda bad but I guess i'm happy with it, If I just use it normally and stop trying new things out on it and stop using programs like SK tools (lol) then I'll be fine. And if I have any small problems I am sure they can get resolved on here.
Anyways I am only 15 so I am going to be happy with what i've got lol!

prank1 said:
Hi
Only had my Orbit 2 for a few days and already there are quite a few problems with it...most of which got resolved so not too bothered there
However there is one problem that I cant fix. Sometimes when I bring up the TouchFLO it will crash on the screen with the radio, copilot, alarm, etc. The text under the icons does not load and the only way to get out of it is by pressing the end call key.
Soft reset doesnt solve the problem, it did once but only temporarily.
Hard reset has solved it (don't know if the problem will come again), wouldn't mind too much about that except I did a hard reset about 2 days ago for another reason so it is clear the device is just screwing up somehow. I barely installed much software on it.
So i've only hard resetted once to see if I can solve the problem and so far its worked. Hope its not temporary.
If anyone could help me I'd be grateful
(P.S. The button with the end call key and 'OK' is a bit loose, I can jiggle it about slightly left and right...)
Never had this many problems with my Artemis and for a device worth over £300 (over $600) I really think this is unacceptable. First the drivers, and now small problems which screw up the device totally. HTC are messing up big time and I think with all their negative feedback O2 might just cut down on buying their products.
Click to expand...
Click to collapse
I had the same problem. You actually have to let it sit for about 10 mins and it will load. If you close it, it might freeze for another 10 mins. After some time, the problem went away for reasons I cannot explain. Then, every time I select a button on the cube, the cube closes and I have to reopen it every time I want to use it.
Also, the bugs related with the "Word Completion" option, which does not function correctly, gave me a miserable experience with writing and typing. It slowed my writing and typing because I constantly have to correct bad guesses. I cannot turn it off either because the "Word Completion" option does not work. Sure I could go into the registry and mitigate the problem, but I returned it as a manufacturer defect.
I assume it will go back to HTC and I hope it will result in a response to fix the problems. For >$800 after tax, I would expect the purchase to function correctly.

Hi
Yes the word completion is annoying, I can't turn it off either. It is annoying when you write smaller words such as 'sed' as opposed to 'said', the word completion decides to change it.. It is really annoying especially when you have to type on the move. Not to mention it uses up a whole lot of characters when you try to said a text message. It is much easier and quicker to write 'thru', it uses only 4 characters whereas the proper spelling of the word 'through' uses up 7 - nearly double. With a limit of 160 characters per message you will find that you will quickly reach that limit. I have quite a lot of free texts so I do not mind much but I hate it when it puts the incorrect word in the place!
Also with your TouchFLO problem, did you try hard resetting the device? I found that if you play about with the registry the phone quickly messes up. That is understandable but harmless registry modifications such as the 'ShowSIM' can even screw up your phone!
If a problem appears on my device can I give it to O2 to repair for a fee -- I do not have a warentee so if they agree to fix it for a fee only then that seems fair.

prank1 said:
I installed an old version of SKTools and did a registry cleanup, maybe that had something to do with it... It did delete a whole lot of stuff..
I remember the problem only occured after I installed SKtools.
Click to expand...
Click to collapse
prank1 said:
Hi
I found that if you play about with the registry the phone quickly messes up. That is understandable but harmless registry modifications such as the 'ShowSIM' can even screw up your phone!
Click to expand...
Click to collapse
Maybe its just me, but while programs like sktools can simplify your life, I really hate the idea of a non-device specific program tweaking my registry. I like to do it myself so that I know exactly what goes in, and I can assess exactly what comes out. FYI: I've never had a crash due to registry mods (but in my early days (pre-Touch Cruise) of installing random cabs and fixes I did get crashes).

prank1 said:
...Also with your TouchFLO problem, did you try hard resetting the device?
Click to expand...
Click to collapse
Just soft resets. I didn't want to wait 10+ hours to resync my emails, contacts, etc after a hard reset.

Questions

So I got my XT720 a few days ago and am loving it. Two things though:
1) I've had to do a quick reset (take out battery) about 4-5 times in the same amount of days. What happens is sometimes the screen will go blank (or when I press the on button all that will happen is the 4 buttons at bottom of phone will light up). Screen/phone becomes unresponsive and only way to get back to normal is to take out battery. I'm pretty sure that every time this has happened has been right (or shortly) after me downloading something on my phone (i.e. putting on a new wallpaper, or a song). Anyone have this happen to them?
2) I don't want to root or put on Dexter's ROM just yet. The reason for this is because a) I just got my phone and I don't want to void the warranty until I know everything works with no issues b) I'd rather wait for the complete/fully polished version of the ROM - I'm in no hurry right now, this phone is a big big upgrade from my previous phone even without 2.2.
Anyways, the point is, I'm pretty sure my phone isn't running with the 720MHz update right now and is running at 550. I want to put on that update to make my phone faster while I wait to root. However, whenever I go to - about phone - check for system updates - and click on that, it always tells me "Server unavailable. Try again later.". Been trying for the past few days and no luck. How can I get the 720MHz update (without rooting - at this point)?
Thanks

If the screen doesn't come on when you turn on the phone, you may have a defective one. My first XT720 was a dud right out of the box. I had to take it back to the Cincinnati Bell store and get it exchanged. I've heard of other people having similar experiences with the phone not turning on. Take it back. If they give you any crap about it, just tell them that the Motorola tech from their forums told you to take it back. This adds a bit of validity to the problem and may make it an easier transaction.

Nah, it works fine for the most part. Turns on and off and runs just fine normally. But my issue is I've just had it basically freeze up 4-5 times in the past week (noticing a possible connection to me downloading things).

I would think your phone is running at 720mhz. I believe the European / Asian versions were originally 550mhz & had an ota udate to the 720 level. You could download Android System Info or Elixer to check it out though.
I would also agree with reverendkjr, it the phone is acting funky take it back & get a replacement.

The XT720 from Wind is 720mhz with stock firmware, the only 550mhz was Korean version AFAIK, maybe some Euro versions.
As for the screen, you may want to try doing a factory reset on your phone. If it persists after that take it back to Wind for a replacement, had my wife's XT720 replaced due to a microphone problem.

R-D said:
The XT720 from Wind is 720mhz with stock firmware, the only 550mhz was Korean version AFAIK, maybe some Euro versions.
Click to expand...
Click to collapse
Oh? I figured it might be at 550 since going back to homescreen - it reloads pretty often (thought 720 wouldn't do that), though it does run snappy enough in all other areas.
As for the screen, you may want to try doing a factory reset on your phone. If it persists after that take it back to Wind for a replacement, had my wife's XT720 replaced due to a microphone problem.
Click to expand...
Click to collapse
Be a bit of a pain to factory reset at this point. The problem isn't terribly disruptive at this point. Doesn't happen often enough to really bother me and restarting is quick. If it does continue and become frustrating I may consider factory reset. I just was wondering if anyone else experienced this.
WIND would give me a replacement at any time (within the year) if I told them about this issue? (Kind of hard to prove since it happens at it's own whim. Don't want to seek a replacement just yet anyways - not unless it continues and is an annoyance)

Just put a call into support so they have a record of the problems, explain to them you cant reproduce the problem, but it is a brand new phone and should not be doing this regardless.
They will suggest the reset to see if the issue persists, but you can decline at this time and at least get the issue logged so you have a better chance of replacement in the future.
Keep in mind though, within 14 days they will replace with a new phone, beyond that you may get a used one.

I can't imagine just ignoring a problem with a new phone like that. Especially since you have the ability to have it replaced for free.
Heck, I took a phone back once because it had ONE dead pixel on the screen. When the girl looked at me and said "Really?" I said "Hell yes, I just bought this damn thing and I want it to be PERFECT!"

you need to setup the APN to connect to 3G to get your 720 upgrade from OTA (if purchased unlocked Euro or Asia models)
if it's a Wind XT720 it should already be on 720

reverendkjr said:
I can't imagine just ignoring a problem with a new phone like that. Especially since you have the ability to have it replaced for free.
Heck, I took a phone back once because it had ONE dead pixel on the screen. When the girl looked at me and said "Really?" I said "Hell yes, I just bought this damn thing and I want it to be PERFECT!"
Click to expand...
Click to collapse
Yeah, I suppose that's true. If it happens again I'll look into getting it replaced.
Thanks for the help guys.

my XT711 has done the "blank screen a few times also and I have to remove the battery to reset it. Very strange thing, but I have had the phone for only a few days so im gonna see what its gonna do first cause sending it back to china is a pain in th butt.

[Q] Random Freezing. HELP! Advice Needed

Hello All,
I am new to this forum. I bought my sensation about two weeks ago. When I was getting into my car one day, the phone slipped out of my shorts and fell, with the screen hitting the concrete. The screen and everything was intact, the phone was only lightly scratched.
Recently, however, my sensation has occasionally been freezing. Its strange because it does not occur in an app. It only occurs when I am scrolling through the homepages or going through the full list of apps. It usually begins working again by itself after about a minute or so. I have done a factory reset, and this problem has reoccurred, just once. The issue only occurs maybe once every few days and isnt that big of a problem. I just have a few questions.
Is this problem most likely software related? Im not sure if it only started happening after I dropped the phone, but it seems to me like this is software related?
Is there anything I can do to fix it? Will the OTA update (if tmobile does it) fix the problem?
Finally, what I am most worried about: is there any possibility (or is it likely) that my phone's condition might worsen later on down the road???
I would like to hear any advice you guys have. Is there anything other than a reset that might be able to fix the problem?

abdelraziq93 said:
Hello All,
I am new to this forum. I bought my sensation about two weeks ago. When I was getting into my car one day, the phone slipped out of my shorts and fell, with the screen hitting the concrete. The screen and everything was intact, the phone was only lightly scratched.
Recently, however, my sensation has occasionally been freezing. Its strange because it does not occur in an app. It only occurs when I am scrolling through the homepages or going through the full list of apps. It usually begins working again by itself after about a minute or so. I have done a factory reset, and this problem has reoccurred, just once. The issue only occurs maybe once every few days and isnt that big of a problem. I just have a few questions.
Is this problem most likely software related? Im not sure if it only started happening after I dropped the phone, but it seems to me like this is software related?
Is there anything I can do to fix it? Will the OTA update (if tmobile does it) fix the problem?
Finally, what I am most worried about: is there any possibility (or is it likely) that my phone's condition might worsen later on down the road???
I would like to hear any advice you guys have. Is there anything other than a reset that might be able to fix the problem?
Click to expand...
Click to collapse
I believe it's the software (sense 3.0) Try changing your home screen. I don't get issues like this since I've changed my homescreen. Try Launcherpro or Go Launcher

do you think that dropping my phone has anything to do with it? Also, do you think it might get worse over time?
Thanks

I dont think it has to do with ur phone dropping...
The random freezes/ force closes/ re-boots seem to be a problem.. wait for the s-off and then some solid custom roms Should fix it all..

abdelraziq93 said:
do you think that dropping my phone has anything to do with it? Also, do you think it might get worse over time?
Thanks
Click to expand...
Click to collapse
I use to think that that's a problem with phones.. but I don't think it actually does has anything to do with the phone acting up, unless it was dropped in a pool.. but otherwise, it's just the software.. sense 3.0 seems really buggy on mines.

Screen Flickering

I've read a few threads on the screen Flickering and there doesn't seem to be any resolution .
I'm on my 3rd tablet now (thanks best buy accident damage warranty!) And this one is flickering worse lately than ever. I updated to the latest firmware, yesterday only to boot up to horrible bouts of flickering during the setup screens.
The odd thing is, there seem to be no consistency to it. Some days it's so had I can't even use the thing, other days it doesn't happen at all. I use the tablet every day for notes or PDF viewing. I've used it with no magnetic cover (totally naked) and with the cover.. doesn't seem to change the occurrences.
I've turned overlays on/off force gpu render on/off.. nothing seems to fix it. Sometimes changing the overlay will reduce the flickering other times it doesn't affect it at all.
I hate to say it, but if I can't resolve it, I'm going to be forced to move to the surface 3.
I'm an electrical engineer and I've done as much trouble shooting as I can think to do.. but I've come up empty handed.
Anyone else have these problems? Has anyone found a definitive fix?

I sent mine back 3 times. The first was a reset. Thanks for wasting my time. The second was a motherboard and that didn’t do it. The third time they did a motherboard, digitizer, and usb port. It's finally stable and back to normal. After 5 trips back, the BB warranty triggers a new unit. Check if it triggers a refund.

I get it occasionally, so far I'm able to resolve it by booting into custom recovery (TWRP) and clearing dalvic to allow all apps to rebuild. Sometimes this resolves it for a few days, sometimes a couple of weeks. Its a repeatable "fix" that makes me question if the issue is related to memory or trim or something like that. Kind of reminds me of how with the first generation nexus 7s one would see slow downs after a while and filing storage with fake data then deleting it would improve performance for a while.

I'm definitely not a tender user of the device. I go back and forth between multiple ROM's and kernels on a daily basis testing what is testable, and unfortunately also what is not. Anyway, even though mine was bought as refurbished on eBay, I have never had any issues like the ones you describe. More specifically, I have never had any issues what-so-ever, that was not created due to my own ignorance. To me the device seems indestructible.
Besides, I would hate to be in the place of my device, or I would definitely have turned schizophrenic. Should I feel bad about pushing it through all this?

Because we're trying to figure out if it's related to a specific device type, which one do you have? P900, 905, 907A or another?

ShadowLea said:
Because we're trying to figure out if it's related to a specific device type, which one do you have? P900, 905, 907A or another?
Click to expand...
Click to collapse
P900 wifi. Us version bought at best buy.
Today the tablet has been rock solid, I have literally done nothing between when it was flickering like mad and now.
I wonder if it might be related to some kid of data transfer. either over wifi, or when data is written or read from storage or SD card. I've take then SD card out to eliminate that as the problem.

Mine was P900 from BB

Issue lies with the screen.
This happened with me I sent it back to Samsung, 3 times. They seem to have finally got it right. They replaced the battery and then the display screen. Now it appears to be working I will let you know after a month if it is still good. They also told me that they will not replace the device even though I bought it and the issue was right from the start. Not even 6 months old. When working the device is excellent.

Ah, so now we know for sure the battery is replaceable. That's good news. Maybe someday our batteries will no longer hold a charge and we can replace it. Now for a good video on tear down and what tools to use to do that and where to get a replacement battery. I know it's early for most of us but someday......we will have to replace that battery. I'm one of those that keep my toys (computers/laptops/tablets/phones,) for many years.

Mine is running like new since last service. Getting the BB Geek Squad warranty has paid for itself already. I get 2 years on anything over $500.

Mine is a p900. I purchased from samsung website. Mine has been doing it fresh out of box. So bummed.

Ive had my 12.2 since march and it recently started flickering. It seems to tuen of the screen for a millisecond especially when lots of refreshes happen. Like scrolling a pdf. A few days back it was bad. Now it has gotten better and I havent noticed anything.

{Diemex} said:
Ive had my 12.2 since march and it recently started flickering. It seems to tuen of the screen for a millisecond especially when lots of refreshes happen. Like scrolling a pdf. A few days back it was bad. Now it has gotten better and I havent noticed anything.
Click to expand...
Click to collapse
My P900 has just begun flickering exactly as you describe. So I should just be patient and hope it goes away by itself?

I'm flickering again. Turning the screen brighter is what triggers it for me. Returning to stock just to get it back and have it flicker again to hit the magic 5 returns may be what I have to do.

https://youtu.be/CvxbVft69Kg
I just followed this guide. Its been a week now, not had any flickering since I did it.

Manya3084 said:
I just followed this guide. Its been a week now, not had any flickering since I did it.
Click to expand...
Click to collapse
Lifting the motherboard only temporary close the gaps of cracked battery connector. The permanent fix need to do: re solder the battery connector.
Look closely under magnified glass or microscope , you'll see the cracked solders. You can test by pushing the connector slightly, a bad one will move easily or lift off from its solder joints.
This video was removed from the poster after I pointed out his guessing solution. Flickering screen has nothing to do with LCD connector on the motherboard.
Lifting mother board actually you're applying pressure on the battery connector from rear cover.

I have had my P900 sent to Samsung service twice without having the screen flicker fixed. I thought this was a known problem and that Samsung themselves should be aware of it? Maybe I should supply some XDA links next time...
Skickat från min SM-P900 via Tapatalk

bluebirch said:
I have had my P900 sent to Samsung service twice without having the screen flicker fixed. I thought this was a known problem and that Samsung themselves should be aware of it? Maybe I should supply some XDA links next time...
Skickat från min SM-P900 via Tapatalk
Click to expand...
Click to collapse
Depend on where you send for service, they know how to fix it now. Service Centers actually are contractors provide services for Samsung and others, the fact that most people don't know.
http://forum.xda-developers.com/showpost.php?p=59573206&postcount=100
It Works. Battery connector replaced. Smoooooth
After 2 visits to Samsung , my unit finally works fine.
Motherboard and LCD were changed first time. But issue persisted.
Second time, battery connector was replaced. Since then it has worked very very smoothly.

Beut said:
Depend on where you send for service, they know how to fix it now. Service Centers actually are contractors provide services for Samsung and others, the fact that most people don't know.
http://forum.xda-developers.com/showpost.php?p=59573206&postcount=100
It Works. Battery connector replaced. Smoooooth
After 2 visits to Samsung , my unit finally works fine.
Motherboard and LCD were changed first time. But issue persisted.
Second time, battery connector was replaced. Since then it has worked very very smoothly.
Click to expand...
Click to collapse
Thanks, missed that other thread. Next time, I'll send them an en explicit request to replace the battery comnector, and refer to those two threads.
Stefan
Tapatalked on some kind of Samsung tablet

Nexus 5, Experiencing Random Reboots across ROMS. Last_KMSG Will donate $5 to EFF

Hey everyone! My Nexus 5 is experiencing random reboots and does so regardless of which rom I have installed. I started by pulling logcats and didn't find anything interesting (not an expert though), so I moved on to pulling the last_kmsg and saving it to a txt file. It says the reason for the last reboot was "kernel panic," but I assume there is more to it. There has to be a message in there explaining what caused it, but to be honest, I'm not really knowledgeable enough to pull it out of what looks like 50% gibberish to me.
http://pastebin.com/315jSBZt
I would be more than happy to provide needed logs or run tests, just let me know what you need. If someone can give me a good answer that is corroborated by someone else in the community, I'll make a $5 donation to the EFF in your honor.

Possible power button issue?

audit13 said:
Possible power button issue?
Click to expand...
Click to collapse
Unlikely. Power button feels good and this phone hasn't really even been used very much. If it's a hardware issue, I think we'll find a clue in the logs. Kernels shouldn't just panic of their own accord, right?

I looked at the log you posted and I do see a kernel panic on the last line.
Does this happen with a stock ROM too?

audit13 said:
I looked at the log you posted and I do see a kernel panic on the last line.
Does this happen with a stock ROM too?
Click to expand...
Click to collapse
Yes, I've experienced this problem on the stock ROM, Cataclysm, and Chroma (what I'm using now).
Some observations that might help:
- Sometimes it reboots more frequently than others. I've had it reboot several times within 10 min. I've also say in front of my computer with logcat running, purposefully trying to make it crash, and for 30min. it didn't do anything. (I got it to eventually, but didn't find anything useful)
- I recently reflashed everything to stock including the bootloader and recovery to see if it would help. I also updated the radio to see if that would do anything.
- It boots up fairly quickly. There are no real performance issues while using the phone
- Before it crashes, it freezes for a few seconds with whatever is on the screen. You can't use any of the buttons or do anything.
- It does not require screen-on or user interaction to prompt a reboot. I've had it reboot while sleeping before and I can hear it vibrate when it hits the "google" screen.
Is there any way to identify the cause of a kernel panic? I assume that the kernel logs what it does or what it's trying to do somewhere. I'd love to be able to pull some intel out of the logs to figure out exactly what's causing it. Any other logs I should be pulling?

Sorry, this is way beyond my analytical skills. You've gone a lot further than I would.
Could the reboots be an indication that the on-board memory is starting to fail? I'm not sure.

audit13 said:
Sorry, this is way beyond my analytical skills. You've gone a lot further than I would.
Could the reboots be an indication that the on-board memory is starting to fail? I'm not sure.
Click to expand...
Click to collapse
Good call. That was one of my possible guesses too. I keep looking for evidence of that in the logs, it's gotta leave a trace somewhere! The phone is "certified refurbished" one that I bought off Amazon fairly cheap ($160-180ish). I think I'm just going to flash it back to stock and return it. Not sure what I want to get as a replacement. I might be able to beat my old Moto G (original) back into submission and use it for a while. It had some problems too, and it was worse when it comes to specs, but it was a really well thought out put together device. Never noticed the little things mattered so much until I bought my Nexus 5. I love it, don't get me wrong, but the positioning of the speaker, the slow-focusing camera, and a few other things keep it from hitting 100% for me. It's odd that two phones from the same manufacturer could be so different feeling when it comes to polish. Maybe I should buy a Moto X just so I can experience them all!

I used to have a Moto g as well. It as a great phone until I damaged the sim reader.
Although Google used to own Motorola, the nexus was made by LG which probably explains the different approaches to building a phone.
I'm okay with my lg which is a frankenphone that I clobbered together using spare parts I salvaged from cheap used nexus 5 phones I bought over a period of a few weeks.