yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi 4] :
[Q&A] [ROM MIUI KK v6] - sMIUI 5.1.2 <<< AROMA,initd,tdb,multilang,zipalign,cpuTweak

Q&A for [ROM MIUI KK v6] - sMIUI 5.1.2 <<< AROMA,initd,tdb,multilang,zipalign,cpuTweaks >>>

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [ROM MIUI KK v6] - sMIUI 5.1.2 <<< AROMA,initd,tdb,multilang,zipalign,cpuTweaks >>>. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Xiaomi Mi 4] Thomash75016:
You use which theme in the screenshots ?
[Xiaomi Mi 4] Hadi al-Haiqal:
What is different between Miui Polska and sMiUi
[Xiaomi Mi 4] Ati20:
Bug

Hi!

The camera app isn't working for me in v 5.1.23.

Any solution?

Thx
[Xiaomi Mi 4] Gotty1991:
Notifications delay

In this rom there are problems of delay in notifications as in the stock , whatsapp messenger etc....?? Thanks for the work
[Xiaomi Mi 4] Gotty1991:
sMiui 5.3.6

I,ve installed the rom on xiaomi mi4 and there some random reboots during the day.....I installed by clean installation after full wipe e reset
[Xiaomi Mi 4] aarishcs2:
what trickery is this ?

after i installed any updates post 27 one on smiui . the system randomly reboots /? any solution to this > bitti ?
[Xiaomi Mi 4] kingchum:
great ROM

I will try tonight
[Xiaomi Mi 4] kingzpalace:
Awesome Rom

Awesome Custom rom for MI4..After updating latest build of 31.07.2015 getting Browser FC...
[General Questions and Answers] SolidSnakex128:
Good day folks,

I've noticed System_Server and a few other items (below) severely draining the battery on my Galaxy S5 (3-4% per hour, when it's normally .75%/hour). In the past few weeks, the top Kernel Wakelocks and "Process" wake time (reported by BBS) have been:

1)	Ipc00000016_Time_Daemon (which I can't find ANY info about, even when just Googling “time_daemon”)

2)	WakelockManagerTimeout (likewise - no useful info, literally only SIX (6) results on Google).

3)	System_Server (nothing concrete besides "try Wakelock Detector")

4)	"IPC_###_Event0"/ “event0-###” every now and then, where ### is a Process ID. When I check the PID via Terminal (Cat /proc/*PID*/cmdline) the PID ends up belonging to "System_Server".

5)	Numerous EventXX-### records, where XX is an event number and ### is a Process ID (usually the same PID tied to Event0 as noted above).

6)	Numerous Kworkers

To make a Windows comparison, it looks like System_Server is "RunDLL32" or "SVCHost", wherein, numerous processes can "hook" into "System_Server" and are thus disguised behind that process name. Is there any way to dig deeper into "System_Server" to find the ACTUAL process/service that is causing all these wakelocks? I've also tried GSam Battery Monitor (thanks to - this post) and WLD (Wake Lock Detector) but the most granular any of them get is just "System_Server", even when I chase all the other Process IDs. As far as I can tell, this did not start as of newly installed software, but it could certainly be due to an update to an existing program. Whatever the cause, though, I need to find out, because a dead phone is useless :(

Thank you and Happy New Year :)
[Nexus 7 (2013) Q&A] Boucherwayne78:
When I boot up my tablet, I get nonstop error messages telling me things have stopped working. I tried getting help from someone else on a different site, and this is what they told me to say: I flashed the GROUPER lollipop ROM onto a FLO. Someone please help me!!! It's a totally clean tablet. no files on it except android.
[Nexus 7 (2013) Q&A] nhizzat:
Go to Google's Nexus firmware page, download the appropriate firmware, follow the instructions: https://developers.google.com/android/nexus/images

Only thing I don't know is whether or not you'll have to repartition the internal flash.
[Nexus 7 (2013) Q&A] Boucherwayne78:
I'm a dummy.

i don't understand how to do all that though:( I'm not good with command prompts... and nexus root tool kit has done me no good. Could you dumb down the instructions for me?
[Nexus 7 (2013) Q&A] nhizzat:
Then it's time for you to learn. The page has step-by-step instructions. There isn't any way too dumb down the instructions.

You have to start somewhere. Now is a good time. If you had learned before, you wouldn't be in this predicament.

So sit down, take a couple deep breaths, then read the instructions a few times. Download the Android SDK and factory image, then get everything set up. Don't panic, it's not nearly as difficult as you're making it out to be. Stop psyching yourself out. Take it step by step. If you get stuck, leave the cmd prompt and post the issue you've run into here.

Might help if you type out the instructions here after you've read them over several times. I'm glad to help but you gotta take ownership of your tablet and put in some effort to learn and educate yourself.

Just try, I'm sure you'll understand it by the end of tonight or the end of the weekend. You don't have to be a master of fastboot and adb, I sure as hell am not. I never recommend the use of toolkits, especially by those with no understanding of fastboot and adb. Once you have a basic understanding of fastboot and adb, go ahead and use any toolkit you want because by then you'll know how to get yourself out of any jams using those 2 tools.
[Nexus 7 (2013) Q&A] JustZaphod:
It is almost impossible to hard brick this device, even if you flash the wrong ROM on this device..

Download this utility and it will bring your Nexus back to life....

http://www.wugfresh.com/nrt/
[Nexus 7 (2013) Q&A] Boucherwayne78:
Giving up

I'm officially giving up. Nothing works. It boots into the OS and then pops up a bunch of error messages. I've tried lollipop, kitkat, cyanogenmod, locked bootloader, unlocked bootloader, and I'm done. GR! Thank you though, for your help.
[Nexus 7 (2013) Q&A] kindofabuzz:
So that means you will sell it to me for $20?
[Nexus 7 (2013) Q&A] madbat99:
Nothing works? Just flash the factory image. Flashing Roms in recovery isn't going to help you. Before you give up, just use wugs toolkit to save it. If you give up without even trying the right procedure (fastboot flash factory image) then i recommend you not root again after you fix it. But wugfresh toolkit will fix it for you with a couple clicks.
[Nexus 7 (2013) Q&A] Boucherwayne78:
I tried NRTK

The toolkit doesn't work. I tried that 9 times, both downloading my own OS to flash, and letting the toolkit download it. Every time it either boot loops it or does the error message spam thing again. That's why I was trying to use SDK... And that didn't work either. And my drivers NEVER INSTALL RIGHT, so it's all just slowly killing me inside...
[Nexus 7 (2013) Q&A] yosmokinman:
Make sure fastboots working first. Put the tablet in bootloader mode by shutting it off then holding power and volume down (or up I forget, you want the screen that says start at the top and has device info at the bottom left.)

Connect to computer then go into the platform-tools folder in the SDK folder, hold shift and right click over the window>open command prompt here.

Type fastboot devices and hit enter. Does it show a serial number or does it show nothing? (waiting for device or something like that) If nothing you should uninstall all drivers for the tablet in device manager and install the google usb driver from the sdk manager in the sdk you installed.

Once you see the serial number you're almost done. If your bootloader is locked type fastboot oem unlock

Now from the factory image copy the image-razor.zip, bootloader.img and flash-all.bat to the platform-tools folder.

Double click flash-all.bat

That's it.
[Nexus 7 (2013) Q&A] AarSyl:
I think that it will be beneficial for you to look into using virtual machines (VM's). It allows you to run different operating systems directly from your computer.

The second half to this equation is learning to use Linux (Ubuntu is my choice). Since Android is built from Linux, you don't need special drivers to recognize your devices.

Another option to run Ubuntu is to create a Virtual Hard Drive on your PC, and install Ubuntu onto it (YouTube it, and follow the directions carefully).

Lastly, you can always get a flash drive that is 8gb or greater (16gb or 32gb is recommended), and install Ubuntu onto it was well. It will move little slower than your PC, but your issues will be solved and manageable.

Why am I advocating for Ubuntu? Because it works. PM me if your are interested in learning more, but don't expect me to do all of the work. You need to educate yourself a bit to actually follow my instructions.

____________________________

Please remember to:

Check Q & A forums before asking!

Search forum for similar post before creating!

Hit "thanks" to everyone who may have helped you (it costs nothing)!

Read the OP!!!!
[Nexus 7 (2013) Q&A] JustZaphod:
First off, let me explain that this device is almost impossible to destroy by flashing the wrong rom. Your over reacting due to inexperience, your Nexus is fine as long as you can boot into Fastboot. When the device is powered down, press the power button and the Volume down key for about 30 seconds, if you can boot into Fastboot, your device is just fine.. Nexus devices are extremely hard to hard brick.. RELAX and realize this is a good time to learn something new, this device is the perfect device to experiment with... You seem to not have the patients and you just need to relax watch a few youtube videos.. No one is going to do it for you.. About 5 years ago I was in the same place you are right now, and I took the time to figure how to fix what ever I did to mess it up.. Its not hard once you realize what your doing. The Toolkit is a swiss army knife of tools that can fix, repair and flash stock roms. Did you unlock the bootloader? Take a breather, give it some time and figure it out like we all did at one time or another, none of us here had our hands held during the learning process with Android devices..

Edit: I'm almost sure you did not unlock your device, to know for sure if your device is unlocked you would see a small padlock that appears to be in the unlocked position at the bottom of your screen while powering on.. If you power your Nexus on, and you DO NOT see a unlocked symbol at the bottom of your screen, you DID NOT unlock your device, thus meaning you have to unlock it to flash it properly.. There are dozens of people in this forum right now that would be more than happy to buy your device cheap and fix it themselves.. If they can do it, you can too..
[Nexus 7 (2013) Q&A] yosmokinman:
^Yeah like my last post, those are perfectly fine instructions. If that don't work, stuck at "erasing user data" or something you're ****ed. Most likely.Try a different cord/usb 2.0/computer
[Nexus 7 (2013) Q&A] Boucherwayne78:
Tried a few things. Got any other ideas?

Thank you for your reply. Do you have any suggestions though for my situation? My bootloader was unlocked. I did try locking it then unlocking it several times though. I've tried two seperate stock ROMs, different usb cables, different usb ports, and it now tells me that fastboot is not working. even a link is greatly appreciated. I think it is a driver problem. My tablet does boot into the OS though. I can use the ui for about 10 seconds, then a notification pops up mid-screen: "unfortunately, the process android.process.acore has stopped." Please, even a link is greatly appreciated. I've tried just about everything to get these drivers working, and to get this tablet working. I will continue to research as well. Wish me luck!
[Nexus 7 (2013) Q&A] azsgolf:
Wug's tool has been invaluable to me in the past. I have gone from KitKat to Lollipop, back and forth, different ROMS, stuck boots, bad flashes. Like Zap says if you can get it to Bootloader then get Wug's tool to connect in fastboot, it will do the rest.

A couple times I have ran into problems where my computer has not seen my Nexus 5 because of the drivers, just google nexus usb drivers and install the latest ones.
[Nexus 7 (2013) Q&A] Boucherwayne78:
Got any ideas on Fastboot.exe stopping working when the flash process begins? it fails sending bootloader and then fastboot.exe fails. It says on the screen when i close the error message it's booting into bootloader, but the tablet never restarts. it stays on bootloader(where i had it in the first place.) It should turn off the screen and go back into bootloader. Please, any feedback is appreciated.
[Nexus 7 (2013) Q&A] azsgolf:
Have you tried selecting the option of hardbrick on the tool?
[One (M8) Q&A, Help & Troubleshooting] PuG3o6:
please how do I fix this problem?

I tried formatting pc and formatting the m8 but still charging and not recognized.

I have 3 original usb cables but still all charging and not recognized

I installed drivers etc still nothing..

can any1 give me latest driver or something?

htc sync manager also doesn't work...
[One (M8) Q&A, Help & Troubleshooting] Riyan_Fransen:
Try diffrent pc and see if it worsks there.
[One (M8) Q&A, Help & Troubleshooting] benbailey84:
Have you enabled developer options on the phone? If not enable them, go to settings - about- tap build number until it says you are now a developer. Go back one screen and open the developer options. About half way down you will see an option that says usb debugging. Make sure that is checked. Unplug and replug your phone. A box should pop up asking you to allow rsa fingerprint click the checkbox and hit accept. Now your phone should be seen by windows.
[General Topics] brandon.smith:
PLEASE HELP ME :) :)

I get connected on TV via my phone, and i show some images on screen accident so am wondering

does my photos or any data stay on TV. I connected via WiFi.

Its important to me..... thank you a lot
[8.9" Kindle Fire HD Android Development] Hashcode:
OFFICIAL CyanogenMod 12.1 for the Kindle Fire HD 8.9"

*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***

BEFORE YOU FLASH THIS, PLEASE MAKE SURE THAT YOU HAVE A 2ND-BOOTLOADER INSTALLED FROM HERE:

http://xdaforums.com/showthread.php?t=2128175

CHECK KNOWN ISSUES BEFORE FLASHING. PROBABLY NOT GOOD ENOUGH FOR DAILY USE.

Official nightly builds can be found here:

http://download.cyanogenmod.org/?device=jem

Download Google Apps for Android 5.1:

https://www.androidfilehost.com/?w=files&flid=25361

(Choose newest *-5.1-* file)

NOTES:

Older versions of TWRP will show a "mount failed error". This is safe to ignore. TWRP 2.8.7.0 and on is recommended for cm-12.1 / android-5.1.

First boot after a clean wipe will take a LONG time. Be patient.

KNOWN ISSUES:

Use XDA Bug Reporter

SCREEN SHOTS:

Use XDA Screenshots

XDA:DevDB Information

CM12.1 KFire HD 8.9 (LP 5.1.x), ROM for the Amazon 7" Kindle Fire HD

Contributors

Hashcode

ROM OS Version: 5.1.x Lollipop

ROM Kernel: Linux 3.0.x

Based On: CyanogenMod

Version Information

Status: Alpha

Beta Release Date: 2015-06-24

Created 2015-01-02

Last Updated 2015-06-24
[8.9" Kindle Fire HD Android Development] Hashcode:
Reserved

KERNEL UPDATES for Lollipop Android 5.0 / 5.1

Added F2FS support which can be turned on (with a full /data format) in a future release of TWRP

Combined defconfig setup to better support all HD models

Picked "Wakeup reason" patchset from Google's common 3.4 kernel (not fully implemented yet)

Picked IPV6 routing changes from Google's common 3.4 kernel

Reverted a hardcoded disable of Secure Discard and added the official upstream patch for Secure Discard support detection
[8.9" Kindle Fire HD Android Development] Hashcode:
Reserved

Android 5.1 / CM-12.1 changes:

SElinux Enforcing as default enabled
[8.9" Kindle Fire HD Android Development] 11fan:
Holy smokes! Was hoping this would be out soon after seeing it released for the 7 inch! Thank

You hashcode for all your hours and hard work that allows us to have a better experience with the kindle! This is awesome and can't wait to try!

Mike

update: did wipe, installed cm12 clean with no errors, installed gapps clean with no errors! this maybe normal but progress bar in TWRP did not move after "swipe to install" until file 3 of 3 gapps was installing and it was almost complete (had my heart beating a little faster than normal) : ) but then all was good! first boot took about 6 to 7 minutes i would say (meant to time it but forgot) have went through all settings and all seems good, wireless good, all gapps seem good, not a single bug/glitch/crash SO FAR! thanks a million Hashcode! continuing to test out everything right now but all seems good!

Mike
[8.9" Kindle Fire HD Android Development] 11fan:
OK I noticed one major thing....I lost root. Why did that happen? I did not lose root after I flashed cm11. Is this because its alpha unofficial release? Thanks in advance for any input!

Mike
[8.9" Kindle Fire HD Android Development] zavien3:
Pretty dang good for a first build. I think a new TWRP and f2fs is going to bring the life back to this device. Its been pretty laggy ever sense the Kit Kat builds. I don't remember Jelly Bean being this slow. Maybe I'm just used to faster devices now, but I've always adored my Amazon Jem. Only thing I've seen thus far is Chrome Browser crashes after a minute or two, a bit laggy overall, a battery whore, and Google Launcher flat out doesn't work. Could be the gapps package though. Awesome work so far my friend, real treat. Thanks Hash'

---------- Post added at 08:42 AM ---------- Previous post was at 08:39 AM ----------

Just flash a SuperSU zip and root is back. I think it's a CM issue because I lost root on other CM12 devices as well recently.
[8.9" Kindle Fire HD Android Development] Thepooch:
Thank you!!.Rom is fantastic..Gap link is a waste some kinda malware...

Here are a couple links while they last.

https://app.box.com/s/80q8qu7l9akgb04u828j

https://www.dropbox.com/s/lwbf3laae901mgo/gapps-lp-20141122-signed.zip?dl=0
[8.9" Kindle Fire HD Android Development] 11fan:
There was two download tabs in the gapps link. Top one was junk as you described, I grabbed that one first also. But the bottom download tab was correct gapps for LP with matching md5.

Mike

---------- Post added at 08:04 AM ---------- Previous post was at 07:53 AM ----------

Flash a zip as in with adb install or just doing regular apk install will work? Thanks

Mike
[8.9" Kindle Fire HD Android Development] jaramosparra:
I installed cm12 and gapps clean with no errors, no problems so far. No root when tried to install apps with root access...the solution was easy: in Configuration, Developer Options, Root Access tab.

Thanks Hashcode!
[8.9" Kindle Fire HD Android Development] 11fan:
[MENTION=5872765]jaramosparra[/MENTION] thanks for the reminder! have been so excited about trying this out i did not even think about enabling those options.!

Mike
[8.9" Kindle Fire HD Android Development] revjkramer:
Root Works Fine

Root is now enabled through developer options.
[8.9" Kindle Fire HD Android Development] revjkramer:
Been running this since release and I have to say that it is functioning remarkably well. Almost a DD.
[8.9" Kindle Fire HD Android Development] zavien3:
Does anyone know if Philz Touch 6.48 (the latest) has F2FS support?
[8.9" Kindle Fire HD Android Development] zcola:
think you for you working!
[8.9" Kindle Fire HD Android Development] narse:
Didn't think that I would have Lollipop on my old KFHD before my HTC One M8!!

I have been running this for 3 or 4 days and all seems to be running great for me. I have found with the previous KitKat builds that it would only start to slow down if I installed too many apps. So far I just installed what I need (I just generally use it to browse the internet, read news and run any apps that cast to my chromecast) and it is certainly not any slower than Kitkat. One thing I did do a bit different was to install the "Micro Modular Package" from the PA Gapps Package in the link that BobJayJr posted (http://xdaforums.com/showthread.php?p=56832776) to keep as much space available as I could.

Thanks very much for your time and effort Hashcode. Has kept my old Tablet going so much longer than I expected when I bought it :)
[8.9" Kindle Fire HD Android Development] thetesterman:
Been running for 2 days without issue. Is there any plans for an LTE version for working Bluetooth ?
[8.9" Kindle Fire HD Android Development] bustr85:
Quick question: Has anybody done a backup from TWRP of the DATA partition and restored it after installing CM12 + Gapps?

I've done it, and it's been stuck on the CM boot logo for 5-10 minutes.

I've tried without restoring data and although it was a long boot but it did eventually boot. Any suggestions?

UPDATE: It booted so just ignore me
[8.9" Kindle Fire HD Android Development] bustr85:
It was a little too slow with restoring the DATA partition so I just started from scratch - anyway so far so good. ROM is wicked. Thanks for the work
[8.9" Kindle Fire HD Android Development] monster1612:
Would it be safe to perform a dirty flash from CM11, or would I need to do a clean wipe?
[8.9" Kindle Fire HD Android Development] raindayqb:
Can I downgrade ROM ?

I just have update Nightly to 5.1.1. I fogot check the version. Can I downgrade ROM without clean wipe ? It will have some problems or not ? :(

Thank you, guys.
[8.9" Kindle Fire HD Android Development] **TheDuke**:
Is anyone having issues with the 0804 nightly?

Is anyone having issues with the 0804 nightly? I dirtly flashed that + GApps last night, and the tablet shut itself off after the optimizing apps step. Rebooted, and it did it two more times. Reflashed nightly only, same issue. Wiped system partition, re-flashed, same issue. I'm backing up my data now and then going to do a factory reset and a clean flash, but this is troubling.

---------- Post added at 02:43 PM ---------- Previous post was at 02:00 PM ----------

Scratch that, I think it's actually a problem with screen brightness. I factory reset and reflashed and got a very dim cyanogenmod first-time user screen. After I completed it, the screen went dark again. This might be because I previously had the screen brightness set to minimum (it didn't do anything in previous versions). Any way to force it brighter from TWRP or ADB?

---------- Post added at 03:04 PM ---------- Previous post was at 02:43 PM ----------

Yes, that was the issue. I could VERY VERY VERY dimly see the outline of the power (off/reboot/airplane) dialog when I held the power button. I pawed around in the dark until I successfully found the brightness slider. Anything below half brightness is completely dark, so be careful.
[8.9" Kindle Fire HD Android Development] Dr. Drax:
Browser problems

I recently upgraded to 12-1-20150801-NIGHTLY-jem from CM11 after doing a wipe. In general, in works great, and seems to be quite responsive. But I'm having terrible performance from browsers. Chrome is the worst, doing all sorts of recompositing that makes the page flicker endlessly. Opera is problematic, albeit not quite as awful. Firefox is the best, but clearly not quite working right. The problem is especially obvious if I go to a site like wired.com where the pages have animated advertisements.

While I haven't done benchmarks, I haven't seen the performance slowdown that others have spoken of. I've found the build to be surprisingly stable and responsive. But this things with browsers having such trouble is frustrating, to say the least. Is everyone having this problem, or is there something unusual in my configuration?
[8.9" Kindle Fire HD Android Development] BobJayJr:
I'm having the same problem with Candy5.1.1. I wonder if this is a LP problem. BTW I just tried the APUS browser which appears (based on my limited trial) to be more stable with Candy5 but slower.