yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] gregferns:
Its still on github and [MENTION=4419114]rovo89[/MENTION] hasnt updated his thread,, and its only for 5.0.x whereas CURRENTLY i am using a 5.1.1 rom,, so i have to wait for [MENTION=2476451]romracer[/MENTION] to update...
[Xposed Framework Modules] ZipAddict:
So you donated to this developer, but plan on ripping off other developers? Your logic makes no sense. Im sorry i cant trust anyone that says they installed an app to cheat developers, but didnt use it. If you read the forum rules then you would know that even mentioning warez is frowned upon here. In other threads the mere mention of warez will have people swarming like piranhas. I guess no one cares in this thread except me. if you respect Xda and want help from developers or to use their software, then i urge you to uninstall warez and not mention them again. Not being rude, just helping you to see from another perspective, so that you might avoid similar situations in the future and avoid messing up your phone with these types of warez. I Cant tell you how many people messed up their phones by installing warez.
[Xposed Framework Modules] trancinguy:
Romracer updated.
[Xposed Framework Modules] rav101:
I have just installed Xposed v71 (Romracer 5.1 arm64 version) on my LG G4 Euro H815. This is the first version to work with the LG G4 so early days yet. I have tried installing Amplify and after rebooting, Amplify sticks at "Checking if Xposed is installed". Sorry but I don't know how to get a logcat otherwise I would post up :(

Regards,

Ravi
[Xposed Framework Modules] Pkt_Lnt:
[Tutorial] Hot to LogCat :D
[Xposed Framework Modules] rav101:
Thanks,

I will read up tomorrow and try getting a text file together to see if that helps... And the learning continues [emoji1]
[Xposed Framework Modules] Pkt_Lnt:
Getting a logcat is The. Single. Best. Thing. to help devs get problems solved. Period. :good:
[Xposed Framework Modules] ZipAddict:
Touch screen all the way on left and pull to the right. Then hit wakelock button. Then hit back button. Then it will say checking for root. Then repeat again. Then It will work then
[Xposed Framework Modules] LGtMgG2t:
Many people use LP to ODEX their ROMs. Google it if you aren't familiar with the concept. Do you know of another tool/app that can ODEX sys apps on lollipop?

Don't assume all users get it to rip off a couple apps that cost a whopping dollar. That's ludicrous.
[Xposed Framework Modules] ZipAddict:
I respect your opinion sir, and you make a valid argument, but i believe you might be misinformed. There are several ways and at least 1 app that i know of that can odex system apps on lollipop. However that may not have been true when you looked into it last. And this was not an argument that he came up with, in fact he clearly stated "Im not even sure if Lucky Patcher works with Xposed but since its framework Iam not even going to try." and "I just have it installed, I didn't use it." so this was not the case in his situation. And i dont assume all users get it to rip off a couple apps that cost a whopping dollar, instead i assume much worse when reviewing previous posts made by someone and finding comments that show a clear misunderstanding of less complex functions than system odexing such as "Do I need to disable some wakelocks/alarms/services manually for the battery life to improve?" and "Now just restrict every wakelock with high usage?" Obviously the latter statement if executed would have negative effects on system performance at minimum, and these statements were made prior to my comment. Furthur no mention of odexing was made in response to my initial comment, or private message, which would have gotten a sincere apology out of me. I am a ludicrous individual, but in this case, that is beside the point. I have no hard feelings over this and even stated that i didnt want him to mess up his phone by using the app as many people have in the past. I would like to see him contribute to xda in the future, and I believe he has enormous potential to do so. Once again you make a valid argument, but in his case it does not apply, unless i intentionally ignore the facts previously stated. Out of respect for this thread i will not make another post regarding this topic as i have fully explained where i was coming from. I would be happy to furthur discuss this in a private message with anyone, anytime to avoid spamming the thread with non-amplify related topics.
[Xposed Framework Modules] cryptyk:
Hi all,

OP here. It looks like there are some issues on 64 bit devices. I'd like to fix that, but I don't have one myself. I could use your help to pull some logs together to figure out why it's not working, since I'll be unable to test and debug it locally.

If you'd like to help, please set Amplify to Verbose Logging, and respond with:

- a logcat of the device booting

- a logcat of Amplify starting the UI

- a really clear description of what the problem is

Also, if this isn't the biggest bug in Amplify right now, let me know. If there's something more important I can fix than the 64 bit issue, I'm happy to switch it up :)

Thanks!

Ryan
[Xposed Framework Modules] cryptyk:
Attached is a version that does some additional logging around the 64 bit problem. If someone can install this one, set Amplify logging to verbose, then reboot and get a logcat of the boot, and a logcat of laucnhing the UI, that would be PHENOM!

Thanks,

Ryan
[Xposed Framework Modules] v7:
No warez talk in XDA!

Tapped from my furious dogo ;)
[Xposed Framework Modules] cryptyk:
Seriously. I show up for five minutes to try to solve a problem and the first thing I get is a question about how to make Amplify work with a program designed to cheat developers out of their work?

:rolleyes:

The crazy thing is that I never tried to make Amplify break with that stuff installed. It just never worked, and I never felt like fixing it was a good use of time.

Now: Anyone with a 64 bit logcat?
[Xposed Framework Modules] lateral18:
Has anybody experience a boot loop after installing the app , the only thing is going on recovery and wiping cache. The phone comes back to normal

Or I'm I the only one with this

The Rom the phone has Android Revolution HD 41.0 with elemental x kernel and the latest firmware
[Xposed Framework Modules] m0han:
not adept at this. but, please check your pm. thanks.
[Xposed Framework Modules] k0rner:
Hi.

Logcat and Xposed log for device booting and then opening Amplify UI attached.

The device is HTC M9, running ViperOneM9 3.5.0 and Xposed by romracer v.67/20150716

the issue is: Amplify is displaying no errors, however nothing is blocked (0 alarms, 0 wakelocks blocked displayed in the UI)
[Xposed Framework Modules] ZipAddict:
Amen brotha! I had to tell people last night too :rolleyes:

So sorry for the disrespect Ryan, I dont have 64 device but im thankful you pop in to support us and help us out. Thanks for your continued work to keep making this app better. Please dont stop. I will continue to stick up for your rights when you arent available like i did last night. WAREZ BUSTERS to the rescue lol! :laugh:
[Xposed Framework Modules] gregferns:
Hi Ryan,

Thanks for showing up... And helping us out... Seriously please ignore the Warez guys.... They should be reported to the mods.... Anyways I'll also try what you have asked today, as I'm home and not keeping a bit well... But that won't stop me from taking logs during the day...

Keep up the good work and cheers...

Greg
[Xposed Framework Modules] cryptyk:
Almost perfect. Can you turn on verbose logging in Amplify for me, then run it again?

Thanks!

Ryan
[Xposed Framework Modules] k0rner:
Strange thing is that it's already set to "Verbose".

Just tried setting it to normal, then verbose, then rebooting - and after that there are still only ~3 messages about Amplify in the log.
[Xposed Framework Modules] cryptyk:
Ah! Makes sense when I think about it. It seems like the Xposed process can't read the files from the activity.

Here's a version that logs all of the debug stuff, even when verbose isn't "readable". Can you try this one? I appreciate the help!!!

Ryan
[Xposed Framework Modules] k0rner:
This time there's more Amplify in the logs, see the attachment.

EDIT: more logs, please re-download the zip.
[Xposed Framework Modules] cryptyk:
Super helpful. The problem isn't what I thought.

Can you zip up the files in your /data/data/com.ryansteckler.nlpunbounce folder and send them to me at gotcode@gmail.com?

I'm headed to bed, but I'll look again in the morning.

Thanks again for the help,

Ryan
[Xposed Framework Modules] qberty:
Hey just in case you need a realllllly verbose log from a different base rom, here ya go.

ROM: CM based

Device: HTC One M9

Xposed 5.1 v67 arm64 build

Same issue: Everything starts up fine, but blocking of actual wakelocks do not work.

I also sent a zipped data folder as well.
[Xposed Framework Modules] k0rner:
Sent via mail.

Offtop: that was your post # 666.
[Xposed Framework Modules] MKh979:
Hi! I'm using amplify donation module with my LeTv x600, everything seems ok and amplify see all the wakelocks and alamrs, but the number of wakelocks and alarms which were blocked is zero?!?!?! Anyone know the solution?!?!?! Thanks!
[Xposed Framework Modules] p50kombi:
Man, did you even read the last 2-3 pages before you posted this question?

I'm not going to spoonfeed you, just take a bit of time and read back a few pages..

Short version, Cryptyk is looking into it...
[Xposed Framework Modules] MKh979:
Sorry Man, but I've read more than 2 or 3 pages before and I've see only one guy that have my same problem and no solution.

I don't speak English very well, may I didn't understand the solution to my problem?!!?
[Xposed Framework Modules] p50kombi:
64 bit processor.....

Just search...
[Xposed Framework Modules] gregferns:
There are many of us with 64 bit phones for whom Amplify is not blocking anything... So it looks like you also have the same issue... so just do one thing..

cryptk has given beta versions in the last 2 or 3 pages.... use that and create logcats and help him to solve it !!!!!!!
[Xposed Framework Modules] m0han:
device: yu yureka (64-bit processor)

rom: blisspop v3.9_r12

kernel: stock rom

amplify version: v3.1.0b

other

xposed modules: none enabled

no. of logs: 4 (inside zip file)

1 log each

on booting

on xposed

v70

and

v71

by romracer, 1 log each

on starting amplify gui

on xposed

v70

and

v71

by romracer. https://www.dropbox.com/s/f0tzb8imzoki50f/amplify3.1.0b.zip

description of the problem: wakelock time, wakelocks and alarms

not

getting blocked.

edit

: just fyi - app version shown in amplify settings is v3.1.0a
[Xposed Framework Modules] sguerra923:
Quick question, I did some searching and didn't really find a solid answer but amplify has StartingAlertService and CdmaInboundSmsHandler on my Safe to limit list but I read on the list not to limit the StartingAlertService anyone limit the CdmaInboundSmsHandler without any issues? Thanks in advance
[Xposed Framework Modules] :
EDIT: Found answer a few pages back. Common 64 bit problem.
[Xposed Framework Modules] rav101:
For reference, after this I got a bootloop so did a fresh install. The second time around, it didn't freeze so wasn't anything to be done with a logcat :rolleyes:
[Xposed Framework Modules] Pkt_Lnt:
Probably not true, but whatever........ shrug
[Xposed Framework Modules] :
Swipe left to right in the play store. Click the arrow and choose the account you used when you bought donation package. That will solve your problem.

---------- Post added at 05:15 PM ---------- Previous post was at 05:12 PM ----------

Just donate. This app is really worth it and you show you appreciate [MENTION=526666]cryptyk[/MENTION]'s work. He has done a very good job with this app and I really don't understand it's free. Best app for battery life out there.

---------- Post added at 05:35 PM ---------- Previous post was at 05:15 PM ----------

[/COLOR [MENTION=526666]cryptyk[/MENTION] I installed your alpha v3.1.0a to log. I got Samsung GS6, with same problem. Can see wakelocks and alarms, but no blocking.

But well, it's stuck on the checking for Xposed part. It's enabled and restarted, but nothing happens. Any workaround so we can start logging?

Thanks in advance
[Xposed Framework Modules] phazey12:
[/QUOTE]

But well, it's stuck on the checking for Xposed part. It's enabled and restarted, but nothing happens. Any workaround so we can start logging?

Thanks in advance[/QUOTE]

Same here for my S6 Edge. Stuck at checking if xPosed is installed.
[Xposed Framework Modules] tangcla:
I have noticed an issue recently where my NlpWakeLock is not being limited even though I have got it set to allow every 86400 seconds. It seems a reboot is required to fix this (and I can't figure out what causes it).

Has anyone else noticed a similar issue on their phone/s?

This is occurring on a Samsung Galaxy Note 4, running Lollipop 5.0.1, stock but deodexed.
[Xposed Framework Modules] furboom1240:
Hi guys. I'm running Amplify on romracer's Xposed 65 and it's commendable. I've been out and about and thought I'd drop by.

Regarding Lucky Patcher, I despise that as much as a density normalizer (permits all apps to be shown in Play) because it defeats safeguards and the meaning of generosity for all these devs do.

I enjoyed Amplify so much, the second time I paid $10 just because it's awesome. I paid $2 at first. When we see the value in software, we want to further our goals further and motivation is key.

Glad to be here! I stand by any creative endeavor and idea that keeps this platform going...?
[Xposed Framework Modules] ZipAddict:
when it says checking for xposed, touch the screen all the way on the left and swipe to the right. Then hit wakelocks tab. then hit back button. Then it will say checking for root. Then swipe from left side of screen to right again. hit wakelocks tab again. hit back button again. Then it will say everything is ok! This method has worked for many people. Hope it helps
[Xposed Framework Modules] :
I removed GApps from my phone and apparently the pro features are now disabled. Amplify requires proprietary Google software to work properly and has absolutely nothing to do with the FOSS principles.
[Xposed Framework Modules] LGtMgG2t:
You positive? I didn't realize there was a safe way to remove Google apps once they were installed. A good test would be to install a ROM without the GApps and see if it works for you.
[Xposed Framework Modules] koko115:
App working, but no block wakelock on S6. I always have wakelock blocked 0, alarms 0.... any idea ?

3.1.0a
[Xposed Framework Modules] locolyric:
seems like so many user report their logfiles with no blocking in 64 bit environment, should i need to upload mine ?
[Xposed Framework Modules] :
Amplify doesn't work on 64-bit phones like S6 yet..

Shamu
[Xposed Framework Modules] NickosD:
Amplify unfortunately requires play store to check the licence. Every time I open Amplify, I first launch play store because I hibernate it and it cannot check for pro features.

Sent from my bacon!!!!!
[Xposed Framework Modules] themadproducer:
[MENTION=526666]cryptyk[/MENTION]

Based on the above, would u consider programming the license check wirh a more relaxed interval.... Eg once or twice a month like some of the other apps do? I mean, Greenifying Play Store contributes to my/our battery savings, but it's very inconvenient to need to launch Amplify from the Play Store.
[Xposed Framework Modules] trancinguy:
Hi, I tried to deny the service "System Update Service" to block the update and it did, but the wake lock just took over and never stopped, so I went the Wake lock Section to see if System Update Service is waking but it was not! Drain kept on happening and Wld and bbs both show The huge wake lock and the only way to calm it down was to re-enable that service and the notification came back and the wake lock stopped. Does anyone know why that is happening? I tried to wipe cache and Dalvik but still got the wake lock.
[Xposed Framework Modules] nick2013:
How to deal with this window manager wakelock.

Battery is draining a lot because of this wakelock and sometimes it goes up like 7-8hours.

Should i limit it?

Or any other solution?
[Xposed Framework Modules] trancinguy:
Try to find out it's name then amplify it [MENTION=353015]240[/MENTION] then wait to see if there is any side effect, then gradually increase until it's controlled
[Xposed Framework Modules] ManUtdkid77:
I've already sent d requested logs to [MENTION=526666]cryptyk[/MENTION]

But here are d Logs, if other members can help with resolving d issue of 0 wakelocks/alarms on 64 bit devices

Phone: YU Yuphoria

ROM : Cyanogenmod 12.1 20150723 Nightly

CPU: Qualcomm MSM8916 Snapdragon 410 (64bit)

Kernel : RaZorReborn v1.8

OS: Android 5.1.1

Xposed Framework : version 69 by romracer*20150804

https://drive.google.com/file/d/0B0LLamdJZpqJRUsyQngzQUJ0bEk/view?usp=docslist_api

https://drive.google.com/file/d/0B0LLamdJZpqJSjc3M3NpQVR6ZXc/view?usp=docslist_api

https://drive.google.com/file/d/0B0LLamdJZpqJazNkcWg1Tk1tY2M/view?usp=docslist_api
[Xposed Framework Modules] cryptyk:
Here's the deal: Google Play Store requires that I collect any purchases through their own Play Store system. That's why you see In App Purchases done through Google (instead of PayPal) even though they take a large percentage. If I accepted PayPal, or some other method of payment, Google would remove Amplify from the Play Store. And yes - Google's IAP system can only verify your purchase when Play Store is installed.

I've done as much as I can to make this work by letting you setup your Amplify settings with Play Store installed, then you can remove Play Store and Amplify will continue to use your settings, including the "non-free" wakelocks and alarms.

Hope that helps explain the situation,

Ryan
[Xposed Framework Modules] cryptyk:
Nope. I have what I need and I'm working on a fix. Not an easy one, but I'm working through it.

Thanks,

Ryan
[Xposed Framework Modules] cryptyk:
Hi folks with problems on S6 devices (or maybe other 64 bit devices):

I got a tip from [MENTION=3562083]wanam[/MENTION] that might help! Can someone please try the following for me?

adb shell ls -al /data/data/com.ryansteckler.nlpunbounce/shared_prefs/

If for some reason that doesn't work, can you try:

adb shell

su (and accept the root request on your phone if needed)

ls -al /data/data/com.ryansteckler.nlpunbounce/shared_prefs/

Post the output of that and we'll see if there's a problem.

Thanks!!!

Ryan
[Xposed Framework Modules] v7:
Did it via Terminal Emulator.This is Amplify 3.0.9.

u0_a100@OnePlus2:/ $ su
om.ryansteckler.nlpunbounce/shared_prefs/ <
-rw-rw-r-- u0_a114 u0_a114 1121 2015-08-23 07:29 com.ryansteckler.nlpunbounce_preferences.xml
root@OnePlus2:/ #

Tapped from my lactuca virosa ;)
[Xposed Framework Modules] cryptyk:
Hmm. Not what I was expecting. Can you confirm that you have the problem where Amplify isn't blocking anything for you? Do you have these two lines in your logcat pretty close to each other within a few minutes of booting?

W/XSharedPreferences( 2470): getSharedPreferences
I/Xposed ( 2470): Amplify: Resetting stat files on version upgrade.

A second person (preferably with an S6) would be awesome.

Thanks!

Ryan
[Xposed Framework Modules] v7:
Yes I'm having the issue.

Here's the logcat within a few minutes after booting.
[Xposed Framework Modules] 307th:
root@noblelte:/ # ls -al /data/data/com.ryansteckler.nlpunbounce/shared_prefs/
/data/data/com.ryansteckler.nlpunbounce/shared_prefs/ <
-rw-rw-r-- u0_a205 u0_a205 1082 2015-08-22 21:10 com.ryansteckler.nlpunbounce_preferences.xml
root@noblelte:/ #

This is for the s6 running back-to-n0t3

Edit:

mega.nz/#!Z1VE3Y4a!lmW3HEvQKd2G6a6dKSJqK9i7lvPvxa1LuvD5yLt1mLQ

I couldn't upload the logcat on xda, so i did on mega.
[Xposed Framework Modules] m0han:
output of command 'ls -al /data/data/com.ryansteckler.nlpunbounce/shared_prefs/' in terminal emulator: -rw-rw-r-- u0_a3 u0_a3 822 2015-08-18 07:49 com.ryansteckler.nlpunbounce_preferences.xml

---------- Post added at 10:24 AM ---------- Previous post was at 10:03 AM ----------

i have the problem where Amplify isn't blocking anything. here's a 1-min logcat with command 'adb logcat -v long > noampblock.txt' taken a few minutes after booting: https://www.dropbox.com/s/ed94p2d6vzsl46b/noampblock.zip
[Xposed Framework Modules] mickg929292:
com.android.internal.telephony.action_check_netsta t

Is safe to limit that alarm com.android.internal.telephony.action_check_netstat? It's the biggest one showed in my amplify stats.

I'm typing by lg g2, with cloudy 3.3.

Amplify donation package.
[Xposed Framework Modules] st0nez0r:
[MENTION=526666]cryptyk[/MENTION]

Galaxy s6, Arcadia v5 rom.

Amplify isn't blocking anything as it should.

pull from adb:

-rw-rw-r-- u0_a68 u0_a68 509 2015-08-22 21:26 com.ryansteckler.nlpunbounce_preferences.xml

logcat below.

08-23 08:43:53.642 W/XSharedPreferences(3647): getSharedPreferences
08-23 08:43:53.642 W/XSharedPreferences(3647): org.xmlpull.v1.XmlPullParserException: Unexpected token (position:unknown @1:5 in java.io.InputStreamReader@3e88c1a1)
08-23 08:43:53.642 W/XSharedPreferences(3647):	at org.kxml2.io.KXmlParser.next(KXmlParser.java:428)
08-23 08:43:53.642 W/XSharedPreferences(3647):	at org.kxml2.io.KXmlParser.next(KXmlParser.java:313)
08-23 08:43:53.642 W/XSharedPreferences(3647):	at com.android.internal.util.XmlUtils.readValueXml(XmlUtils.java:1303)
08-23 08:43:53.642 W/XSharedPreferences(3647):	at com.android.internal.util.XmlUtils.readMapXml(XmlUtils.java:735)
08-23 08:43:53.642 W/XSharedPreferences(3647):	at de.robv.android.xposed.XSharedPreferences.loadFromDiskLocked(XSharedPreferences.java:122)
08-23 08:43:53.642 W/XSharedPreferences(3647):	at de.robv.android.xposed.XSharedPreferences.access$0(XSharedPreferences.java:112)
08-23 08:43:53.642 W/XSharedPreferences(3647):	at de.robv.android.xposed.XSharedPreferences$1.run(XSharedPreferences.java:105)
08-23 08:43:53.642 I/Xposed (3647): Amplify: Resetting stat files on version upgrade.

That was in my second file uploaded to dropbox

(this was the first time I've ever grabbed a logcat - if it isn't right let me know and i'll try to do it correctly. be gentle)

Here is a second one from a different log cat program that seems to contain more info...

https://www.dropbox.com/s/b6shv32g1az823u/2015-08-23-08-44-09.txt?dl=0
[Xposed Framework Modules] cryptyk:
Thanks all. It looks like permissions isn't the problem. I've asked for some help from the Xposed experts on this. Worst case scenario, I'll go buy a 64 bit device so I can debug the problem locally. I'm trying to avoid that because there just aren't any devices out there that I'm really excited about, and I still really love my HTC M8!

Thanks for your patience and cooperation getting us to this point. You guys are the best! Standby and we'll get it fixed one way or the other.

Thanks,

Ryan
[Xposed Framework Modules] J-Hop2o6:
I guess i'm not the only one having Wakelocks and Alarms not being blocked.

I'm using a SGS6 w/ Rapture Rom v2.1 (5.1.1) + UniKernel v7.b

The SGS6 just got Xposed working this week. Wonder if there's still some tweaks that need to be made to 5.X+64bit Xposed.
[Xposed Framework Modules] Pkt_Lnt:
It's being worked on and users have provided logs. Read back a few pages. :rolleyes:
[Xposed Framework Modules] J-Hop2o6:
I know.... Just adding to the list of ones with the issue.
[Xposed Framework Modules] pim:
cryptyk, if you really need to buy a 64bits phone, you can order this one : http://www.mstar.hk/Mobile/show/12.html

It's cheap, not bad, and I have the problem with amplify on it
[Xposed Framework Modules] Tardeaux:
Likewise seeing the 0 wakelocks blocked on my S6 edge. When I look in xposed logs, i'm seeing "Amplify: Resetting stat files on version upgrade." like clockwork every 5 minutes, constantly.
[Xposed Framework Modules] 0rigin:
edit: wtf am I doing, messed up and deleted posts...

Ok, it's quoted below..
[Xposed Framework Modules] ManUtdkid77:
It's Mainly coz d G4 is running on a 64bit cpu.

Cryptyk is working on a fix for dat bug, don't worry.
[Xposed Framework Modules] 0rigin:
Ah, thank you...