I recently tried out the Tiamat 1.1 kernel on MIUI 1.8.5 to see if it would alleviate the low in-call volume issue that is prevalent on AOSP roms. When i did, my wifi would only return an "error" status when i turned it on. I remember vaguely seeing where someone referenced that the iptables might be causing issues, but the problem doesn't seem to be widespread. Reflashing after wiping dalvik vm cache and system cache didn't help. Anyone else having this issue?
Related
I would like to know if anyone else has experienced similar issues using any of the MIUI roms?
If you have experienced this how did you remedy the situation?
So here is the story:
I was never keen on using MIUI roms as i am a fan of sense, but lately i have been growing tired of sense and have been looking for greener pastures.
My device is rooted(S-On, pvt-3, 0.93 hboot) and i have been running plenty of custom(sense based) roms with no trouble. Last night i flashed Pays MIUI rom and the phone was rebooting evey few minutes ... so i decided to call it a night and went to bed ... then this morning i went to the MIUI site and downloaded the latest 0.12.24(or something) and the phone was running smoothly the whole day without any hicups ... or reboots ... yes you guessed it ... now its rebooting again!
I dont think its the hardware on my device as i havnt experienced any problems with any other roms, and i perform a full wipe each time i flash.
Any advice would be greatly appretiated, thanx in advance!
Try flashing this kernel:
http://forum.xda-developers.com/attachment.php?attachmentid=472705&d=1293232742
it could be that the HAVS kernel is causing your problems. This is a SVS kernel and should be more stable for some people.
Wipe dalvik cache after you flashed the kernel (same way as flashing rom). Disable verfication before flashing.
Lennyz1988 said:
Try flashing this kernel:
http://forum.xda-developers.com/attachment.php?attachmentid=472705&d=1293232742
it could be that the HAVS kernel is causing your problems. This is a SVS kernel and should be more stable for some people.
Wipe dalvik cache after you flashed the kernel (same way as flashing rom). Disable verfication before flashing.
Click to expand...
Click to collapse
Thank you for the reply ... i also thought it might have something to do with the kernal, will flash after the phone has charged ... will post results!
Hi all,
I own a Desire GSM version and been running a pre-rooted stock ROM for quite a while and have been very happy with it. I have been running this with an ext3 partition and ran app2sd+ script to make use of it. All good.
My sense of curiosity got stronger and always wanted to try a custom ROM so I tried Cyanogenmod 7 RC1 on Monday.
I have been running the latest Radio (32.49.00.32U_5.11.05.27) so didn’t have to update that for CM7.
I formatted the DATA as well as the CACHE before flashing the CM7 ROM, then applied GAPPS to the ROM then restarted the phone.
All went OK and I loved this new ROM, except that I have been experiencing very strange connection issues whether I am on WiFi or 3G (Vodafone AU). The phone will establish connection; however sometimes will not be able to get data out of a request as simple as getting emails, opening a webpage through the stock browser etc …
The workaround to that was to tun off wifi and turn it back on, same for 3G …
I re-flashed numerous times the ROM (formatting the CACHE/DATA each times) but was still experiencing these issues, when sometimes I couldn’t even set my Google account at the first start of the phone…
After a couple of days of scratching my head I did find a potential solution that was suggesting updating the /system/lib/libhtc_ril.so file with the one provided in the nightly build. This had no effect what so ever to the situation.
I then decided to go back to FroYo () so re-flashed the pre-rooted ROM, but then I experienced the exact same issue!! I then re-flashed the Radio ROM thinking this may have been affected by all these changes but no changes at all …
I am a bit at a loss here and don’t know how to fix that really …
Is there any setting that resides on the phone relating to Radio ROM even if I format both Data and Cache each time I flash the ROM??
Thanks for your help guys.
Any ideas on this issue at all ??
Hi, I'm fairly new to this sort of thing, that is, rooting my phone and messing with ROMs and Kernels, but I seem to be having an issue.
I have MIUI 1.11.4 installed, with the Tiamat 1.1.5 kernel. My problem is that I have no data. My 1x/3G is gone, and I'm not sure what I did wrong.
If someone could talk me through the steps needed to have the MIUI ROM and Tiamat Kernel and Data working simultaneously, I would be most grateful.
Here is what I have been doing:
1. Boot to recovery.
2. Factory reset/wipe.
3. Install MIUI from .zip.
4. Reboot.
5. Wait 10 minutes or so.
6. Boot to recovery.
7. Clear Cache.
8. Install Tiamat 1.1.5 from .zip.
9. Reboot.
10. Scratch my head, wondering where my data went.
Well that's been a problem that has been around since about the last three updates. If your looking for a good alternative here's a couple
rootzwiki.com/topic/7717-kernel-aeroevan-vivow-kernels-for-aosp/[/url]
rootzwiki.com/topic/7911-kernelvivow-kernel-core-betas/[/url]
I personally use areoevan because the last time I tried the core beta one, setcpu didn't play well with it. But back to your question I don't think anyone has found a fix for the tiamat issue.
Thanks, I'm using the aeroevan now. It seems to be working well enough.
I've been using aeroevan's 0.4 kernel with MIUI 10.21 for some time now and I had no loss of data and battery life is awesome
So far, MIUI 1.11.4 with Aeroevan 0.6 is working fantastically. Any errors I have encountered were self-inflicted.
Sent from my MIUI-ed Incredible 2, using xda premium.
I too encountered this problem with MIUI and Tiamat Kernel. All of a sudden i couldn't get a data connection at all....everything had to be wifi.
How did i solve the problem? since I have Verizon's unlimited data plan, all i did was go to the monitor app and increase the allowed monthly data to 200 GB.
Have had no issues since.
Note: Don't know if this is the EXACT same issue you were having, but that's how i fixed it for me.
Hi all,
I've been having an issue and I cannot figure it out. While using my phone the screen will freeze. On screen and physical buttons will not respond. The only way to solve this has been battery pull.
Its happened across different ROMs and kernels (all jelly bean based if that makes a difference) including aokp unofficial nightlies, cm10 official nightlies, and stock, air, and popcorn kernels. I have done factory reset to wipe data/cache and wiped dalvik (came from og droid and that's been my habit) but the problem persists. I read somewhere about reboots being caused by permissions issues, but I ran fix permissions in CWM to no avail.
Could anyone offer advice/suggestions/solutions?
I've recently had my notification LED stop working, the only time it lights up is when I receive a call. I'm running AOKP JB-MR1 milestone 1 with lean kernel, and when I attempt to test the LED in the rom settings, nothing happens. LightFlow doesn't work either (though it used to). Is anyone else having this issue?
Nope can't really say cause i'm not running aokp last time i ran aokp it was on ics you could try clearing caches and dalvik through recovery and trying again :-S or dirty flash your rom +gapps might be helpful
This issue has persisted through multiple factory resets and clearing cache, etc., never thought to dirty flash, but again it's still around after installing roms and factory resets