The app can control pretty much everything on your phone plus it had an app manager way better than titanium IMO
[ROM][ICS][FINAL](2/25/13) MIUI 3.2.22 - Closing For Business
The app can control pretty much everything on your phone plus it had an app manager way better than titanium IMO
Very cool app...and I'll probably keep it in my arsenal, but I don't see settings for the GPU stuff in CPU master Pro or undervolt.
I'm sure if ya hit him up he'll put it in there he is very responsive and is always adding more features
Re: Launcher force closing
This kept happening to me after installing new apps from Google Play, and only after the build where launcher columns were set to 5 as the default. I managed to fix it by moving my apps/widgets into the "normal" 4x4 area, setting the launcher to 4x4, and restarting the launcher app.
Haven't had any problems since. I think the launcher occasionally freaks out when trying to place an icon (from a new app install) outside the normal 4x4 region.
Edit: Oh yeah, FANTASTIC job on this rom dude. I've been doing the ICS/Sense shuffle for the past few months, but your MIUI build broke the vicious cycle. Hell, if you get PRL updates working, I'll have zero reason to ever see Sense again.
This kept happening to me after installing new apps from Google Play, and only after the build where launcher columns were set to 5 as the default. I managed to fix it by moving my apps/widgets into the "normal" 4x4 area, setting the launcher to 4x4, and restarting the launcher app.
Haven't had any problems since. I think the launcher occasionally freaks out when trying to place an icon (from a new app install) outside the normal 4x4 region.
Edit: Oh yeah, FANTASTIC job on this rom dude. I've been doing the ICS/Sense shuffle for the past few months, but your MIUI build broke the vicious cycle. Hell, if you get PRL updates working, I'll have zero reason to ever see Sense again.
Last edited:
You can backup/delete the gb keyboard with Titanium and won't have that issue...
How about I just remove it, and include only ICS keyboard and swype by default?
Got the camera fixed on lockscreen...just had to tell it which app to look for by default.
Working out the bugs now in the weather too...I'm going to rip apart a theme for 9s right now and see if I can't find the proper api calls for the weather values.
Agreed. Good news for us is that someone is already working on that. I can't wait.
Evolution is speaking using XDA Premium
---------- Post added at 05:38 PM ---------- Previous post was at 05:13 PM ----------
I use swiftkey and swype so I wouldn't mind at all
About the camera, makes sense. Thanks.
The random 1 unread message glitch disappeared after I deleted all my messages. I'll let you know if it happens again. Weird because I went through every thread in Go SMS to make sure I hadn't just overlooked one. Maybe it was caused when I switched over from stock to Go SMS and I chose to disable the notifications from stock.
Thank you for the bug fixes.
Hopefully we can get the battery issue figured out soon.
Dude its nice its a good miui/aosp rom love it better then the other miui roms out there.
Bluetooth is force closing randomly again but it still connects to both phone audio.
E/AndroidRuntime( 4132): FATAL EXCEPTION: main
E/AndroidRuntime( 4132): java.lang.NoSuchMethodError: android.bluetooth.BluetoothAdapter.listenUsingEncryptedRfcommOn
E/AndroidRuntime( 4132): at com.android.bluetooth.pbap.BluetoothPbapService.initSocket(BluetoothPbapService.java:336)
E/AndroidRuntime( 4132): at com.android.bluetooth.pbap.BluetoothPbapService.startRfcommSocketListener(BluetoothPbapService.java:313)
E/AndroidRuntime( 4132): at com.android.bluetooth.pbap.BluetoothPbapService.access$900(BluetoothPbapService.java:61)
E/AndroidRuntime( 4132): at com.android.bluetooth.pbap.BluetoothPbapService$1.handleMessage(BluetoothPbapService.java:569)
E/AndroidRuntime( 4132): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 4132): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 4132): at android.app.ActivityThread.main(ActivityThread.java:3703)
E/AndroidRuntime( 4132): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 4132): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime( 4132): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime( 4132): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime( 4132): at dalvik.system.NativeStart.main(Native Method)
I/ActivityManager( 629): Process com.android.bluetooth (pid 4132) has died.
W/ActivityManager( 629): Scheduling restart of crashed service com.android.bluetooth/.opp.BluetoothOppService in 5000ms
W/ActivityManager( 629): Scheduling restart of crashed service com.android.bluetooth/.pbap.BluetoothPbapService in 15000ms
I/TelephonyRegistry( 629): notifyServiceState: 0 home Sprint Sprint 31000 EvDo rev. A CSS supported 25 4151RoamInd: 128DefRoamInd: 1EmergOnly: false
W/InputManagerService( 629): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@40b45e88
I/ActivityManager( 629): Start proc com.android.bluetooth for service com.android.bluetooth/.opp.BluetoothOppService: pid=4314 uid=10007 gids={3003, 3002, 3001, 1015}
I/TelephonyRegistry( 629): notifyServiceState: 0 home Sprint Sprint 31000 EvDo rev. A CSS supported 25 4151RoamInd: 128DefRoamInd: 1EmergOnly: false
E/AndroidRuntime( 4314): FATAL EXCEPTION: main
E/AndroidRuntime( 4314): java.lang.NoSuchMethodError: android.bluetooth.BluetoothAdapter.listenUsingEncryptedRfcommOn
E/AndroidRuntime( 4314): at com.android.bluetooth.pbap.BluetoothPbapService.initSocket(BluetoothPbapService.java:336)
E/AndroidRuntime( 4314): at com.android.bluetooth.pbap.BluetoothPbapService.startRfcommSocketListener(BluetoothPbapService.java:313)
E/AndroidRuntime( 4314): at com.android.bluetooth.pbap.BluetoothPbapService.access$900(BluetoothPbapService.java:61)
E/AndroidRuntime( 4314): at com.android.bluetooth.pbap.BluetoothPbapService$1.handleMessage(BluetoothPbapService.java:569)
E/AndroidRuntime( 4314): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 4314): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 4314): at android.app.ActivityThread.main(ActivityThread.java:3703)
E/AndroidRuntime( 4314): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 4314): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime( 4314): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime( 4314): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime( 4314): at dalvik.system.NativeStart.main(Native Method)
I'm also adding some pictures regarding my battery use as promised.
I don't know if its just me but even with everything stripped down, battery still seems to be draining.
E/AndroidRuntime( 4132): FATAL EXCEPTION: main
E/AndroidRuntime( 4132): java.lang.NoSuchMethodError: android.bluetooth.BluetoothAdapter.listenUsingEncryptedRfcommOn
E/AndroidRuntime( 4132): at com.android.bluetooth.pbap.BluetoothPbapService.initSocket(BluetoothPbapService.java:336)
E/AndroidRuntime( 4132): at com.android.bluetooth.pbap.BluetoothPbapService.startRfcommSocketListener(BluetoothPbapService.java:313)
E/AndroidRuntime( 4132): at com.android.bluetooth.pbap.BluetoothPbapService.access$900(BluetoothPbapService.java:61)
E/AndroidRuntime( 4132): at com.android.bluetooth.pbap.BluetoothPbapService$1.handleMessage(BluetoothPbapService.java:569)
E/AndroidRuntime( 4132): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 4132): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 4132): at android.app.ActivityThread.main(ActivityThread.java:3703)
E/AndroidRuntime( 4132): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 4132): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime( 4132): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime( 4132): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime( 4132): at dalvik.system.NativeStart.main(Native Method)
I/ActivityManager( 629): Process com.android.bluetooth (pid 4132) has died.
W/ActivityManager( 629): Scheduling restart of crashed service com.android.bluetooth/.opp.BluetoothOppService in 5000ms
W/ActivityManager( 629): Scheduling restart of crashed service com.android.bluetooth/.pbap.BluetoothPbapService in 15000ms
I/TelephonyRegistry( 629): notifyServiceState: 0 home Sprint Sprint 31000 EvDo rev. A CSS supported 25 4151RoamInd: 128DefRoamInd: 1EmergOnly: false
W/InputManagerService( 629): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@40b45e88
I/ActivityManager( 629): Start proc com.android.bluetooth for service com.android.bluetooth/.opp.BluetoothOppService: pid=4314 uid=10007 gids={3003, 3002, 3001, 1015}
I/TelephonyRegistry( 629): notifyServiceState: 0 home Sprint Sprint 31000 EvDo rev. A CSS supported 25 4151RoamInd: 128DefRoamInd: 1EmergOnly: false
E/AndroidRuntime( 4314): FATAL EXCEPTION: main
E/AndroidRuntime( 4314): java.lang.NoSuchMethodError: android.bluetooth.BluetoothAdapter.listenUsingEncryptedRfcommOn
E/AndroidRuntime( 4314): at com.android.bluetooth.pbap.BluetoothPbapService.initSocket(BluetoothPbapService.java:336)
E/AndroidRuntime( 4314): at com.android.bluetooth.pbap.BluetoothPbapService.startRfcommSocketListener(BluetoothPbapService.java:313)
E/AndroidRuntime( 4314): at com.android.bluetooth.pbap.BluetoothPbapService.access$900(BluetoothPbapService.java:61)
E/AndroidRuntime( 4314): at com.android.bluetooth.pbap.BluetoothPbapService$1.handleMessage(BluetoothPbapService.java:569)
E/AndroidRuntime( 4314): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 4314): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 4314): at android.app.ActivityThread.main(ActivityThread.java:3703)
E/AndroidRuntime( 4314): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 4314): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime( 4314): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime( 4314): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime( 4314): at dalvik.system.NativeStart.main(Native Method)
I'm also adding some pictures regarding my battery use as promised.
I don't know if its just me but even with everything stripped down, battery still seems to be draining.
Last edited:
Bluetooth is force closing randomly again but it still connects to both phone audio.
E/AndroidRuntime( 4132): FATAL EXCEPTION: main
E/AndroidRuntime( 4132): java.lang.NoSuchMethodError: android.bluetooth.BluetoothAdapter.listenUsingEncryptedRfcommOn
E/AndroidRuntime( 4132): at com.android.bluetooth.pbap.BluetoothPbapService.initSocket(BluetoothPbapService.java:336)
E/AndroidRuntime( 4132): at com.android.bluetooth.pbap.BluetoothPbapService.startRfcommSocketListener(BluetoothPbapService.java:313)
E/AndroidRuntime( 4132): at com.android.bluetooth.pbap.BluetoothPbapService.access$900(BluetoothPbapService.java:61)
E/AndroidRuntime( 4132): at com.android.bluetooth.pbap.BluetoothPbapService$1.handleMessage(BluetoothPbapService.java:569)
E/AndroidRuntime( 4132): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 4132): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 4132): at android.app.ActivityThread.main(ActivityThread.java:3703)
E/AndroidRuntime( 4132): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 4132): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime( 4132): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime( 4132): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime( 4132): at dalvik.system.NativeStart.main(Native Method)
I/ActivityManager( 629): Process com.android.bluetooth (pid 4132) has died.
W/ActivityManager( 629): Scheduling restart of crashed service com.android.bluetooth/.opp.BluetoothOppService in 5000ms
W/ActivityManager( 629): Scheduling restart of crashed service com.android.bluetooth/.pbap.BluetoothPbapService in 15000ms
I/TelephonyRegistry( 629): notifyServiceState: 0 home Sprint Sprint 31000 EvDo rev. A CSS supported 25 4151RoamInd: 128DefRoamInd: 1EmergOnly: false
W/InputManagerService( 629): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@40b45e88
I/ActivityManager( 629): Start proc com.android.bluetooth for service com.android.bluetooth/.opp.BluetoothOppService: pid=4314 uid=10007 gids={3003, 3002, 3001, 1015}
I/TelephonyRegistry( 629): notifyServiceState: 0 home Sprint Sprint 31000 EvDo rev. A CSS supported 25 4151RoamInd: 128DefRoamInd: 1EmergOnly: false
E/AndroidRuntime( 4314): FATAL EXCEPTION: main
E/AndroidRuntime( 4314): java.lang.NoSuchMethodError: android.bluetooth.BluetoothAdapter.listenUsingEncryptedRfcommOn
E/AndroidRuntime( 4314): at com.android.bluetooth.pbap.BluetoothPbapService.initSocket(BluetoothPbapService.java:336)
E/AndroidRuntime( 4314): at com.android.bluetooth.pbap.BluetoothPbapService.startRfcommSocketListener(BluetoothPbapService.java:313)
E/AndroidRuntime( 4314): at com.android.bluetooth.pbap.BluetoothPbapService.access$900(BluetoothPbapService.java:61)
E/AndroidRuntime( 4314): at com.android.bluetooth.pbap.BluetoothPbapService$1.handleMessage(BluetoothPbapService.java:569)
E/AndroidRuntime( 4314): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 4314): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 4314): at android.app.ActivityThread.main(ActivityThread.java:3703)
E/AndroidRuntime( 4314): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 4314): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime( 4314): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime( 4314): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime( 4314): at dalvik.system.NativeStart.main(Native Method)
I'm also adding some pictures regarding my battery use as promised.
I don't know if its just me but even with everything stripped down, battery still seems to be draining.
Are ROM Toolbox and SetCPU both set to control the governor?
That is some pretty bad battery drain there...far worse than anything I've ever experienced.
One thing...you should set your low frequency to be much lower. With it set at 700, it's never going to throttle lower than 700mhz. Drop it all the way, set your OC a little higher, and see if that helps. It's possible that if you don't give the governor some headroom, it has problems.
Edit: I also looked up the issue with Alarm Manager causing wakelock...
It says here that a dalvik/cache wipe may fixe the problem.
http://xdaforums.com/showthread.php?t=1221733
Last edited:
I was thinking about it. As there don't appear to be any glaring errors with this build (outside the usual BT), I may take a little more time to add more thorough features.
I've already done a total rewipe of the base (AGAIN). Shaved some 50MB off the install size. This also allowed me to have a unified base so I can release .US or .DH editions at-will with just a few minor addons.
Next build should see the custom config script, smartassv2 set as default governor, cleaned-up lockscreen (going to try to use weathergenie instead of 9s for the weather source, as 9s is hard-coded to use celcius)...and fixes to the theme where it's dark grey text on black bg.
And the xloud vs. dsp manager thing...I'll check it out as well. Perhaps there's something I'm missing that will allow for both features. Or, the other solution is to figure out how mr. Chad.Goodman increased the volume in his kernel and replicate...
I got plans, dawg. Gotdamn plans!!
Edit:
And...we got Xloud+DSP manager. Plus I threw in a beats patch that claims to be for any GB ROM. I don't have beats headphones to use it, so who knows what it actually does...but...I just listened to a bunch of songs w. all of the dsp manager features on, +xloud, and no FC's.
Few more things w. the lockscreen, and then I'll have it xferred over to use the genie widget...which already comes w. the ROM so it should require no configging. Plus it's ad-free.
Last edited:
Just loaded this bad boy up on bootmanager ...NOICE job on this Ben. I have never been an aosp fan but this rom will be getting some screen time.
Sent from my PG86100 using Tapatalk
Sent from my PG86100 using Tapatalk
I haven't touched the OC on ROM toolbox. If it's automatic I don't know how to disable it.
I will give some breathing room to setcpu and report back tonight.
I just realized that the smartass governor is just overclocking it and not moving from the max at all. This is probably what's causing the drain.
Evolution is speaking using XDA Premium
Last edited:
Either way, I've got two new uploads going to this folder right now:
http://www.mediafire.com/?3ucbuzh1axsyo
It's 12:34AM in WIsconsin and they're 15% uploaded now. You do the math.
ONe is called _WIPE, the other _NOWIPE. They're identical, minus the three lines commented out in the installer-script for now.
I installed the NOWIPE one and it definitely doesn't wipe and all my stuff is still there, only down side is it wipes the screen layouts so I have to re-setup everything. It's by no means a deal breaker for usings this ROM, hell or even the WIPE version but curious if there's anyway to get it to install over the old version without having to setup anything?
BTW, looking forward to the new base coming out. I'll be wiping then for sure!
Thanks again for your hard work, hands down I dig this ROM over the regular one!
One of you with installed rom could say how is the HW Acceleration? I love AOSP but most roms have much less HW accel than a sense rom. Also, can you play heavy games like shadowgun, dead space and more games like these at full speed or not?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
112
Team CrashOverride Is Proud To Present
MIUI v4 3.2.22 FINAL For HTC 3VO
This is most likely the final release of this ROM, as MIUI is discontinuing builds for v4/ICS devices. I may release bugfixes or "addon" updates, but unless I can port from JB to ICS, this will be the end of updates from China. Please see my JB version of MIUI for the latest release.
Downloads
Download the full ROM
Modded HTCFMRadio.apk (for theme)
Modded SystemUI (fixes cutoff close button in notification bar)
Installation Instructions
1. Download the ROM.
2. Open in Recovery.
3. Select wipe settings (uncheck 'data' for dirty flash).
4. Select Carrier.
5. Select installation mode. Minimal installs ROM only. Max installs everything. Custom lets you select options.
6. Profit.
Notes:
This works with all Hboot versions, no need to upgrade/downgrade.
Features
Working MMS/VVM for Virgin Mobile Users
Aroma-based installer with customized theme & Custom Wipe options
Based on OFFICIAL X515 build - This is not a port
Working 3D Camera/Gallery/Games
All working hardware except for 4G
MAC Sense Kernel 3.5 with Overclock to 1.7ghz, Linaro Optimizations,
USB Host Mode, Zram Compression, Sweep2Wake, and lots more
Coolz Cam Mod with super HD Video, HDR, and panoramic mode
Custom MIUI Control Panel for Center Clock/Custom Banner
Custom MIUI Keyboard
MIUI EQualizer
4-in-1 Reboot Menu
Custom init.d scripts for performance
Adreno_Config Mods for video performance
3G/Data Speed Mods for optimized signal
GPS/AGPS mods for faster GPS fixing
Updated HOSTS file for Ad blocking
FULLY WORKING Google Now/Search
Integrated Gapps
HTC Car Dock application
Goo.IM updater application
Optional Apps/Features:
MIUI V5 Iced Theme - Theme made specifically for this ROM, features MIUI v5 resources and look - with an ice blue touch. Features a number of modifications specific for HTC-based MIUI, including camera and FM Radio.
Ultimate Custom Clock Widget + US MIUI 4x2 Clock Widget Clone Skin
Playstation Certification
Flv Player
Moavi Flv Player
TrevE Wifi Tether
Gmail
Maps
Chrome Beta
JB 4.2 Camera/Gallery
JB 4.2 Emojii Keyboard
9S Weather
MIUI Game Center
MIui Video
Goo.im ROM updater
Online Nandroid Backup
Youtube
Not Working
4G
Changelog
Code:[URL="http://en.miui.com/thread-1960-1-1.html"]CLICK HERE FOR WEEKLY MIUI CHANGELOG (OFFICIAL)[/URL] 2.25.13 Updated to latest MIUI version (3.2.22) Updated theme to MIUI v5 Iced. Updated Kernel to MAC 3.7 Added a host of new tweaks courtesy of JRummy16 Fixed installer-script causing issues breaking ability to back up data via nandroid Custom modification to MIUISystemUI and framework-res for JB styled notification area, as well as mod to FMRadio.apk to match MIUI theme in MIUI v5 Iced 2.11.13 Updated Coolspace Deluxe theme to 2.2, added theme elements for custom apps Extra tweaks in build.prop, hope to increase sound quality, image quality, data speeds Added option to installer for JB Keyboard and Camera Removed function of installer where MIUI Browser is deleted if Chrome is installed Updated Kernel Tuner and UCCW to latest versions 2.4.13 (contains changes from 1.29.13): Added Aroma installer. All "custom" options now install as designed. Not sure if I mentioned it last week, but I updated the MIUIHome's default layout to take "Talk" out of that stupid "recommended" folder and just put it on the desktop. Also took and put "themes" and "settings" into the "tools" folder on the main page and changed the layout so that they're all in the same row. In the future, I plan on switching the MIUI search widget with the google one...just haven't gotten there yet. Coolspace Deluxe theme is included by default, but not installed. Updated to 2.1 to fix various issues with missing app themes and framework-res 9pings being screwed. Installer will copy it to /SDCard, where you can then import it from Theme manager. MIUI 2x4 Widget is included as an .apk...not 100pct if it will show up properly if UCCW has been installed before. Please test and let me know. Moved Gmail, Maps, Kernel Tuner, Gamecenter, MiuiVideo, and Goo.im to the "optional" category as well, and set their install location to /data/app instead of /system/app to allow for removal if desired. Wipe menu - for future use, you can choose to leave data sections untouched and do a dirty flash. Added 9S weather, 2 different FLV players, TrevE's wifi tether app, Playstation certification, and Online Nandroid backup app as optional installs (in addition to others mentioned). Updated to 3.3 MAC kernel. Fixed boot animation sometimes causes OOM issues due to size by deleting half the frames used. Modified goo setting in build.prop to hopefully fix the issue where it always shows an old update in current. Attempted MMS fix for Virgin users may/may not work - will be fixed "fo sho" next week. 1.29.13 (not officially released): Updated to latest MIUI version. Added Aroma installer (Thanks CMB!) Created Custom Aroma Installer skin/gfx Added aroma feature for Virgin Mobile users. Please report on effect. Updated Coolspace Theme to 2.0. Fixes framework glitches, updates icons, etc. Included MIUI Weather 2x4 widget skin for UCCW. Modified MiuiHome.apk to change default layout. Theme manager and settings are now in the tools folder. Added optional online nandroid updater. Moved several apk's to data/app instead of system, hope to retain settings between flashes. 1.18.13: Updated to latest MIUI version. Updated latest MIUI Control panel version. Re-added Coolz camera mod. Added download option for dirty flash/update.zip Added experimental MMS fix for Virgin Mobile users. 1.11.13: Updated to 1.11.13 Missed the rotation addition to MMS this week...will put it back next. That's all. It's nice when you don't have anything to fix. :D 12.24.12: Updated to 2.12.21 from Xiaomi Fixed APN in framework-res, should automagically add Sprint APN now. (Virgin WIP) Removed a few extra unneeded files Updated Kernel installation method to alleviate possible weirdness with reboots and wifi. (oooh, pretty lights) Fixed MIUI Equalizer (used Awesomebeats libs) 2.12.7: Added MIUI Keyboard. Added MIUI Control Panel. Added MIUI EQ (Actual EQ Portion causes f/c. Use for adjusting bass levels.) Fixed Bootloop issues. Fixed wonky crash in previous upload. Added HTC Car Panel. What the hell, right? :D Camera *should* have Panorama/HDR re-implemented. Reverted Kernel to previous MAC build to fix wifi issues. Added AGPS/GPS tweaks again. Added data mods in build.prop. Adjusted media_profiles.xml to improve recording bitrates. Release of [URL="http://goo.im/devs/digitalhigh/Coolspace_Deluxe_1.6.mtz"]Coolspace Deluxe Theme[/URL] with specific 3VO mods for camera and Google Now. Added landscape mode to MMS/messaging app. 11.27.12: Updated to 2.11.23 build. Updated kernel to MAC 3.0 Sense Updated Kernel Tuner.apk to latest version. 09/21/12: Switched from DC script to Kernel Tuner - installed latest version Fixed MMS issue. Updated to 2.9.21 from MIUI Git. 09/16/12: Fixed Google Now issue. Updated to V7 of MikeyXDA's app, added offline voice searching (explains the increase in filesize) Fixed Audio. Beats notification wooooorks. Added custom translated version of GameCenter. Re-added DC Control script (caution, may be dragons). Updated DC script to control sweep2wake. Added Virtuous OC. Added Self-updating HOSTS file - disableable via DC. Added notification sounds from CM7. Added extra MIUI wallpapers. A few extra goodies are there too. ;) 08/31: First public release built straight from PatchROM!!!! Go CMB go!! Switched (back) to AwesomeBeats DSP manager. Thanks to ...Awesome...! Included MikeC's new "unnamed" kernel. Thanks to Mike and team! Should see an improvement in signal strength. Fixed issues with Permission Manager not working on requests. 08/10: Fixed MMS. Fixed 3d in boot animation. Added Google Now w. voice. Fixed "About Phone" menu. Fixed Superuser issues, removed supersu. Added "improved" Evo 3d Camera (panorama, HDR, improved video quality, etc.). Added Bravia Engine & Xloud. (Thanks Patcha!!) Put EXT4 mounting back into boot.img. 08/03: Using Official GSM port as starting point. Merged files from Official OTA ICS from Sprint. Included SuperSU as a temp fix for permissions app. User Feedback app now sends error reports directly to me. Removed shutter sound from camera app. Implemented 4g menu - not fully working yet. Updated to 2.8.3. [url]https://plus.google.com/108531052526575991056/posts/baQviEGpoZm[/url] 07/13: Fixed issues from the ill-fated 7/6 build. Updated base to Devil Toast 6.1. Should fix wifi speed issues, hopefully battery drain. Updated to 2.7.13 MIUI-side. [url]https://plus.google.com/108531052526575991056/posts/51Z1VkAQqfa[/url] Re-added ghost VM fix. 06/29: Added AwesomeBeats DSP manager app - uses Beats libs from Sense. Thanks ...Awesome...! Added SpareParts app from Myn2.34 - Thanks to MikeC84 for the find! Added modified DroidSansFallback font to include missing emoji. Integrated phone ghost VM fix into phone.apk. :D Updated Gapps - should fix market issues and FFC. Included Bravia and Xloud engines. Removed MIUI.us Update.apk due to FC issue. Goo updater still included. Switched to 30dhultra tuning script in init.d instead of ViperRom. Modified framework-res.apk to use brighter auto-backlight values in bright lighting conditions. Updated MIUI-side to 2.7.13 version. [URL="https://plus.google.com/108531052526575991056/posts/51Z1VkAQqfa"]Full changelog here.[/URL]
Thanks
CMBaughman, Agrabren, Team Nega for the aroma-installer I used as a guide, Blind, Scott from MIUI.us, Valdesr11, all of team MIUI.us, MiuiAndroid, MiuiAustralia, Xiaomi, the folks at goo.im and dev-host for providing us a free way to distribute our work, freeza, viperboy, il duce, vanessam, and all the staff at XDA for helping make this such a great community...all the people who's work I've borrowed code, images, or even inspiration from - if credit is omitted, it is not deliberate or intentional. Anybody else I missed. You guys rock.
36How to report a bug the right way
Allright...
Been getting a lot of bug reports lately, and the vast majority of them don't have any kind of system information included whatsoever. People just blurt out stuff like "Camera ain't workin'", and expect me to go "Oooooooh. Your camera don't work. Please, allow me to customize you a script to fix it based on that thorough explanation of the issues."
To be fair, there are some issues that may be simple to replicate and don't require a lot of information to track down. Stuff like "This program is missing" or "the cap button backlights misbehave from time to time".
For all the other stuff...there is a right way and a wrong way to ask for help.
The wrong way involves complaining about the issue while providing as little info as possible. Degrading the ROM itself is a nice touch. You know, like "This POS won't boot."
That, my friends, will get you one reply...which will be me telling you you'd probably be better off using a ROM that doesn't require common sense to run.
The RIGHT way to ask for help involves the following:
1. Provide as much information about your system as possible. This includes, but is not limited to, the following pieces of information:
a. What Hboot version you are using.
b. Your S-off status.
c. What recovery you're using.
d. What firmware you're using.
e. A detailed description of the issue. When it happens, the frequency, anything that you do that causes it to happen...tell me what I need to do to make it happen on my phone.
Additionally, for issues related to hardware (camera, data, screen, wifi) - and hell, for any issue, it is more often than not a good idea to include a logcat.
A logcat is like a system log...it runs as soon as your phone starts up, and it tells me when something goes wrong so I can try to figure out why. A logcat will make the difference between me yelling at you, and me being very grateful for your thoughtful and well-constructed request for assistance.
Now, for some odd reason, it seems that every time I ask someone for a logcat, they make a face like this at me,, and then vanish off the face of the planet.
Contrary to what you may think...bugs bother me. A lot. The majority of nights end with me lying in bed thinking about the first thing I'm going to attempt to fix tomorrow.
SO, when you post saying something doesn't work, and then I say "get me a logcat, please", and you switch to a Sense ROM and don't look back...it helps nobody.
With all that said...below is a link to some very simple instructions for how to install Android SDK and do a logcat. It's pretty damned simple. If you can follow instructions for flashing a ROM, then you should be able to do this.
http://www.shahz.net/android/adb-installation-and-how-to-logcat.html
If THAT is too daunting for you, then the next step would be to get Alogcat from the market.
https://play.google.com/store/apps/details?id=org.jtb.alogcat&hl=en
Alogcat is even easier. Something crappy happens...you open alogcat, save the output, and send it to me.
Can we do that? Please? I'm so tired of asking for a logcat around every turn. Help me help you.20
You can say that again!!!!
So, here's the skinny:
I can now say, 100%, that we have been able to build a working MIUI port on top of Agrabren's CM9 work.
I also want to specify, that by "we", I mean CmBaughman. While I've been running around in circles beating my head against the wall, he's been doing smali magic and all kinds of joy to get this thing going...and succeeded.
So first and foremost, everybody should give him a big thank you. All I did was explained a few things I'd been trying, and he ran with it.
Now, obviously, Agrabren's side of things isn't quite ready yet. BUT, the fact that I am currently running a port of MIUI that has working camera, wifi, data, phone, bluetooth, and rear camera...well...it assures me that when Agrabren's got his stuff where he wants it, we will have no problem building on it in the future.
Again...working rear camera and bluetooth. Hell, I'll post a screenshot here just as soon as I'm done restoring my data.
So, I'll be talking with Cmbaughman & Agrabren tonight to make sure everybody is fine with it...but I anticipate having a 2.6.1 release for you guys tomorrow.
And again...maaaaaad thanks to both these guys for their incredible work.19For those using the CM nightlies from Eyeballer, he just posted a quick update with GPS working.
For those wondering what order I'm doing things:
1. Camera clocking issue (gives 2D camera and camcorder)
2. Bluetooth Phone audio
3. Wakelock/Battery life issues (latest builds have *awful* battery life)
4. -- Alpha Build --
5. 3D Framework support
6. 3D Camera/Camcorder/Gallery support
7. 3D YouTube support
8. Any critical issues from Alpha
9. -- Beta Build --
10. MHL / HDMI mirroring / video output
11. MHL / HDMI 3D Video out
12. Any critical issues from Beta
13. -- Release Candidate --
14. Bugfix only
15. -- Official "CM9 Devil Toast" release
Obviously, this list may change as things are discovered.
