Develop Bugs

HDMI Mirroring in MIUI Help

Hey kids. I'm trying to get HDMI mirroring going so as to use my variety of emulators on my TV. Only problem is i can't figure out how to mirror the display with MIUI.
So far, i've tried HDMIwin, no luck. I tried flashing the Tiamat kernel, no luck. Tried Tiamat with HDMIwin, no luck.
The strange part is in each case, the TV would switch from no signal to a black screen as if it were connected to something, but it never displayed a picture.
What am i doing wrong??

Did you update the binary? It prompts you at the beginning when first loading HDMwIn. I am mirroring with no issues using the latest MIUI with Tiamat's latest kernel.
Sent from my PC36100.

I'm not really sure what you mean! I simply flashed the new kernel Zip and rebooted. Did i miss a step?

SilverStone641 said:
I'm not really sure what you mean! I simply flashed the new kernel Zip and rebooted. Did i miss a step?
Click to expand...
Click to collapse
Ok.
Try flashing Tiamat's 4.1.0 or 3.3.7, they have been great for me, they all are. Clear Data on HDMwIn and Force Stop the app, or just uninstall and then reinstall from the Market again.
Plug in your cable and then when you first run HDMwIn. It will give you an option to "Update to the latest Binary," if I am not mistaken, you have to accept and then that is it. Press "Start Mirroring" and under "Advance Options" make sure "Route Audio to HDMI" is checked, you know, to make sure you get the audio out of the TV set.
One more thing you can do is clearing Dalvik and Cache before reinstalling HDMwIn.
Hope that helps.

It worked!! You rock!!
As soon as i uninstalled HDMIwin, reinstalled, it fired right up. Thank you so much!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

May have spoke too soon. I'm getting some weird results. It seems that HDMI only works after I uninstall, or reinstall HDMIwin. As soon as my phone hits standby, i lose HDMI and i have either add or remove HDMIwin. No clue what the connection is.

SilverStone641 said:
May have spoke too soon. I'm getting some weird results. It seems that HDMI only works after I uninstall, or reinstall HDMIwin. As soon as my phone hits standby, i lose HDMI and i have either add or remove HDMIwin. No clue what the connection is.
Click to expand...
Click to collapse
Under "Advance Options" make sure to check "Keep Screen On" and also make sure you plug in the charger. You will need it.

Gotcha. But if it's only the screen falling asleep, why is the connection still broken when i wake the phone?

SilverStone641 said:
Gotcha. But if it's only the screen falling asleep, why is the connection still broken when i wake the phone?
Click to expand...
Click to collapse
Have not a clue. I have not experienced the same issue. I have been on CM7 and just now MIUI and I have not had a problem. I have been playing a lot of N64 ROMs and Plants v Zombies and have not had that issue. Are you under clocking the CPU?

Nope. No overclocking. Just running the V6 super-charger script.

SetCpu issue

I'm not sure if this is normal behavior or not but ill have my max and min values set and when I leave the app and come back to, the value sliders will still be set but it will display the min as 384.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't recall it doing this before, unless I just never noticed. But I did a restore and also reflashed the kernal and it has not solved it!
I also tried Cpu Tuner and it did the same thing! What would be causing this?
"Edit - I forgot to add I'm on juggernaut 4.1 with bullet kernel"
Tap-A-Talkin it ... Galaxy S ii

Try un-installing set cpu. Boot into recovery and wiping data cache and dalvik. Then fix permissions. Reboot and re-install set cpu.

Thanks for the reply!
I just tried the method stated above and it Is still doing the same thing! I'm stumped! I really hope its not a hardware failure!
When adjusting clock speed with setcpu does this change the frequency for both processors? I'm wondering if the second processor is causing this issue.
While looking at the info tab in setcpu it lists processor 0, and processor 1 every once in awhile processor 1 dissappears from the screen. I'm assuming that's normal behavior though since both cpus aren't being used at all times and I guess its going into standby.

Try faux clock instead of setcpu.

Alright I wiped cache and dalvik once again fixed permissions amd than installed faux clock and still the same thing.
I'm really starting to think my SGS2 has a bad cpu.
I set the values to this, exited the app, reloaded the app and minimum was back down to 384
Sent from my SGH-T989 using Tapatalk

I remember I had an issue something like this. I had to do a wipe data/factory reset in recovery to fix it. You could back up your apps and try that. I know its a pain tho.

I still have not figured out what's going on, I have tried everything I can think of. I've even odin back to stock, updated latest firmware from kies, reflashed juggs... nothing has changed this behavior.
Even using fauxclock, if I set both min and max frequencies to the same setting when I exit the app and re open the app, the max frequency is where I set it to. but the min frequency goes back to 384. Anyone elses do this?
This is my first time owning a dual core phone and I'm beginning to think its normal! Might be panicked for no reason!
Tap-a-Talkin it.... Galaxy S !!

Is there a reason you want your minimum frequency so high? 384 is normal.
Sent from my SGH-T989 using xda premium

No reason, I just found it strange and was thinking there was a problem with the hardware, but I actually did a few test on it tonight and it's working, So I can rest easy!
Tap-a-Talkin it.... Galaxy S !!

Chainfire3D working:

REQUIRES ROOT.
I figured this deserves its own thread in here.
I had Chainfire3D purchased for my old myTouch 4G/HTC Glacier. I installed it on this device but was a bit worried about it doing some damage, so I made sure to do a nandroid backup before I even went with this experiment.
First thing you have to do is have C3D install its drivers which comes with a dire warning about it causing your phone not to boot. The installation will reboot your machine automatically.
The reboot took a few moments longer than usual, but it booted fine, and has since rebooted as normal since.
I tried Asphalt 6, which I also purchased some time ago for my Transformer tablet, and no dice. I went into C3D and installed the Nvidia emu that's attached below, and set it on a per-app basis against Asphalt 6, and voila! Runs perfect with no issues. Also, since our phones res is high, it looks even better than ever did on the Glacier.
Secondly, I used the market fix within C3D, and I can now view content not normally seen with our devices, as you can see below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
^ Runs and plays fine as well.
I had both emulator files attached, which you install by placing them in the internal SD. I used the "install plugin" option within C3D, and it scanned the SD card automatically for these files.
Fair warning: again, I did a nandroid backup on my machine prior to this. I also took a risk with the plugins, since they were designed for my Glacier's single-core Qualcomm. The risk paid off for me, but I won't take responsibility for anyone else's machine.
I am running stock rooted with the Adama003 kernel.

Sweet! Works great for me. I have a bunch of Tegra games from when I had my Droid X2.
Sent from my SCH-I535 using Tapatalk 2

Weird, it boot looped on my phone

freeza said:
Weird, it boot looped on my phone
Click to expand...
Click to collapse
Sorry to hear that. Was this ever resolved?

Thank you for testing and posting this ...
I loved Chainfire3D, if only for Nightmode and CF Lumen, since I don't play games on my phone ...
On my Droid X2, I had to disable screen animations or Chainfire would obliterate the screen/notification bar when rotating from portrait to landscape view. Is this still the case?

pdinphx said:
On my Droid X2, I had to disable screen animations or Chainfire would obliterate the screen/notification bar when rotating from portrait to landscape view. Is this still the case?
Click to expand...
Click to collapse
I have no such issues on my GS3.

Tested and working great on my T-Mobile GS3. Thank you
Sent from my SGH-T999 using Tapatalk 2

Everything is working great, but what is the powervr plugin?

Not charging as quickly as used to since Cyanogenmod 11 Nightly flash

Hello,
Not sure if I am supposed to (allowed to?) ask for help or troubleshooting on Nightlies. ^_^' So sorry if I am doing something wrong. I'm fairly new and have only really helped a couple of people fix stuff here on XDA.
I have an LG Optimus G pro e980 running cm-11-20140425-NIGHTLY which is Android 4.4.2 KitKat. When I flashed it I factory reset, cleared cache, cleared dalvik cache, and flashed the ROM and flashed Gapps. When the ROM booted up I didn't do a second factory reset, don't know if this is bad. Here is the tutorial I followed. http://true-android.blogspot.com/2013/12/update-lg-optimus-g-pro-e980-to-android_10.html I still have excellent battery life, it just doesn't charge as quickly as it used to. I think the battery life is actually better with Cyanogen.
I was having terrible battery life but it was because I had setCPU holding the CPU at 1.7ghz constantly, and CleanMaster wouldn't allow the phone to deep sleep. I can deep sleep now and have resolved all battery drainage issues.
Here's screens of CPU
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://sta.sh/0171wdoktq5v (images weren't showing for me so these are the links)
That is after 23 hours uptime.
http://sta.sh/0272iovco1ib
http://sta.sh/0x3evjyycsq
On stock ROM I could 100% the phone in 45 minutes to an hour from like 20-30% range. it would take only a few minutes when I was around 85%. It charged ridiculously fast and I loved it. Now on Cyanogenmod it takes 6-8+ hours to charge. I find myself tied to a charger all day now. Sometimes when I put it on the charger at night and wake up it'll only be at like 94%. I did some research and I think it might be the kernel changing the voltage regulator's amperage limit. I don't know if this is the issue, or how to go about fixing it. I haven't flashed a kernel myself (at least I don't think so). Kernels are new to me. Perhaps there is an app to change the voltage regulator's setting, or a different kernel? or maybe it's just a problem with the Nightly and it will be resolved eventually? Seriously this is almost enough to make me go to the stock ROM again, lolxd.
Also, I get the message every few minutes "Unfortunately, Google+ has stopped responding". Could be this be because I didn't do the second factory reset?
Thanks, the best.

Bad flash? Have you tried a clean install?
Sent from my LG-E980 using XDA Premium 4 mobile app

stulzerl said:
Bad flash? Have you tried a clean install?
Sent from my LG-E980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did a clean install and it is still charging much slower than it was on the stock ROM. The "Unfortunately, Google+ has stopped" error is gone though. That's good. ^_^ Think it's just because KitKat draws in too many system resources? Then again my battery life is still great as far as I can tell... Hmm...

working
Thought I would update on this. It's working now.
Thanks for the advice on flashing again as that solved a lot of problems i was having.
It seems to have sorted itself out over time, though. It's charging just as quickly as ever now. (If not faster than ever). It probably just needed a few charge/discharge cycles for the new ROM to adjust to the battery capacity. Thanks for the help, though. ^^

Anybody kernel tweaking?

I wasn't interested, really. Phone runs fine. But, I came across some stuff, was reading, decided to try ktweak. I'm running Lineage 17.1 on my edge. Seems to be no problem and if I noticed anything at all thus far it's maybe a bit more battery life. I wouldn't swear to it, though, hasn't really been long enough. Also, it could be that SD Maid was faster when listing all the phone's apps in the appcontrol section, which is something I would care about. The edge was already pretty fast in that the apps listed in about 2.3 seconds. Seems to be just under 2 now. Could be wishful thinking, I dunno.
THere's lots to do if you get into tweaking your kernel - that's a big rabbit hole, and I'm just not that geek anymore. Ktweak is just a script, it just runs that one time to make its changes. It won't survive a reboot, but, there's an apk for an interface that lets you toggle to run at every boot.
THere's already a ton of info about it so I won't throw my ignorance in. Just wondering if anyone else decided to make a few kernel changes, or, is maybe using this script. You can see the tweaks here.

I noticed an error since utilizing this script. Coincidence or not, I dunno. 3C all-in-one has a cache feature for the 'drives' on your phone. You can increase it following a quick test. I have done it in the past on this phone and ROM, without ill effect. I had a 'download' error yesterday in Firefox and in Aurora. I didn't a few days ago, so I reset the cache option to default in 3C, rebooted, and the download error was gone.
I set the cache option in 3C after I ran this script.
It's all anecdotal to this point, but maybe the 3C cache setting doesn't play well with the default hacks this script performs. I didn't even look, I don't even care - it's just a thing I noticed and currently all is well.
Since utilizing the kernel mods set by this script I haven't really noticed anything different in real-world usage in the phone, other than mentioned. It has always been responsive, fast, it runs really well with Lineage, it ran well with stock, too. I'm not performing experiments or anything remotely similar, I am just using the phone as normal.
What is interesting is that I got almost 4 days out of my last charge. That is definitely an improvement. It's not that big a deal, really. The phone gets 2 days anyway and I have a routine that alleviates battery/charge concerns.
4 days, 6 hours+. That's something.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}