Database Info

[Q] MIUI Problems

I switched to MIUI a few days days ago, and I've been loving it so far. But I have been having a couple of issues.
Every so often my phone restarts for no reason. Sometimes when I'm in the settings application. Other times when I'm playing music. Regardless which music app I'm using, it'll restart my phone after 15-20 minutes.
My other issue is that my phone thinks its a Desire HD. is there a way to change
that? I can't access certain apps in the market because of that.
Thanks in advance.

I would try reflashing the rom. What kernal are you using with the rom and which version of MIUI? There is a discussion somewhere in the MIUI thread about changing the description in the build.prop file to make it show as an Inspire

I'm running miui 1.7.23. Not sure which kernel, probably the stock one. I haven't really read anything about the differences or why one is better than another.
Sent from my Inspire 4G using XDA App

theox88 said:
I'm running miui 1.7.23. Not sure which kernel, probably the stock one. I haven't really read anything about the differences or why one is better than another.
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
It sounds like a bad rom flash. I would wipe data, cache, and dalvik cache. Then I would reload the rom. The stock kernal that comes with the latest rom needs to be updated with the latest Lordmod kern but it should not cause the problems you are having.

[Q] Sensation with Revolution HD Glitch, please help.

I am running Mike's Android Revolution HD based on HTC Sensation "non-XE" HTC base ROM and am experiencing a strange glitch. I would have posted this in the developers section but I have under 10 posts.
I have a Rooted S-OFF Sensation running this ROM and it works very well, exept for one thing. When my TMOUS Sensation's screen turns off, I normally can just hit the top button and the unlock screen comes right up, but sometimes, the lockscreen does not come up and I am forced to pull the battery on my phone. This happenes about once every couple of days. I have tried wiping and reflashing to no avail.
Please help.

Shenkoa said:
I am running Mike's Android Revolution HD based on HTC Sensation "non-XE" HTC base ROM and am experiencing a strange glitch. I would have posted this in the developers section but I have under 10 posts.
I have a Rooted S-OFF Sensation running this ROM and it works very well, exept for one thing. When my TMOUS Sensation's screen turns off, I normally can just hit the top button and the unlock screen comes right up, but sometimes, the lockscreen does not come up and I am forced to pull the battery on my phone. This happenes about once every couple of days. I have tried wiping and reflashing to no avail.
Please help.
Click to expand...
Click to collapse
Hi,
Which ROM are you running,and with which kernel?
Clean install,upgrade,what have you wiped before you started.
You need to provide some more information,so that you can get the correct help.

Info
Mike's Android Revolution HD based on HTC Sensation "non-XE" HTC base ROM 4.1.6, I have tried wiping using Mike's Superwipe and reflashing this version (Newest version) twice, same issue, I am running 2.6.35.14-Sensation-faux123-v0.2.3r+ Kernel and my radio version is 10.58.9035.00p_10.15.9035.02_2. I flashed the newest radio listed for this ROM, oddly, it is suposed to be 10.58.9035.00u, I use T-Mobile so that could be affecting it.
ROM - Mike's Android Revolution HD based on HTC Sensation "non-XE" HTC base 4.1.6
Kernel - 2.6.35.14-Sensation-faux123-v0.2.3r+
Radio - 10.58.9035.00p_10.15.9035.02_2
Carrier - TMOUS

Shenkoa said:
Mike's Android Revolution HD based on HTC Sensation "non-XE" HTC base ROM 4.1.6, I have tried wiping using Mike's Superwipe and reflashing this version (Newest version) twice, same issue, I am running 2.6.35.14-Sensation-faux123-v0.2.3r+ Kernel and my radio version is 10.58.9035.00p_10.15.9035.02_2. I flashed the newest radio listed for this ROM, oddly, it is suposed to be 10.58.9035.00u, I use T-Mobile so that could be affecting it.
ROM - Mike's Android Revolution HD based on HTC Sensation "non-XE" HTC base 4.1.6
Kernel - 2.6.35.14-Sensation-faux123-v0.2.3r+
Radio - 10.58.9035.00p_10.15.9035.02_2
Carrier - TMOUS
Click to expand...
Click to collapse
Hi,
Thank you.
There are known issues with that kernel.
I suggest you try the latest kernel,which you can find in my signature.
Go into recovery,
Wipe your cache partition and dalvik,
Flash the kernel,(exactly like a ROM)
reboot and enjoy.

Flashed newest Faux Kernel.
I flashed the new kernel, and I also flashed your battery mod, looks great btw
One last question, isnt my baseband suposed to be U and not P? why does it say P despite the fact I flashed the newest one for this ROM? and will it negatively affect performance?

Shenkoa said:
I flashed the new kernel, and I also flashed your battery mod, looks great btw
One last question, isnt my baseband suposed to be U and not P? why does it say P despite the fact I flashed the newest one for this ROM? and will it negatively affect performance?
Click to expand...
Click to collapse
Hi,
Glad you like the mod.
Those letters in the radio just refer to the carrier,and do not affect the performance in any way.

Thanks!
Awsome, I really really apprechiate it.
Thank you!

hey shenoka.. how is it?
I am really annoyed with this rom... I used it for my desire hd and never had a problem with it.. since I started using it on my sensation mike screwed it up massively... He is too stubborn to use the bricked kernel which rips on the faux rubbish that he is using now. I switched over to insertcoin because of this massive stuff up. So many people have complained about it and it took him this long to fix it if he hasn't already. The faux kernel is a joke and has always frozen up and have to be rebooted on me even especially in the morning when u expect the alarm to go off but the stupid faux kernel doesn't think it should go off.
And this same problem was happening for me on the de version so it definitely has to do with the kernel.
Anyways enough of my frustration has been let off about this rom. How is the new 0.2.5.2 kernel? Because I know that the 0.2.3r was rubbish for me and still did the stupid screen not turning on. I'm not going back to this rom until I am certain that the kernel won't do this same thing again.
Also has anyone noticed that with this rom u also have to sometimes fight to turn off the screen because it turns back on when u only click the power button once? Doesn't happen on insertcoin.

eddie_d4 said:
I am really annoyed with this rom... I used it for my desire hd and never had a problem with it.. since I started using it on my sensation mike screwed it up massively... He is too stubborn to use the bricked kernel which rips on the faux rubbish that he is using now. I switched over to insertcoin because of this massive stuff up. So many people have complained about it and it took him this long to fix it if he hasn't already. The faux kernel is a joke and has always frozen up and have to be rebooted on me even especially in the morning when u expect the alarm to go off but the stupid faux kernel doesn't think it should go off.
Click to expand...
Click to collapse
Why so much hate for 2 devs that are giving their wares away for FREE? There are numerous posts (today & yesterday even) on the development thread discussing how this happens, the fact that yes it is the faux kernel that has the bug, and how to install bricked if you wish.
Your frustration is understood. Isn't it nice to have so many choices of ROMs/kernels for your phone for free? I think these devs deserve more respect.

HTC one x Clean Rom installed, unresponsive lock screen

I installed Clean Rom 5.1 on my HTC one X, and it installed properly, everything was good, hone turned on alright but when it booted to the lock screen, its unresponsive to touch. the time counts up ad the bttery shows that its dying/charging but i cnt unlock the phone. anyone know how to fix this? ive tried clearing all the caches and ive tried factory resetting/system clearing but still, no movement.

Did you OTA update before rooting? to jb that is.

Is your htc a OneXL or att OneX, or perhaps yours is the international quadcore? More info please?
Sent from my HOX w/CM10.1

Does sound like you have the latest update (HBoot is version 2.14), which I have. Viper XL is working on my phone, other roms that use the stock kernel will work, though I'm not sure which ones do.

Cleanrom is ICS, you took the jb update
You will need to flash a jb sense ROM (such as viperxl) no way around it right now, sorry bro

mirGantrophy said:
Cleanrom is ICS, you took the jb update
You will need to flash a jb sense ROM (such as viperxl) no way around it right now, sorry bro
Click to expand...
Click to collapse
mirGrantrophy.... Grim or absolutegrim was easier to remember. op doesn't seem to wanna answer. Hows its going? Can i call you trophy or hows mir?
Sent from my HOX w/CM10.1

Roms that work with T-Mobile htc one s

I started this to see if anyone can list a few ROMs that work with T-Mobiles htc one s. Please help by listing the ROM you are on and by saying if the ROM has any issues; such as WiFi not working for example.
Sent from my HTC One S using xda app-developers app

I'll be first
Cm10 nightly- works excellent but it takes WiFi about 5 mins to kick in after I toggle it. If any one knows how to fix it please reply to this post
Sent from my HTC One S using xda app-developers app

I've been using $droyd$'s AOKP 4.2.2 ROM and the only issue is that as of right now, you can't record in 1080p. Other than that, its very smooth and fast.
Also if you were unaware before, wifi-calling doesn't work on any jelly bean rom.
Good luck!
Sent from my HTC One S using xda premium

tjsinghlion said:
I started this to see if anyone can list a few ROMs that work with T-Mobiles htc one s. Please help by listing the ROM you are on and by saying if the ROM has any issues; such as WiFi not working for example.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
WIFI issues are a nuance of this phone and the tmobile seems to be the most affected - it's different for each access point, user, phone, rom and firmware. In short you'll have to try it.
My tmobile worked with wifi on CM10 and CM10.1, it would not work with Viper until I downgraded my hboot (partial s-off enables some firmware write access) and flashed my wifi firmware. It get's interesting - I then put the old firmware back and the wifi still worked!!
Did you see the S-OFF thread? This will enable you to flash the radio firmware which will solve any problems.
Remember your WIFI channels - different countries use different range of channels and some access points 'helpfull' set the channel automaticlly. I have many devices that cannot cope with channel12.

Not trying to be a buzz kill here, but what's the purpose of this thread? I mean the Dev section is right over there, and the first page is flowing with fully working or close to fully working new ROMS.
Just saying.

I see what your saying. But honestly when you go through the a certain ROMs thread, they never say how WiFi doesn't work on T-Mobile phones. Or any of the problems Tmobiles users face.And who wants to go through a thread having to look for that one specific detail about a ROM whether or not to see if WiFi works. Also when looking through these ROM threads you find people that just like to say thank you (which there is nothing wrong with) that fill up the pages, making it harder to know if everything in that ROM is really going to work on your tmobile HTC one s, because people do search through comments to see what the users say. Therefore I made this thread for all T-Mobile users who want to post and say whether their ROM they are using works perfectly or if they are experiencing problems. And who wants to go through the process of flashing a new ROM without even knowing whether something like WiFi works. So yeah that's why i made this thread
Sent from my HTC One S using xda app-developers app

I get that, ROM posts can be a little all over the place sometimes. I didn't understand at first; I'm one of the few T-Mo users with pretty much no problems. It also doesn't help that the ROM database that some guy did in the Dev section hasn't been updated for some time.

Thankyou
skyline93r34 said:
I've been using $droyd$'s AOKP 4.2.2 ROM and the only issue is that as of right now, you can't record in 1080p. Other than that, its very smooth and fast.
Also if you were unaware before, wifi-calling doesn't work on any jelly bean rom.
Good luck!
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Ok thank you. Now i think im going to go Flash that rom. And also did you do anything specific to get your wifi working. and what Hboot are you on

If you are S-ON and have high HBOOT and want a Sense-based ROM with working WiFi, you were looking at TrickDroid 7 (TMOUS based), Unknown Retribution, and I think one more (Energy Blue, IIRC) that were based on recent updates. Since they were all based on the TMOUS ROM, everything should work without doing anything super special, including WiFi-calling. Virtuous Ville+ also had working WiFi, but no WiFi-calling. Recent CM 10.1 nightlies are working really well. At least, those are the ROMs I've used.

ardax said:
If you are S-ON and have high HBOOT and want a Sense-based ROM with working WiFi, you were looking at TrickDroid 7 (TMOUS based), Unknown Retribution, and I think one more (Energy Blue, IIRC) that were based on recent updates. Since they were all based on the TMOUS ROM, everything should work without doing anything super special, including WiFi-calling. Virtuous Ville+ also had working WiFi, but no WiFi-calling. Recent CM 10.1 nightlies are working really well. At least, those are the ROMs I've used.
Click to expand...
Click to collapse
Wait are you saying that Recent cm10.1 nightlies have wifi working on our device. and by wifi working i mean it automatically turns on, and not just hangs and turns on later .

I haven't had any WiFi hangs.

I just started using Liquid Smooth. Pretty nice IMO. The only issues I've notcied were a bluetooth hang that fixed after a reboot, and Voice search keeps crashing.

ardax said:
I haven't had any WiFi hangs.
Click to expand...
Click to collapse
so let me ask you a question. What radio are you on. And also what HBOOT version are you running

tjsinghlion said:
so let me ask you a question. What radio are you on. And also what HBOOT version are you running
Click to expand...
Click to collapse
Right now I'm on Viper 2.1.0 with the full firmware from the 3.16 WWE OTA -- I only made that jump because S-OFF makes it easy to switch without having to downgrade HBOOT. So HBOOT is 2.15 and Radio is 1.11.50.05.28. But I've just started using that and can't give you much in the way of impressions on WiFi stability yet. Just flashed it last night and didn't have any WiFi problems downloading my apps last night or weather checks this morning.
Before that I was using a recent CM 10.1 nightly on the TMOUS 2.35.531.10 firmware. So HBOOT 1.14 and 1.11t. I ran that firmware combination from shortly after its release until flashing Viper. ROMs in use were either CM 10.1 nightlies or Unknown Retribution (TMOUS 2.35 based).

ardax said:
Right now I'm on Viper 2.1.0 with the full firmware from the 3.16 WWE OTA -- I only made that jump because S-OFF makes it easy to switch without having to downgrade HBOOT. So HBOOT is 2.15 and Radio is 1.11.50.05.28. But I've just started using that and can't give you much in the way of impressions on WiFi stability yet. Just flashed it last night and didn't have any WiFi problems downloading my apps last night or weather checks this morning.
Before that I was using a recent CM 10.1 nightly on the TMOUS 2.35.531.10 firmware. So HBOOT 1.14 and 1.11t. I ran that firmware combination from shortly after its release until flashing Viper. ROMs in use were either CM 10.1 nightlies or Unknown Retribution (TMOUS 2.35 based).
Click to expand...
Click to collapse
noob question- What do you mean by TMOUS 2.35 based. And how does that affect the cm10.1 nightly

I mean ROMs that were built using T-Mobile US's 2.35 ROM as a base. Other Sense-based ROMs, like Viper, start with different ROMs as a base. The different Sense bases are part of the reason people run into WiFi problems when using ROMs originally created for other regions.
CM 10.1 has an entirely different heritage so it has its own ways of dealing with those issues.

tjsinghlion said:
Ok thank you. Now i think im going to go Flash that rom. And also did you do anything specific to get your wifi working. and what Hboot are you on
Click to expand...
Click to collapse
I'm on hboot 1.09 and the wi-fi worked right from the start.
p.s. sorry for the slow reply

Gotta Tell you the Viper 2.1.0 rocks...its fast awesome battery life and its got working wifi...not wifi calling but just wifi in general...it honestly is the best sense ROM...I have tried CM 10, Virtuous Ville+, P.A.C Man and even the ICS ROMs and I gotta say the Venom team makes an awesome product...:laugh:

"[rom][S4][15FEB]Updated_4.2.2_AOKP-Working-video" seems to work great with TMOUS hboot 1.14, added the new camera (in the post) with photosphere, The only little bug I found is the bluetooth doesn't list station info on my car stereo. I saw a tearing fix using bubba kernel, but I'm just living with it for now. Everything else seems to work great!

I just flashed the LiquidSmooth JB ROM from Droyd and this thing is amazing.. Coming from a rooted Stock Sense there really is no comparison, I might give Viper a try but this is clearly gonna be my daily driver

Data disconnecting only on Sense Roms

So I decided to flash cm Rom to see if my data would stop disconnecting. And it worked. Had data without any problems.
But when I went back sense data started to disconnect again.
Any opinions?
Sent from my HTC One S using Tapatalk 2

No-one ?
Sent from my HTC One S using Tapatalk 2

First thing that comes to mind that it might be a radio issue. CM for example uses 1.08t version of the radio as stock JB (and Sense roms based on that) use a newer version (mine seems to be 1.11). Kernel is also a possible troublemaker in these kind problems. Could you give some more details? Which roms you're trying?
Sent from my One S. Please hit thanks if I helped.