Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,768,220 Members 44,517 Now Online
XDA Developers Android and Mobile Development Forum

[Suggestion] Version name and code in log file

Tip us?
 
Falseclock
Old
#1  
Falseclock's Avatar
Senior Member - OP
Thanks Meter 291
Posts: 495
Join Date: Jun 2012
Location: Almaty

 
DONATE TO ME
Default [Suggestion] Version name and code in log file

Dear @rovo89,

What if add version name and code in log file when modules are loading?

Loading Xposed v54 (for Zygote)...
Running ROM 'KOT49H release-keys' with fingerprint 'htc/htc_europe/m7cdug:4.4.2/KOT49H/342802.6:user/release-keys'
Loading modules from /data/app/kz.virtex.htc.tweaker-1.apk
Loading class kz.virtex.htc.tweaker.XMain
Name: 8.5.13, Code: 256
Loading modules from /data/app/com.sensetoolbox.six-1.apk
Loading class com.sensetoolbox.six.mods.XMain
Name: 1.0.7, Code: 15

Very useful when receiving logs from users and during development when module crashes system.
 
rovo89
Old
#2  
rovo89's Avatar
Senior Recognized Developer
Thanks Meter 13865
Posts: 2,367
Join Date: Jan 2012
A good idea, but the problem is that the package manager service isn't running at that time. So this information would have to be parsed out of the AndroidManifest.xml manually. There is a PackageParser class, but it's quite complex. It could be considered, but it would have to be carefully tested to avoid unwanted side-effects. Keep in mind that this code runs before Android begins to start, and from past experiences I know that some classes on some ROMs should better not be used that early. Not sure if this would also be the case for PackageParser or its dependencies.
Tired of updating your mod for every new ROM release?
You want give users the possibility to combine different mods without creating tons of different files for all possible combinations?
Then have a look at my Xposed framework - modifications without APK changes!
 
GermainZ
Old
#3  
GermainZ's Avatar
Forum Moderator / Recognized Developer
Thanks Meter 6032
Posts: 5,262
Join Date: Aug 2012
Could it not be stored by the Xposed Installer? Basically, instead of saving the module's name on each line in modules.list (IIRC), it'd put the name, version name and code separated by e.g. commas.
 
rovo89
Old
#4  
rovo89's Avatar
Senior Recognized Developer
Thanks Meter 13865
Posts: 2,367
Join Date: Jan 2012
That would be an option. Not 100% reliable, but unless something goes really wrong (e.g. someone replaces the APK directly), it should be fine.
This topic and your suggestion goes a bit into the direction of a suggestion @M66B made - storing the start class name in the manifest instead of assets/xposed_init.
Tired of updating your mod for every new ROM release?
You want give users the possibility to combine different mods without creating tons of different files for all possible combinations?
Then have a look at my Xposed framework - modifications without APK changes!
The Following 3 Users Say Thank You to rovo89 For This Useful Post: [ Click to Expand ]
 
hamzahrmalik
Old
#5  
hamzahrmalik's Avatar
Senior Member
Thanks Meter 1095
Posts: 926
Join Date: May 2013
This doesn't really solve the problem but I think I'll share
For one if my mods I provided a report error button
The button creates a log by getting the Xposed Log and appending version
Number etc and saving to SD card
So users can easily get logs AND I can easily sove problems
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes