[CLOSED][OFFICIAL XDA][BETA][MAR 19]XDA Labs: Forum App + App Installer + Xposed Repo

IronTechmonkey · May 26, 2020

Wood Man said:
This is related to what is red-squarred in the attached pic. Post #2, known issues.

And can be seen here for instance too: https://xdaforums.com/android/apps-games/labs-t3241866/post72604833

Oswald Boelcke said:
:good: Ok, thanks for the explanation, and I'm glad that it's already known. I didn't refer to the issues described in post #2 as the example was not a multi- but single quotation.
However - and lesson learnt (will remember), I wasn't aware that CODE tags often break post rendering within Labs.:good:

I doubt I have any new details to add, or very old details as the case may be, but anyhow; I did not get back to the MiXplorer thread in time with follow up (which I was going to do in this thread, linking from there) but in the post preceding Mohan's I mentioned this being an old issue, and the follow up with which I was late is this: This glitch has been known for years (at least since May 2016) but may be experienced to differing degree based on usage. E.g. In Labs PM one particular username containing [] routinely and predictably breaks quoting but in threads accessed by Labs the issue seems less common than in Labs PM, and it does not seem to occur in web browsers much if at all.

bveditz · May 27, 2020

Got a question and maybe it's answered somewhere in this 1200 page thread. But maybe someone can help. I also have the 'can't login' issue and from what I've read, it's been an ongoing issue that folks haven't figured out yet. I'm not too concerned about that not working on some devices (in my case), except its kinda impacting me on something right now. I'm trying to use the AAGateway app which is a paid app that you can only get through XDA Labs. I need to try to get that app installed on some of my older devices (Android 4.x, 5.x, etc) however the only way to install it is via the xda labs app and it seems many of them have the can't login error message. I can login and download the app fine on my pixel or a couple late OS model phones, but sadly that particular app doesn't work that great on later devices and it's better with older devices that have root, which those devices seem to be the ones with the login issue on XDA Labs. Anyway, since there isn't a lot of progress on the login issue, is there any other way to install XDA Labs paid apps other then via the XDA Labs app?

Side note, I tried both logins (regular and google) to no avail. Regular login gets the invalid user/pass (and yeah, i've tried the various password reset tricks) and the google login. The google login just gets a green screen with a refresh circle. Whats funny is if you rotate the display at all during this process, it just goes back to the 'welcome to the app' screen.

Eleo · May 27, 2020

bveditz said:
Got a question and maybe it's answered somewhere in this 1200 page thread. But maybe someone can help. I also have the 'can't login' issue and from what I've read, it's been an ongoing issue that folks haven't figured out yet. I'm not too concerned about that not working on some devices (in my case), except its kinda impacting me on something right now. I'm trying to use the AAGateway app which is a paid app that you can only get through XDA Labs. I need to try to get that app installed on some of my older devices (Android 4.x, 5.x, etc) however the only way to install it is via the xda labs app and it seems many of them have the can't login error message. I can login and download the app fine on my pixel or a couple late OS model phones, but sadly that particular app doesn't work that great on later devices and it's better with older devices that have root, which those devices seem to be the ones with the login issue on XDA Labs. Anyway, since there isn't a lot of progress on the login issue, is there any other way to install XDA Labs paid apps other then via the XDA Labs app?

Side note, I tried both logins (regular and google) to no avail. Regular login gets the invalid user/pass (and yeah, i've tried the various password reset tricks) and the google login. The google login just gets a green screen with a refresh circle. Whats funny is if you rotate the display at all during this process, it just goes back to the 'welcome to the app' screen.

You can contribute with logging and providing logs of login issues as previous users to help devs:
https://xdaforums.com/android/apps-games/labs-t3241866/post82627561
https://xdaforums.com/android/apps-games/labs-t3241866/post82628741

Rotation resets display layout, that is why. Paid apps require XDA Labs app logged in the smartphone

Sent from my Google Pixel 3a XL using XDA Labs

BeeJ1109 · May 28, 2020

Eleo said:
I noticed this in logs:

This should help devs to find out the culprit. Thanks for reporting

The rest is left to see whether other users who can't login experience the same logs or this is special for your device. Let's wait until they upload their logs as well @BeeJ1109 and @elocnix

Hi All,
I would gladly help !!!!

All I want is a concise method on MatLog app, setup of the parameters needed firstly.

Then the correct procedure from start to finish, using "MatLog v1.2.3 to record and save "only the lines of text" in regards to the Login issue with XDA Labs v1.1.6b-debug. Removing ALL the useless lines of text.

That is it, and I only need to extract or setup the Matlog app, Functional to record only the login and the response back, that XDA server is rejecting my Username and Password. As being "incorrect" on only one device.
Whereas xda-1.1.6b-play.apk works correctly on ALL other devices, I own.

I have also posted a PM to the Dev, plusCubed.
Mike Channon, XDA Forum Administrator, whom informed best to contact the Dev.

Suggest others, do the same, "more the merrier", might get a response.

Mike, also informed me, there is another completely new update of XDA Labs app, being released soon. After 2 years of no updates, last released in early 2018. Not xda-labs-1.1.7b-rc2-debug.apk.

Please respond, so I can provide the appropriate logcat required for examination, to hopefully find a solution to this Annoying Login problem, many others are also finding issues with this XDA app.
.
Cheers

---------- Post added at 05:43 AM ---------- Previous post was at 05:14 AM ----------

barcia99 said:
Try this, @Eleo gave me these instructions.

---------- Post added at 08:00 PM ---------- Previous post was at 07:59 PM ----------

Sorry, video link didn't upload

---------- Post added at 08:04 PM ---------- Previous post was at 08:00 PM ----------

By Kindle you mean Amazon Kindle Fire? Because the other kindle doesn't use Android as a system OS.
About logging, once you install matlog, open the app and give root permissions, it will start collecting logs. As simple as that. I don't know what are you unsure about. But nevertheless, here you can find more info on logging using matlog:
https://www.celsoazevedo.com/files/android/how-to-save-logcat/
It also has a video record in case you are still confused.

Good luck

Hi Thanks for the links.
Sorry Video is OK, explains the basics, includes the Procedure in text, to help understand the accent, what he is describing.
But found it a little too basic.

I can assure you, it is not simple to create, the correct info, in regards to the logcat, required to investigate a precise issue.

1. Requires a concise "step by step" procedure.
2. Includes the "best settings" in the app's setup, prior to recording.
3. What is required to search and extract a partial log.
4. That only creates a logcat file, that is useful to Devs., and other knowledgeable members .
5. Post to investigate and hopefully fix the issue.

So far, all my attempts are full of useless info, and nothing, about the errors, or what is the cause of the failure.

Cheers

barcia99 · May 28, 2020

BeeJ1109 said:
Hi All,
I would gladly help !!!!

All I want is a concise method on MatLog app, setup of the parameters needed firstly.

Then the correct procedure from start to finish, using "MatLog v1.2.3 to record and save "only the lines of text" in regards to the Login issue with XDA Labs v1.1.6b-debug. Removing ALL the useless lines of text.

That is it, and I only need to extract or setup the Matlog app, Functional to record only the login and the response back, that XDA server is rejecting my Username and Password. As being "incorrect" on only one device.
Whereas xda-1.1.6b-play.apk works correctly on ALL other devices, I own.

I have also posted a PM to the Dev, plusCubed.
Mike Channon, XDA Forum Administrator, whom informed best to contact the Dev.

Suggest others, do the same, "more the merrier", might get a response.

Mike, also informed me, there is another completely new update of XDA Labs app, being released soon. After 2 years of no updates, last released in early 2018. Not xda-labs-1.1.7b-rc2-debug.apk.

Please respond, so I can provide the appropriate logcat required for examination, to hopefully find a solution to this Annoying Login problem, many others are also finding issues with this XDA app.
.
Cheers

---------- Post added at 05:43 AM ---------- Previous post was at 05:14 AM ----------

Hi Thanks for the links.
Sorry Video is OK, explains the basics, includes the Procedure in text, to help understand the accent, what he is describing.
But found it a little too basic.

I can assure you, it is not simple to create, the correct info, in regards to the logcat, required to investigate a precise issue.

1. Requires a concise "step by step" procedure.
2. Includes the "best settings" in the app's setup, prior to recording.
3. What is required to search and extract a partial log.
4. That only creates a logcat file, that is useful to Devs., and other knowledgeable members .
5. Post to investigate and hopefully fix the issue.

So far, all my attempts are full of useless info, and nothing, about the errors, or what is the cause of the failure.

Cheers

I will attempt to help as much as possible.
1: Open matlog
2: Hit x button top right to clear logs, then quickly
3: Hit three dots button top right for drop-down click file then the record button. At this point it's recording. Minimize matlog (don't close) at this time.
4: At this time go straight to XDA login and try to reproduce the failed login. Once done go back to matlog app.
5: once back in matlog app stop recording by hitting the blue stop icon bottom right corner.

From there I go to internal storage and find a file named matlog. Open that and logs should be there. Hopefully! In regards to partial logs I really don't know and don't want to steer you in the wrong direction. Good luck.

bveditz · May 28, 2020

Eleo said:
You can contribute with logging and providing logs of login issues as previous users to help devs:

Got it. Not sure what you use for logs (again, this thread is too long), so I just used matlog to capture the log. I attempted both logging in normally and via Google login. I didn't remove anything from the logs, but I did just go from matlog to the XDA app and back after so hopefully the logs aren't too bloated. For now I've just done it on one of the devices, the second device isn't rooted (damn verizon Moto E) and the third device is currently without internet access after some kernel modifications I was in the midst of. Anyway, I'll try to capture other logs from this or other non-working devices, just let me know if this is what you're looking for.

In any case, I've found a way around logging in to get the paid app installed and I don't otherwise use this app, so i'm no longer affected. Hopefully they'll find a fix for others though.

Good luck!

Eleo · May 28, 2020

bveditz said:
Got it. Not sure what you use for logs (again, this thread is too long), so I just used matlog to capture the log. I attempted both logging in normally and via Google login. I didn't remove anything from the logs, but I did just go from matlog to the XDA app and back after so hopefully the logs aren't too bloated. For now I've just done it on one of the devices, the second device isn't rooted (damn verizon Moto E) and the third device is currently without internet access after some kernel modifications I was in the midst of. Anyway, I'll try to capture other logs from this or other non-working devices, just let me know if this is what you're looking for.

In any case, I've found a way around logging in to get the paid app installed and I don't otherwise use this app, so i'm no longer affected. Hopefully they'll find a fix for others though.

Good luck!

Lines 1604-1661 and 3150-3188 have the errors of login in your logs. They coincide with logs shared by barcia99, which could be good news, as it defines the reason of login issue

Sent from my Google Pixel 3a XL using XDA Labs

DB126 · May 28, 2020

Eleo said:
Lines 1604-1661 and 3150-3188 have the errors of login in your logs. They coincide with logs shared by barcia99, which could be good news, as it defines the reason of login issue

Agreed - albeit no active (at least visible) development at present. XDA labs is a glider.

BeeJ1109 · May 29, 2020

bveditz said:
Got it. Not sure what you use for logs (again, this thread is too long), so I just used matlog to capture the log. I attempted both logging in normally and via Google login. I didn't remove anything from the logs, but I did just go from matlog to the XDA app and back after so hopefully the logs aren't too bloated. For now I've just done it on one of the devices, the second device isn't rooted (damn verizon Moto E) and the third device is currently without internet access after some kernel modifications I was in the midst of. Anyway, I'll try to capture other logs from this or other non-working devices, just let me know if this is what you're looking for.

In any case, I've found a way around logging in to get the paid app installed and I don't otherwise use this app, so i'm no longer affected. Hopefully they'll find a fix for others though.

Good luck!

I downloaded your log.
Sorry useless.
I mentions XDA-labs once.

So your point. I understand the basics of getting a logcat.
I need someone. To provide the best settings they use to get a log that isonly capturing , errors or faults.
The rest is useless text. Irrelevant to the problem.

The reason for long thread is to explain the problem fully.
If you read my post fully, I have an issue with one device, the other 3 or work.
That's it.

Thanks for your effort.

Cheers

Eleo · May 29, 2020

BeeJ1109 said:
I downloaded your log.
Sorry useless.
I mentions XDA-labs once.

You don't read logs by searching for keywords only. That would be easy and fast way, but also wrong, since you would miss some important clues. Logs have levels; I, V, D, E and F (which is fatal error in framework, but is written as WTF in apps; that mostly ends up with a app/device restart or not boot at all). Those are more of your concern rather than keywords to look for app name (sometimes app package name may not even show up in logs). More info you can get in following links:
https://developer.android.com/reference/android/util/Log
https://www.scalyr.com/blog/logging-levels/
and similar...
Without going too much off topic, please check the lines that I posted above. They are the culprit.

BeeJ1109 said:
I need someone. To provide the best settings they use to get a log that isonly capturing , errors or faults.
The rest is useless text. Irrelevant to the problem.

You can filter logs to show different levels. You click on 3dot button and log levels, and you see a list. This list means the following:

- if you choose verbose logs, you will see V, D, I, W, E and WTF (no kidding) in your logs
- if you choose debug logs, you will see D, I, W, E and WTF (still no kidding) in your logs
- if you choose info logs, you will see I, W, E and WTF (again, serious) in your logs
- if you choose warn logs, you will see W, E and WTF in your logs
and so on

As you get more to the end, you don't get "useless text" in your logs

But

Sometimes that useless text can provide a missing link in the issue. In that case you might be asked to provide "full logs". So, you have following as an option:

- take FULL logs, save it, then open it in matlog, filter warn (or error), save as second version, share it. If you are asked to provide full logs, share the first one (full logs).

Sent from my Google Pixel 3a XL using XDA Labs

BeeJ1109 · May 29, 2020

Eleo said:
You don't read logs by searching for keywords only. That would be easy and fast way, but also wrong, since you would miss some important clues. Logs have levels; I, V, D, E and F (which is fatal error; that mostly ends up with a app/device restart or not boot at all). Those are more of your concern rather than keywords to look for app name (sometimes app package name may not even show up in logs). More info you can get in following links:
https://developer.android.com/reference/android/util/Log
https://www.scalyr.com/blog/logging-levels/
and similar...
Without going too much off topic, please check the lines that I posted above. They are the culprit.

Thanks for your info.
I am not really up with this Matlog. app. You may have gathered.

I will further investigate by reading the info within the links provided.
I can see the log levels.
So a simple Q&A. What setting did you use to achieve the numbered line numbers mentioned.
What text reader are you using.

All I have asked for, is a concise dot point guide. For New Users to learn from the experts.

If I know the settings, then I should be able to replicate,
using my non working Device, compared to one of my working Device.

Cheers

Eleo · May 29, 2020

BeeJ1109 said:
Thanks for your info.
I am not really up with this Matlog. app. You may have gathered.

I will further investigate by reading the info within the links provided.
I can see the log levels.
So a simple Q&A. What setting did you use to achieve the numbered line numbers mentioned.
What text reader are you using.

All I have asked for, is a concise dot point guide. For New Users to learn from the experts.

If I know the settings, then I should be able to replicate,
using my non working Device, compared to one of my working Device.

Cheers

Well, for now, as a user who provides logs, all you need to do is following:

- be sure to have other apps turned off (not uninstalled, but probably, force stopped), as signals from those can provide more impurity in logs
- try to be done as fast as possible

About the line numbers; you just need a correct software to read logs. If you want to read logs:
- In PC I use notepad++ (freeware)
- In android device, I use Mixplorer (it is a file explorer app, that has inbuilt code editor), but you can also use quickedit text editor if you dont want the file explorer part of Mixplorer

Both of the software above will view the logs with line numbers.

About dot point guide; nobody gets it. You figure it out yourself. Same was for me. If you don't try yourself, but instead do it from a written guide, you wouldn't understand what is where and what means what. So, my recommendation would be to try out stuff.

I can't go into more details as it really is an offtopic discussion.

Sent from my Google Pixel 3a XL using XDA Labs

coal686 · May 29, 2020

Eleo said:
I can't go into more details as it really is an offtopic discussion.
Sent from my Google Pixel 3a XL using XDA Labs

bveditz · May 29, 2020

BeeJ1109 said:
I downloaded your log.
Sorry useless.
I mentions XDA-labs once.

Not sure why you replied to my post, since I'm just an affected user like you who posted their logs. As an aside, when I captured my logs (using matlog) and posted them, I did skim the logs and there really isn't anything confidential captured in the logs so I don't see any issues with just posting full logs and not worrying about trimming them or anything else. It's also not up to us to figure out what the problem is or isn't, because we're not the developers so we have no access to the code, it's just up to us to help show what's happening on our device and if we're lucky, it'll provide some insight to the developer. Seems like you're thinking too much about how it'll help the developer instead of just giving them the logs and going about your day.

BeeJ1109 · May 30, 2020

Eleo said:
Well, for now, as a user who provides logs, all you need to do is following:

- be sure to have other apps turned off (not uninstalled, but probably, force stopped), as signals from those can provide more impurity in logs
- try to be done as fast as possible

Question How Do I "force stop" 147 apps at once.
I could backup apps, using Titanium Backup apps only, which I do regularly. Remove 145.
Leave only 2 apps. But Google is always running crap in Back ground.
Makes a total 350 , if you include systems apps, some of which are necessary otherwise the Tablet will not work.
After completed the Matlog, can reinstall app backups.
So what is your suggestion.??

About dot point guide; nobody gets it. You figure it out yourself. Same was for me. If you don't try yourself, but instead do it from a written guide, you wouldn't understand what is where and what means what. So, my recommendation would be to try out stuff.

OK, I understand where are coming from, in regards to learning the process by experimenting.
I wrote TECHNICAL manuals for >20 years to assist 100s of employees, as a Technical Specialist, on Mobile Networks. I can tell you there are lots Q&A , Feedback, Corrections to improve the process. It's called "Best Practice".

So if you will not offer a guide on "how to".
Then at least tell me something, that will help me understand the process of logging. Called "a Hint".
1. Create a full log - Understand that.
2. Log levels are set for initial log before record, or set to default as original install setting. or select another option.
3. Log levels Only used when Reviewing the saved log.
4. The captured log. Can edited, using Full Log, then Partial log extracts the relevant parts, that relates to the issue we are investigating.

I can't go into more details as it really is an offtopic discussion.

Do not understand comment "offtopic discussion". Please explain what you are referring to.

Hi eleo,
Thanks for your help,
Cheers

barcia99 · May 30, 2020

BeeJ1109 said:
Do not understand comment "offtopic discussion". Please explain what you are referring to.

Hi eleo,
Thanks for your reply.
Cheers

I think the bottom line is we're all here to help each other when possible. All that's truely needed is for you to upload the (full) log and have the developer's look at it along with the logs I uploaded and any others. Bottom line is we all would like a solution. Just my thoughts

BeeJ1109 · May 30, 2020

bveditz said:
Not sure why you replied to my post, since I'm just an affected user like you who posted their logs. As an aside, when I captured my logs (using matlog) and posted them, I did skim the logs and there really isn't anything confidential captured in the logs so I don't see any issues with just posting full logs and not worrying about trimming them or anything else. It's also not up to us to figure out what the problem is or isn't, because we're not the developers so we have no access to the code, it's just up to us to help show what's happening on our device and if we're lucky, it'll provide some insight to the developer. Seems like you're thinking too much about how it'll help the developer instead of just giving them the logs and going about your day.

Hi bvedit,
I am just trying to understand the process.
There does seem to be a guide as to what settings are required for the initial log.

I don't have an issue with the privacy part you mention.

It's ALL about getting a log that will be useful to publish.
A complete waste of time for all, if you attach a log that is useless to the developer, whom is asking for the log, thinking everybody automatically knows the process.
A little help goes along way to solve the problem, in a quick efficient way. Time is money.

Just tell me your settings, that's it.
I have been trying to get a similar log to you.

Thanks again,

Cheers

knpk13 · May 30, 2020

BeeJ1109 said:
Do not understand comment "offtopic discussion". Please explain what you are referring to.

The sentence I'm typing out right now (with the blessing of coal686) is considered "offtopic discussion". :fingers-crossed:

Eleo · May 30, 2020

BeeJ1109 said:
Just tell me your settings, that's it.
I have been trying to get a similar log to you.

You just need to follow the steps you were told. That is it. There are no settings, no rules, no musts, no have to's.

You have a post with link to webpage that tells you exact steps you need to do:
https://xdaforums.com/android/apps-games/labs-t3241866/post82621265

You have a post that explains the steps you need to accomplish:
https://xdaforums.com/android/apps-games/labs-t3241866/post82621429

There is a post that tells you what to read in logs:
https://xdaforums.com/android/apps-games/labs-t3241866/post82694739

There is a post that tell you how to read logs:
https://xdaforums.com/android/apps-games/labs-t3241866/post82695219

By now you have everything you need. You have not only stuff you need for providing logs, but also to read them. And truth to be told, you, reading the logs will not help developer or development of this app.

BeeJ1109 said:
Do not understand comment "offtopic discussion". Please explain what you are referring to.

This thread is XDA Labs app development thread. You will find numerous amount of threads in XDA that are meant to explain HOW to get logs, how to read logs, how to use a specific app and etc. Each topic is covered in not one, but several threads meant for them.

Discussing these topics in XDA Labs development thread is not normally ok, because we are re-stating what is mentioned (and in a more thorough way) on those threads. Which also means, we are going off the track from the main point of this thread. As you see above, I have shown you a number of post only meant to explain you the logging event. Only. Nothing about this apps development. It is plain logging that is meant to be used at any app force close/app not respond/app fail to execute an action and etc.

BeeJ1109 said:
There does seem to be a guide as to what settings are required for the initial log.

No, there isn't. All you need it to follow steps as written. That is it.

BeeJ1109 said:
It's ALL about getting a log that will be useful to publish.
A complete waste of time for all, if you attach a log that is useless to the developer, whom is asking for the log, thinking everybody automatically knows the process.
A little help goes along way to solve the problem, in a quick efficient way. Time is money.

We never have said any such thing. Logs are shared to provide info. But they also may not. And we never wrote any post saying "your logs didn't help, it is waste of time". It was you, who said that a log was useless (here: https://xdaforums.com/android/apps-games/labs-t3241866/post82694647 ) but instead it was quite useful and gave the idea about the issue. So, it wasn't our claim. You claimed that post and now say that we would write that. We won't.

And yes. Time is money. Longer it takes you to share logs, more time is wasted.
Just an FYI.

BeeJ1109 said:
I need someone. To provide the best settings they use to get a log that isonly capturing , errors or faults.

Truth to be told, I don't like this expression. It comes up too many times in kernel, ROM and camera app discussion. There is an illusion in users, thinking there is A ONE, absolute and perfect setting, in which they can perform everything in a best way. But no. There cannot be an ultimate perfect setting. And if even there is one, then it is the default setting, coming right after launch. So, please, do not get into that illusion as well. All you need to do is to perform the steps and log the event.

I know coal686 gave permission to extend off-topic, but I am rules-guy myself. And as I extend this offtopic I feel unwell.

Wish you luck.

Auf Wiedersehen,
Eleo

Sent from my Google Pixel 3a XL using XDA Labs

bveditz · May 31, 2020

BeeJ1109 said:
Just tell me your settings, that's it.
I have been trying to get a similar log to you.

Oh, I didn't do anything special, so if you're trying to get the same log... I basically did this (forgive my slight vagueness on the exact dropdown names, i don't have that phone in front of me and its no longer running matlog or xda labs anymore anyway):

1) opened xda labs
2) opened matlog
3) hit clear logs in matlog.
4) switched over to xda labs
5) tried logging in
6) switched back to matlog and did the 'save log' command
7) copied log to pc and added to an email.

That's it, but if that doesn't work for you then I would just give up.. This might be a bit out of your depth, no offense.

[CLOSED][OFFICIAL XDA][BETA][MAR 19]XDA Labs: Forum App + App Installer + Xposed Repo

Recognized Contributor

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Moderator / Developer Rel. / Mod Liaison

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts