Any ideas what app is constantly giving me this notification randomly?

It keeps happening throughout the day on the home screen, in apps and even on the lock screen.

Attached Thumbnails

 

[Themes] All my themes - Ideas and WIP

Hello guys,

You will find here all my themes, WIP and if anyone have Idea please share it :)

Thanks!

Themes:

Flat (Gold / Purple / Vivid / Blue) Theme - S6/E
Cyber Theme
iGalaxy Theme
Rainbow Theme
Flatron
Orion


WIP:

Hope - theme






Ideas:
?

Nexus 6 stock on Boot (not bootloop). Please help with ideas?

Hi,
So I wanted to prepare my unlocked Nexus 6 on T-mobile for my brother by completely un-rooting and then relocking to setup stock firmware. With the help of “Nexus Root Toolkit” it was a quick update. I simply picked up the latest firmware for t-mobile, then relocked - and off you go.

The Phone was ok for couple of days, but then google pushed new update – which would render my phone useless. After update Initially the phone went through the boot almost to the end, and then exception happened. Something about system UI crashing and then screen was unavailable. So I could not do anything on the phone.

I tried fixing with “Nexus Root Toolkit” (unlocking, rooting etc.), but at this point the phone is stock on booting (few colored dots signifying loading), but the phone never actually boots. Going to Factory reset or Recovery does nothing.

Is there anything else I can try please?

Thanks,
-Mariusz

Display broken, need ideas for the way ahead

I had purchased the Moto Turbo (Indian Version XT 1225) for ~USD 650. Recently, in a minor accident it broke. Ouch
>> Visible damage: Top glass seems fine, but the display underneath is cracked, no longer functional (We do not have the free one time screen replacement option that Verizon gives. Plus I did not have any other insurance).
>> Possible invisible damages: Right after the accident, the phone became pretty hot, and it was vibrating every 15 odd seconds for about an hour or so (till it ran out of battery, perhaps). I don't know if the internals suffered from any shock or heat damages.

The authorised service center says the Display unit replacement will cost ~USD 280. Any other possible, though unlikely, damages to the battery/motherboard can be determined only after the display is replaced. I have not been able to find out if display units for the Turbo are available for cheaper from third parties in India, any idea about that?

Now my dilemma. Do I go for the screen replacement for a very expensive ~USD 280. Or do I go in for a cheaper handset. I really liked my Turbo, more than what we have on the market right now, the only two gripes being the camera quality compared to it's peers and the doubtful upgrade to Android M. But it has not had a price reduction, and in the current mobile market, shelling out ~USD 650 for it seems too much.

Thoughts?

[REQUEST] Ideas for solving locked bootloader soft-brick

Hey guys, Kyuubi10 here again.
Recently I had an issue with my nexus 9, which is becoming increasingly common.
Where one can permanently soft-brick their nexus, for lack of ticking the "Enable OEM unlock" button, then bootlooping their device while locking their bootloader, thus making it impossible to reflash a system image through fastboot.
If you're lucky enough to still be able to access your custom recovery your device is still salvageable, but if as me you were performing a factory reimage when you locked your bootloader chances are that you have gone back to stock recovery, and only after realised that your OS was bootlooping.

From reading about it, I found out that it was virtually unrecoverable, unless you managed to keep your custom recovery, by either flashing a new system or if your recovery refuses to flash new system you can use this: http://forum.xda-developers.com/nexu...nlock-t3113539.

But in all of these cases you still need a custom recovery.

At the end most people gave up and either bought another device or used their warranty to replace their device (Which I am trying to attempt, if my warranty isn't completely voided.)

So, finally reaching the important point of this thread, I have had a couple ideas which could work to solve this issue but since I don't have enough knowledge I am unable to actually test the idea.
For the device to recognize the lock status of the device even without an OS present means that there must be a flag the bootloader reads. By reading further I found this. http://newandroidbook.com/Articles/Nexus9.html

This basecally explains that Nexus 9 has a partition called PST (Persist) whose only job is to provide the value of this flag. I was wondering whether it is possible by using Linux could get a more direct access to the partition and change its binary value to enable the "enable OEM unlock" variable (Described by fastboot as "Ability is 0").
I had this idea because one day when I bootlooped another device and ADB on windows failed to recognize the device I booted linux and used ADB from there. And the phone was reconized.
This works because Linux can view partitions with different filesystems, where as windowns can only see partitions which have been formatted into "Windows" partitions (e.g. FAT32, NTFS).
So in theory using a Linux OS to access the different partitions in Android should show up much more information, and give you better access. But apart from this I don't know much more. I will be testing this theory out in more detail. But I am challenging the more experienced contributors out there to help out in overcoming this issue!

Please, this is a real issue which is limiting newer nexus devices. If anyone has any new ideas please share by commenting, and lets help each other out to find a solution to this problem.