yashsingh1/xdaforums huggingface dataset:
[Android Themes] TwoMountains:
MATERIAL. INTERACTIVE. ANIMATION

THIS IS THE BEST LIVE WALLPAPER IN THE STYLE OF "MATERIAL DESIGN"

Tap the screen to create a animation circle. Many animated themes, support multi-touch and vibro-touch, a lot settings and more.

:good:Please download the FREE app to support project:svetius:

[YOUTUBE]Nm2VjvIqFjA[/YOUTUBE]​

FEATURES​

44 Animated theme

Animation circle

Ideology of Material Design

Multi-touch and Vibro-touch

60 frame-per-second

Energy savings

Support all launchers

Many options settings

DOWNLOAD​

​

LINKS​

Website (online interactive demo)

YouTube

Twitter

XDA:DevDB Information

MATERIAL CIRCLE, Theme for all devices (see above for details)

Contributors

TwoMountains, TwoMountains

Version Information

Status: Stable

Current Stable Version: 1

Stable Release Date: 2015-11-17

Created 2015-11-17

Last Updated 2015-11-17
[Android Themes] blackbuffalo:
So beautyfull

I'm current use ChroomaLWP but now I have reason to switch to this
[Android Themes] TwoMountains:
Many thanks :):good:
[Android Themes] jarkony:
Excellent!

I like this, really! Beautiful, concise, simple. Keep it up.
[Android Themes] TwoMountains:
Thanks! :)
[Android Themes] jejehtc:
I follow you on twitter and I re-twitter message.;)
[Android Themes] TwoMountains:
Merci bien! :)
[Android Themes] jejehtc:
are you Frenchy ?
[Android Themes] TwoMountains:
:) no
[Android Themes] TwoMountains:
Video review

Hello :)

New video review of the MaterialCircle

[YOUTUBE]Nm2VjvIqFjA[/YOUTUBE]
[Android Themes] peps16:
Nice Work! Beautiful :)
[Galaxy Note 4 Q&A, Help & Troubleshooting] chrisplettuce:
I accidentally selected to block premium texts on my Note 4 on O2 and now I can't find out how to unblock it. I phoned O2 who said they had taken the block off but my Note 4 still won't allow me to send premium texts which is a nuisance as i'm trying to make an important donation to an animal charity. Can anyone point me towards instructions on how to take the block off please?

Thanks in advance to anyone kind enough to help.
[Nexus 6 Q&A, Help & Troubleshooting] cyber_pete:
Hi all, I have been running my Project Fi Nexus 6 stock but rooted and love it. I am contemplating upgrading to Marshmallow but was hoping to get some feedback from other who have gone there. So anyone out there on Fi and Marshmallow? How do you like it? Do you recommend upgrading? Some other questions:

Which ROM? Stock or Pure Nexus?

I have heard downgrading the bootloader is a bad idea after going to Marshmallow, has anyone gone back to 5.1.1?

Is there a radio that seems better for Fi?

Any concerns with the new root method?

Anything else you can add.

Thanks for and advice.
[Nexus 6 Q&A, Help & Troubleshooting] NLBeev:
It is personal, but here are my choices. An already rooted and updated rom. http://xdaforums.com/showthread.php?t=3059493 Goto the OP.
[Android Stick & Console AMLogic based Computers] hcorreo:
Hello,

Perhaps all can make a list of clones of MXIII-G that can admit the same ROM:

The First:

- MXIII-G

- TRONSMART MXIII-PLUS

<MOD EDIT - RESELLER LINKS ARE NOT PERMITTED.>

Thank All.
[Android Stick & Console AMLogic based Computers] hcorreo:
UPDATE

- MXIII-G

<MOD EDIT - RESELLER LINKS ARE NOT PERMITTED.>

- TRONSMART MXIII-PLUS

http://www.tronsmart.com/products/tronsmart-mxiii-plus-2g/8g-quad-core-android-tv-box

- ACEMAX M8S+

- CX-S806

- BEELINK S82PLUS

USE AT YOUR OWN RISK.

I dont have tried this.
[Android Stick & Console AMLogic based Computers] jimacid:
How do you tell if a device is genuine or clone?

I bought this one

http://m.banggood.com/MXIII-G-Amlogic-S812-Quad-Core-2GB8GB-Bluetooth-1000M-LAN-Android-TV-Box-Mini-Smart-PC-p-985181.html

Is it a genuine or a fake?
[8525, TyTN, MDA Vario II, JasJam ROM Development] dharle:
Has anybody already changed the page pool size with hermes 100 and rom Schap's 3.60a ?

Thank you
[8525, TyTN, MDA Vario II, JasJam ROM Development] kinky-chinky:
Check this post:

http://xdaforums.com/showpost.php?p=1458362&postcount=106

k-c
[8525, TyTN, MDA Vario II, JasJam ROM Development] pietrucci:
who hasn't???

try the small program pagepoolchanger, search the forum.
[8525, TyTN, MDA Vario II, JasJam ROM Development] jcespi2005:
http://xdaforums.com/showthread.php?t=325118
[Huawei Ascend Mate 2] Netrunner157:
So I installed the Lollipop stock rom via the dload folder in the official manner by rebooting and holding vol up + power. Rom installed just fine and everything works but the CPU frequencies are driving me up the wall. This rom/kernel seems to ignore SetCpu's or No Frill Cpu's settings.

Here is what I did and what I see:

1) Yes I've commented out the build.prop entry where it says min=787 and rebooted several times.

2) On boot up I see via Setp CPU min frequency is 787. Draging the min value to any value below 787 doesn't work.

3) Sometimes after turning on the device I'll go into SetCpu and see min set to 300. However several times in the day I'll check out of paranoia and it's back to 787.

4) I've used both Set Cpu and No frils cpu app and set "Set on boot" and that does nothing. I'll often catch the min value floating @ 787Mhz. This is also confirmed by checking time in state and even when turning off the screen, I'll see the 787 usage jump but not the 300 or 384 speeds.

5) Sometimes I see really whacky ****. Like I had Set Cpu open, and the Max was changing from 1593, to 1497, to 1400, to 1100 and then back to 1497.

6) Powersaving is set to normal, not smart, or ultra.

Has anyone gotten the kernel to follow the min/max settings for CPU freq? Anyone have a solution?
[Huawei Ascend Mate 2] robertbarber:
Have you checked to see if CPU hotplugging is turned on? If it is then it will make changing the min almost impossible.
[Huawei Ascend Mate 2] Moody66:
Mpdecision.. Qualcomm closed source. Hate it.
[Huawei Ascend Mate 2] Netrunner157:
> Have you checked to see if CPU hotplugging is turned on? If it is then it will make changing the min almost impossible.

How do I do this?

> Mpdecision.. Qualcomm closed source. Hate it.

Is this a tool that fixes this?

So many people have upgraded to Lollipop and yet how is it that I'm the only one bringing up this 787 issue?
[Huawei Ascend Mate 2] Davinci50:
https://www.google.com/search?q=Mpd...ome..69i57&sourceid=chrome&es_sm=122&ie=UTF-8
[Huawei Ascend Mate 2] robertbarber:
This is from the program kernel adiutor program you can find here( http://xdaforums.com/android/apps-games/app-kernel-adiutor-t2986129) If you turn hotplugging off you might have better luck setting the min. It will be listed as CPU hotplug in the menu.
[Huawei Ascend Mate 2] Netrunner157:
Oh man I did not know how to use google. You opened my eyes. /s

> kernel adiutor

kernel auditor did not help, even after two reboots. i still see min stuck at 787. Is this issue perhaps solved in the lollipop pacman rom?
[Huawei Ascend Mate 2] Moody66:
CM drops to 300.. Turn off mpdecision.
[Huawei Ascend Mate 2] Netrunner157:
OK so I definitely turned off mp decision both via the app and by renaming /system/bin/mpdecision --> /system/bin/mpdecision-lolololol

Rebooted and checked setcpu and my min is still stuck at 787. Granted I check in a few times a day and sometimes I catch the min at 300 yet sometimes I catch it at 787. What else am I missing?
[Huawei Ascend Mate 2] Netrunner157:
Is it a stable rom? How many reboots do you get, wifi issues, force closes etc? I'm not a fan of rom's not based off of stock rom, because of instability. I left those behind with the Note 1, Motorola Atrix.
[Huawei Ascend Mate 2] Moody66:
Its in snapshot phase. Of course its stable.
[Huawei Ascend Mate 2] Netrunner157:
Yes it might be a stable version of CM but is it stable on the Mate 2. I know the difference between stable and nightly.
[Huawei Ascend Mate 2] Moody66:
Its fine. Read the cm forum thread.
[Huawei Ascend Mate 2] Davinci50:
[MENTION=5530607]Moody66[/MENTION]

No probably like most of the rest he wants to be spoon fed, I was able to determine what you meant in your first post about mp desicsion and determine the appropriate course of action that I wanted to take and also referenced your thread about battery life.

Make a backup, load the rom ,and test drive it like we all do.

God I love Google NO /s
[Huawei Ascend Mate 2] Moody66:
I found a governor that replaces mpdecision. Going to add it to a build. Last two attempts I had issues. Nothing related to governor though. Soon. Pilled a nub mistake with boot.IMG. lol three year old distracting me. So all good. Should help tremendously with cpu. A couple of builds floating around with another governor that does help quite a bit.
[Huawei Ascend Mate 2] Netrunner157:
So the general consensus is that Lolipop stock rom cannot have the 787min freq fixed and the solution is to switch rom's altogether? Like I said I disabled mpdecision and even renamed the binary and commented out the entry in build.prop. What else is left?
[Huawei Ascend Mate 2] Moody66:
Isn't that easy. It will always default of there isn't something to takes its place.
[Huawei Ascend Mate 2] Netrunner157:
what is easy? You mean to tell me stock lollipop will default to 787 until what takes it's place? No one knows?
[Huawei Ascend Mate 2] Moody66:
It's stock ROM. If you want to make changes flash a ROM. Huawei isn't going to give you that customization.

Noone has made a custom kernel for it. Obviously since it has emui.
[Huawei Ascend Mate 2] Netrunner157:
Is 787 hardcoded somewhere in this rom that it's usually defaulted to?
[Huawei Ascend Mate 2] Netrunner157:
Installed a SSH server and used Linux's grep command to find all instances of the 787 string. Besides 787 appearing randomly in binaries, pictures I found it exists in a shell script in /system/etc/init.qcom.post_boot.sh.

Well what do you know:

root@hwMT2L03:/system/etc # grep init.qcom.post_boot.sh -e "787"
echo 787200 > /sys/devices/system/cpu/cpufreq/ondemand/optimal_freq
echo 787200 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 787200 > /sys/devices/system/cpu/cpufreq/ondemand/optimal_freq
echo 787200 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

Search is still running, but I believe that if I comment these few lines out, 787 should no longer be messing with setCpu's settings and remain 300 min cpu.

I'm going to backup first and then see if my theory holds true.

edit: It works and cpu idles at 300, setCpu TimeInState confirms 300 is the new optimal frequency as well. So yes you can use the stock rom and get great battery usage!
[Xperia Z1 Original Android Development] optimumpro:
Here is updated Thermanager, which could be flashed in recovery. I have made some changes after I played Asphalt game for about one hour. With this update, on performance governor the temperature never went higher than 58. And we are talking 1 hour straight. I doubt you can have that on stock. What was interesting that performance governor produced less heat than interactive, which supports my claim that when cpu jumps frequencies, it creates additional overhead.

Now, regarding myths and fiction about stock rom not overheating. There are some dudes on this forum who complain that their Z1 overheats to 70+ on custom roms when they play their beloved games; on stock, they say, there is no overheating.

Here is a short answer. You, guys, don't know what you are talking about.

Custom roms (and custom kernels) give you tools that are not available in stock. You just have to learn how to read/use them. Here is one example: some roms allow you to have internal cpu temperature on screen. Now that you have it, you watch. When it hits 70, you panic, but if you touch the back door, it will be barely warm. So, when you are on stock and without temperature reading, you think your phone is not overheating, while it can still have 65-70.

I used a modified version of M5 kernel compiled with GCC 5.2.1 Ubertc; CPU at 2457; performance governor, inteliplug balance with touch boost disabled; GPU overclocked to 600 with msm-adreno-tz idle wait 30 and workload 3; swapiness 10; enthropy 1024 read/write. That was on DU rom, but I bet the result would be the same on Jaguar and some other custom roms.
[Xperia Z1 Original Android Development] ScatteredHell:
lol, that dude is Me, and I will try this, in the stock rom I can see an process running as overheat manager or something, I think it might have to do something with it. I'm sure that my device got heated very much, I didn't meant to offense but you seems to got it wrong. btw I will try this. I use Jaguar atm.

Thanks
[Xperia Z1 Original Android Development] SuperLamic:
I don't think that my phone won't reach 60 C on stock, but I like watching YouTube, so I can see how fast it warms. (I have xposed module that shows me cpu temp even on stock). And as much as I can say my phone warms faster on custom roms than on stock. No matter what governor I use.

Also all animations (like status bar showing) are kind of laggy on custom roms. I don't know it it got better in past 2 months, but last time I used custom rom my phone reached 50C even only with chrome.

Interesting thing is that this all (including animations) is not present on 3.10 kernel, but there are no usable roms at the moment with 3.10 kernel, so I have to use stock.
[Xperia Z1 Original Android Development] optimumpro:
So, what's the temperature your xposed module shows on stock under stress?
[Xperia Z1 Original Android Development] SuperLamic:
Usually after 20-30 minutes of YouTube it's around 53-54°C
[Xperia Z1 Original Android Development] optimumpro:
Which browser or is it a youtube app? I have similar temps on Firefox and about 44-48 when using Chromium (not chrome).
[Xperia Z1 Original Android Development] optimumpro:
Overheat manager: whatever it is, all it does is throttling and thermanager does the same on custom roms. So, the trick is to throttle enough without you noticing any lags...
[Xperia Z1 Original Android Development] SuperLamic:
It's a YouTube app. Really? It's weird, maybe I'll try, but I can see the difference on battery time when I come home from school - on stock I have ~70% and on custom roms I have ~50. Anyway I'll try and report after few days.
[Xperia Z1 Original Android Development] SuperLamic:
Okay, I can say that custom roms are now ok for me when it come to battery life. I compared usual usage of mine on stock and custom roms and now it really gives me same battery life. The only change I made this time is that I used DU instead of Jaguar and this thermalmanager settings.

Though there are still two things that bother me on custom roms: laggy UI - I don't know what causes that, I tried changing lot of cpu/gpu thing to sort it out, but nothing helped. And the other one is headset connecting - I have to press and hold (for a little while) all the buttons on headset to get it recognized.

I'm returning back to stock, but I can say that now is overheating on custom roms gone.

Thank you, [MENTION=5075064]optimumpro[/MENTION]
[Xperia Z1 Original Android Development] optimumpro:
OK. Nice to hear that about battery life and overheating. With regard to lagging: it is not cpu, but rather animations. Either disable them completely in developer options or in DU you can go to tweaks and pick and choose whatever animation you want. I just disable all animations and have absolutely no lag.
[Xperia Z1 Original Android Development] AnrgKrshn:
Oddly enough, I find custom ROMs hae smoother animations than stock, in my phone. But I don't have good battery life when compared to stock..
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Tabrune:
I've been doing research and experimenting for the past few days, with only 6 hours of sleep in the last 48 hours. Long story short, I had a Droid TURBO on Verizon, loved it, the best phone I've ever had hands down. A month or so into having my Turbo, my family switched to Sprint, rendering my Turbo completely useless as a phone :( Skip a few more months ahead to 11/15 when I broke my Samsung S6. I was looking for an excuse to figure out how to do this, I'd done a few hours of research, but never really had a reason to attempt what I have been. My goal is to allow my droid turbo to call/text with my sprint number and plan. My first idea was to simply open up some bands, maybe change some APN settings, BOY was I in for a trip. I'm currently running the 5.1 OTA of Lollipop on my Turbo, which means I have a locked bootloader, however I've gotten as far as getting temporary root access on 5.1 OTA (SU3TL-39). I wasn't sure how temporary root worked at first so of course, I was trying to get "XPOSED" working with this temporary root, then I could modify the phones information and trick Sprint into thinking that my Droid Turbo, is actually my old phone. I attempted to change the IMEI swap the two different IMEI's however it was soon after that, that I found out that my temporary root doesn't actually save after a boot, or even in-between roots. Kingroot seems to have to keep re-rooting itself in order to keep it's temporary root alive. Anyways, I've been up all night, and I've got to get to Uni. I'd like to see what other ideas you all might have. At this point I've gotten invested in attempting to find my own method to rooting, or flashing a modified firmware of some type. I'd really like some guidance in these fields even if my Turbo will never work with Sprint. I appreciate those of you who read the post entirely. :)

EDIT: I've gotten many different theories, but the only way I see myself doing this is by somehow downgrading and starting from complete scratch, maybe even rebuilding the OS just to miss the security update? (All of these things are probably impossible, but I'd really like to think that we can figure something out together instead of letting the TURBO die.)

EDIT 2: ****, I really need to leave, but I had one last idea as I walked out the door, I'm sure it's out of the question, but maybe there's some way to physically modify the TURBO, or even modify the IMEI that the SIM card is looking for in the first place, but all just theories, will come back later with more ideas!
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
There are two problems that you're up against:

1. The /system partition is write protected. Even with temp root (or permanent root, for that matter), /system cannot be modified. To use anything via the xposed framework, the framework must be installed, which requires writing to /system, which is impossible. The only way around this is the moforoot exploit, which allows flashing of pre-modified /system images, eliminating the need to modify /system while the phone is running. However, this does not work on the 5.1 bootloader, which you have.

2. As you correctly state, the bootloader is locked. That means no downgrading and no flashing of modified firmwares using official flashing methods (fastboot, mfastboot) or non-mofo unofficial methods (TWRP, FlashFire).

This thread discusses hardware modifications. It's way above my head, so I'm not sure how useful it is: http://xdaforums.com/droid-turbo/development/rd-turbo-jtag-emmc-direct-hardware-t3162558.

Hope this is at least moderately helpful.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Tabrune:
I suppose there's no way to disguise an exploit within some of the core system files? Since all of these files are signature checked, but how exactly does signature checking work with the Lollipop, I doubt that it would be easy to trick, but maybe some reverse engineering of it? Trick it into thinking that everything is okay even though an exploit is riding alongside a system file.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Even if that were possible, it would not help you, since that would require being able to write a file to where the core system files are stored (/system). As for how signature checking works, I think it is enforced by whatever is stored on the /boot partition, but I'm not sure about that. A locked bootloader will not allow flashing modified images to /boot, and there are no known ways to bypass this.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Tabrune:
When I get home, I'm going to do some experimenting on attempting to strip down and down grade to KK. I know that it most likely won't work, but I will gain some knowledge about it at least.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] classic757:
Yep, the boot partition is what would have to be bypassed or unlocked in order to be able to write to system. That is where all the sig checks are locked in, right in the boot partition.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] xBr4v3x:
Well, we had a BL Unlock coming to us in a few days, maybe a week or two. With that, you can flash what you need to attempt to use with sprint possibly, depending on the bands the Turbo has
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Tabrune:
I've gotten the phone to work to an extent, I'm hoping if the BL unlock happens that it will open up lots of opportunity.
[Nexus 6P General] Slacker101:
I've seen a lot of people asking if their 6P is covered by Asurion through Verizon and I would like to clear up any misconceptions or questions about the matter. I have seen a lot of conflicting information or wrong assumptions on the forum. This is all based on my experience and conversations I have had with BOTH Verizon and Asurion and I am 100% confident it is true. I have called to verify and if I wished I could make a claim on my 6P. The option was validated and presented to me by a manager of their customer support.

There are two types of coverage through Verizon Wireless. Total Mobile Protection and Total Equipment Coverage. Total Mobile Protection includes Total Equipment Coverage.

Total Equipment Coverage includes both Verizon's Extended Warranty Program and the Asurion Wireless Phone Protection.

If your line has Total Equipment coverage and you currently have a 6P activated then your Verizon Extended Warranty Program eligibility is nullified. For the simple reason that they do not carry the phone in stores, thus they will not extend the warranty of troubleshoot it. Pretty straight forward. However, the Asurion Wireless Phone Protection does still apply. Asurion's insurance applies to any device that is both activated and natively supported by Verizon's network. The 6P does in fact activate, and stock is 100% compatible with their network. Thus they will honor the insurance and issue a claim for the device, no problem.

So, while the Extended Warranty is useless, the insurance is valid and, in my mind, worth the $8 a month I pay for it rather than mess with nexus protect where theft is not covered and the deductible is essentially the same.

I cannot guarantee that they will replace the phone with a Nexus 6P, though it does look likely. The manager wasn't sure and was going to get back to me. They have a relationship with most of the major US carriers, so the manager is confident they will carry them.

Note: This also applies to the Nexus 5x and the Moto X Pure Edition and any other phone natively compatible with Verizon's network
[Nexus 6P General] fatboypup:
Sprint made me drop TEP too when I added my 6p
[Nexus 6P General] Fanaticalism:
Sprint doesn't use assurion anymore.
[Nexus 6P General] bbedward:
The deductibles are so high that I would think nexus protect or squaretrade would be better still, at least in my past experience with asurion.
[Nexus 6P General] Slacker101:
I could be grandfathered into a lower deductible but I only paid $100 dollars when my phone was stolen on the train. Is it higher for others?

Someone snatched it out of my hand when I was pulling it out of my pocket. Living in a large city and taking public transportation I find the theft coverage important.
[Nexus 6P General] fury683:
Am I correct in my understanding that my Nexus Protect would be great for a defective or broken phone to ensure I get a brand new unit from Google, while Assurion will cover a lost/stolen phone? I don't think Nexus Protect covers lost/stolen, only damage.