yashsingh1/xdaforums huggingface dataset:
[Lenovo Zuk Z2 Pro Questions & Answers] angekcc:
On this website, although not the same terminal advise the 3.0.2.2.

https://www.technobuzz.net/android-7-0-nougat-twrp-recovery-install/

What I also get a lot of extra is that: TWRP 3.0.2.2 are 46Mb

TWRP 3.1.0.0 occupies 19Mb

TWRP 3.1.1.0 occupies 18MbView attachment 4232825

Enviado desde mi ZUK Z2121 mediante Tapatalk
[Lenovo Zuk Z2 Pro Questions & Answers] angekcc:
Twrp officialView attachment 4232830View attachment 4232831View attachment 4232833

Enviado desde mi ZUK Z2121 mediante Tapatalk
[Mogul, XV6800 ROM Development] Asphyx:
Now that we have a rom available to enable the internal GPS (much thanks to DCD!) would it be possible to add a GPS enable/disable icon to the HTC Comm Manager?

Or is this even necessary?
[Mogul, XV6800 ROM Development] sfld:
from what ive heard... once you shut your phone to standby it closes the gps port. some people claim with no apps running such as google maps or live search that by going to ##debug#... it still shows their gps location. If i had a bet and we made a button that did that, all it would do is disable the LOCATION ON setting in your phone settings. Then when you want to turn it on.. you would turn that back to location on
[Mogul, XV6800 ROM Development] dcd1182:
i havent played with commmanagers much, but assuming we can point a button at a mortscript, theres already quite a few gps startup morts floating around. im sure we could modify the start script to be a toggle.. let me look around

edit: check out talynone's thread here and see if any of the launcher-type apps he linked might give us a start. the real project is coming up with what you want to call your gps toggle, i think sticking that in the commmanager will be easy at that point.
[Mogul, XV6800 ROM Development] Asphyx:
Thanks guys,

Really there isn't anything to shut off technically...it's not like shutting off Bluetooth transmitter which drains battery power...

But a toggle to switch bet location on and "911 only" would be helpful for those who have friend tracking apps and don't want to be located at certain times.

It's really a very low priority to have I must admit, but it would be nice to know I didn't have to dig deep into phone settings to toggle that off.

I'll look around for something that already toggles this for those who have built in GPS stock and WM6, And post whatever I find here.
[Mogul, XV6800 ROM Development] vernk:
friend tracking apps?
[Mogul, XV6800 ROM Development] Asphyx:
there are a few of those services like Loopt that will let friends track you via GPS (probably AGPS)....

https://loopt.com/loopt/sess/index.aspx

It's available for Sprint now...

there are also Parental trackers out there for Smartphones but I have never seen one for the PPC yet...

They also use the location on settings in the smartphones which is really the capability we are enabling with the new radio.

So a quick way to turn location on and off seemed like a good idea.
[Mogul, XV6800 ROM Development] hohnan:
If there isn't anything to turn on or off, then why do I need to run AstroGPSLauncher to get the sats up for TomTom? Or is this just making a connection that already is live and leads TomTom to it?

P.S. I have seen CommManagers with a GPS icon in the past. Maybe even on one of your ROM's dcd.
[Mogul, XV6800 ROM Development] Asphyx:
Well hohnan - It's very different situation than the other things you turn on and off in the Comm Manager...

IE: when you turn off Bluetooth your really turning off the transmitter and shutting down the port (com usually) that the receiver uses to send data it recieves to the device...but the receiver stays on.

The GPS location off feature is similar in the respect that it does not transfer data it receives to the rest of the phone because the com port is shut down. There is no radio transmitter being used at all. I'm willing to bet that they use a single Radio receiver for all the radio signals the unit can see (Cell BT WiFi GPS). So by shutting location to 911 only your GPS is still receiving Sat data and running (cause it can see the sat transmissions) but it simply doesn't send the data anywhere as there is no port to communicate with.

I think the primer app your running is simply initializing the communications between the radio and the phone so that Tom Tom can use it.

I suspect in due time both Tom Tom and Garmin will be more aware of the built in GPS settings of WM6 and negate the need to run something else before it will work.
[P8lite Q&A, Help & Troubleshooting] Giuseppe300715:
Can you post link to download emui 4.1 to use rom aosp??
[P8lite Q&A, Help & Troubleshooting] Vinnipinni:
Don't know if you saw it yet, but someone posted the direct link in the aospa thread. I can't link because I'm on mobile.
[P8lite Q&A, Help & Troubleshooting] Giuseppe300715:
Ale b895 ?
[P8lite Q&A, Help & Troubleshooting] JpegXguy:
For anyone that comes here, you can get the update in surdu's post in the respective thread
[General Questions and Answers] Atronid:
Hello there!

Today I'm asking this question because I didn't found a question like this on XDA, and I was wondering why.

However, this is not so obvious in my opinion!

I know that you can find the Java code (in some sort) in the apk file.

But I checked some system apps (i.e. TouchWiz Mass Launcher, SystemUI) and I didn't find any code into these apk, only XML, resources, drawables and stuff.

So where can I find it? I'd like to modify system apps to add new features, not only for theming

Thank you in advance.

(P.s: Please avoid "U should install xposed its mor easy" thing because I do know that and I got it already. Just answer - or don't-, thanks)
[Sprint Samsung Galaxy S6] Jrayokc87:
I had or have (yet to be decided) a sprint galaxy s6. It was rooted with a twrp recovery. The last action I took before I had a problem was re-download the stock antivirus Lookout. After it installed i ran it and lookout instructed me to switch off my unlock oem and unknown sources and I think the develop settings all together. After doing that I restarted my phone. Here is where my problem separates from the others and becomes quite a bit different... The Phone will boot up to the Samsung powered by Android screen then the red letter frp lock comes up and it shuts off and continues on the boot loop. It will not boot up into recovery when it is attempted it acts in the same manner as just turning it on. Normally not a giant issue because the phone DOES boot up into download mode. But the hits keep coming. No computer I have attempted to connect it to will read my phone. I've installed every Samsung driver i can think of but i will re investigate if i had a clue which ones are necessary. Currently it will say USB device not recognized and and the driver reads unknown device. So if anyone knows how to fix it please any suggestion or ideas will b tried.
[Xiaomi Redmi 3s Questions & Answers] zainifame:
Can anyone guide me about upstream kernel, merge and etc? Thank you :fingers-crossed:
[Xiaomi Redmi 3s Questions & Answers] The Arrow:
Thread closed on OP's request.

Regards,

The Arrow
[General Questions and Answers] ItzBluestone:
Hello. I have a question. could any developers Make a one click root (android) that roots your phone with chainfire supersu? that would awesome if someone could :D
[General Questions and Answers] pr1jker:
Did you search xda?

Sent from this galaxy
[ZTE Axon 7 Questions & Answers] WesTD:
Hi everyone. There is a build by [MENTION=5492451]NFound[/MENTION] but it is outdated. Can anyone build it?
[Android Q&A, Help & Troubleshooting] alexruedi:
Hi together,

I am coming from a Huawei Mate 7, where a build.prop mod changed max volume, removing codec folder improved audio quality. And audio_effects.conf cleanup except viper4android delivered really nice sound.

Now it broke and I bought a Huawei ALE-L21 (P8lite), but i am running out of ideas. How can I remove their bad sound enhancements? I was able to remove srs, sws, nxp, tfa (no idea what those are but it improved already quite) and viper is running. But I cannot adjust /system/etc/audio/mbdrc, /system/etc/audio/hissc and /system/etc/audio/dts properly (not sureabout proper values). Those are always 8 files with suffix alice, alicepa, carmel, cherryplus, cherryplusglobal, cherrypro, default and shine. what do they mean?

Has someone an idea? The audio could be much better... zippyshare[dot]com/v/bYJGh5JW/file.html sorry i cannot find the "Attachments"

Thanks a lot for any help,

Alex
[Android Q&A, Help & Troubleshooting] alexruedi:
No ideas?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] henriquemac:
I have a GT-I9195 (kitkat 4.4.2) that I inherited from my dad and it is locked to Vodafone (TCL)(Portugal).

I want to unlock the SIM and i have tried some methods.

The ServiceMode method didn´t work because there wasn't a "PERSO SHA256 OFF" option;

The GalaxSIM app didn't work, the app said i needed to downgrade the baseband to MJ7 or lower.

The Galaxy_S Unlock also didn't work.

I have twrp installed, and i installed a custom rom (aospextended v4.4) to see if it did anything. I also tried the ServiceMode method in that rom but it replied "Network not available" and didn't open (guessing the rom doesn't have ServiceMode).

After A LOT of digging i found a MJ7 baseband (4.2.2), and this is were i am currently struggling.

I'm worried that if i flash it something bad will happen because when downgrading from 4.4.2 to 4.2.2 there is only one particular firmware (from Brazil ZTO) that reportedly works.

Any help will be appreciated.

KEEP IN MIND THAT I HAVE A MAC (el capitan) (SORRY) and i don´t have 24/7 acess to a windows machine, also, i have heimdall 1.4.1 (1.4.0 didn't work for me) and Jodin3 doesn't work for whatever reason.
[General Questions and Answers] Atronid:
Hi everyone,

I posted a thread about a TWRP issue where I was complaining that it didn't work anymore (doesn't want to make backups) after partitioning my SD Card. Now I fixed that, but this incident raised an annoying question: is there any way to use TWRP and still using Link2SD without conflict or you must choice?

Explain for those who didn't already understand :

Basically, Link2SD needs a second partition to move application (data, code, apk and even dex), in order to free up internal storage and more efficiently than only "moving" app on SD Card.

Problem: TWRP on his part can't write on SD card if there is more than one partition. And this for a dark reason (story of single block, blah-blah-bruh)

I already searched around XDA to fix that but I didn't found anything (as usual...)

Well, could you help me?

Thank you in advance
[Galaxy S II Q&A, Help & Troubleshooting] ze7zez:
Obvious obviousness.

Custom ROMs are not meant to replace commercial firmware, but so that the community can learn and be happy to discover new things.
[Galaxy S II Q&A, Help & Troubleshooting] JaLoou:
The screenshots, published with this message, proof the big battery drain after reboot and yet just after charging without even using the Galaxy S2.

I had experiment specially:

after the middle of a night I had swithed off my smartphone, I charged it to 100%, unplugged then I switched it on and leaved immidiately for several hours while I sleeping to late morning.

Then I got the varios battery stats and saved it on the 3 screenshots.

So, everyone can see that the battery lost 39% from full charge without the smartphone being used by the user for several hours.

Moreover, there is a big battery drain just after every charging without the smartphone using and 4th screenshot proofs it too.

And later in response to some nit-pick criticism about this battery consumption test then I had attached yet here a 5th screenshot of the same stand-by battery test on my device swithing on after a full charge but with Samsung's latest official firmware with Android 4.1.2. So, 5 screenshots here give a full picture for compare easy the custom ROMs and Samsung's latest official firmware with Android 4.1.2 in the terms of power consumption.

You can see it clearly that Samsung's latest official healty ROM with Android 4.1.2 consumes not only much less power in stand-by mode but also it consumes power for another purposes at all mostly for cellular network only while the suspicious custom ROMs like LOS 14.1 or RR 5.8.3-5.8.4 consume the enormous big amount of power like crocodiles at stand-by mode for the unwanted excessive file scanning on the user's smartphone!
[Galaxy S II Q&A, Help & Troubleshooting] JaLoou:
The next screenshot proofs the bug of inability to install over-the-air updates (after a firmware update file already downloaded the smartphone shows the error message 'Unable to reboot into recovery').
[Galaxy S II Q&A, Help & Troubleshooting] BenjyTec:
Please keep in mind that none of the developers gets paid for his work. Complaining about bugs not being fixed like this appears disrespectful to me.

Thanks anyway for the thread, might help some people to decide whether to give this ROM a shot or not.
[Galaxy S II Q&A, Help & Troubleshooting] sokri:
A big thanks to the XDA-Devs for this ROM which I have on my phone since 2 months.

In this time, I haven't been able to "seriously" use my phone. Everything is working except the bugs mentionned above, but the phone has become soooo slow... and some issues with battery life also. Sometimes the device just gets hot in my pocket for no reason, drains half the battery in a few minutes (though I have done the "calibration").

Every action becomes a hassle, but works in the end. It's like using Windows 95 on a 486.

So: nice if you want to try out stuff, but no to recommended for every day use IMHO.
[Galaxy S II Q&A, Help & Troubleshooting] JaLoou:
Concealing many bugs the ROM developers did lured me (and many others) as free unpaid beta-testers for their unreliable ROM.

Moreover, the bug tracking functions in Lineage OS and Resurrection Remix are not clear and suspicious. Persons who manage it can get easy a various sensitive information about the smartphone users and can use this data by unappropriate way.

If sort the all known bugs then it is possible to reveal easy that the most part of they haves access to user files on the smartphone. These bugs are:

- the unwanted blocking filter at bluetooth,

- excessive user files scanning,

- wrongly provided Android APIs accompanied with attempts to constraint the users to use only the bloatware ersatz file managers implemented in the custom ROMs and an ugly bloatware ersatz camera app.

The bugs mentioned above are well known but did not fixed for a long period of time. And it triggers really an assumption that they can be specially implemented in the custom ROMs for get a full control over the user files without the user knowledge about it. By another words they are not the unfixed bugs but they are the traces of hidden viruses implemented in the custom ROMs.

These viruses can be ordered and paid masking via chains of proxies by an interested party. Ordered viruses and vulnerabilities can be easy implemented villaintly inside some of many allegedly useful patches on every stage in a long way from an initial open publication of Google's Android source code to a last compilation for get a firmware binary file for a target gadget model.

The device Samsung Galaxy S2 was sold over 40 millions (according to Wikipedia). High probably several millions (may even decades of millions) are remain in use today. And they are an attractive target for an interested party.

Moreover, viruses implemented in a firmware almost impossible to determine by an antivirus software.

The party interested in productions of infected custom ROMs can be also discovered easy by researching and proper sorting the several users of the XDA forum, which was indicated in the hostil activity: they was against the public exposures of serious issues in the custom ROMs, they did tried masked to blackwash me and they lure really new people to become unwill victims of the unreliable custom ROMs. The convinced persons are all have same specific feature...

Unfortunately, one of the XDA moderators forbid to explain about it futher.

But what I allowed to tell here is that any custom ROM development can be supported by a party interested in a mass distribution of viruses hidden in firmwares.
[Galaxy S II Q&A, Help & Troubleshooting] CHEF-KOCH:
Fully disagreed, as long it's constructive critism it helps other to see what is currently working and what not to easier decide to switch to the ROM or not. The main reason is (I asume) to show the list of bugs, which make sense cause the specific LOS thread not shows the current issue, or you need to go trough each comment separately.

I'm glad we still getting updates and **** but some bugs are years old and just migrated because no one seriously took a closer look at it, so I'm happy that this thread exist to share the experience and to list the known issue.
[Galaxy S II Q&A, Help & Troubleshooting] toy_story:
Here you are, not the developers, not doing the right thing.

You want everything at once, and what you did for it.

https://xdaforums.com/showpost.php?p=73346796&postcount=1814
[Galaxy S II Q&A, Help & Troubleshooting] BenjyTec:
Exactly what I wrote in the second half of my post ;)

I understood the purpose of this thread. What I said just refers to two or three sentences the OP posted. Thank you and goodbye.
[Galaxy S II Q&A, Help & Troubleshooting] JaLoou:
Hello.

It is good that the ROM developer had come here in this topic at least.

First of all I do not offend all people. I help Galaxy S2 users to do not fall in the trap, in which I had falled already after being lured by false messages on the XDA forum about allegedly the existence of good ROM Lineage OS with Android 7.1.2 for i9100...

But the ROM is very buggy actually.

For second, all bugs which I described in this topic do not exist in the Samsung's official firmware for Galaxy S2 but only in Lineage and Lineage related ROMs like Resurrection Remix 5.8.3.
[Galaxy S II Q&A, Help & Troubleshooting] ze7zez:
In my opinion, you are making a cardinal mistake comparing Stock Android with version 4.1.2 with custom ROM version 7.1.2.

Each of these versions represents a far different operating model in the hardware layer.

But test yourself, if you have enough free time.
[Galaxy S II Q&A, Help & Troubleshooting] JaLoou:
I'm explaining about bugs exactly. They are simple stupid bugs in the Lineage ROM for Galaxy S2, which people face with.

It is also clear that the ROM developers conceal bugs only instead of fixing they.

I had attached the screenshot to this message, which proofs the bug with a manual inability to enter the current year correctly in a date settings at a portrait mode due to an unwanted limitation of number of years available for choose from.
[Galaxy S II Q&A, Help & Troubleshooting] rINanDO:
That's important information you describe about the wifi. Please determine which security and password you are using so we can reproduce the issue. The Name of your sid doesn't matter.
[Galaxy S II Q&A, Help & Troubleshooting] rINanDO:
Found the bug! It was introduced in linageos since April 27th. https://github.com/LineageOS/androi...mmit/9663c3179fad5e7de7bf4bf31e40649749f33861

The newly introduced faulty input validation is incorrect for WEP. It should not distinguish hex values or plain characters on input. I will create a fix for this.
[Galaxy S II Q&A, Help & Troubleshooting] JaLoou:
Some serious camera apps report clearly about the wrong implementation of Camera2 API in Lineage 14.1 for Galaxy S2. I had attached screenshots to this message for proof it.
[Galaxy S II Q&A, Help & Troubleshooting] JaLoou:
Hello.

The bug with entering password for connect to some WiFi hot spots, which about I did reported here few times, this bug was fixed or such reporting was my mistake and I really sorry for that. Now I'm able to connect to the 2 WiFi hot-spots, to which I was unable to connect before. Probably, both WiFi hot-spots are WEP secured with passwords of 10 (decimal) symbols length.

Please, excuse me for disturbance about this bug. Probably, I was mistaken due to I did not know about password lenghts limits to 5 and 10 (decimal) symbols in the WEP.

Very sorry.

But another bugs in the ROM continue to exist and they need to be fixed.
[Galaxy S II Q&A, Help & Troubleshooting] rINanDO:
It is ok. No bad feelings. The very confusing password length has been removed in the official. It was not in Google's android source anyway and the LOS team has merged my commit.

Other good news, I found a workaround to get the camera scene-mode working! It is possibly a bug in the camera firmware which resets the scenemode when the camera starts streaming. It will be in the next official build. As far as I can reproduce, the actual 'night vision'-mode is fireworks.
[Galaxy S II Q&A, Help & Troubleshooting] JaLoou:
Hello.

The semi night vision trick for videorecording by A Better Camera app is to choose manually ISO800 and then choose the scene mode 'Fireworks'.

For more brightness enhancement you can yet choose the 'Cloudly' white balance preset.

I have an old small app, which updates the camera firmware on i9100. I had attached this app to the message. May it will help to someone.

I'm a noob but I think the problem with A Better Camera app is not in the camera hardware but somewhere close to a memory (RAM or flash). And I will try to explain it:

if I launch A Better Camera app for a first time then it shows a simple introductive help on its screen.

If I close the app and run it again then it does not shows the intro help at next launches. It is ok.

But if I press the home button for long time then I get a list of recent apps on the screen and if I scroll it up and clear all the recents list

then only A Better Camera app loses all its settings and becomes like at its first launch (there an introductive help appears again after the app launch).

This bug was not with the Samsung's official firmware Android 4.1.2.

A Better Camera app can improve the camera of our smartphone significantly for video recordings at low light conditions. Moreover, A Better Camera app provides the best DRO-mode among other camera apps, IMHO. It is like a second life for the old camera of our smartphone. So, please pay attention to fix the bug with A Better Camera app.
[General Topics] Anjow:
I'm using Vista Ultimate x32 and hence the mobile device centre, I have an XDA Orbit WM6. Each time I restart my computer it forgets my phone exists and I have to set it up from scratch. The upshot of this is that my contacts all get deleted and re-added, meaning that my speed dial numbers are erased and I have to re-add them.

Needless to say this is a pain in the posterior.

Does anyone know what could be the problem? Or how I can start troubleshooting this?
[Windows 10 Mobile] mautz001:
Greetings

after I hard resetted my Lumia 650 I can no longer download the MS Facebook app with contact sync (People App --> News is the important one for me) . It worked before.

Maybe it updated to a new insider build which removed the functionality?

When I try to install an old MS Facebook APPX Package (Microsoft.MSFacebook_10.3.2.0.AppxBundle) it works but it only shows contact pictures. If I click on "News" or "Recent updates" it shows nothing :(

Any help ? Thanks!

Robin
[Windows 10 Mobile] juanitoriv:
The MS FB app just doesn't work anymore. Facebook removed access from all older & 3rd party apps. So, you're stuck with FB's latest version... I know "Boo", right?
[Windows 10 Mobile] saq333:
If you sideload the MS version of Facebook (the Appx is in the forums, search for a thread with my username), you will get connect back. ONLY if your OS build is prior to Creators Update. I don't know if the 650 was eligible for the CU, hopefully its not, because the CU will remove even that possibility. MSFT killing off every good feature one by one.

I still have FB connect working on my Lumia 1520, but it went away on my HP Elitex3 after Creators. I did do a factory reset on my HP, restored it to my Lumua 1520 restore point...I had FB Connect for a few hours, but once Creators Update kicked it, it was gone. Perhaps, if you find a way to prevent windows mobile from updating, you could prevent CU from kicking in.

good luck. I was upset about this too!