yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] XXMrHyde:
Darkkat Build dk-6.0.1-20160209 is available

Changelog:

Status bar:

Ticker:

Use the default push animation

Apps:

DKLauncher:

Merged in the latest Android source

Settings:

Button settings:

Fix volume keys switch

Battery settings:

Fix double Wake on plug switch

Installation:

Take a look at the updated installation instructions at post #2,

("MultiRom and root")

SuperSU/MultiRom:

Update MultiRom and MultiRom-TWRP to the current version from 2016.02.07.

Primary rom installations:

SuperSU will be installed in system mode.

Secondary rom installations:

SuperSU will be "installed" in systemless mode,

but SuperSU isn`t installed (or disabled and hidden),

also root isn`t working at all.

There are 2 possibilities to "install" DarkKat as secondary rom with working root:

System mode:

force the SuperSU installation in system mode

Systemless mode:

(tested on the Nexus 6 only, but should work on other devices, too)

Install DarkKat as primary rom,

and force the SuperSU installation in systemless mode:

Create a backup, and add a secondary rom from backup,

(tested)

Use MultiRoms swap rom feature,

(untested)

Download:

dk-6.0.1-20160209-RELEASE-flo

md5: 6bf15f3c2343c29e7bec7d4c4e5ea2b4
[Nexus 7 (2013) Android Development] SHABBYLEA:
Thanks for your efforts, much appreciated.

Thanks again.
[Nexus 7 (2013) Android Development] SHABBYLEA:
Have to say again...this is a cracker of a ROM...I'm surprised that its not more popular.

If you haven't tried it, give it a go...you won't be disappointed...

Cheers.
[Nexus 7 (2013) Android Development] quickdraw86:
It's been awesome since android KitKat, I agree, no idea why there aren't more users of it. I guess a lot of people get fixated on running ROMs with more frequent updates, but the main difference with darkkat in that regard is that the updates are meaningful. I'm also shocked that krexus and zombi-pop weren't/aren't more popular.
[Nexus 7 (2013) Android Development] SHABBYLEA:
Think you've hit the nail on the head there with DK....
[Nexus 7 (2013) Android Development] XXMrHyde:
I don`t do anything to make the rom popular:

No social media, no web side,

the rom is only available on devices I own by myself

I don`t build the rom to be popular:

in general I build the rom to have a rom which suites my needs,

I only include features I like, (except some requests),

I don`t include features because a lot of users will like them,

or I don`t include almost all features which are available,

to have "the" rom with most features, ...

Also the missing theme support is a no go for some (a lot of) users.

The removed Quick Settings isn`t a "feature" to make the rom popular for sure.

Of course there are some points which are not planned, (disappointing):

Update frequency:

A big problem,

with L, I tried to use beta and release builds,

this didn`t worked at all, there were to much bugs on the release builds,

but the update frequency was better.

Builds with big/much bugs:

Unfortunattely I didn`t found a way to "solve this issue",

I can test a build for one week or more,

but when I release it I find a bug,

or a user found one,

also beta testing isn`t the solution,

I had about 10 beta testers on KK/L,

most of them installed one beta rom, (I guess),

but I didn`t got any feedback,

except the beta testers mentioned in post #1 (KK/L thread),

if one of you read this, big thanks you done a great job.

But unfortunately, all of them changed the device, didn`t have time any more,

or I droped the support for this device.

Time:

The rom needs much of my time,

I would be happy if "my" day has more than 24 hours,

more time means better update frequency,

and/or less bugs.

On the other side,

as mentioned above, I build the rom to have "my", ("a rom for me"),

I don`t even build the rom to release it,

I release it because I like "sharing", and if only one user

uses the rom it worth it to release, isn`t it?

So for me it`s ok that the rom isn`t as popular as other roms are.
[Nexus 7 (2013) Android Development] quickdraw86:
My comment about the popularity of the ROM wasn't a criticism at all, your ROM is spectacular to me. Was meaning that others that may be lurking should give it a try. Thank you as always for continuing to support flo :)
[Nexus 7 (2013) Android Development] XXMrHyde:
No, no, I didn't thought your comment was a criticism, I just want to explain why the rom is not popular, and maybe won't become more popular.

Gesendet von meinem SM-G925F mit Tapatalk
[Nexus 7 (2013) Android Development] XXMrHyde:
Darkkat Build dk-6.0.1-20160521 is available

Changelog:

General:

Updated Android to 6.0.1 (MTC19T)

Updated security patch level to 2016-05-01

Weather:

Switched from CyanogenMods LockClock, (cLock), to "DK Weater Service"

Fix weather images colorizing

Lock screen:

Weather:

Show/hide the weather

Show/hide the weather location,

(also on Ambient display)

Ambient display:

(only Nexus 6)

Customizations:

Mode:

Notification and pickup

Notification

Pickup

Option to schedule ambient display on new notification

Custom ambient display brightness

Fade in duration

Visible duration

Fade out duration

Added Battery status:

Show/hide

Option to show the additional button bar

Weather:

Show/hide the weather

SystemUI:

Fix FC

Status bar:

Weather:

Removed long click feature, (for now),

(open forcast dialog)

Removed weather when on lock screen,

(moved to lock screen)

Status bar expanded:

Quick access bar:

Fixed NfcButton

Apps:

Removed CyanogenMods LockClock, (cLock)

Some infos about this update:

Removed LockClock , (cLock):

As I included LockClock for the weather feature,

and now switched to "DK Weater Service", LockClock isn`t needed

any more, (at least for the weather),

but as LockClock is also a home screen widget,

you may still like to use LockClock,

(as home screen widget), if so,

you have to backup the LockClock app,

(Titanium backup, ...)

Note: you can also use CyanogenMods original LockClock,

but the LockClock settings at:

Settings -> Advanced ... won`t work with the original app,

(Settings FC)!

Weather:

From function/feature side, you won`t notice a bad difference,

(as far as I know), except the long click function of the weather on the status bar.

Yahoo should be working again, (at least for me it does).

To be fair, even if it`s called "DK Weater Service",

it`s based on OmniRoms "OmniJaws", with some minor changes (for now),

but there will be more changes/features in the future.

Note:

You have to re setup the weather,

(Settings -> Weather), all rom related weather settings,

status bar (expanded) will stick.

Also I use my own api key for Open Weather Map,

this key has "very" limited access, (60 calls per minute),

this should be enough, (hopefully), but maybe when to much users

updating the weather at the same time, not all users will get an weather update.

I plan to include a possibility to set an own user key soon.

(as long as this is realy needed at all).

Download:

dk-6.0.1-20160521-RELEASE-flo

md5: 96f3ae65d2ab9dba6d755ba35173dd86
[Nexus 7 (2013) Android Development] SHABBYLEA:
Thanks MrHyde...
[Nexus 7 (2013) Android Development] moralesd66:
Any update to this ROM. Been my fav since day 1. Tyvm for all your work Mr. Hyde!
[Nexus 7 (2013) Android Development] XXMrHyde:
You can expect an update 1 or 2 days after Google releases the July security patch update.

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 7 (2013) Android Development] XXMrHyde:
Updated the installation instructions related to SuperSU and gapps.

SuperSU:

As the latest SuperSU version is a stable build,

I changed the SuperSU link to the stable SuperSU thread.

It seems with new SuperSU packages, the installation

on internal roms, (or without Multirom) is forced to systemless mode.

Gapps:

As the rom no longer needs the CyanogenMod cLock app,

(LockClock widget) for the weather functions, I removed the

info about the gapps configuration related to CyanogenMod apps.
[Nexus 7 (2013) Android Development] SHABBYLEA:
Thanks Mr Hyde...?
[Nexus 7 (2013) Android Development] XXMrHyde:
I guess I messed up the current kernel branches/tags, so some new AOSP commits are not included in the kernel. Possibly there are issues (WiFi not working) with some custom kernel. This also means the "ROM" security patch level doesn't represents the current AOSP security patch level. Sorry about that. For now, (till the fixed build is released), I recommend to use the default ROM kernel, (at least if you get issues with a custom kernel).

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 7 (2013) Android Development] XXMrHyde:
Darkkat Build dk-6.0.1-20160710 is available

Kernel:

Include latest AOSP changes

Settings:

Color picker:

Animations:

Materialize

Favorites:

Animate palette color buttons motion on show/hide favorites

Help screen:

Push down out animation on hide

Push up in animation on show

Prevent help screen from clicking through

Update help screen text

Change "Show Help" to "Hide help" in the overflow menu

when the help screen is shown, (text and function)

Nexus5:

Updated wifi firmware

Nexus6:

Updated wifi firmware

Some infos about this update:

Security patch level:

As alredy mentiond, in the last build I made a mistake,

and didn`t included the AOSP kernel changes for the current

July security patch level, this build fixes my mistake.

Wifi firmware

I thought about, if I should mention this in the changelog,

because this is a "selfmade" issue and related to the "Android version" I`m building for.

E.g. the current "Android version" for the Nexus 5 is:

"mob30p", there aren`t any wifi issues using this "Android version",

but as I also build for my Nexus 5X, which uses "mtc19z",

I decided to use "mtc19z" for all devices,

(which wasn`t a problem in the past, and is done in other roms, too),

but with the current July security patch, Google didn`t updated

the wifi firmware for some devices "using" the "wrong Android version",

(which can be expected of course).

But as this is a change of the AOSP source,

I decided to mention it in the changelog.

Bugs:

Detailed weather view:

Rotating the screen while the detailed weather view

is visible, will result in a FC of the "DK Weather Service".

This needs some overwork, and it`s more important for me

to fix the kernel and wifi issues first.

Hopefully this will be fixed in the next build.

dk-6.0.1-20160710-RELEASE-flo

(MD5Sum: 214249685ffd37020334f45d1596d512)
[Nexus 7 (2013) Android Development] XXMrHyde:
Darkkat Build dk-6.0.1-20160802 is available

General:

Updated Android to 6.0.1 (MTC20F)

Updated security patch level to 2016-08-05

Weather:

Detailed Weather view:

Fix FC on orientation change

Made location optional

Status bar expanded:

Quick access bar:

Use vector drawables

Added sync button

dk-6.0.1-20160802-RELEASE-flo

(MD5Sum: 08d029003bfc70afad7964d8ed74d12a)
[Nexus 7 (2013) Android Development] SHABBYLEA:
Thanks Mr Hyde....?
[Nexus 7 (2013) Android Development] moralesd66:
Thanks! Any news on a Nougat base?
[Nexus 7 (2013) Android Development] XXMrHyde:
Sorry for the late reply. I'm working on it.

Gesendet von meinem SM-G930F mit Tapatalk
[Xposed General] AnaOka:
:confused::confused:

Please can someone tell me does the new official xposed for lollipop work on Lenovo A7000 regard that it's lollipop 5.0 sdk21 arm64 v8a???

Is sdk21 arm64 v79 match with it?? help please

:rolleyes::rolleyes:

and

how to install OTA after root

and

how to hide root from some programs ​
[Xposed General] Portgas D. Ace:
Yes, it should work. Refer to the table in post #2 of the official Xposed for Lollipop thread to identify the correct version for your device. Afterwards, boot into recovery, make a full backup, flash the files and confirm by yourself whether it works or not.

By the way, the latest Xposed version right now is v78, not v79.

For hiding root, use Root Cloak, an Xposed module.
[Xposed General] AnaOka:
Thanks​
[XDA Assist] kennethgirvan:
my rooted phone didnt want to access to any google services, so i reset it. but when i reset it keeps searching for network for google services though it has been connected. i tried to wipe cache in the recovery, turns out it rebooted but stuck in samsung logo.

i tried to flash a rom which i downloaded and i got this

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> aboot.mbn

<ID:0/003> NAND Write Start!!

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

how to fix my device?? thx
[XDA Assist] Primokorn:
Hi,

Try posting your question here with all relevant details:

Galaxy Grand Prime Q&A, Help & Troubleshooting

The experts there may be able to help.

Good luck!
[Nexus 6P Q&A, Help & Troubleshooting] VanGolfer:
My Nexus 6P comes with MDB08L and I rooted (traditional) with MDB08M. When I find my company email app (Good Work) does not work on rooted phone, I unrooted back to all stock MDB08M. Today I try to use recovery but I got Red Exclamation in middle of Recovery every time and the stock recovery seems dead. When I flash MMB29M and I flash the recovery again specifically but still got the Red Exclamation in middle of Recovery. I searched the see this video (https://www.youtube.com/watch?v=gzzYV1BjMNs) and tied but still no luck. But I do see the Android Recovery is the MMB29M version when I do the video thing. Can anyone please help to fix this? Thanks a million in advance!
[Nexus 6P Q&A, Help & Troubleshooting] chichu_9:
Why dont you try to revert back stock using a factory image?
[Nexus 6P Q&A, Help & Troubleshooting] VanGolfer:
I used MDB08M factory instead of MDB08L which originally from the phone, I am not sure this the course of the problem.
[Nexus 6P Q&A, Help & Troubleshooting] dontbeweakvato:
The red exclamation usually means either no recovery or incompatible recovery. Did you flash mmb29m recovery for mdb08m rom? If you get stuck too bad you can always enter fastboot and just reflash everything its not that hard to do.
[Nexus 6P Q&A, Help & Troubleshooting] VanGolfer:
Yes, I flashed whole mmb29m factory image over mdb08m. Still can't boot to recovery manu . I'm worried about OTA will fail.
[Nexus 6P Q&A, Help & Troubleshooting] Powell730:
Once you're on that screen, you've held down the power button then pressed and released volume up right?
[Nexus 6P Q&A, Help & Troubleshooting] spc_hicks09:
Get into fastboot, then "fastboot flash recovery xxxxxxxx.img" obviously replacing the x's with the file name. Just reflash the recovery for the same factory image you flashed. Very possible that you just need to reflash the recovery image.
[Nexus 6P Q&A, Help & Troubleshooting] VanGolfer:
Tried but doesn't work.
[Nexus 6P Q&A, Help & Troubleshooting] kauemelhado:
Flash the recovery via fastboot :

fastboot flash recovery xxx.img

fastboot reboot-bootloader

Now, when your phone reboots to bootloader, using the volume keys, find "recovery" and use the power button to confirm.

profit.
[Nexus 6P Q&A, Help & Troubleshooting] chaco81:
he has to press the power button and vol up on that screen to get into recovery just like guy in post 7 said...

factory recovery doesnt boot all the way into it by default, requires a user button input once it gets to that android exclamation screen
[Nexus 6P Q&A, Help & Troubleshooting] VanGolfer:
I did this, the red little thing didn't go away
[Nexus 6P Q&A, Help & Troubleshooting] kauemelhado:
Did you try downloading another recovery file?

That's really strange.

I was having this error when I tried to flash twrp and boot direclty to system (skipping the recovery boot).

Did you try to install twrp?

---------- Post added at 01:53 PM ---------- Previous post was at 01:48 PM ----------

Another thing..

The system boots up normaly?

To solve this, I did the procedure that I just told you + before booting into twrp, I flashed vendor.img..

Dunno if that could cause this issue
[Nexus 6P Q&A, Help & Troubleshooting] VanGolfer:
When I root I installed TWRP, revert back all to stock after unroot. I have to stay unroot because of the company app. Just want to be easy to update on OTA,
[Nexus 6P Q&A, Help & Troubleshooting] kauemelhado:
I know that feel bro, my company also use an app that verifies for root..

I'm rooted, but on 6.0 I had only twrp w/ no root. no problems..
[Nexus 6P Q&A, Help & Troubleshooting] VanGolfer:
So you can install twrp without root as I understand. Then do you need to lock your phone after install twrp (unlock before install twrp, right?), and also how do you do the update OTA or upgrade to 6.0.1, etc..? Thx
[Nexus 6P Q&A, Help & Troubleshooting] kauemelhado:
I guess you can't lock your bootloader with Twrp.

Then, to take ota's just simply flash the img files.

;s
[8125, K-JAM, P4300, MDA Vario Software Upgrading] nostromo76:
:confused: Please, anyone, how can I flash my wizard from the bootloader screen?. All the procedures around explain flashing with ROMUpdateUtility, but none from the bootloader screen ... Do I have a brick????

Please, help and thank you in advance !!!
[8125, K-JAM, P4300, MDA Vario Software Upgrading] mestrini:
It works just the same. The only difference is that the updater doesn't know the version of the ROM installed.

When one starts the updater (RUU) with device running normally the process loads two files called RUUGetInfo.exe and EnterBootLoader.exe . The first gets the OS version currently running and the second sends the phone into the 3 color mode. As you see the updater HAS to work from the bootloader ;)

But i guess the wiki could have told you that... (why bother?)
[Sony Xperia M4 Aqua] SharpnShiny:
Hey,

I bought the 06 model in Canada. I've moved home to Europe.

Now all apps are priced in dollars, not Euro. I also just found out that various apps don't even appear in the store but they do on everyone else's phone. Some apps also say region not supported so they won't even allow me to download.

I flashed an 03 generic FTF. Everything worked except 4G. I didn't even get 3G. I used exactly the settings the network advises. No luck. So I flashed the custom firmware ftf of the new European network, same problem. Next I flashed the original Canadian network custom firmware and 4G works perfectly, no settings needed, the network installs the right settings immediately. I checked them, they're the same I inserted before.

How to solve this? Ideally I'd like to use generic European firmware, have 4G and see local apps.

P.s. My phone is network unlocked, and I noticed a tremendous speed difference with 4G back, it's not just a symbol issue.

Thanks
[Sony Xperia M4 Aqua] sanjai001:
Hay first u need to first fft file that come along with ur mobile

---------- Post added at 08:34 AM ---------- Previous post was at 08:31 AM ----------

Hay first u need to flash the first firmware that come along with ur mobile.it has all the problem fixed for u mobile
[Xperia SP Q&A, Help & Troubleshooting] KoRTaN:
Im Flashed This Rom..

[ROM] [4.4.4] [KK] [Unofficial] Omni-X Rom - Xperia SP [SLIM][DAILY][FAST]

http://xdaforums.com/xperia-sp/development/rom-unofficial-omni-rom-ported-yuga-t3122753

Now I Have Problems... :(

Small Dim Green Light Always Show [Illuminating transparent band] And Screen 100% Not Off After Screen Locked !!!
[Xperia SP Q&A, Help & Troubleshooting] GuestK00243:
Try flashing the kernel with flashtool that should sort out the issue

IF not then flash the ROM over the top again

Then look at any apps you may have added and remove them one by one (you may have to boot inbetween to get results)
[Nexus 9 Q&A, Help & Troubleshooting] musashi109:
Doesn't enable oem command/or any other command/ Cant flash it "Device locked"

Good day/afternoon/night... I have a problem for several days now with my nexus 9; I had the 5.1 version I I couldnt updated because when I try it the tablet would restart and the update would iniciate normally but more o less half way would show an error message and the tablet would restart without the update; I downloaded the 6.0 update from the oficcial page to try to flash it with the nexus tool but I coulnt because the bootloader is "Locked" Then to open the bootloader the tool tries to open the "oem" and restart the tablet but it kept how is shown in the video, An eternal looping, So I cant access to the device configuration and activate the oem option from the developer menu. HELP.

https :// www .youtube.com /watch?v=7qIuh7oPaq4&feature=youtu.be

forerver loop :(
[Nexus 9 Q&A, Help & Troubleshooting] peterk-1:
I've had those symptoms or something very close. I managed to get it fixed with 10 minutes of button pressing - it was a case of holding the power button until the screen went blank and then

guessing

when to release the button before an immediate "hold volume down and press power" to get to the bootloader.
[Nexus 9 Q&A, Help & Troubleshooting] musashi109:
I tried that, but it did not work. anyway... I have smooth access to hboot :crying:
[E 2015 Q&A, Help & Troubleshooting] johnomaz:
Ok, I've read around and since there are so many different answers, I need to ask and hopefully get a redirect to a confirmed thread or a straight up answer. I bought my daughter a 2015 Moto E phone. I got it from Amazon and it was advertised as factory unlocked GSM for use on AT&T or TMobile. Great, we are on TMobile so thats just right. I get it in the mail and its in an AT&T GoPhone package. Its the right XT1527 model and had all the right bands for TMobile so thats ok. I've already gone to att.com/deviceunlock and am waiting for my unlock code which customer service said wouldn't be an issue. But, its got all the crap AT&T apps preinstalled. I know where to find the 5.1 TMobile XT1527 firmware. If I flash that on my phone, will there be any negative side affect since its officially an AT&T branded phone? Do I have to wait for the SIM Unlock to be done first?
[E 2015 Q&A, Help & Troubleshooting] xtermmin:
If you ordered this specific (http://www.amazon.com/gp/product/B00TFAVFL4) from Amazon, return it and get your money back. The factory unlocked model sold through Amazon does not come in a GoPhone package, comes in the standard Moto box. It also does not need any unlocking via AT&T's device unlock, just pop in the SIM and go.

Both the Moto-factory-direct and the AT&T/Cricket Moto E2s have the same model number, XT1527, but the AT&T/Cricket model has a bootloader that cannot be unlocked at present, so no perm. root, no /system read-write access, no custom recovery/ROMs, etc.

T-Mobile never carried the Moto E2, so there are no T-Mobile-branded ROMs available. And with a locked bootloader, I doubt you'll be able to install the Moto-factory-direct stock ROM (with no carrier bloat).
[E 2015 Q&A, Help & Troubleshooting] johnomaz:
Thank you. For this phone, I'm not concerned about unlocking the bootloader. Its for my daughter, shes 9, as an emergency phone as well a starter phone. I got the ATT unlock code and it worked so its working fine on my TMo SIM. I tried a couple other firmwares and they softbricked the phone so I put the ATT one back on, disabled the ATT apps and its as close to stock as its gonna get.