Related
I have a weird issue with my TP2.
When i reset it... it boots up and i can see the HTC logo but tf3d won't start.. i went into settings unchecked tf3d and reticked it.. no difference!
How is the executable called? anyone elese experiencing this issue?
Known problem.
The best workaround I found till now:
1. Switch on Flightmode. (use the red phone button press for more than 3 seconds)
2 Reset/Restart
3. Switch off flightmode. The PIN screen comes up automatically.
Works in 100% of the cases.
Huib
You can run the manila.exe found in the Windows folder but I've found that when doing this, the clock on the home tab doesn't refresh/change and the notification balloons don't come up (the little round icon on the sms tab when you have unread sms's for example)
the workaround worked like a blast. Thanks..
I could not find that thread describing it.. i wonder why HTC did not release any hotfix for this.
How is the manila.exe started???
Hi!
I have the same issue, Touchflo3d not starting after boot on my swedish Touch Pro2.
If i try to manually start manila.exe i also get the clock freeze on the start screen and no mail/message notifications.
I've tried two hard resets, and adding programs and settings one at a time just to try to find the reason for this, but no luck. It feels like it's all random, it all works with apps installed, and suddenly it stops working, no changes made.
I notice that when i manually execute \windows\manila.exe the screen goes from the black screen with the HTC logo directly to the start screen of touchflo3d. When everything works the way it should do, there is a difference, a text appears on the black screen under the HTC logo, something like "starting Touchflo3D".
I'm not that good at windows mobile myself, but i hope someone on this forum, that has a phone with touchflo3d, can find the difference between starting the manila.exe manually, not seeing the "starting Touchflo"-test, compared to the automatic start with that text.
I hope that would lead to a solution or fix, i would not mind very much having to start touchflo myself with a click, but i'd like to start it the same way it does when working so the clock and notifications work as it should.
Let's all hope some of the many extremly skilled members here picks up the glove and takes a good look at this!!
Best regards
Cerebral Cortex
Phone screen will disapper?
herpi said:
Known problem.
The best workaround I found till now:
1. Switch on Flightmode. (use the red phone button press for more than 3 seconds)
2 Reset/Restart
3. Switch off flightmode. The PIN screen comes up automatically.
Works in 100% of the cases.
Huib
Click to expand...
Click to collapse
Thanx it worked for me!
But now TF3D will come in front when I make a call. So after 5 seconds calling the first screen of TF3D (the clock) will appear. Then I have to press the first button (phone) to get the phone screen again. Verry sad.
I also can not use the program Notes anymore when calling, the program will go to the back. And TF3D will come to the front!
Someone know the answer?
Thanx in advance,
Richard
Hi,
i had the same problem and tried many solutions until i found what was the cause for that problem: S2U2. Once i disabled the S2U2-autostart on boot up, tf3d is always starting the way its supposed to. I simply removed the ilock2-shortcut from windows/autostart and start it manually after tf3d has launched. Not really perfect, but better than everything else for me.
Do you use S2U2?
Regards
MiDiAN
MiDiANx360 said:
Hi,
i had the same problem and tried many solutions until i found what was the cause for that problem: S2U2. Once i disabled the S2U2-autostart on boot up, tf3d is always starting the way its supposed to. I simply removed the ilock2-shortcut from windows/autostart and start it manually after tf3d has launched. Not really perfect, but better than everything else for me.
Do you use S2U2?
Regards
MiDiAN
Click to expand...
Click to collapse
I did the same, disabled s2u2, and no more problems. After a while however the hanging came back randomly.
S2u2 is back now. Mothers little helper! I can live with the flightmode on and off solution.
Huib
Quote:
Originally Posted by daveke0201
have a problem with s2u2 v2.04 wvga and 3dtf. after installation it wont boot anymore.
this is what i tried.
start stop 3dtf => not starting
stop ilock2, stop start 3dtf => not starting.
does work with the 1.62.
can anyone help me?
************* reply from ac ************
Try to set a longer "Boot-up Delay" (S2U2 Settings->Advanced).
__________________
Cheers,
A_C
http://ac-s2.com
*******************************************
I've set my bootup delay in the advanced menu to 20seconds and my problem is gone.
pieterbotes said:
I've set my bootup delay in the advanced menu to 20seconds and my problem is gone.
Click to expand...
Click to collapse
Nope, 20 secs does not do the job in my case.
Tried several combinations and different ways of startup, but no deal.
I already had the problem without S2U2 so I cannot possibly blame them.
I still am stuck at the flightmode trick which gives a 100% success.
Huib
Moisture damage perhaps???
herpi said:
Known problem.
The best workaround I found till now:
1. Switch on Flightmode. (use the red phone button press for more than 3 seconds)
2 Reset/Restart
3. Switch off flightmode. The PIN screen comes up automatically.
Works in 100% of the cases.
Huib
Click to expand...
Click to collapse
I have the same issue. The first time this behavior surfaced for me was right after i´d applied Zagg´s inivisible shield.
I must admit that i lacked the patience to be leaving the phone for 12 hours drying up.
I´d put it in a dry, warm & well ventilated place for approximately 4 hours and thought that should suffice.
When the phone started acting up i used up all the non-printable 4 letter words i knew and did a hard reset.
Anyway - the problem has showed up about every third time i do a soft reset.
To me the solution has so far been another soft-reset.
Regards
Have the same problem, it's driving me nuts. Hate reseting the phone - it takes ages to boot up.
Won't spend time trying to fix this, will just not reboot/reset often. Hopefully the WM6.5/TF3D official package sometime in October will cure this.
vasra said:
Have the same problem, it's driving me nuts. Hate reseting the phone - it takes ages to boot up.
Won't spend time trying to fix this, will just not reboot/reset often. Hopefully the WM6.5/TF3D official package sometime in October will cure this.
Click to expand...
Click to collapse
I combine the flightmode trick together with the SlidetoShutdown, where I use the restart slider.
Doing it this way makes it more acceptable.
Huib
Hmm... I've had success with the 20 second thing but now that is also not working for me anymore... not sure what changed.
pieterbotes said:
Hmm... I've had success with the 20 second thing but now that is also not working for me anymore... not sure what changed.
Click to expand...
Click to collapse
It is quite random.
The flight-on/restart/flight-off always works, at least in my tp2.
Huib
so i've tried checking on/off Today/Item/TF3D, tried Flight Mode, and it still won't work. i'm talking like only 30-50% of the time it does work. and I never had PIN1 enabled!
i'm no programmer but it is conflicting with apps we install because TF3D works perfectly when the phone was fresh or hard-resetted. btw i'm using 6.1 Stock T-mobile
Hey all,
I have owned my Tilt 2 for a little over 6 months now and have seemed to have problems with it since day one. Its a little hard to describe the exact issue but I will do My Best.
First of all, I am currently Using the Latest Energy Rom for the Phone from xda developers. I have installed both hot Fixes on my Phone from HTC and I do a hard reset every time I upgrade my rom.
This is a problem I have had since getting the phone and seemed to be present in the Stock Rom that came from ATT so I am not convinced that it is a software problem, but I thought I would get some opinions here first. My Concern is that the phone itself has issues and I may be out of luck because I have had the phone and dealt with the issues for so long.
So, My Biggest problem is one with Freezing. I have to reset my phone at least 5-10 times a day. I always have. Sometimes I even have to remove the battery to get the phone to reset. I do quite a bit of Texting with my phone and the freezing almost always seems to happen after I have sent a text and am trying to get back to the Home/Today Screen. The Phone just sits there, I can hit the end call button as much as I want and it will not go back to the home screen. The Phone is not completely locked tho because most of the time the Calling features still work, and I can even hit the windows button and get into the menu where I can get to task manager or a software reset button. If I try to hit the home Icon tho nothing seems to happen. The Phone just sits there and I have to reset it to get it working again.
This is frustrating me because the phone is not actually frozen, it seem to be stuck thinking but will never come back to life. When the phone works, its works great and does everything I need it to do. The Constant freezing and resets are driving me crazy. Any help or suggestions would be appreciated. I am pretty tech savy and have been installing roms on my phones for a couple years now. Please Help before I toss this thing out the window.
Vgamer4550 said:
Hey all,
I have owned my Tilt 2 for a little over 6 months now and have seemed to have problems with it since day one. Its a little hard to describe the exact issue but I will do My Best.
First of all, I am currently Using the Latest Energy Rom for the Phone from xda developers. I have installed both hot Fixes on my Phone from HTC and I do a hard reset every time I upgrade my rom.
This is a problem I have had since getting the phone and seemed to be present in the Stock Rom that came from ATT so I am not convinced that it is a software problem, but I thought I would get some opinions here first. My Concern is that the phone itself has issues and I may be out of luck because I have had the phone and dealt with the issues for so long.
So, My Biggest problem is one with Freezing. I have to reset my phone at least 5-10 times a day. I always have. Sometimes I even have to remove the battery to get the phone to reset. I do quite a bit of Texting with my phone and the freezing almost always seems to happen after I have sent a text and am trying to get back to the Home/Today Screen. The Phone just sits there, I can hit the end call button as much as I want and it will not go back to the home screen. The Phone is not completely locked tho because most of the time the Calling features still work, and I can even hit the windows button and get into the menu where I can get to task manager or a software reset button. If I try to hit the home Icon tho nothing seems to happen. The Phone just sits there and I have to reset it to get it working again.
This is frustrating me because the phone is not actually frozen, it seem to be stuck thinking but will never come back to life. When the phone works, its works great and does everything I need it to do. The Constant freezing and resets are driving me crazy. Any help or suggestions would be appreciated. I am pretty tech savy and have been installing roms on my phones for a couple years now. Please Help before I toss this thing out the window.
Click to expand...
Click to collapse
It is usually not desired to post the same information twice on different forums. The NRG thread has some responses to THIS EXACT POST that was made there. I know that cut-n-paste is easy, but avoid the temptation.
stevedebi said:
It is usually not desired to post the same information twice on different forums. The NRG thread has some responses to THIS EXACT POST that was made there. I know that cut-n-paste is easy, but avoid the temptation.
Click to expand...
Click to collapse
Will Do, I was just not sure where this questions belonged as I am unclear as to whether this is an NRG issue or a Phone Issue.
I have not had this experience, but I have read a lot of posts in the tilt forums where people complain of slow/laggy behavior using the htc messagaing tabs... I wanted to avoid that, so I just mapped my push-to-talk button to the windows mobile messaging client and use it. You might try doing that, if the HTC is what you are using now...
Off subject (new to this) but you mention "tilt forums" How do I find these s for my tilt phone? Looking for new apps also... I'm old
Hey gents,
After some searching with no answers, I decided to ask the question myself. I apologize if this has been addressed before. I'm currently running a stock r800x with the 2.3.3 ota update. I've had the phone for about six months, but shortly after the update my leading had been acting up. It's almost impossible to send messages now. When the icon is tapped, the window opens but is completely empty for at least 40 seconds. when the keyboard is pressed, it takes another 30 seconds our so and words lag five seconds after key presses (swype and android keyboard). finally, after tapping enter, the message won't appear in the window for some time and I get the "force close or wait" option. After 2 or 3 times touching "wait" and a good 45 seconds to a minute each time, the message will send. I'm at a complete loss here, because I have plenty of space on both my phone and sd card. Does anyone know wtf is going on? Any help would be greatly appreciated and I thank you in advance.
nom nom apple said:
Hey gents,
After some searching with no answers, I decided to ask the question myself. I apologize if this has been addressed before. I'm currently running a stock r800x with the 2.3.3 ota update. I've had the phone for about six months, but shortly after the update my leading had been acting up. It's almost impossible to send messages now. When the icon is tapped, the window opens but is completely empty for at least 40 seconds. when the keyboard is pressed, it takes another 30 seconds our so and words lag five seconds after key presses (swype and android keyboard). finally, after tapping enter, the message won't appear in the window for some time and I get the "force close or wait" option. After 2 or 3 times touching "wait" and a good 45 seconds to a minute each time, the message will send. I'm at a complete loss here, because I have plenty of space on both my phone and sd card. Does anyone know wtf is going on? Any help would be greatly appreciated and I thank you in advance.
Click to expand...
Click to collapse
Do you have a lot of messages in there? The next time you go in try deleting all threads, then make sure to set you limits to 50 messages per thread and 10 MMS per thread. If you have too many messages/threads it takes a long time of the phone to load them, and unfortunately unless you set those options properly the phone has no way to communicate this other than crashing.
My settings were all good, so I decided to bump it down 20 per conversation. It may have had something to do with 58 different threads open and almost 50 messages each :/ . Turns out you even androids need some good old fashioned house keeping. A quick wipe of all threads did the trick. Thanks for helping me out
-jason
nom nom apple said:
My settings were all good, so I decided to bump it down 20 per conversation. It may have had something to do with 58 different threads open and almost 50 messages each :/ . Turns out you even androids need some good old fashioned house keeping. A quick wipe of all threads did the trick. Thanks for helping me out
-jason
Click to expand...
Click to collapse
No prob glad it worked out and that my folly (I battled with this over a week before I figured it out) can help others!
I have a problem where, I am in a conversation in Whatsapp, and i am done writing a message, and then i lock the screen, and when i unlock it maybe 15 seconds later, i type, but nothing is showing up, its just records what i press but doesn't type. I have to go the the main screen, and reopen Whatsapp to get it working again...
Anyone else notice this?
Its really annoying if you are in an intense conversation and have to act fast
ROM: Codename Android 1.5.5
Kernel: FrancoKernel Milestone 2
I have wiped everything 1000x times and reinstalled everything. Found some people who had the same issue, but no one found a solution.
Thanks XDA,
David
Dubadai said:
I have a problem where, I am in a conversation in Whatsapp, and i am done writing a message, and then i lock the screen, and when i unlock it maybe 15 seconds later, i type, but nothing is showing up, its just records what i press but doesn't type. I have to go the the main screen, and reopen Whatsapp to get it working again...
Anyone else notice this?
Its really annoying if you are in an intense conversation and have to act fast
ROM: Codename Android 1.5.5
Kernel: FrancoKernel Milestone 2
I have wiped everything 1000x times and reinstalled everything. Found some people who had the same issue, but no one found a solution.
Thanks XDA,
David
Click to expand...
Click to collapse
Happens sometimes to me too and I am rooted on stock. Pretty sure it has nothing to do with us and everything to do with whatsapp having an ICS bug.
Sent from my Galaxy Nexus using Tapatalk
Whatsapp used to have exact same problem on my Nokia 5800XM too, I think it happens because of Whatsapp.
confirmed this happening occasionally on LG optimus one.
therefore, it is definitely because of the whatsapp app itself
usually i just press back button for once, back to conversation list and go back to my conversation. typing works back so you dont need to go homescreen thats two steps back
Confirmed bug for me too
Galaxy Nexus GSM
AOKP M4
Franco M2
To everyone who replied, thank you! Makes my life easier knowing its not ROM/Kernel etc...
Filed a complain to Whatsapp, such a great app apart from this bug!
Miasmic said:
confirmed this happening occasionally on LG optimus one.
therefore, it is definitely because of the whatsapp app itself
usually i just press back button for once, back to conversation list and go back to my conversation. typing works back so you dont need to go homescreen thats two steps back
Click to expand...
Click to collapse
I usually press home button and then my Whatsapp icon on my main screen, usually goes fast, but still... rather annoying
How deep would this 'error' lie? Could devs fix it?
I get this exact same problem with Handcent! Currently using Swype, and like 30% of the time I will have to go back to the conversation list and re-select my conversation to start typing again.
Sent from my Galaxy Nexus using Tapatalk
Quick question, is everyone using NovaLauncher too? It sometimes happen with normal SMS as well. But 95% of the time it is Whatsapp
ohh3nry said:
Quick question, is everyone using NovaLauncher too? It sometimes happen with normal SMS as well. But 95% of the time it is Whatsapp
Click to expand...
Click to collapse
I am also using Nova, but I'm not sure why that would affect other apps like this.
Any solution to this problem?
Got the very same at my galaxy s6, too. Android 5.1.1
I'd also like to know if there's any workarounds for this. My wife's having the issue and she's blaming me. :silly:
I may have a workaround. I have the galaxy note 3 and i use a custom rom thats pretty much close to stock and I notice that if I lock the device and unlock shortly after, I can't type anywhere, on kik, what'sapp, gosms pro, even google search. So I've just decided to test things out and see what's going on and here is what I found....
Eventually I can type again if I simply wait, but no one likes to wait but this is the longest solution.
Clearing the RAM using built in cleaner or 3rd party memory cleaner seems to allow me to type again.
I didnt like playing the guessing game in knowing how long to wait before I can type again so in kik or go sms pro, I would type one of the native apps' emoticon and then hold the backspace button down until it erases it...then I knew it was ready to let me type again (I have haptic feedback on for keyboard presses so I can look away as I hold down the backspace button - this would let me know when it eventually erased due to the haptic feedback of the smiley getting deleted).
Since the issue occurred only after unlocking, I tried turning off the lock screen completely and turning off phone and back on again....keyboard types right away with no issues!
Its more secure to have a lock screen on the phone so turning off lock screen isn't the best option unless you're like me and are the only person at home with no worries of someone else taking your phone so I decided to try something else that seemed to solve the issue, and that is..............turning off "Multiple Widgets" in lock screen.....tested and worked! I can totally type again right away after unlocking the lockscreen shortly after locking it.
This is what worked for me and for you developers out there....if you can use this to pinpoint why this happens on android, perhaps you can use this information to rectify it.
Hope I helped!!!
I don't know exactly what I did that made this start happening, but right now every time a toast message pops up it stays on the screen for over 10 seconds. If there are other messages queued up then it will display all of them one after another each for over 10 seconds. I did a Google search and could not find a solution. Has this happened to anyone else?
I've tried everything short of a factory reset. I rebooted and safe mode and it still happens. I reset all of the application preferences, as far as permissions and that sort of thing goes, that fixed a few issues I've been experiencing but the toast problem persists.
Is this a bug? is there a solution? Can you adjust the timeout for toast messages? Are there any third party apps that change this setting on an unrooted phone that I unwittingly may have used?
Will I be forced to do a full factory reset to fix this problem? It's really annoying, haha!
thanks in advance for any help
I did everything including a factory reset and those toast messages still did the same thing, so I am thinking it definitely is an OS system upgrade problem!!! It is so annoying !!
twowreally said:
I did everything including a factory reset and those toast messages still did the same thing, so I am thinking it definitely is an OS system upgrade problem!!! It is so annoying !!
Click to expand...
Click to collapse
I still don't understand if this happens on everybody's Pixel 3 or if it's just ours. if it's just a few people then there has to be a common thing that caused it to start doing this. I haven't thought about it too much but my first suspicion was SystemUITuner. did you by chance install that and change anything using it?
I can't think of anything else that I have had to enable permissions with ADB for on here that would have messed with the display settings.
I've been rooting every phone I owned since cupcake. usually owning more than one at a time because well that just makes your power level go up exponentially ... through carelessness and not reading what I needed to before purchasing my Verizon Pixel 3 XL, This is the first phone I've had in my life for more than a month or so that was a daily driver without root.
my point is, I really can't think of a reason why the timeout for all toast messages system wide would suddenly change to be 30 seconds long instead of three. I would have bet on it that that is something that you need root to alter. ??*
typos are speech to text
Sent from my Google Pixel 3 XL using XDA Labs
looking at Google's past release schedule and also starting to hear rumors about Android 11 (they did put a system image up on Google's page but you cannot install it without an unlocked bootloader), we should start hearing official announcements about it soon, with beta1 probably end of April beginning of May.
Even if there are a few not annoying bugs I think it would be worth the upgrade to get rid of these toast messages covering all kinds of stuff that I need to be reading NOW! not in (in the case of three or four toasted pop-up great after each other) 2 minutes later when I've already Ben distracted and can't remember what I was wanting to be able to tap on that was under the eternal-1 toast message timeout.
it's very interesting to me that if you Google this problem there's maybe one or two results. I'm very curious what we are doing to cause this issue. if you or anyone from the future is reading this and knows This information please leave a little response or just post a link it, so maybe I can die happy having finally solved this riddle
thank you in advance
Sent from my Google Pixel 3 XL using XDA Labs
I stumbled upon this after googling the same issue.
I'm not sure if we had the same issue, but I just noticed that it was the "Time to take action (Accessibility timeout)" option, under Settings > Accessibility that made my toasts be long than 3 seconds.
Although it should be on "Default" by default (duh), so if you didn't change this, it must be something else.
Just thought I'd mention it.
testbug said:
... it was the "Time to take action (Accessibility timeout)" option, under Settings > Accessibility that made my toasts be long than 3 seconds.
Click to expand...
Click to collapse
Oh my, thank you so much, I had the same problem and this solved it!!!
I wish there was a way to make it shorter than 3 seconds but from my research it can not be changed can it?
syndre said:
looking at Google's past release schedule and also starting to hear rumors about Android 11 (they did put a system image up on Google's page but you cannot install it without an unlocked bootloader), we should start hearing official announcements about it soon, with beta1 probably end of April beginning of May.
Even if there are a few not annoying bugs I think it would be worth the upgrade to get rid of these toast messages covering all kinds of stuff that I need to be reading NOW! not in (in the case of three or four toasted pop-up great after each other) 2 minutes later when I've already Ben distracted and can't remember what I was wanting to be able to tap on that was under the eternal-1 toast message timeout.
it's very interesting to me that if you Google this problem there's maybe one or two results. I'm very curious what we are doing to cause this issue. if you or anyone from the future is reading this and knows This information please leave a little response or just post a link it, so maybe I can die happy having finally solved this riddle
thank you in advance
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
Just an FYI, coming from AT&T prepaid 6 years during the covid party the depth AT&T is it has taken me 9 months to move to postpay. It is a corporation a complete morons above customer support. All my problems are met with an upsell attempt and I have bit once or twice in return I was kindly bitten all this to say that they put a Motorola one 5G Ace 64 4G ram in my hand and I have the same issue except might hang for 20 to 45 seconds it seems like 90 seconds! May well be. Obviously they're not translucent but the desktop or any operation underneath it will take a finger command if you know where the hell to push. I did not get it from Amazon but I was looking to upgrade to the 128 prior and post this phone and one of the main salesman there with Motorola America which of course is not a Motorola product it's just a Motorola name. The ruination of a long-standing pioneer groundbreaking company! and he wanted to know more information from me and wants me to become a free paid intern or some crap and help them figure out what's going on so there you go? I am sure I am not the only one and just as sure as I am of that, I am sure that the people that make them and sell them and talk about them all day to potential customers or two customers have no freaking idea what their products do.!!
metpet said:
Oh my, thank you so much, I had the same problem and this solved it!!!
Click to expand...
Click to collapse
testbug said:
I stumbled upon this after googling the same issue.
I'm not sure if we had the same issue, but I just noticed that it was the "Time to take action (Accessibility timeout)" option, under Settings > Accessibility that made my toasts be long than 3 seconds.
Although it should be on "Default" by default (duh), so if you didn't change this, it must be something else.
Just thought I'd mention it.
Click to expand...
Click to collapse
dude... thank you.
i dunno how leaving a toast message on top of the buttons you need TO take action helps but that is what caused, likely, or at least what corrected the issue for me.
Moto G7 Supra (Power)
testbug said:
I stumbled upon this after googling the same issue.
I'm not sure if we had the same issue, but I just noticed that it was the "Time to take action (Accessibility timeout)" option, under Settings > Accessibility that made my toasts be long than 3 seconds.
Although it should be on "Default" by default (duh), so if you didn't change this, it must be something else.
Just thought I'd mention it.II
Click to expand...
Click to collapse
I can't find this accesability option on my note 10 + g975fd bubi know it was some kind of setting somewhere because I remember turning it on trying to see some message it waS throwing while I was setting up some Tasker task. Which makes me think it might have been turned on by option for a tasker action but I'll be damned if I can find it again. It's actually nice most of the time but lately it's been really annoying to me because it shows over the keyboard and most of the time an OK or cancel prompt. And like previously mentioned if there are ten of them its quite a long time to wait. And I also turned something on that does a toast every time an intent is launched so you can see how this has multiplied the issue. I think it's one of those situations like (in Tasker you can say launch so n so app, one of the potions is to make the app launch a new instance and another is to have the app not appear in recents. That's all fine gravy for that instance but nobody anywhere ever says that from now on any time you launch that app that it will launch a new instance and it won't appear in recents) whether it's in Tasker or from the Launcher or if you just switch to another app and back. It quickly becomes an issue when you are trying to enter passwords or watch Netflix and do something else real quick. And if you don't put 2 together with 2 because you didn't notice right a way it can be a brain bender trying to figure the little problem out. I'm thinking that's what I have done is set some obscure option for God knows what experimental task and now its stuck that way. But it's really not something I want to bother joã (Tasker de"sorry for spelling") with and he may not know anyway. But thanks for the thread and any other suggestions would be appreciated.