26
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: + + + + + + + + + + + + + + + + +
no edit summary
This is a good place for [[User:Haixinshi]] to discuss his progress [[User:Podehaye|Podehaye]] ([[User talk:Podehaye|talk]])
This is a good place for [[User:Haixinshi]] to discuss his progress [[User:Podehaye|Podehaye]] ([[User talk:Podehaye|talk]])
== 7.25([[Item:Q1185|Le Temps]]) ==
=== Progress: ===
# √ Make corresponding methods that can parse and save JSON and other information. This point is very important for me to improve efficiency. Previously, I have to write all '''smali''' inside a target function, which would not only cause register overlapping and control flow error, but also introduce complexity since one line Java code can be compiled into multiple lines smali code. After reaching this point, in the future, I only need to write java code, which is more efficient, and then transform an integration into target smali code. It can speed up a lot!
# × Try to dynamically test SDKs in terms of advertisement.(I was stucked by point 4)
# × Try to find and collect message flow in Le Temps in terms of advertisement network. (I was stucked by point 4)
# √ Let Storing Data Locally work in different environments. Currently Storing Data Locally can work well in my Android Emulator, but it is more tricky to adapt to other environments like the Samsung Phone Paul gave me. The reasons are:
* If there is no SdCard, we have to store data into internal memory. However, if the mobile app is not '''rooted''', it is hard to access to data in internal memory(Users can not access to this data, and only the app itself can).
* Now, I can get the correct absolute address to store data in internal storage and external storage, which can be adapted to any mobile phones.(But it is not convinient for me to debug on Samsung Phone, since I can not view text easily). So I will use Android Emulator in next steps for efficiency.
=== Questions: ===
# Can I root the phone? Unfortunately, root is not reversable. But it is very common in dev teams.
# The problem about '''Saving Data Locally''' is unavoidable in teh future. I have a basic idea about how to design it. We can create a floating window for the users(users can hide it of course). In this window, users can view what type of advertisement they are exposed to; users can choose and send data to our server for further processing. But I am not very sure about this, because it seems like a heavy modification for an APP. The Game Testing Team in ByteDance would choose to use another APP to dynamically inject into targeting APP.
=== Plans: ===
# Try to dynamically test SDKs in terms of advertisement.
# Try to find and collect message flow in Le Temps in terms of advertisement network.
== 7.23([[Item:Q1185|Le Temps]]) ==
== 7.23([[Item:Q1185|Le Temps]]) ==
=== Progress: ===
=== Progress: ===