Related
i just got my touch pro 2, it was used, but it was still new
it still even has the original plastic on the screen.
ever since ive had the phone though, everything on it is really really slow.
opening up a text, sending a text, going back to the home screen, opening up opera, clicking on the notification tab. EVERYTHING is really slow, or has some kind of lag to it. Why is this happening? What can i do to fix it?
This is really bothering me, and im about to trade for another phone because i cant take it. It takes me 5 minutes to send a text message, after i hit the send button.
ANY help is appreciated, thanks!!
First thing you want to check is which ROM is running on the device. Is it stock or a cooked ROM. Which version TP2 do you have? is there a carrier logo on it? The more information you can provide about the hardware/software on the device the better we can help you.
its the stock ROM. Original T-Mobile branded version. Its pretty much new out of the box it seems.
Since you just got it, and someone may have been using it before. i would suggest hard reset first off to remove any junk the previous user may have installed.
ok thats sounds like a good idea, how would i go about it?
(sorry for some of the questions i have been / will be asking, i just came from android to WinMo, so im completely lost)
1. While the HTC Touch Pro 2 is off, press and hold Talk/Send, End and Power until you see a message on the screen about deleting all data.
2. Release the buttons after the message appears.
3. Press the Volume Up button.
once you are done with that I would recommend disabling push internet and also the Dynamic Resource Proxy...
nayr1482 said:
once you are done with that I would recommend disabling push internet and also the Dynamic Resource Proxy...
Click to expand...
Click to collapse
The T-mobile stock ROMs do not have push pages and as such I do not believe it makes use of the Dynamic Proxy.
I came from an Android device (briefly, in between my Wizard to Rhodium). The screen itself is different. This may be part of the lag you are experiencing. I actually prefer the WinMo platform over the Droid one, as it feels more responsive and stable to me. My friends however, who have the the G3 or iPhone hate my Rhodium...so again, I suspect that if, after hard booting your device, it still feels laggy, it may be the differences in how the screen responds versus a Droid screen. The Devs here could explain it in much better techie terms than I.
There is a thread here pushing for a Droid port over to the Rhodium, and I sit here scratching my head asking why. I truly believe that much of it is perception, mine being that Android just isn't for me. You may consider checking out that thread and seeing if the port over is any closer to happening.
In the meantime, I have heard that the Energy roms are quite stable and fast, so you may consider flashing one and seeing if maybe your response issues are handled. Be sure to read up on unlocking/flashing your device first so you don't brick it.
I'm sorry I'm not much help here. I do think though that perhaps some of the issue may be the screen...I could be way off base here too, though.
I am testing out the Dymanic Resource Proxy hack to see if it makes any difference to me. Will let you know what i find, so far idling at about 55%
update:
well, i went ahead and did a system restore, it was faster, but still not to my liking, so iwent ahead and flashed a ROM to make one final test. i went ahead a flashed energy ROM, and i have to say, i very much enjoy it now. ALOT faster, much smoother transition between applications, accelrometer works alot better, an overall greatly improved experience.
thanks to everyone that helped me!
one last question though, after flashing the ROM, my ALT key doesn't seem to work. Any fix? i would do a search, but im already typing a response, so i thought i would go ahead and include it here.
http://forum.xda-developers.com/showthread.php?t=550559, should have your solution It's a sticky on this sub-forum a few posts on top of your post =p
b1ck132 said:
http://forum.xda-developers.com/showthread.php?t=550559, should have your solution It's a sticky on this sub-forum a few posts on top of your post =p
Click to expand...
Click to collapse
haha thank you, i knew it would probably be somewhere obvious, but i was just responding and figured i would go ahead and throw it in there
Hi Devs
I'm from Mumbai India and i'm using galaxy nexus gsm.
It is an awesome phone but lately i'm having problem
My phone screen flashs and blackouts out of nowhere While operating my nexus and than i have to reboot it.
This has been happening from the time when i tried few custom roms (xylon, miui, overdrive, pa, minco v6 and madoco) back to back couple of weeks back. I don't know what is the cause of it and why is it happening.
So guys i need little help here.. Plzz help me fix it.
Right now I'm using baked 7 rom and gapp 4.2.1 12/12/2012.
Thank you in advance
I believe this is referred to as a Screen of death, or sod. Search the forum, and you may find some answers. Ive heard this is common on 4.2.1, but have yet to deal with it myself. Actually, though, ive had some close calls where the power button will not wake the phone, and i believe ive also seen where the actual issue is waking the phone from sleep..
Actually, I've just noticed that you're using the old gapps as well. The baked downloads page has the new gapps, and perhaps that may help you.
THANK YOU
bodh said:
I believe this is referred to as a Screen of death, or sod. Search the forum, and you may find some answers. Ive heard this is common on 4.2.1, but have yet to deal with it myself. Actually, though, ive had some close calls where the power button will not wake the phone, and i believe ive also seen where the actual issue is waking the phone from sleep..
Actually, I've just noticed that you're using the old gapps as well. The baked downloads page has the new gapps, and perhaps that may help you.
Click to expand...
Click to collapse
thanks alot,..
Have you tweaked the kernel options, messed with thecpu clock? Maybe try bringing all of that back to stock.
hi,
you guys may find reading this helpfull (it's dev's only, but reading it doesn't do any harm): http://forum.xda-developers.com/showthread.php?t=2080690
cheers
YES may be
jackbane said:
Have you tweaked the kernel options, messed with thecpu clock? Maybe try bringing all of that back to stock.
Click to expand...
Click to collapse
i had tweaked the kernal options once long back,.. it twisted kernel i guess
I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.
mkanet said:
I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.
Click to expand...
Click to collapse
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...
Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
dwitherell said:
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...
Click to expand...
Click to collapse
My annoying fix...
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.
I forgot to mention that lock screen prevents this bug from happenening. I'm guessing that's why not everyone has complained about the issue.. and why the bug somehow sneaked passed beta testing of 4.1.2. I would think this changed behavior was a new "feature" as horrible as it is, but it looks like it dad unintentional since its not consistent behavior.
I'm hoping that a kind android developer who also can't stand this problem, Kay offer a small script or app for rooted user to patch this problem.
mrtolles said:
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.
Click to expand...
Click to collapse
mkanet said:
Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
Click to expand...
Click to collapse
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test
You did it! Your fix works perfectly! The bug is gone! ...like the bug was never there. My understanding is the fix prevents the phone from stupidly trying to launch the task manager when the screen wakes by the home button. I also donated for you time and effort. Thanks a million.
dwitherell said:
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test
Click to expand...
Click to collapse
No, thank you for making me learn how to put an odexed mod together and testing it for me!
So this fix will work for anyone running a stock odexed version of 4.1.2 UVBMB4 - you just need to be rooted, and having a custom recovery would be nice so you could flash it but you could also just copy the files over. That being said - would this be worthwhile to post?
I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.
mkanet said:
I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.
Click to expand...
Click to collapse
The flashable zip is just one method to get the files where they need to go. Literally all it does is overwrite the 2 files in /system/framework by moving the 2 files over from the zip - but there are definitely other ways to do such things. Some are more comfortable with this route, others are more comfortable w/ getting /system to be rw and move the files manually.
I'll likely post this at some point in the next few days
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
Glad to hear
Is it possible that my phone isn't affected? If its a 4.1.2 bug, it should be in all phones with same version right?
This is not happening to my phone. Whether I have lock screen activated or not. I'm rooted but running stock ROM and I have Nova launcher installed if thats even important.
It's not all notes.
Sent from my SGH-T889 using xda premium
kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Yes you'll need to be rooted unfortunately - sorry
wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Absolutely. just PM me. Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.
kabuk1 said:
...Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.
Click to expand...
Click to collapse
^^^ THIS - a thousand times over
Don't hate, I have some noob questions, first is after a clean install of the latest slim rom, I can no longer find the option to turn off my hardware lights (back and menu) I just spent the last 40 minutes looking, maybe I am blind, but they were off on the previous build.
Next, and the reason for the reinstall, how does I get the OTA to work, I just get an error.
And I don't have enough posts to post in the slim thread.
slim
cMACr said:
Don't hate, I have some noob questions, first is after a clean install of the latest slim rom, I can no longer find the option to turn off my hardware lights (back and menu) I just spent the last 40 minutes looking, maybe I am blind, but they were off on the previous build.
Next, and the reason for the reinstall, how does I get the OTA to work, I just get an error.
And I don't have enough posts to post in the slim thread.
Click to expand...
Click to collapse
I was told that The OAT wasn't incorporated on the Note 2 and that came from someone from the IRC...
Thanks
thatmetaldude85 said:
I was told that The OAT wasn't incorporated on the Note 2 and that came from someone from the IRC...
Click to expand...
Click to collapse
Was wondering, seen a few threads in other devices that said it needed to be turned on.
Thanks for the repy.
Does anyone thing the option to turn off the capacitive lights got lost in the menu restructuring in the latest 7.8 build?
Hello?
Is anyone running Slim that can check their settings to see if the option is there, please?
Woot! Finally found it. Thanks for all the help.
For anyone else looking, advance options, device, screen, touch key...
Q&A for [ROM][SM-T320][5.1.1_r3][UBERTC 4.9]UnofficialTemasek v12.3[June4]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][SM-T320][5.1.1_r3][UBERTC 4.9]UnofficialTemasek v12.3[June4]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Thanks
Thanks for that awesome rom, super fast and solid as a rock, full of features, some that I never see on other rom like otg usb notification unmount, it's the best rom that i tried on my tab pro, continue your great job :good:
Deleted
dead tablet
Hi guys. I installed this ROM a few days ago was very happy even though the battery durava unless the rom official ... but today I've run into a problem I connect to the tablet in the morning around 30 min. and he had 96% of battery I have left and I have gone to work my surprise was at the vuelata my tablet etaba off and there is no way to Ramp up've left more than 4 hours to charge and so far nothing, alkene over them past that ??? and that I can do to get right the problem. sorry for the language.
a greeting
Keyboard sound
How to turn off or change that ugly keyboard sound the first ROM for me so far it is good few glitches
Disabling back and recent hardware keys
i originally dirty flashed this rom over cyogenmod 12.1 and it mostly worked but had some issues. doing a clean install helped most of them, but i ran into a new problem i didn't have with the dirty flash. i prefer an onscreen nav bar to hardware keys but i want to keep the home button working, just disable the back and recent buttons. in the dirty flash disabling hardware keys did just this, but now it disables all 3 of them. i noticed that i can leave the hardware keys turned on and disable the recent button, buy changing the short press and long press action to nothing, but i don't have a way to disable the back key.
My question is if there is any method which i missed that would allow me to disable to back key aswell? did i miss a setting somewhere? oddly enough with all the problems i had with the dirty flash, this one thing worked how i wanted it too, and now its not. i know i can change the key bind for it with xposesd, but as was discused before it causes a boot loop.
other then this problem, this is a fantastic rom and i am extremely great full for all the time and work that went into making it possible. and especially thank all the people that come to these fourms and help clueless people like myself.
innocentus said:
How to turn off or change that ugly keyboard sound the first ROM for me so far it is good few glitches
Click to expand...
Click to collapse
It should be under settings>control>input
bricked device
so i flashed your rom one week ago and 2 days ago without warning or something the device shut down .when i try to power on i cant only black screen and thats all no recovery no download mode only a black screen ,the battery was full what can i do?thank you
innocentus said:
so i flashed your rom one week ago and 2 days ago without warning or something the device shut down .when i try to power on i cant only black screen and thats all no recovery no download mode only a black screen ,the battery was full what can i do?thank you
Click to expand...
Click to collapse
Known as sleep of death. Hold power button for at least 30 seconds. I sent mine back before I discovered that to reset takes way longer than most devices.
---------- Post added at 07:19 PM ---------- Previous post was at 07:11 PM ----------
@konchar
Disable in settings, buttons, hardware keys. The navbar height is set to 0, increase this or you won't see it
New version of the ROM out today. Much improved, xsposed working again. IMO Temasek rocks.
Thanks gscollier i didn'try that even i browse the web all day. I sent mine too at warranty service mine i think it's death because. I keep it in charge 4hours and still nothing. Thanks again for the news it's really a good rom and fast just trebuchet stops from time to time
@gscollier
@konchar
Disable in settings, buttons, hardware keys. The navbar height is set to 0, increase this or you won't see it
New version of the ROM out today. Much improved, xsposed working again. IMO Temasek rocks.
Click to expand...
Click to collapse
thanks for the response, but it doesn't quite help me with my problem. I think you misunderstood, i know how to disable all hardware keys and have no problem with the onscreen nav bar. what im trying to do is disable the hardware keys for back and recent while leaving the home button functional. it can be done with xposed modules but i cant seem to get xposed to work here, even with the new update.
once again thanks for the reply, i will keep looking for a solution.
konchar said:
@gscollier
thanks for the response, but it doesn't quite help me with my problem. I think you misunderstood, i know how to disable all hardware keys and have no problem with the onscreen nav bar. what im trying to do is disable the hardware keys for back and recent while leaving the home button functional. it can be done with xposed modules but i cant seem to get xposed to work here, even with the new update.
once again thanks for the reply, i will keep looking for a solution.
Click to expand...
Click to collapse
Got it, don't think you can disable only back and recent but not home. So, xposed. I don't know what module you are using but make sure you have the xposed alpha from here:
http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
Many modules cause bootloops but I have 4 working with no problems on the latest Temasek ROM. I strongly recommend ROM backup before flashing the xposed zip and also each time you try a module. Slightly time consuming but quicker than flashing the ROM from scratch. If a module causes bootloop you can wipe cache and davlik cache in recovery. If it still bootloops that module just won't work for now. Trial and error I'm afraid.
Niathi said:
Hi guys. I installed this ROM a few days ago was very happy even though the battery durava unless the rom official ... but today I've run into a problem I connect to the tablet in the morning around 30 min. and he had 96% of battery I have left and I have gone to work my surprise was at the vuelata my tablet etaba off and there is no way to Ramp up've left more than 4 hours to charge and so far nothing, alkene over them past that ??? and that I can do to get right the problem. sorry for the language.
a greeting
Click to expand...
Click to collapse
Try to press start button more than 30 seconds, it will reboot,
BT-tethering
Sorry, if it is a known CM-issue!
I couldn't get bluetooth-tethering to work. For me that is a very important feature on a mobile device without SIM-Slot. That's why I had to go back to laggy TW-ROM.
So for this ROM you flash then wipe data/factory reset? Is that considered a clean flash?
ntdouglas said:
So for this ROM you flash then wipe data/factory reset? Is that considered a clean flash?
Click to expand...
Click to collapse
A "clean flash" is wiping everything first, then flashing.
Thanks vasumit! How frequently do you plan on providing updates to this ROM? I'm trying to decide between this and CM12.1 as my daily driver.
in the last build from 7.10 doesn't show the performance tab of the kernel . anybody same problem on a clean install thanks
Thanks sharkie. Developers instructions stated otherwise. I clean flashed this ROM and it is nice. Has anyone noticed on the android launch screen its grainy or pixelated? Games and internet look awesome. Same problem when I was running stock CyanogenMod 12.1. Also how do I get the clock widget out of military time?
---------- Post added at 03:40 AM ---------- Previous post was at 02:57 AM ----------
Another problem to report. I flashed the gapps package recommended by the developer and all I see is the play store. What's up?
Can anyone share your performance setting with me?
This ROM is nice in term of general performance and feature, especially in comparison with the original CM12.1 which gave me huge unresponsive issue during app installation.
However the CPU temperature is quite hot and my tab have broken down three time in a row during the last two days. I have to let the it rest for about an hour before turning it back on and right now i'm still waiting, don't know if it will come back to life or not. Really scary, this one.
Can anyone confirm the temp issue? This is the first time i encounter this much trouble on a device after install CM based ROM. First is the unresponsiveness of original 12.1, now this.........................................