yashsingh1/xdaforums huggingface dataset:
[Xposed General] rovo89:
Current status (Feb 19):

The most important issue seems to be the incompatibility with Samsung stock ROMs, especially because it's leading to boot loops. I have been working hard on fixing this in the days since the release, however it's not just a single spot that needs fixing. Thanks to GermainZ for testing and providing good log files! So far, I have detected the following issues:

- Enhanced .oat file format: Samsung has added a "TypeLookupTable", probably for performance reasons. The table itself will be ignored by Xposed, but it also means that the file format is slightly different. I have finally understood what they have done and added some logic to skip the referenes to this table.

- Different size of the String class: They have added a clear() method, which is unusual as strings are usually immutable. As this class is one of few that have special support in native code, I had to add one entry to the virtual table of the class.

- Additional fields in DexCache class: Offsets to some fields are different due to this and need to be handled in native code (as this another central class with native parts directly implemented in ART).

- Verifier rejects ViewDebug class: Doesn't seem to be overly critical to me, yet to be tested whether it's working fine with original libraries.

- Implementation missing for some native methods: Some methods in the reflection classes have been implemented in native code instead of Java. This means I will have to implement them as well.

The changes done by Samsung are bigger than I expected, especially given that ART is very complex and mostly undocumented. Anyway, I still think that once these issues have been overcome, it's better to replace the libaries than trying to manipulate data structures and behavior from "outside" (app_process). Think about it: If they have done such big changes, it's very likely that offsets in these data structures are different from AOSP and would need special handling as well.

It would of course be helpful to have an uninstaller ZIP in case you run into a bootloop. I didn't have time for that yet, but maybe someone can build an initial version that basically reverses the steps of the installer ZIP. For the ART libraries, that should be rather easy. You might want to stay away from moving app_process32 back in case you have SuperSU installed. It will need a special procedure to ensure you don't break either part or even your ROM.

There are other issues for sure, for example it seems that some methods cannot be hooked. That's something that needs more investigation, but I would like to fix the more critical issue like the ones for Samsung first.

That said, I won't be able to work on Xposed for the next days, definitely not before Monday. Keep in mind that this isn't my fulltime job and that an alpha phase might take some time. It would be illusionary to assume that we reach a stable state after a few days, with all the changes that have been done.
[Xposed General] rovo89:
I have just uploaded alpha2. It fixes several issues:

java.io.IOException: Invalid argument while reading /data/data/de.robv.android.xposed.installer/conf/modules.list (sometimes it worked fine after a soft reboot), see https://github.com/rovo89/Xposed/issues/25

ClassNotFoundException for system services (e.g. ActivityManagerService) shown in the log, see https://github.com/rovo89/XposedBridge/commit/6b49688c929a7768f3113b4c65b429c7a7032afa

Resources-related incompatiblity on newer CM12-based ROMs

Hooks for very simple methods not working, see https://github.com/rovo89/android_art/issues/4

app_process version not displayed in XposedInstaller

When you flash the new files, the next boot might take a bit longer, as it effectively clears the Dalvik cache (which is necessary because of a change in the ART compiler).

Note that this version is still not compatible with Samsung ROMs (custom ROMs might work if they're not based on stock ROMs). Don't install it, otherwise you'll get into a bootloop and need to restore your backup!

I have already done a lot of investigations and adjustments, as also mentioned in the previous post. However, there are still differences that need to be addressed and it will take more time to resolve them. I can't give any ETA on that.
[Xposed General] rovo89:
Ok, quick status update.

Sure, I have heard that Android 5.1 is out. However, it currently makes more sense for me to stablize Xposed for Android 5.0, as I have two productive devices plus the Genymotion emulator running on it. Hopefully, it can then be ported to Android 5.1, but that's hard to tell without having had a look at it.

It's generally hard to estimate any timelines for Xposed-related stuff, for mainly two reasons:

a) Working on Xposed is mainly analysis of AOSP code, traces, closed-source files, followed by some development and testing (often trial and error). I never now which other obstacles are still undiscovered, so the effort is unclear beforehand.

b) Even if I know the effort (= net time), I can't say when I will have the time to actually work on it. For example, this week I probably won't spend a single hour on development. Sorry, but I'm not going to sacrifice my private life for Xposed and I can't spend several hours per evening for this project (anymore).

One of the next steps will be the creation of some scripts that help me to compile and package Xposed. Apart from simplification for me, I hope that this might help other experienced developers to try and contribute themselves (e.g by analysing the issues they noticed themselves).

So much for now, keep enjoying the stuff that is already working and please refrain from asking me when Xposed for 5.1 will be stable... I simply don't know that myself.
[Xposed General] rovo89:
It took longer than expected, but I also think it's better than what I had planned originally:

https://github.com/rovo89/XposedTools

I hope this makes it easier for others to compile the native parts of Xposed and the modified ART runtime themselves and get involved, just like [MENTION=2476451]romracer[/MENTION] did. It also makes it easier for me to build and package the Xposed framework, as it was quite a hassle to make sure that all files are compiled correctly, pushed to my PC etc.
[Xposed General] rovo89:
I have just uploaded a new flashable ZIP for Xposed 3.0 alpha3 (xposed-sdk21-arm-20150426.zip).

You only need to flash the ZIP again, the Xposed Installer app remains the same (and therefore still shows version alpha2). If XposedBridge.jar has version 64 after a reboot, the new version is active.

Changes:

- Fixed issues with replacing drawables

- Fixed NoSuchMethodError in handleInitPackageResources

- Possibly fixed some errors on ROMs that start in permissive SELinux mode and switch to enforcing mode later
[Xposed General] rovo89:
As the question probably comes up:

- No, this version doesn't support Android 5.1 yet.

- No, this ZIP doesn't support arm64/x86 processors yet.

I will eventually support them as well, but as there are unofficial versions for these, I try to work on a few known issues for Android 5.0 before (when I find time for it).

Regarding Samsung ROMs: No progress. No ETA. No promise that it will be supported, although I don't exclude it either. It's simply unclear what further differences between their and AOSP's ART variant come up.
[Xposed General] rovo89:
alpha4 (20150430) is now available. It fixes bootloops and crashes on some ROMs, especially on Sony devices. In the logs, there used to be "Too many open files" errors.

References for this bug:

https://github.com/rovo89/Xposed/issues/31

http://xdaforums.com/crossdevice-dev/sony/workaround-bootloops-xposed-lollipop-t3089203

http://xdaforums.com/z3/general/xposed-bootloops-lollipop-t3085627
[Xposed General] rovo89:
Those who had issues with installer version 3.0 alpha3 displaying the framework as not installed, please try 3.0 alpha4. ProGuard optimized a bit too much in one very specific case... unfortunately, this never appeared during development, just in the release build.

If modules aren't loaded after a reboot because modules.list wasn't found, try to disable/enable any module. This will write the file again.

One addition to the changes in framework v65: The ZIP files are now signed. This wasn't possible before integrating the custom BusyBox version as some recoveries failed to unzip the signed ZIP.
[Xposed General] rovo89:
I have just uploaded ZIPs for Xposed framework version 66 and also replaced the uninstaller ZIPs. There are no changes in the framework itself, so if you installed version 65 successfully, there's no need to update. If you got messages containing "Invalid argument" or "Wrong SDK version: 19, expected 21" while flashing the ZIP files, this should fix them. Thanks to [MENTION=2476451]romracer[/MENTION] for the fix!

EDIT: Had to reupload. If you downloaded the ZIPs within the first 15 minutes after this post was published, please download them again.
[Xposed General] rovo89:
New files for framework version 67 are now available. They fix an issue with recoveries that have SELinux disabled (even though they might claim that "Full SELinux support is present" in the log, like TWRP does). This seems to have happened mainly on LG devices and caused boot loops, but could affect others as well. Details about the fix are in this commit: https://github.com/rovo89/XposedTools/commit/c55ac907e16947d66012950d119d8db1aea69124

The uninstaller has also been updated, although it's unlikely that it would have caused real issues.
[Xposed General] rovo89:
framework version 68 fixes two reported crashes:

"Fatal signal 11" reported for dex2oat or "Compiler driver" in the Xposed log. I have seen a few posts about such issues, but the one I tested the fix with was about Quickoffice. If you notice further issues like this, please report them on GitHub with the full logcat (as only that contains the command line that crashes).

"com.android.phone has stopped" on LG G3. Don't confuse this with support for encrypted apps (LGWeather, LGCover), this can't be fixed unless someone comes up with a decrypter, ideally one that can be executed on the device.
[Xposed General] rovo89:
I had another look at their encryption, or rather the library they use for it. Fortunately, all the decryption logic is in that library (liblgalmond.so), not in ART itself. So I did a lot of digging into their libraries and finally figured out how to call the relevant functions to detect and decrypt their encrypted apps on the fly. That's the requirement to recompile and run these apps.

So here it is, framework version 69 with support for LG's encrypted apps (LGCover, LGWeather, maybe more). Please make sure to clean your Dalvik cache after flashing the ZIP if you have an LG device and had issues with these apps.
[Xposed General] rovo89:
It turned out that some LG devices (at least G2 mini and G Pad 8.3) are using encrypted precompiled (odex) apps. These need to be handled differently than apps which contain just the encrypted dex file. With framework version 70, Xposed supports both encrypted dex and odex files. Again, clearing the Dalvik cache might be necessary. If you don't have an LG device or don't get FCs, you can skip this update.
[Xposed General] rovo89:
In framework version 71, I have fixed a boot loop on various devices/ROMs related to the "SettingsProvider". If you were getting boot loops with earlier versions, you might want to give this a try.

Apart from that, it should now work properly with Sygic (after reinstalling the app or wiping the Dalvik cache). Note that some modules might not work properly with this app, as they "hack" Android's resource processing (e.g. for images/texts) on a low level. As this conflicts with Xposed (which does a similar thing), I had to disable parts of the API for this app.
[Xposed General] rovo89:
I finally created an official version for Android 5.1 (aka SDK22). You can download it as v72 from the first post.

This version is not directly based on [MENTION=2476451]romracer[/MENTION]'s port, however there aren't many differences. He had merged AOSP 5.1 into the Xposed codebase, I did it the other way around and used this opportunity to reorder and combine the commits. So it's a little bit cleaned up now, which will hopefully make it easier to port these changes to future Android versions. I have also cherry-picked two of his changes that weren't in the offical version yet: A fix for a special case in resource handling on 64-bit and compression of the backup Xposed creates during its installation. Many thanks to [MENTION=2476451]romracer[/MENTION] for providing the unofficial version - this gave me the chance to fix and improve many things (which were in turn merged by him and others).

That said, there are also a few new changes:

- In error messages, the Android version is now display as well, e.g. "Wrong Android version: 5.1 / SDK22 ... This file is for: 5.0 / SDK21"

- The files for Android 5.1 can now handle gzip-compressed odex files (*.odex.gz). Those files only exist on certain ROMs (e.g. CM) that merged a few commits proposed by Intel. These commits weren't accepted into AOSP because the way they're handling the compressed files has some flaws. With Xposed installed, these files will be unpacked on-the-fly and recompiled.

The gzip support might also be interesting for ROMs where the /system partition is almost full. It should be possible to gzip some of the .odex files before installing Xposed in order to free up some space. This should work on any odexed 5.1 ROM, even if the Intel commits aren't included. However, this would be very experimental. Volunteers are welcome, but don't forget to create a backup.

Finally, I have updated the uninstaller zips. They include a timestamp now, as new installer zips might require new uninstaller versions. You should always be able to uninstall older versions with the latest uninstaller though. v72 requires at least the uninstaller from today (20150831).
[Xposed General] rovo89:
With framework version 73, a bug on 64-bit ROMs is fixed which prevented modules from reading their preferences. I believe that the root cause is a bug in AOSP, but whatever - it should be fixed now. Thanks to [MENTION=2476451]romracer[/MENTION] and [MENTION=526666]cryptyk[/MENTION] for the fix.

I have additionally merged a few changes from CyanogenMod. Most of them control when the Dalvik cache is cleared automatically after a bootloop (new feature in 5.1 AOSP, now improved) and one is supposed to increase the compile performance on some ROMs. Don't expect too much though.
[Xposed General] rovo89:
In framework version 74, I have fixed some more incompatibilities which could lead to bootloops or crashes. I assume that most of these crash logs contained the string "Incompatible set properties", which is actually a consequence of previous method verification errors. It's hard to say which ROMs and devices were affected - but flashing the new version shouldn't hurt even if everything looks fine with older versions. If you do notice any issues and are sure that it's not caused by yourself, you have higher chances of getting them fixed if you open a detailed GitHub issue (usually I will need at least a full logcat).

I won't be able to work on Xposed for the next 2-3 weeks - no time for development, support or questions at all. If the rumors I have read are right, I should be ready just in time to start porting Xposed to M.
[Sony Cross-Device Development Themes and Apps] ogunja:
Update app Filmes

Download - http://goo.gl/8krFut

New update - https://app.box.com/s/2vdbkg0yv320ktqb17g0xof7tkmav5ao

http://goo.gl/wgHFoC
[Sony Cross-Device Development Themes and Apps] ogunja:
New update

Sent from my Sony Xperia Z3 Sensation - D6643 by Ogunja ??✌
[Sony Cross-Device Development Themes and Apps] ogunja:
Lastest update Filmes - 9.1.A.0.8
[Sony Cross-Device Development Themes and Apps] Hamidreza2010:
[MENTION=4716941]ogunja[/MENTION] does it work on 4.3?
[Sony Cross-Device Development Themes and Apps] ogunja:
I can not confirm friend, I'm at the lollipop, do the test
[Sony Cross-Device Development Themes and Apps] Hamidreza2010:
Ok dear i,ll test it
[Android Q&A, Help & Troubleshooting] P5music:
Hello,

I have an Android app on Google Play. I would like the user was able to install old releases apk packages directly when some troubles occur with the official one on Google Play.

I need to know which safe and secure websites/services allow me to have an account so the users can download the apk packages. I would like to have an account on more than one service, for redundancy purposes. (Note: my app is not open-source)

Thanks in advance
[Galaxy Note 4 Q&A, Help & Troubleshooting] Lambetts:
Hey guys,

Silly question but how far are we away from a G and F lollipop kernel? So keen to try lollipop but have a G version and just seeing if there's any updates?

Thanks in advance guys.
[Galaxy Note 4 Q&A, Help & Troubleshooting] pratik_193:
too early, unless samsung releases the source , there wont be any kernel.

masters like @ friedrich420 will be able to do a magic only then..
[YU Yureka Q&A, Help & Troubleshooting] kenil89:
Hello

I want to create folder in homescreen and in the menu but not able to create like samsung or sony.

Any one know about how to create folder in Yureka??

Thanks in advance.. :):)

http://www.mobixpose.com
[YU Yureka Q&A, Help & Troubleshooting] aashking:
keep the apps which you want to put in the folder in the home screen, then move the app and place it upon another app and leave, now your folder will created and you can rename it :)
[YU Yureka Q&A, Help & Troubleshooting] kenil89:
Ohh great man..its working...

Any idea about menu???like 3pages for apps..so i want to move unused apps in one folder
[YU Yureka Q&A, Help & Troubleshooting] AVS_rokz:
For creating a folder on the home screen. You should first drag one app over another. Which will create an option to combine and put both apps in an home screen folder. Stop dragging to confirm your choice. You can now add many more apps to the folder according to your choice. You can touch on the folder and then rename it by typing the desired name you want to give, on the place where written untitled.

Hit thanx if helped.
[YU Yureka Q&A, Help & Troubleshooting] kenil89:
Ya but what about menu???likes all the apps are display..its for homescreen..
[YU Yureka Q&A, Help & Troubleshooting] ujilraj:
Try a different launcher... like for eg., next launcher or go launcher or something like tht which can meet ur requirements.
[YU Yureka Q&A, Help & Troubleshooting] AVS_rokz:
In cyanogen mod of yureka you have a option in settings>apps>protected apps. Just add the unwanted apps to the list of protected apps and you wont see them again until you unprotect them or you can create a folder for the apps on home screen and lock that folder and the apps won't show up anywhere else. Until you unlock the folder or remove the apps from protected apps.

Hit thanx if helped

[MENTION=2741799]avsoft[/MENTION]wareSolutions.co.vu frm MMX canvas 4
[YU Yureka Q&A, Help & Troubleshooting] kenil89:
I had done already this thing..i thought is there any way to create folders..

By the way thanks man
[HTC Desire 510] meeniemuffin:
Long story short, I uninstalled it, now my lockscreen says “weather unavailable". It bothers me more than you may think . Please help.
[HTC Desire 510] Burtrum57:
Have you thought of installing an after market weather app.

Is it the Google weather app or HTC's app you want?
[HTC Desire 510] meeniemuffin:
HTC. When i
[HTC Desire 510] meeniemuffin:
HTC. When I look for it on the market it shows up but said something along the lines of its not available on my device?
[HTC Desire 510] Burtrum57:
I'll see if this works.

I found these 2 files in the /system/priv app folder.

Next download I'll try and find the HTC weather. The weather file is 13 meg whish is larger than the the 8meg XDA allows
[HTC Desire 510] meeniemuffin:
Awesome. Thank you,stranger. You've been mighty helpful.
[Galaxy Note 4 Q&A, Help & Troubleshooting] uridium_uk:
Is mine just a bad upgrade to Lollipop or is everyone else missing the 'downtime' options from

Settings>Sounds and Notifications>Interruptions?

Downtime options should be there at the bottom but i don't have them....without it there doesn't appear to be any other way of setting downtime options to stop notifications etc at night. (Yes i know i an download other apps to do this but that's not the point)

Tried wipe/reset but still not there.
[Galaxy Note 4 Q&A, Help & Troubleshooting] marleyb:
Not a bad upgrade m8, this is not implemented in Samsung's current lollipop release [emoji4] you can enable priority notifications to stop sounds at night though.
[Galaxy Note 4 Q&A, Help & Troubleshooting] uridium_uk:
OK thanks....thought it was just me :)

hopefully Samsung will add it to an update soon....
[XDA Assist] XDA Visitor:
Hi there . I want to know if there is any way to use 3g only netwok cz if there is a slight change in 3g signal then korean samsung handseta will shift network to 2g . As there is no optiin for toggleing 3g only network .

Shall b thankful .
[ONE Q&A, Help & Troubleshooting] thegios:
I am opening this thread not to complain about battery performance in general, as i find it stellar.

Still, when I leave the phone untouched overnight, I lose 1% per hour, which I find strange.

As you can see from screenshot 1 and 2, the phone has been idle 9 hours and has lost 9%.

I usually leave the phone with DATA SYNC, WI-FI, 3G and GPS on, as I rely on GOOGLE NOW.

From screenshot 2 you can see that GPS has never been active, only 3G SIGNAL and WI-FI.

From screenshot 1 you can see that 41% of battery has been used by ANDROID OS, followed by PHONE INACTIVE, WI-FI, CELLULAR SIGNAL IN STANBY, ANDROID SYSTEM and GOOGLE PLAY SERVICE.

Being GOOGLE PLAY SERVICE at 5% I do not believe this is the problem, even because 8as you can see from screenshots 5, 6 and 7) in Privacy Guard I have denied to GOOGLE PLAY SERVICES the WAKEUP and the KEEP ALIVE.

So, the two main drainers are ANDROID OS at 41% and PHONE INACTIVE at 15%.

In screenshots 3 and 4 you can see details about these two services.

ANDROID OS has kept the phone active for 1h while PHONE INACTIVE for 8h.

Is this PHONE INACTIVE that i do not understand: what is this? Does screenshot 4 means the phone has been inactive for 8h or that PHONE INACTIVE service has kept the phone active for 8h?

Anyhow, any hints would help.

Thanks
[ONE Q&A, Help & Troubleshooting] elcom:
It seems that your signals (wifi & cell) are very low. I would bet that this is the reason for the drain.
[ONE Q&A, Help & Troubleshooting] thegios:
no it is not that: I took the screenshot from the changing room where indeed the signals are very low, but next to my bed both signals are at maximum.
[8525, TyTN, MDA Vario II, JasJam General] felixtmwu:
I am using Hermes, (Dopod 838Pro Hong Kong Version) with

ROM 1.23.708.4

Radio Rom 1.06.00.10

Protocol 32.37.7010.01H

The network I am using supports HSDPA, UMTS, EDGE and GPRS where I have not subscribed HSDPA service.

When I was with my Prophet, I saw there were an "E" icon and "G" icon to differentiate between EDGE and GPRS network respectively. However, I only get "U" icon and

"G" icon to identify UMTS and GPRS connection respectively.

My question is

1. HOW TO FIND OUT THE "E" ICON FOR EDGE?

(I have tried the registry tweak EnableDifferGprsEdgeIcon, but it was not successful)

2. IS THERE ANY "H" ICON FOR HSDPA CONNECTION?

3. IF I HAVE HSDPA SUBSCRIPTION, IS THERE ANY PROCEDURE TO CONNECT HSDPA / DISCONNECT HSDPA BACK TO UMTS?

Thank you very much! :)
[8525, TyTN, MDA Vario II, JasJam General] unwired4:
I dont think you will get HSDPA with that radio. You will need to upgrade the radio rom at least (if not the OS too).
[8525, TyTN, MDA Vario II, JasJam General] mgmchan:
Oh yes, I do have HSDPA with that version of Radio ROM. There's no indication for HSDPA. You have to use FieldText.exe to check it out. Or simply browse a web site and note the download speed (I use Spb GPRS Monitor)