yashsingh1/xdaforums huggingface dataset:
[Galaxy S6 Edge General] veener79:
It is kind of weird right now when I got my HTC M7 I was loving trying new ROM's. As time went on it was not as big of a deal. Right now on my Edge I am just having a hard time just putting the time into rooting it. I am just not seeing what hug plus I am getting from rooting right now. If someone come out with something that allows me to clean off all the bloat ware with just root then I might do it. Or if there is a clean ROM to do it I would be for it too.
[Galaxy S6 Edge General] done12many2:
The Edge is about as good as it gets right out of the box. It definitely gets better debloated if you can believe that.
[G2 Q&A, Help & Troubleshooting] AhmedRana:
Regarding my question here.there hasnt been any answers herehttp://xdaforums.com/showthread.php?p=60651149

So I am asking the g2 community.

I was considering to buy g3.

I am confused between g2 or g3?

Which is more faster. Which has more battery life?

As due to high resolution screen i have heard g3 performance isnt as good as g2.

Are these true?

Im getting a d850(slightly used 3gb ram) or d802(new).

Which one is a better choice
[G2 Q&A, Help & Troubleshooting] diogofd8:
G2's performance is better than 16GB ROM 2GB RAM G3. The 3GB/32GB is better. I believe it will not have game performance as good as the G2 but the screen is bigger and better and the RAM will make multitasking better too.

Battery the G2 is one of the "battery kings". Much better than the G3.

G3 Pros:

Screen quality

Camera

Accessories avaiable at the moment

Design (IMO)

G2 Pros:

Battery

Performance (better than 2GB G3, slightly better than 3GB G3 I believe)

Price

Sources: My girlfriend has 2GB G3 and I have D802 G2. So I am used to both of them.
[G2 Q&A, Help & Troubleshooting] danieldp1990:
G2 VS G3

I already used both of the phones, first the G2 and then the G3 (16gb), but now that my G3 was stolen I decided to get a G2.

The truth is..

G3 have a better display resolution (but it drains battery really fast, and colors are less vivid).camera on G3 is actually the same as the G2 the only difference is the laser focus (upgrade the G2 to lollipop and it will be almost the same ). The speaker on the G3 is much more lauder and clearer than G2 for sure (speaker on G2 is not bad at all, is good). You can expand the memory on G3 while on G2 you can only have 16 or 32GB (I bought the 32GB version of G2, and when I had G3 16GB version I never needed an extra memory, so 32GB is more than fine for me). Now for performance the G2 is clearer the winner, les lag on gaming due to the screen, and much mire battery life. and for design I love both but it feels much better to hold the G2 on hands than the G3.

In conclusion il stay with the G2 and later buy the G4 or G5...:highfive:
[G2 Q&A, Help & Troubleshooting] maydayind:
I have both phones.

I gave the g3 to my girlfrend and I'm keeping my g2 with cm12

Battry life is beter. It's faster with cm then g3.

The GPS on g3 is aufull and it's not as reaponsive.. The soc 801 is to slow to handle the display on g3.

I'm not bying a g4 think il switch to nexux
[G2 Q&A, Help & Troubleshooting] AhmedRana:
Thanks for the advice. I already bought the g3
[Galaxy S 5 Q&A, Help & Troubleshooting] RBEmerson:
I'm having no luck finding a howto to move my rooted VZW SM-G900V from KitKat 4.4.2 to Lollipop 5.n I found one howto that supplies the kernel but conveniently uses Rapidgator and another pay-to-play d/l site. Other than that, nothing. What am I missing??
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
sammobile dot com

samsung - updates dot com

Use ODIN to flash
[Galaxy S 5 Q&A, Help & Troubleshooting] RBEmerson:
Um, thanks, but no thanks. Both sites are "pay to play". Please see XDA rules 11 and 13.
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
Umm no they are not, why not actually read things first, and try to download from them before guessing?

Don't you think by now I would already know XDA rules?

Not need reminding by someone with very few posts who could have easily found the same advice and ROM download sites offered over and over on these forums if they had actually read a few threads?
[Galaxy S 5 Q&A, Help & Troubleshooting] RBEmerson:
BTDT - pay to play
[Galaxy S 5 Q&A, Help & Troubleshooting] RBEmerson:
Let's see... I go to Samsung-updates.com and find SM-G900V. I hit the download button and there are rapidgator.net and uploaded.net. OK, let's try the "I'm not up for paying you" button and... "file too big" (uploaded.net) or "upload your files here" (rapidgator.net). So I have to buy into premium, leaving credit card info on an otherwise unknown site. If that isn't pay to play, then what is?

OK, let's try sammobile.com... SM-G900V? Nope, not listed.
[Galaxy S 5 Q&A, Help & Troubleshooting] Rakuu:
Lol that site is not payed in any way, for the stock roms at least, having ads or making you wait to download is not pay to play either, you can go on that site and get what you want living off the streets on McDonald's wifi. Check your device model specific secton http://xdaforums.com/verizon-galaxy-s5
[Galaxy S 5 Q&A, Help & Troubleshooting] RBEmerson:
What site is "that site"? sammoble.com only knows about the SM-G900F. Samsung-updates.com knows about the SM-G900V but the download moves to rapidgator or uploaded, and neither will d/l the file in free mode, period. Again, BTDT.
[Galaxy S 5 Q&A, Help & Troubleshooting] *Detection*:
Sammobile actually knows about the device you say it doesn't

And would you believe it, RapidGator allows the download in free mode without any problems from samsung - updates dot com

----

Just leave OP to it guys, he's looking for a free ride, not willing to do any work himself to get the ROMs
[Xposed Framework Modules] tonyp:
Battery Shutdown Manager

Download @ Google Play

​

Do you know that moment when you're on 1% of battery and think "I'll just use my device 20 more seconds then I'll get my charger" - and at exactly that moment it'll switch to 0% and you'll see the threaded "Shutting down" dialog and know it's too late now?

This Xposed module will help by showing you a dialog with a countdown before the actual shutdown, so you'll have time to attach your charger.

The module achieves this by postponing the shutdown for a couple of seconds to give you time to connect the charger.

Please post any kind of feedback or ideas you have regarding this app :fingers-crossed:

I tested the module a lot but can't possibly test it for all those different phones and versions out there.

Thus I will flag it as beta for now so you can provide feedback before I'll release the 1.0 version.

It would be great if some more people could test it. I used the StabilityTest app to quickly drain my battery down to 0%.

Compatibility:

I wrote this module and tested it with AOSP devices as well as on Cyanogenmod.

It should work without any issues on all Nexus and Google Play Edition devices from Android 4.2 to 5.1+.

As almost all Custom ROMs are based on either AOSP or CM they should work without issues, too.

Some vendors might have changed the original code and thus render this module incompatible on their device. Nothing bad will happen when you install it, it just won't work.

Compatible:

Nexus / AOSP / GPE ROMs

Cyanogenmod

Almost all custom ROMs (as they're usually either based on AOSP or CM)

Sony Stock ROMs

Not compatible:

Currently not working for LG Stock ROMs due to internal code changes by LG.

Android devices <4.2. Support for Android 4.0.3+ and 4.1 might be added when I see a greater demand for it.

Installation:

- Download the app

- Activate the module in the Xposed Insaller

- Reboot your device

- Open the app to change it's options to your liking

Bugs/Issues:

If you encounter any bugs just report them here and I'll try to fix them. Always include as much information as possible, including your device model, android version and exact ROM details.

Note that I will most likely need a log to fix the issue, a generic "doesn't work on phone xyz" won't help me fixing the issues.

There are two possibilities to get a log.

Use the Catlog app. In the app press Menu > Record Log before the device shuts down, then attach the logcat to your bugreport.

Alternatively you need to use adb to grab the log.

Unfortunately logging is a bit more complicated for this module as the interesting part happens on shutdown.

The best solution (and what I do personally for debugging this app) is to use ADB over WiFi (e.g. with this app) and grab the log.

Download:

Google Play Store

Xposed Module Repository

Google+:

www.google.com/+thetonyp

Last but not least an obligatory huge thanks to [MENTION=4419114]rovo89[/MENTION] for his amazing Xposed framework!

If you like this module don't forget to press thanks, rate this thread with 5 stars, consider a donation etc. etc.

:fingers-crossed:
​
[Xposed Framework Modules] BackToMyFuture:
I love your icon pack!
[Xposed Framework Modules] mobihack:
Tried it on my cm12.1. No bootloops here. Will edit after full uncharging

EDIT: Turned turning on full brightness, hot spot, gps, flashlight, mobile data, etc... Still 8% to go. Your module and me are waiting eagerly lol

EDIT2: Finally reached 0

And tonyp, I am pleased to say your module works in cm12.1

Suggestion: Make the dialog box closable. So if I am playing a game or writing to a File I can save my progress. Hope you understand.

And I appreciate your idea. Well implemented.

And do you mind sharing that icon pack :hungry:
[Xposed Framework Modules] shivadow:
Samsung galaxy s3 i9300 4.3 mk6 stock rom, bootloops.

Sent from a stolen phone!
[Xposed Framework Modules] DecypherT:
Bootloop on Nexus 4, Stock Android 4.3.3...

EDIT Because OP asked how the bootloop occurs on Nexus 4, Android 4.3.3:

Bootloop occurs after activating module and normal (not soft) reboot.

Before reboot app can be runned and configurated.

I have no log app running, so I'm not able to deliver logs.
[Xposed Framework Modules] tonyp:
Yes, please send me a logcat. Bootloops are great, then you can just get the log after the reboot. I literally can't do anything without a log.

Thanks for the feedback, then I will add 5.1 to the compatibility at the Play Store.

Regarding the closable dialog, I made it non closable on purpose but I'll consider adding an experimental feature to change that. At first I'd like to fix the bugs, though.
[Xposed Framework Modules] mobihack:
More suggestions:

Add some animations to the dialog

Add option for an alert tune or notification 1min before

Add buttons to dialog box for shutdown(sometimes I dont like to wait)[optional]

Happy with what you had already done and you forgot me an icon pack
[Xposed Framework Modules] akhilkbaby:
bootloops

Bootloop on MMX Canvas Magnus stock ROM (JB 4.2.1) :(
[Xposed Framework Modules] tonyp:
I'd like to fix the issue, could you kindly send me a logcat of the bootloop?

Unfortunately there is literally nothing I could possibly do without a log.

I'm using the stock dialog which guarantees the highest possible compatibility with other devices.

Regarding the notification, I don't know when the battery will be empty before, so there's no way to display a message one minute before. All I could do is starting the dialog at 1% (which I'm considering for a future version), but that would be quite different.

I like the idea for a shutdown button, an option to include that will be in an upcoming version.

Oh, true, the icon pack is called etched material.
[Xposed Framework Modules] HydraS4:
Phone freezes when I get a notification from an app. Specifically when I get a notification from Messenger(Facebook app). Is it possible to grab a log if it freezes and I have to restart?

And to make sure it wasn't anything else, I uninstalled it and the freezing stopped.

Galaxy S4 4.4.2 Stock ROM w/ Root

Thanks
[Xposed Framework Modules] tonyp:
This sounds very strange, the module is only hooking into one class which has nothing to do with receiving messages.

Yes, usually it works to log the freeze, just start logging (best would be with adb logcat) before it happens.
[Xposed Framework Modules] Mubasher96:
Can not install on 4.1

I am trying to install it on my xperia x10 running cm10 but it does not install. Please help me so that I can test the module on it.
[Xposed Framework Modules] tonyp:
The module currently requires Android 4.2 or higher. You can't install the module on CM10 as that is based on Android 4.1.

To support Android 4.0 and 4.1 I need to write some custom code which I need some people to test, so everyone interested in this module on a 4.0 or 4.1 device (including CM9 / CM10 etc of course) please write here or send me a PM and I'll contact you as soon as I have a version ready for testing! Can I count you in?

Thank you very much for the logcat! It contained exactly what I needed!

Thanks to that I identified the issue and pushed out a new version (0.94) to fix it.

It will probably take a couple hours in the Google Play Store to appear, in the meantime you can find the new version at the Xposed Repo or attached to this post.

Additionally this version fixes a potential bootloop cause for devices running Jellybean (4.2 / 4.3).

Could the affected people please test this and confirm? Again, if you manage to get me a log it will make it a lot easier for me to fix any issue whatsoever.

Changelog v0.94:

fixed a soft reboot on Kitkat devices when the countdown reaches 0

fixed a potential bootloop on Jellybean devices
[Xposed Framework Modules] DaniPhii:
Nice! This is so necessary… I'm gonna test it. :)
[Xposed Framework Modules] Fif_:
The 0.94 update fixes the soft-reboot after countdown problem for me on CM11 M11 for Nexus 5. I haven't checked the other devices, and won't be any time soon.

Also, I just bought the Pro version on one device.

The Pro option won't unlock on the other devices, I get a "You already own this item." Error.
[Xposed Framework Modules] exodius48:
[MENTION=3605868]tonyp[/MENTION] I'm using WSM Manager (Xposed for MIUI) , but this app still ask to download xposed installer. How to fix this?
[Xposed Framework Modules] tonyp:
No worries, they're using the same codebase so it will work on all devices.

Thanks a lot for buying pro :)

That purchase should work on all devices of course :o sometimes it takes a little while to propagate at Google, when you still have the issue after a couple more hours could you please drop me a PM? I did test the IAP purchases with all possible ways Google offers for me, but unfortunately that's something that could be greatly improved on their side.

Ah, I didn't know there exists an alternative manager. I'm explicitly checking for the Xposed Installer. You can ignore the warning for now and I will push an update which recognizes the WSM Manager as well :)
[Xposed Framework Modules] dark_knight_95:
No bootloops on moto g stock 5.0.2
[Xposed Framework Modules] dark_knight_95:
The module is working but the timer repeated 5-6 times before the actual shutdown
[Xposed Framework Modules] tonyp:
Again it would be great if you could get me a log.

If you don't know how to grab logs with adb (over wifi in this case) you could try to record the log to a file with this app:

https://play.google.com/store/apps/details?id=com.nolanlawson.logcat

Additionally: Are you using the newest version?

This shouldn't happen unless the battery reading works unreliability and jumps around (which a log would tell me).
[Xposed Framework Modules] dark_knight_95:
I am using version 0.94& I'll try getting the logs
[Xposed Framework Modules] Erick.criminal:
Bootloop

Bootloop on Nexus 4, Stock Android 4.3.3
[Xposed Framework Modules] Fif_:
I don't think this was a problem with Google Play, or other kind of "cloud delay".

Let me describe the problem further.

I started by installing BSM on three devices (A, B, C)

After testing yesterday, since the software was working for me, I decided to buy the Pro version.

I did the purchase on device A. BSM on device A went to Pro mode and worked fine.

On devices B and C, however, BSM was still in non-Pro mode, and I was not able to get to Pro.

When I clicked on the unlock/get pro button on devices B or C, I was getting the Play error "You already own this item."

And BSM was not unlocking.

I since found a work-around: I first uninstalled BSM from the device, then reinstalled from Google Play. Then BSM was detecting Pro at the first run.
[Xposed Framework Modules] Purerawenergy:
Working on Blisspop 5.1.1. Great module and very useful.

"Give a man a mask and he'll tell you the truth."
[Xposed Framework Modules] tonyp:
Great you got it working! I double-checked my code which seems to be fine, but I'll see if more reports like this turn up. As you noticed, no purchase will get lost so at least we're on the safe side here.

I tested it again and the sync works from one device to another for me, even when the app was installed and executed on both devices before the purchase, so let's hope it was a Google glitch.

The whole In-App-Billing is quite unreliable unfortunately, let's hope Google polishes that a bit for the I/O. They don't even offer a proper library for developers, it's a shame.

Are you using the newest version (0.94)? It includes a fix for Jellybean devices.

I tested the v0.94 with CM10.1 (Android 4.2) and CM10.2 (Android 4.3) and did not run into any bootloop or other issue so far.

Without a log this is really hard to debug. Additionally I need to know the bootloop happens exactly? Right after activating the module or during/after the countdown?

Great, that's the third confirmation I got so far.

Before I finally flag 5.1 as compatible I'd like confirmation for the following two scenarios. Would be great if someone could test these two:

Cancelling the dialog by plugging in the charger

Letting the dialog countdown to zero so the device will shut down

Note that there's a security measurement in place which only allowes the dialog to show a second time when the battery percentage at least climbed back to 1%, so you can't just unplug the charger at 0% again to test the second scenario but need to wait a little bit.

When both tests turn out successful I will flag the module as compatible with Android 5.1 :)
[Xposed Framework Modules] PixelPatrik:
Why Google Play Billing permission?
[Xposed Framework Modules] DecypherT:
Because of the Pro version.

[MENTION=3605868]tonyp[/MENTION], See my initial post on how the bootloop occurs on Nexus 4, 4.3.3.
[Xposed Framework Modules] tonyp:
I read your edit. All I can say is that I can't reproduce it with the newest version on CM10.2, thus I have no way of fixing it without a log :/
[Xposed Framework Modules] Jhon_Locke:
So it works with 4.4.4?

You have tested it on kitkat?
[Xposed Framework Modules] serkanturkel:
thank you
[Xposed Framework Modules] tonyp:
I tested it with Android 4.2, 4.3, 4.4 and 5.0. Additionally I got lots of reports that it's fully compatible with 5.1.

But I couldn't use a wide selection of phones and ROMs, and I can't promise that it isn't working on some custom ROMs.

This log is really weird. It's complaining about an error opening a file from the sdcard, but my module doesn't access the sdcard at all.

Are you using a tool, xposed module, app, script or anything like that that's modifying or messing some sdcard mounts, links etc?

Edit: Scratch that, this error has nothing to do with my module, it's caused by xRenamer (as seen by the de.galaxyinabox.xrenamer part in line #8).

If not, could you please enable the debug log in the app and send me a bigger logcat which captures more than just that single error so I can identify when and where the error gets thrown. You can email me a text or upload it to pastebin and send me the link.
[Xposed Framework Modules] Mihil:
Maybe that exception is triggered by another module. Currently, the following modules are activated on my phone:

- Amplify

- Battery Shutdown Manager

- G3 TweaksBox

- Greenify

- Notification Count

- Play Store Changelog

- Secure Settings

- XPrivacy

- YouTube AdAway

- xRenamer

The log was captured with the app CatLog (Log Level 'debug'). I can retry with the adb method if that helps.

Complete log: I'm not yet allowed to post links and I can't send you a PM due to a error ("Sorry, we encountered an error processing your request. Please go back and retry or wait a minute."). I'll try again tomorrow.

I deactivated all Xposed modules except your app to get a cleaner logfile. But this time, there are no entries of xposed listed.

Here is the new logfile: I'm not yet allowed to post links and I can't send you a PM due to a error ("Sorry, we encountered an error processing your request. Please go back and retry or wait a minute."). I'll try again tomorrow.
[Xposed Framework Modules] tonyp:
I have updated my old post, the error is due to xRenamer and has nothing to do with this module. Btw, I did receive your PM (three times actually :D).

As a general advice: Always disable all other modules except the one misbehaving to allow a valid analysis.

We need to debug this further, maybe LG changed the shutdown methods. First step: Enable the debug log option, do a reboot, wait a while, plug in the charger a couple times, then send me the Xposed Log. I'd like to verify if the module loaded successfully.

To not clutter this thread I'd say we continue this discussion via PM or email.

But it might be great if some other people using LG ROMs could verify that it indeed isn't working on the LG Stock ROM, then I might need someone to send me some files from an affected ROM to analyze the source.
[Xposed Framework Modules] treydev:
Android 4.0.4

Hi! Please give me a test version for ICS 4.0.4 and I'll post back how it works.

By curiosity, what is it that causes bootloops?
[Xposed Framework Modules] tonyp:
[MENTION=5553467]Mubasher96[/MENTION] and [MENTION=5370981]aquaalex[/MENTION]: Please find attached v0.97 which includes experimental support for Android 4.0.3+ and 4.1.

Note that I did not test it at all, so the worst case scenario could be a bootloop.

On 4.0 and 4.1 are bootloops? I restricted the app to work for Android 4.2+ only, so you shouldn't be able to install it on these versions at all.

If you asked in general: The module is hooking system functions - if the hook is done "wrong" (e.g. because a vendor changed the internal handling of the shutdown sequence) it can cause a bootloop as it's trying to do something that doesn't work.

For v1.0 I want to add another safety net to avoid bootloops, but for the moment it does somewhat help to identify issues. Ideally until then all ROM related issues have been tracked down and are properly reflected in code :fingers-crossed:
[Xposed Framework Modules] treydev:
Installed and done a soft reboot on 4.0.4. No bootloop. Waiting to reach 0%
[Xposed Framework Modules] Alexey71:
Nice mod, cm12.1-11 work.
[Xposed Framework Modules] treydev:
On Android 4.4.2: when getting 0% your module countdown dialog shows up for a secound and then my default one and shuts down. No countdown.

Do you need logs?
[Xposed Framework Modules] tonyp:
Always. And please post more information about your exact phone and ROM combination.

Steps to create logs:

a) Open the app and enable the debug mode

b) Plug and Unplug the charger a couple times and get me the log from Xposed -> Logs

c) Especially when the dialog isn't showing properly on shutdown: Extract a log with adb over wifi or alternatively (which might be easier for some) it might be possible to use the Catlog app.

Inside you can press Menu -> Record to record the log, then after the shutdown the log is hopefully still at the SDCard and contains the relevant lines.

Then send the logcat to me as well.

P.S.: How did your Test with Android 4.0.4 go when reaching 0%?

Still waiting for a confirmation if my code adaptions work as expected on Android 4.0 and 4.1 devices.