Related
Hi all,
I read through a lot of threads and downloaded tons of ROMS for my TyTN II. Most of them were from dutty's or no thrills. Problem however is that everything seems to work, it is also very fast.
However after a while my (hardware) keyboard and also the buttons (e.g. sliding wheel and keypad on the front) does not respond anymore. When I click any of the hardware buttons the light goes on so it does react on the buttons, however it just doesn't do anything...
Did anyone else experience this issue? I will no try to switch back to the original HTC rom (6.0) since I have no choice but if anyone knows how to fix this?
P.S. I just noticed that all my buttons do not work, it is no hardware issue since It does work after a hard reset, might be caused by incompatible applications? (e.g. SPB phone or SPB theme)
Kind Regards,
Nico van der Linden
If a hard reset fixes your problem each time, then it sounds to me like a bad flash. I would try reflashing the ROM you are currently running. Make sure to hard reset immediately after the flash also.
ok thanks, I'll try to download the ROM flash again , and perform an hard reset directly after the flash. Hopefully this times the ROM update will go better.
Regards,
Nico...
Just my 0.02$:
I think this is related either to WM6.1 builds or to a hack/fix/setting that most custom ROMs use.
I flashed Dutty's Apr 01 ROM and i had this issue. Then i flashed Mobile Vista 1.3 and it happens again . So it's not present in just one ROM, or just in ROMs cooked by a certain chef.
By "issue" i mean every once in a while the touchscreen stops responding to clicks and the keys stop working (but the keys backlight comes on, so HW seems ok).
During this unusual behaviour i noticed that the device is NOT frozen - BatteryStatus updated it's CPU usage while the keys and touchscreen didn't respond, so only the input stops working, the system is ok.
I have a feeling this is a common issue, but people see it as a freeze, and think their processor is too loaded, and they don't report it.
EDIT: Oh, and i got flamed and ignored whan i reported this here: http://forum.xda-developers.com/showthread.php?t=385080
EDIT2: I have a feeling this will get a lot of attention soon, just like the time i noticed the Tytn II is underperforming, and the fact that's it's missing 3D HW support
RPG0 said:
By "issue" i mean every once in a while the touchscreen stops responding to clicks and the keys stop working (but the keys backlight comes on, so HW seems ok).
During this unusual behaviour i noticed that the device is NOT frozen - BatteryStatus updated it's CPU usage while the keys and touchscreen didn't respond, so only the input stops working, the system is ok.
I have a feeling this is a common issue, but people see it as a freeze, and think their processor is too loaded, and they don't report it.
Click to expand...
Click to collapse
The quickest way to get out of that situation is turn off the backlight and turn it back on again, aka power button...and your screen will work again.
Also I noticed that if I flash the radio again my screen taping problems go away.
Also sometimes flashing to the original shipped ROM and then flashing back to a WM6.1 ROM also works.
Well I do not have an problem with the touch screen, this always keeps working (although the device does get VERY slow sometimes) . 'Only' my hardware buttons do not work anymore (including the hardware keyboard). It is strange that it does work after a hard reset or an install of another ROM. However, also then it stops working after half a day or so.
It might occur as soon as I change the hardware button assignment but I am not sure about this yet.
However, if anyone knows a ROM where this does not occur (e.g. an original HTC WM6.0 ROM dutch or english) then please let me know which one. I just want a working Tytn II back and I do not care anymore which version .
Kind Regards,
Nico...
Ah by the way, when this problem occurs it does not go away anymore when I turn of the device. I also tried removing SIM, memory card and battery but after it is started again the problem remains. Only a hard reset solves it....
But I am a bit confused? Is there nobody else who get these issues???
yeah...
i can confirm all of your bug...
with Vega R8 italian ROM from UDK
So my FUZE was working fine since I bought it when it first came out. It was on Stock ROM, Radio, and SPL. I decided to flash the EnergyROM to try out the new Manilla. I installed the Hard-SPL, flashed the 1.12.25.19 radio, and then flashed EnergyROM 2.0 32209. First thing I noticed was that the DPAD was HORRIBLE.
It would not correctly sense what I am pressing! I press home, and some times it doesn't register anything, sometimes it thinks I pressed left. I try the back button but it thinks I pressed right. I have had this thing since it came out so I know how to use the DPAD now, but whatever happened has completely screwed it up! I thought it was the ROM so I went to the leaked AT&T Test ROM which is also VERY nice. But the problem is still there, the DPAD just does NOT work correctly.
Also, I was unable to send an SMS earlier until I soft reset the phone. That had never happened before either.
Since it is not the ROM, it is either the Radio or the SPL. What I don't understand is that many many people have installed both the same Radio and SPL without any problems. How can I fix my DPAD?
petard said:
So my FUZE was working fine since I bought it when it first came out. It was on Stock ROM, Radio, and SPL. I decided to flash the EnergyROM to try out the new Manilla. I installed the Hard-SPL, flashed the 1.12.25.19 radio, and then flashed EnergyROM 2.0 32209. First thing I noticed was that the DPAD was HORRIBLE.
It would not correctly sense what I am pressing! I press home, and some times it doesn't register anything, sometimes it thinks I pressed left. I try the back button but it thinks I pressed right. I have had this thing since it came out so I know how to use the DPAD now, but whatever happened has completely screwed it up! I thought it was the ROM so I went to the leaked AT&T Test ROM which is also VERY nice. But the problem is still there, the DPAD just does NOT work correctly.
Also, I was unable to send an SMS earlier until I soft reset the phone. That had never happened before either.
Since it is not the ROM, it is either the Radio or the SPL. What I don't understand is that many many people have installed both the same Radio and SPL without any problems. How can I fix my DPAD?
Click to expand...
Click to collapse
Did you try flashing back to the stock ROM? If that doesn't work, I wonder if flashing back to stock everything (ROM, radio, SPL) might kick out the bugs (?)
Did you hard reset after flashing? That might be your problem. And what programs/settings did you install? I would hard reset-don't run UC-then see if the dpad is working fine.
I had the problem without installing anything over the ROM itself. When you flash a ROM, it hard resets, so what does hard resetting again do? I spent like 2 hours getting it the way I like it so I don't want to hard reset again. I tried reflashing the radio but it still had the problem right afterwards, but now it seems to have stopped. This is very weired.
EDIT: It started doing it again but if I put the phone to sleep and bring it back, it normally fixes it. What an annoying problem. I am going to try to flash a different radio and see what happens. I just like this radio so much its GPS actually works decently.
petard said:
I had the problem without installing anything over the ROM itself. When you flash a ROM, it hard resets, so what does hard resetting again do? I spent like 2 hours getting it the way I like it so I don't want to hard reset again. I tried reflashing the radio but it still had the problem right afterwards, but now it seems to have stopped. This is very weired.
Click to expand...
Click to collapse
No, it doesn't do a full hard reset when you flash. A lot of crap is left over, and if you just start using the ROM, you get a bunch of random bugs, like, say your DPAD doesn't work. You're supposed to hard reset when the the phone asks you to align the screen. It's a must. Seriously, hard reset and start over and all of your problems will go away.
I reverted to my stock radio and the problem seems to have disappeared. I will try it out more tomorrow.
How is anything left over? It just seems so odd because I can't ever find anything from before when I flash a ROM.
It seems that I can still get fast GPS locks with this radio too, so I guess the A-GPS fix is all in the ROM.
petard said:
I reverted to my stock radio and the problem seems to have disappeared. I will try it out more tomorrow.
How is anything left over? It just seems so odd because I can't ever find anything from before when I flash a ROM.
It seems that I can still get fast GPS locks with this radio too, so I guess the A-GPS fix is all in the ROM.
Click to expand...
Click to collapse
I have no idea how anything is left over, it just is. Here's what mskip's thread says:
mskip said:
[FONT="]Flashing Via ActiveSync[/FONT]
[FONT="]1. Download your prefered Rom from the Raphael Rom Develpoment Page and unzip/unrar it to your computer.[/FONT]
[FONT="]2. REMOVE SIM and microSD CARDS!![/FONT]
[FONT="]3. Turn phone back on and wait until it syncs with your PC.[/FONT]
[FONT="]4. Run the Raphael_RUU.exe (or [/FONT][/SIZE]RaphaelWrapper.exe if thats included instead) [FONT="]from the Roms Folder.[/FONT]
[FONT="]5. Once phone finishes flashing and gets to the screen where it configures the stylus, HARD RESET[/FONT]
[FONT="](hold the VOLUME DOWN and ENTER (center) Buttons, press the RESET button with the stylus tip, then release the RESET button but continue to hold the VOLUME DOWN and ENTER buttons until the reset screen appears)[/FONT]
[FONT="]6. Follow onscreen instructions to set up your New Rom.[/FONT]
[FONT="]7. Once phone has gone through the customisation procedure then replace Sim and microSD Cards.[/FONT]
[FONT="]8. Turn phone back on and set up as required.[/FONT]
[FONT="]Flashing Via MicroSD Card[/FONT]
[FONT="]1. Make sure your microSD is Formatted to fat32 using a PC (you dont have to delete all files but it is safer if you do).[/FONT]
[FONT="]2. Download your prefered Rom from the Raphael Rom Develpoment Page and unzip/unrar it to your computer.[/FONT]
[FONT="]3. Goto the Roms Folder and rename the .nbh file to RAPHIMG.nbh[/FONT]
[FONT="]4. Copy the RAPHIMG.nbh file to the root of your microSD Card.[/FONT]
[FONT="]5. Plug the microSD Card into the phone.[/FONT]
[FONT="]6. Press and hold the volume down button, then press the reset button with the stylus. Release the volume down button when bootloader tricolour screen appears.[/FONT]
[FONT="]7. Follow the onscreen instructions to start flashing.[/FONT]
8. Once phone finishes flashing and says Update Complete, reset with the stylus
[FONT="]9. When it gets to the screen where it configures the stylus, HARD RESET[/FONT]
[FONT="](hold the VOLUME DOWN and ENTER (center) Buttons, press the RESET button with the stylus tip, then release the RESET button but continue to hold the VOLUME DOWN and ENTER buttons until the reset screen appears)[/FONT]
[FONT="]10. Follow onscreen instructions to set up your New Rom.[/FONT]
Click to expand...
Click to collapse
Here are flashing instructions from At0mAng:
Install Instructions
Read The Flashing Your First GSM ROM Guide
Make sure your battery is 50% charged or more
Power off & Remove SIM Card
Power back on and sync with PC
Flash ROM
Hard Reset where it ask you to align screen
Click to expand...
Click to collapse
They're not telling you to do the hard reset just for the heck of it; there's a very good reason for doing it. Not following the standard flashing instructions and then posting in the chef's thread that his ROM is buggy is just not cool.
It turned out to be the radio causing my problems not the ROM. I have never hard reset after flashing a ROM and never had a problem (and that time wasn't a problem because it was due to the radio ROM)
Not that I am asking for it, but unless there is actual proof that you need to hard reset, I don't think there is a point of doing it.
Ok the problem is back! So annoying. Does flashing the SPL hard reset the phone? I want to try going back to the stock SPL since that is the only thing it could still be, but I would rather not now if it hard resets.
Just get it over with and do a hard reset. Jeez, it's not that complicated.
roms and radios will not adjust the dpad i used the same rom u talk about and never had an issue
Hey petard, did you ever fix the issue with the D-pad ?
I have the exact same issue with my Fuze and can't figure it out.
It is a hardware issue. I had to replace it. My replacement worked fine until about 3 weeks ago where it just started to act up. I called for another replacement a couple days ago and should get it tuesday. They offered me a different phone (Epix or Incite) but I declined but told them to note it that I was offered a different phone.
In about 3 months (when my warranty ends) I will call for another replacement. If they have refurbed Touch Pro 2s by then I will ask for that, if not I will get another FUZE which will extend my warranty for 3 more months (you get 3 months or whatever was left of your original warranty, whichever is longer) and by that time they have to have refurbed Touch Pro 2s where I will then try to get one.
petard said:
It is a hardware issue. I had to replace it. My replacement worked fine until about 3 weeks ago ...
Click to expand...
Click to collapse
It figures, no easy fix. It's strange how it started to act up, mine crapped out right after a flash as well.
Good luck on aquiring the TP2 though.
I have a device that used to belong to a MSFT employee. At Microsoft you can just hand in your device and they will put a new ROM on it for you. So first thing I did when I got it is to HardSPL (OliNex 1.90) it and load up a new ROM (the one on it was a couple of builds back, and GPS didn't work etc.).
The strange thing is that ROMS seem to be 'loosing' files (as far as I can tell - apps won't open etc.) after a few days of otherwise great operation. If the device is rebooted, it's almost like a hard-reset; although the installation takes next to no time: and it gets stuck on the splash. Hard resetting the device makes it work for a few days more. The device didn't have these problems with the MSFT ROM (which I stupidly didn't backup).
I have tried a few ROMs and they all seem to have the problem:
MagicROM_23541_Sense25_Mar01
TAELROM_v4.23541_SENSE_2.5_28FEB10_LD
Timolol_5100207TH (awesome ROM)
So my current plan:
Flash stock ROM.
Flash stock SPL.
Flash stock ROM (hoping it will clear anything funny MSFT put on it).
Hard SPL.
Flash Timolol Stock-Like (seems to have the problems the soonest - 2 days max).
Does anyone have any other ideas?
Thanks guys.
I assume since you posted in the Touch Pro2/Tilt 2 section, that you own one of those devices. The roms you have mentioned below are (I believe) for a touch pro/fuze device. That could be your problem. Although, I would assume that you have one as I'm sure a rom for a different device would even flash to the device period. If you have the right rom/device combo and its a touch pro, then you should post in the thread for the roms. More details such as network and device will help the most.
Ah crap - the dangers of having too many tabs open. Can I move the thread myself?
moitoius said:
Ah crap - the dangers of having too many tabs open. Can I move the thread myself?
Click to expand...
Click to collapse
i moved it for you good luck at finding a solution
I don't think it's a hot idea to flash the stock spl. I'm not sure that it can be over-written with hard spl-you'll have to ask in the hard spl thread. If you do it, you might be stuck with the stock rom. Just try flashing the stock rom, then going to the custom one you want. That seems to work for a lot of people.
Farmer Ted said:
...Just try flashing the stock rom, then going to the custom one you want. That seems to work for a lot of people.
Click to expand...
Click to collapse
Thanks, that is significantly fewer steps . I will do that for now and report back in 2 or so days...
Small update - just flashed the latest stock Fuze ROM. Just before the customization app come up I saw that device.exe crashed... In any case, I will see what happens with the custom ROM.
You may need to reformat the memory of your phone. Having device.exe crash on a stock rom during bootup is kind of weird. I've never done it myself, but there are threads on it in the Leo forum. I wouldn't try the apps that they've put together, though. I guess you can search around for "Task 29" to find out how to do it properly.
Moved as not ROM Development.
@OP:
If the device was flashed on a regular basis, it's possible that the device flash memory is near end-of-life.
You could try running Raphael Diagnostics on it to see if that sorts it out.
HTH,
What is the lifespan (in terms of flashes) for a device like this?
Plus minus 2 days - it has been able to go as far as 5.
According to this post: http://forum.xda-developers.com/archive/index.php/t-514940.html
These are good options:
http://forum.xda-developers.com/showthread.php?t=435527
http://forum.xda-developers.com/showthread.php?t=491554
This one in particular: http://forum.xda-developers.com/showpost.php?p=3446141&postcount=16 (it applies to Rhodium, but people have had success with it).
Apparently Task 2a (equivalent of 29) is disabled on the OliNex 1.90 SPL - so I can't do a NAND format without reflashing the stock SPL (not that I would attempt that myself in any case ).
I'll run RaphaelDiagnostics and see if that comes up with anything.
Thanks for the help so far guys, I first want to see if the stock flash I did works (I smell a Wiki page).
I tried out the raphdiag-it's pretty cool. I've been having a few weird issues lately on my fuze. In particular, all of a sudden my boot-up time seems to have gotten slow (millisecond to idle thread went from 65-70 sec to 90-95 sec, and I hadn't messed with start up programs). Also, I have been having an issue with files on the main memory becoming corrupted, which has just been weird. Anyway, I ran an 'info 8' with mtty a few weeks ago, and it came up with 7 bad blocks, which seems normal. So, I ran raphdiag this morning, and ran the format nand routine. I was a little surprised, because after running it, I soft reset and the phone booted up normally like after a hard reset. I thought that it was going to wipe the entire rom memory clean, leaving only the radio, bootloader and splash screen. It didn't seem much different from a hard reset. The good news is that my startup is faster. With a setup I was using beforehand, the millisecond-to-idle-thread speed was 76 seconds, and after the format it was down to 71 seconds. However, I ran an 'info 8', and the memory analysis hadn't changed at all (same 7 bad blocks). I'm not sure if the formatting (task 29 or this) is supposed to clear that up, though.
I put both the raphdiag.nbh and a raphimg.nbh on the root of my normal 16 gb card. When you go into bootloader, it does a quick image update (takes about 2 seconds), then the screen tells you to push power for a rom update or push the action button to go into diagnostics. From there, you have maybe 4 or 5 choices. Scroll up and down with the up/down buttons, then push action. The first is a set of hardware tests, the second is something like 'run in/on', which appears to be a test scheduler. The 3d is the NAND format option, and I think the 4th and 5th options are 'calculate rom checksum' and then 'skuid', or something like that. To exit, I just soft reset, or used soft reset/vol down to go back to bootloader. After the format, I tried to flash (I think it called it re-flash), but it said there was no image present. You may need to do this on a clean card to get it to work (that is, format and then flash off the same card without swapping things out).
The diag tests are kind of cool. There's an auto mode that runs through all of them, but you have to do things to get it to work. The first is an LED test. The screen turns red, you stare at it for 5 min wondering what the hell is going on, then push the action button for the hell of it. Then the screen turns green. Push it a bunch more times, and it goes through shaded and checkered screens and whatnot, then it tells you it passed the test. There's a test for the slider, and you need to slide the keyboard in and out. The qwerty test was weird. It's configured for a touch pro (not a fuze), so I didn't know what the hell to do at first. The screen just says 'QWERTY_KBD_1', or something like that. I tried hitting the '1' button, and fn-1, and it did nothing. Then I just hit the top left button, and it said OK and prompted to hit 2. So, you just push all the keyboard buttons from left to right, top to bottom. There are also tests for the other hardware buttons, except for the 4 main buttons on the d-pad (home, back, send, end), which was kind of weird. If you think your power button or vol down button is effed, this tool will confirm/deny it for you.
Right, so the RaphDiag didn't brick your device. It's a bit risky - so I will first resort to less extreme measures - at least I know there is one success story.
I seriously wouldn't worry about it, but you may want to have a card reader available in case you need to remove raphdiag from you sd card to get a flash to work. It's possible that I didn't get the nand format to work properly, but I think I did it right, because the device definitely needed to cold boot. I was just surprised that there was still an OS there.
I'll take your word for it - BUT - in terms of gaining knowledge I am going to try the steps in the posts I found. If the NAND does need a format there is no doubt that I will land up doing it - but I will have first-hand experience.
This really needs a Wiki page once I am done; so I want to squeeze as much info out of the device as I can.
Can anyone else think of any gotcha's before I potentially brick it?
I ran the format a second time. It's really fast; it takes maybe 5 seconds. I haven't figure out how to exit from that part of the diag other than soft resetting, which leads to a cold boot. I'm surprised it's so fast. A hard reset takes about 30 seconds. I guess that it's working properly.
Farmer Ted said:
I ran the format a second time.
Click to expand...
Click to collapse
You are either very brave or very rich . Right, so here is hoping I have to go the final resort route - nothing yet though.
Okay, this is my first time actually posting anything on XDA. I won't bother with an introduction and I'll just get to the meat of the issue. I am currently running CM 10.1 JB 4.3 with vincom's Superlite 4.0 (kudos to vincom btw, easily the best rom for this phone imo). Now, I know the problem is not related to the ROM as this exact same issue was occurring when I was running the Liquid Smooth ROM (I apologize I don't remember the dev for that one right now) and the Slimbean JB 4.2 ROM. Without fail, when I turn my phone off, restart it, whatever, it shows the Samsung logo for the appropriate amount of time, then goes to a blank screen. Zip, nada, nothing else. I've alowed it to sit for an entire night in such a state to see if it was just really slow. Still nothing. To make things stranger, when you hold down the power button to hard reset, the screen does the CRT monitor off animation... No clue why it manages that, but not to start up. Tried just tapping the power button when in this state and it still does nothing. I won't bother with logs unless someone truly wants them, but here's where things get really interesting (at least to me): I found that I can get the phone back up and running, and so far I've done this 50+ times and it's still a working method, but if I 3 button hard restart (or just 3 button power on) the phone to recovery, which for me is TWRP 2.6.3.0, there are no issues entering recovery. Then, after many many many trials and errors I found that if I make a recovery image for JUST the data (instead of the cache, android secure, etc etc), then flash the image for just that data, then tell the phone to reboot from within TWRP, viola! The phone boots up, no issues, no lost data, nothing. I would really just like to get this issue resolved . Sorry if this was more of a book to read than necessary, i'm just very confused and thought a detailed explanation would be best. Thanks to anyone for any leads, ideas, or suggestions!
apetwaffle said:
Okay, this is my first time actually posting anything on XDA. I won't bother with an introduction and I'll just get to the meat of the issue. I am currently running CM 10.1 JB 4.3 with vincom's Superlite 4.0 (kudos to vincom btw, easily the best rom for this phone imo). Now, I know the problem is not related to the ROM as this exact same issue was occurring when I was running the Liquid Smooth ROM (I apologize I don't remember the dev for that one right now) and the Slimbean JB 4.2 ROM. Without fail, when I turn my phone off, restart it, whatever, it shows the Samsung logo for the appropriate amount of time, then goes to a blank screen. Zip, nada, nothing else. I've alowed it to sit for an entire night in such a state to see if it was just really slow. Still nothing. To make things stranger, when you hold down the power button to hard reset, the screen does the CRT monitor off animation... No clue why it manages that, but not to start up. Tried just tapping the power button when in this state and it still does nothing. I won't bother with logs unless someone truly wants them, but here's where things get really interesting (at least to me): I found that I can get the phone back up and running, and so far I've done this 50+ times and it's still a working method, but if I 3 button hard restart (or just 3 button power on) the phone to recovery, which for me is TWRP 2.6.3.0, there are no issues entering recovery. Then, after many many many trials and errors I found that if I make a recovery image for JUST the data (instead of the cache, android secure, etc etc), then flash the image for just that data, then tell the phone to reboot from within TWRP, viola! The phone boots up, no issues, no lost data, nothing. I would really just like to get this issue resolved . Sorry if this was more of a book to read than necessary, i'm just very confused and thought a detailed explanation would be best. Thanks to anyone for any leads, ideas, or suggestions!
Click to expand...
Click to collapse
read the sticky right above ur post |READ THIS B4 POSTING | THE MOST Common Questions Answered HERE Q27
As of last night my tab 2 (p3100) has been playing up, have it running a pac rom, not updated in a while but all was working fine. Now when I do get it on, it lags a lot on home screen, can only really access anything for about 30 seconds before its practically unusable. When I try to power off or reboot it begins the process but ends up freezing, only way I can get it properly off it to plug it in to charge and then hold power for ages. Then getting it on again takes ages. Only thing I recall doing prior to these issues was installing the peel remote earlier that day, maybe just a coincidence but after that it all went wrong. I've just tried a factory reset and data wipe, seemed to initially solve the problem but after a few mins back to the same issues, any ideas?
edingal said:
As of last night my tab 2 (p3100) has been playing up, have it running a pac rom, not updated in a while but all was working fine. Now when I do get it on, it lags a lot on home screen, can only really access anything for about 30 seconds before its practically unusable. When I try to power off or reboot it begins the process but ends up freezing, only way I can get it properly off it to plug it in to charge and then hold power for ages. Then getting it on again takes ages. Only thing I recall doing prior to these issues was installing the peel remote earlier that day, maybe just a coincidence but after that it all went wrong. I've just tried a factory reset and data wipe, seemed to initially solve the problem but after a few mins back to the same issues, any ideas?
Click to expand...
Click to collapse
Try flashing another ROM, like CM 10.2 or one of the stock-based ROMs. Make sure to wipe data, system and cache before flashing. If the issue still persists, try restoring a backup that you know worked.
Will give that a go, thanks.