Hello boys, girls, and friendly animals.
I installed MIUI.US yesterday and noticed the same thing that's always bothered me from non-stock or non-CM ROMs: there's no way to use the phone's Quick Keys (other than setting them to work like, say, a Back button using ButtonRemapper).
One of the things I use the most from the stock ROM is the shortcut to send an SMS to a contact. I've found that without this, ROMs eventually annoy me.
Is there any way to go about and making these work? I tried installing UserKeysTool.apk (com.tmobile.userkeystool) from a stock ROM (s14mc's 1.6 Slim) to no avail; the app simply crashes upon opening it, which means I'm missing some other file I'm not aware of.
Any help would be appreciated here.
Sent from my HTC Desire Z using Tapatalk 2 Beta-3
Related
I was wondering if there is a way to export the Phone/Contact Manager off the original Mytouch4g ROM to use on any ROM. Cyanogen mod is underway and i kind of got used to the new dialer and will miss it. Maybe there are alternatives i can look at, but the original one works well on hd screens.
On another note, maybe we can get the dropdown Recent apps also individual? Is this possible?
Thank you in advance
Hey guys,
My Launcher Pro crashes almost everytime I want to apply a custom made dock icon or dock background. I have noticed that when I use icons made by someone else it usually works, but if I try icons that I made it simply crashes...
Any suggestions?
Thanks
Hello Alex
Working on LauncherPro Plus v0.8.4 and it works flawless. I tryed (quickly, I admit) the things that fail with you, and have no problem at all. I'm working on the stock froyo.
Perhaps a stupid question since you are more experienced then me, but have you already tried to whipe the cach or reinstall the application? I have had some "unexplanable" problems with other apps that were solved this way.
Erwin.
I found the error.
I downloaded the .png files using dropbox and thats the reason it wouldn't work.
So when I transfered the files using a usb cable it worked perfectly...
Very strange but I'm glad it finally works
Sent from my HTC Wildfire using XDA App
Hey guys, I have posted this in another forum but didnt get much luck.. wanted to try it here before I gave up and hung myself.
Very briefly: I have just flashed my fourth rom, this time I went for MIUI. Fantastic, really good speed, very aesthetically pleasing, etc.
Anyway, I have tried to run some GBA emulators and they havent worked. They flash the black screen for about 5 seconds, and the game plays in the background but it minimises the program; it says it is still running in the notification area but when I try to access it it just minimizes again.
Is this a common problem on MIUI? Has anyone else had a similar issue? Im sure its MIUI related as I have had the program running on several different ROMS..
Please dont make me choose between this awesome rom and being able to play Mother 3!!
Thanks guys;
Vincent.
Edit:
Turns out it is a gingerbread incompatibility. Can be fixed by installing a compatible emulator *facepalm*
Since I'm still too n00b to post in the Dev Forum I'll post this here.
I just installed this awesome ROM and it all woks pretty fine... except for the bugs everybody has already mentioned in some topic or another.
About the bug regarding the capacitive buttons (the little Home/Menu/Back/Search) non correctly lighting up I found out a peculiar thing not mentioned by anyone else (afaik).
Maybe it could be useful, maybe not.
Anyway... in my phone (DHD ex-Cyanogenmod7, s-off, wiped) they are consistently turned off except when I open an ebook with Aldiko.
It always happens, and they stay ON untill I leave the ebook's pages.
It happens with both pdfs and epubs.
It only happens with Aldiko ... both Kindle and MoonReader failed to show the same glitch.
Just wanted to let people know u_u
Hasimir said:
Since I'm still too n00b to post in the Dev Forum I'll post this here.
I just installed this awesome ROM and it all woks pretty fine... except for the bugs everybody has already mentioned in some topic or another.
About the bug regarding the capacitive buttons (the little Home/Menu/Back/Search) non correctly lighting up I found out a peculiar thing not mentioned by anyone else (afaik).
Maybe it could be useful, maybe not.
Anyway... in my phone (DHD ex-Cyanogenmod7, s-off, wiped) they are consistently turned off except when I open an ebook with Aldiko.
It always happens, and they stay ON untill I leave the ebook's pages.
It happens with both pdfs and epubs.
It only happens with Aldiko ... both Kindle and MoonReader failed to show the same glitch.
Just wanted to let people know u_u
Click to expand...
Click to collapse
its look like kernel problem try diffrent rom on ur phone.
Maybe I will ... this ROM is still too raw (performance-wise) for me right now.
Browser navigation is quite slow and the overall phone is not very snappy (compared to CM7).
But my post was intended as a little help for the Dev Team ... maybe noticing this Aldiko glitch may help them understand where to put theor hands on the kernel.
Or maybe not XD
Umm use a different reader .if the lights stay on maybe a kernel issue just flash lords kernel from the dev section .failing that man use a devs Cyranogen infused rom
Sent from my HTC Desire HD using XDA Premium App
Forgot to ask what rom r u running
I used to run CM7.
With that rom the buttons were always ON, as they were meant to.
I usually use the Kindle app and it did nothing strange.
Then I installed (and am currently using) Virtuous Quattro RC2.
With this the buttons are always OFF, which is a bug.
Searching the forums I found out that this is a more or less common bug, and there is no fix for it right now.
But then I read an article about how awesome this Aldiko app is, and decided to try it along with MoonReader and a few others.
Doing this I accidentally discovered that Aldiko somehow "fixes" the button's bug.
Searching the forums it appears no-one else reported this thing to the Virtuous devs.
So I thought: if Aldiko "does something" that fixes the bug, maybe telling the Devs may help them look in the right place and find a solution or a workaround.
That is all
Also running that rom...after trying several. This seems to be the least buggy of all of...I have tried several. The 1beta4 (LC) was the quickest/smoothest. but I had numerous small but annoying issues and loaded Quattro on 1/23. I have an Inspire. I also loaded the Quattro wifi fix and had to load Lordmod for the sound to work..appears to be an issue with Inspire and ICS. Anyway, long story longer...I am also an Aldiko fan/user and don't have any issues with the buttons at all...maybe the difference in phone...or the 2 additional zips made it a non issue?
I'm now running RC3.
Wifi problem is solved.
Capacitive button problem is solved.
General lagginess appears to be solved.
Battery life seems better too.
Strange enough, there is no way to remove the 3g toggle from the task bar
Good job team Virtuous! :-D
Sent from my HTC Desire HD running Virtuous Quattro RC3 - with XDA App
Hasimir said:
I'm now running RC3.
Wifi problem is solved.
Capacitive button problem is solved.
General lagginess appears to be solved.
Battery life seems better too.
Strange enough, there is no way to remove the 3g toggle from the task bar
Good job team Virtuous! :-D
Sent from my HTC Desire HD running Virtuous Quattro RC3 - with XDA App
Click to expand...
Click to collapse
I have been running RC3 on my HTC Incredible S for the past few weeks and I never had any problem with the capacitive buttons until recently they stopped glowing and as you mentioned earlier they start working when I open Aldiko app. I read that the problem got solved for the RC3 then why am I having these issues?
Hey guys!
Does anybody have any idea why only the TW/Stock dialer works on my phone despite trying multiple AOSP/CM ROMs, kernels, PRL/Firmwares, and recoveries? I'm having tons of trouble finding others with this problem. The CM-style dialers all glitch and will not allow the input of keys from the phone/dialer app and will on some roms black the screen out completely despite my using the home button to minimize the app. In a few ROMs I've had to hard reboot the phone to get it out of the call screen. In others, only the dialer/phone app itself freezes up and the screen glitches with mild to moderate system ui problems.
Anybody? Or maybe I could provide some more info to anyone who has questions that we might figure out what the dilly is, here?
Dirty flashing? I don't know why you're having this issue but I have had issues in some roms where the aosp dialer come up blank with no digits.
What I did was search for blacked out dialer apks. Grabbed one for aosp and one for TW. Each time I go to a new rom I just overwrite the dialer apk, change permission reboot and good to go. Maybe that could be of some help maybe not. Just an idea and good luck
Sent from my SPH-L720 using xda app-developers app
HPferoxCraft said:
Dirty flashing? I don't know why you're having this issue but I have had issues in some roms where the aosp dialer come up blank with no digits.
What I did was search for blacked out dialer apks. Grabbed one for aosp and one for TW. Each time I go to a new rom I just overwrite the dialer apk, change permission reboot and good to go. Maybe that could be of some help maybe not. Just an idea and good luck
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Thanks. Yeah, it's hard to explain exactly what happens, but it's not involving the omission of digits or lack of recognition. It's on all non-TW ROMs and causes the phone to totally wig out and the screen blinks on and off, sometimes locking the phone, sometimes not. It never used to do it before, and I suspect . It works great for every other aspect of the ROMS other than the dialer/phone app. It's not so simple at all that I can use one of those fine ROMS and just uninstall the CM dialer and install the TW version, is it?
arikdahn said:
Thanks. Yeah, it's hard to explain exactly what happens, but it's not involving the omission of digits or lack of recognition. It's on all non-TW ROMs and causes the phone to totally wig out and the screen blinks on and off, sometimes locking the phone, sometimes not. It never used to do it before, and I suspect . It works great for every other aspect of the ROMS other than the dialer/phone app. It's not so simple at all that I can use one of those fine ROMS and just uninstall the CM dialer and install the TW version, is it?
Click to expand...
Click to collapse
I don't think that would work. You'd need aosp dialer on AOSP and TW dialer on TW. There's other apks and libraries involved. But you can always cherry pick apks from other 'like' roms that you know work fine. I just play around till something sticks, I break more than I fix but that's why we make backups.
Sent from my SPH-L720 using xda app-developers app
To fix the dialer app not sending or receiving calls and getting stuck after call hang up.
You gotta use the method at the below link to fix this issue. I like AOSP over touchwhiz roms so i am so glad this xda member came up with this solution for us.
http://forum.xda-developers.com/showthread.php?t=2539794