yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] tommo1982:
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
[Android Q&A, Help & Troubleshooting] phonedriller:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
[Android Q&A, Help & Troubleshooting] tommo1982:
I had issues with adds being displayed at home screen and I was not able to close them. I had to use NetGuard to find that FOTA talks to 'adsup' and it is a known malware provider. I learned that some of the system apps try to talk with Alibaba servers and AdOppo (whatever it's called). Kaspersky might not be wrong, actually.

I'm trying to download stock firmware, but I don't know the file name. The website with it is locked, so unless I know exactly what I need, I cannot download it.
[Android Q&A, Help & Troubleshooting] phonedriller:
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
[Android Q&A, Help & Troubleshooting] phonedriller:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
[Android Q&A, Help & Troubleshooting] phonedriller:
Ps use root + apps2sd or titaniumbackup to stop/disable the bad apps and replace them with playS app,not possible on all apps of course :(
[Android Q&A, Help & Troubleshooting] tommo1982:
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
[Android Q&A, Help & Troubleshooting] phonedriller:
Flashing is super easy use spflashtools or. Odin compiling a Rom is not , were you able to get the original firmware? You will need the original firware to get the boot and partition info from what i read so far
[Android Q&A, Help & Troubleshooting] tommo1982:
Unfortunately not. I will ask at the shop where I bought it how to contact tech. It should be freely available. I don't understand why Qilive restricted access to firmware.

I'll post when I learn anything.
[Android Q&A, Help & Troubleshooting] tommo1982:
Well, you can download the firmware if you know the file name. The bad news is, it seems the stock firmware has malware preinstalled. If there is anyone who could help confirm it. I have the ROM, and I can upload it to Google Drive if needed.
[Android Q&A, Help & Troubleshooting] xdacktheresianum:
Hi all,

I'm coming back to a question lingering since the very first post here and mentioned again in post #9:

Is there a successful way to install TWRP on this Qilive model?

Re this topic:

- has anybody tried/has anybody been successful with the procedure described in post #9?

and

- has anybody seen the following TWRP builders' version (do an in-page search on Q8S55IN4G2)

https://twrpbuilder.github.io/fr/downloads/twrp/

with the download belonging to it

https://androidfilehost.com/?fid=890129502657591798

???

any successful installations to report???

Wouldn't THAT be great!!??

thanks

xdack
[Verizon Samsung Galaxy S8 Guides, News, & Discussi] dtroup64:
Just got the CRC5 update.
[Tilt, TyTN II, MDA Vario III General] joreto787:
hi all,

i have a big problem. after flashing my radio and unlocked by sim unlocker every thinh was fine. BUT, after i get all my files back by sprite buck up, i can not start the kaiser again. After rebooting, the boot process is going up to the gtc icon and thats it. i have alreade try it with the mtty.exe and also with hard reset but nothing helps.

PLEASE ANY IDEA?
[Tilt, TyTN II, MDA Vario III General] ach2:
What rom have you got, what radio version etc. Any more info will help.

My gut instinct is that you've got the wrong radio.
[Spice Dream Uno] skd123:
Hi Friends,

My Dream Uno MI-498, a 3 yr. old set, presently running Marshmallow, is behaving

strangely since last 3-4 months. Due to some unknown reasons, battery is depleting

very fast & sometimes as low as 4-5 hrs till zero level. While checking battery

details, I find that "Mobile standby" is the major culprit & consumes 95% of battery. e.g., at say, 10% battery remaining, Mobile standby usage is around 85%, screen- 1%, voice calls-1% etc . While checking history, I find that system shows Wi-Fi signal is on, but actually, in order to save battery, I never keep Wi-Fi on while not in use. Since my ROM is only 4 gb, I uninstalled majority of apps, disabled un-installable apps like Flipkart etc, switched on battery saver to increase battery life but nothing improved. Strangely, I have found that, if I keep Wi-Fi always on & surf net for some time depletion of battery halts to a great extent & then battery can last for more than 2 days. Earlier, same handset gave me 6-7 days battery strength. I am also having another Android one set from Micromax, which incidentally showed identical problems with battery lasting for 3-4 hrs without any usage. In this case also, battery history indicated that all signals( mobile network, Wi-Fi, Awake, Screen ON) are always ON which is not true excepting mobile network signal. Luckily, keeping Wi-Fi always on & surfing net for some time, mobile standby usage reduced & battery life increased to a great extent (now 3-1/2 day running with 55% battery remaining).

Being a newbie, I am clueless to these strange behaviors of Android 6.0.

I am now requesting my member brothers to give some suggestions/settings(without

rooting) so that battery life of my Spice mobile increases to at least 4-5 days.

My mobile service provider is BSNL(Bharat Sanchar Nigam from India).

Thanks & regards,

S. K. De
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] fosseperme:
edit

*** mod edit: thread closed ***
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] fosseperme:
Do not ask for ETA's.
I am not responsible for bricked devices, dead SD cards, thermonuclear war,
or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this ROM before flashing it!
YOU are choosing to make these modifications,
and if you point the finger at me for messing up your device, I will laugh at you.

INSTRUCTIONS

- Make total wipe and format data in A and B partitions

- Flash the latest build at this link https://drive.google.com/open?id=1YQqUhZA8v0UVUMKBsCPDt9-Dp0MXoPFr with Deadman Recovery in slot A

- Reboot forcedly in fastboot mode with vol - and power, and after return to TWRP

- Finally flash (without reboot the phone) Gapps Pico arm64 8.1 and Magisk in slot where is installed the system (you can easily understand this in the backup section of TWRP and see the system partition how space take)

- Make the first setup with the Wifi connected!

- Enjoy with Viper OS!

What's working :

Boots

RIL (Calls, SMS, Data)

Fingerprint

IR Blaster

Wi-Fi

Bluetooth

Video Playback

Audio

Sensors

Flash

LED

GPS

Volte

Camera

Known issues:

You tell me

V2 Fixed Camera and added Snapdragon Audio

V1 Initial Release

XDA:DevDB Information

[ROM][UNOFFICIAL][8.1.0] AOSVP: Viper OS [2018-04-10], ROM for the Xiaomi Mi A1

Contributors

fosseperme (aka Antonio Greco), Karan, Aaryan Sharma, Omar Benziane, Basha Shaik, Akhil Bhatia

Source Code: https://gitlab.com/AOSVP-O/manifest

Kernel Source: https://github.com/GamingDevilsCC/android_kernel_xiaomi_msm8953

ROM OS Version: 8.x Oreo

ROM Kernel: Linux 3.x

ROM Firmware Required: Oreo With TWRP

Based On: AOSP

Version Information

Status: Beta

Created 2018-04-10

Last Updated 2018-05-03
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] radogost:
This flashing instructions are weird. Why we can't just boot from official TWRP and install like every other rom?
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] dback31:
So is the stock cam included as the default camera app?

If yes, why don't you use snapdragon cam or gcam?
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] nicolasmart:
You finally bought the device so you can get booting things duh!

---------- Post added at 04:58 AM ---------- Previous post was at 04:57 AM ----------

You should be able to. He just made these instructions for better compatibility. Otherwise you can just flash as usual without formatting.
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] Custom rom 243:
This was my fav rom when it arrived for 7.1.2 for tissot . The version is now 8.1.0 gotta try it asap . Thanku developer [MENTION=2245972]fosseperme[/MENTION]
[Xiaomi Mi A1 ROMs, Kernels, Recoveries, & Other De] fosseperme:
V2 Fixed Camera and added Snapdragon Audio
[Android General] dewizard11:
I am looking for a custom ROM for my dns air tab M83w is there one I can use to improve a bit the performance?
[Nexus 7 (2013) Q&A] AeroplaneMode:
Hello there,

My Flo-Device keeps locking me out, resulting in a short black screen and throwing me back to the lockscreen. Based on the behaviour it seems that this is related to the sensor that is use for magnetic cases.

Unfortunately, I never used such a case, most threads I found are talking about cheap cases with a poor placing of the magnet itself - which does not help me out here.

Any hints on overriding that sensor by software or hardware? Any way of fixing the sensor or even a hint on the location on the Motherboard? I have read about an exposed module disabling it, but to configure the module it may be neccesary to be able to use the tablet in the first place. Currently it is still completely stock.

I appreciate your help or any reference to a solution that I may have overseen in my search. Thanks!
[Nexus 7 (2013) Q&A] k23m:
Hall effect sensor's location is on the first attachment. I can assure you that there is no need to fix it directly because this and many other sensor problems are caused by the LCM connector. Disconnect the battery and just re-seat the LCM connector but be careful, watch this first https://www.youtube.com/watch?v=C9PwK9eGrCY
[Nexus 7 (2013) Q&A] AeroplaneMode:
Thanks for the fast reply and for pointing out the sensors' location on the PCB. Unfortunately, this did not solve the problem. Do you have any other ideas?
[Nexus 7 (2013) Q&A] k23m:
Please also re-seat the other end of LCM cable.

Check if a magnet placed over the sensor's position (top or bottom) has any impact.

Perhaps ROM builders know if something can be changed in /system/build.prop

Remove lock password - start ADB and do:

rm /data/system/locksettings.db

rm /data/system/*.key

Finally, we'll consider a hardware mod.

:good:
[Nexus 7 (2013) Q&A] AeroplaneMode:
I already reseated both end of the ribbon cable to be sure - and again after the first unsuccessful test run. I never used a magnetic case on the device and there ar no other magnets near - my other Nexus 7 is fine though :)

What exactly does the locksettings.db do? I deleted It and rebooted, but no change in behaviour.

btw, as I am unable to properly use the touchscreen, I tried to enable usb debugging via an usb-otg cable and an attached mouse - which worked fine so far. It seems that there might be some interference or mechanical problem. Maybe the first thought with the hall sensor was wrong track :eek: I repaired a lot of devices over time, but (un)fortunately none of them showed that behaviour before, so I'm somewhat out of ideas in this case.
[Nexus 7 (2013) Q&A] k23m:
It removes the lock password and makes it go into LOCKSCREEN-NONE mode, but you have to also remove all files with the ".key" extension from the folder.

Since you repair such devices, then measure voltage on the output pin of the sensor, and measure it again with a magnet over it.
[Nexus 7 (2013) Q&A] AeroplaneMode:
Good idea. Without the magnet I get 2.98 V and with the magnet 0.001 V between GND and out. So I guess the sensor itself may not be the problem? As I recognized that it might be a mechanical problem, I got a friend to use the touchscreen and measured output at the sensor again, it seems to work as intended.

As the lockscreen does not have any further protection set up after a factory reset, I guess this could be the reason that I did not find any *.key files in that directory? So currently it is just 'swipe to unlock'.

Problem with the lockseetings file is: The device is all stock, locked and has no root - and to get a bit more weird, is not recognized when in recovery. My other Nexus 7 with twrp already on it is recognized instantly. I may have to fix that first, as in a weak moment I may have overseen the "access denied" while trying to delete that file and already typing the nex command. My bad - it was already late.

Honestly, I wonder what the problem really is and really appreaciate your help so far.
[Nexus 7 (2013) Q&A] k23m:
The sensor is OK indeed.

As you did factory reset, there is no issue of user data loss anymore, so just unlock it and do factory flash https://developers.google.com/android/images

This should fix the recovery recognition problem too.
[Nexus 7 (2013) Q&A] AeroplaneMode:
Yeah, so I unlocked it, reflashed it with the stock rom, installed twrp and su...and finally got to delete the mentioned files. But still - the issue continues to exist. Also, I see no difference after deleting the files. Does something else prevent that no locksreen-mode?

Do you have any more ideas? I could wildly start changing parts, but unfortunately the device isnt worth that much anymore :-/ As mentioned, using the device with the Mouse hooked up via otg, the screen behaves normal.
[Nexus 7 (2013) Q&A] k23m:
No worries, we'll fix it, but it seems that my opening statement "this and many other sensor problems are caused by the LCM connector" still holds true. On the schematic, R150 and R151 are presumably located next to the sensor on the daughterboard, so if LCM cable connection to main mobo is open, the CPU will constantly sense 0V level, right? And as you measured earlier, 0V means that magnetic flux is detected. Now, about the ribbon cable... you did re-seat it, but this thing is awful and tends to fail repeatedly because of contact oxidation and weak connector lock pressure. Two solutions:

spray with https://www.amazon.com/CRC-5103-Quick-Electronic-Cleaner/dp/B000BXOGNI/

apply a thick tape/spacer over the lock so N7's back cover will add extra pressure on it

Finally, here is a brute-force workaround fix, go: settings - system profiles - default - lock screen - disable :highfive:
[Nexus 7 (2013) Q&A] AeroplaneMode:
I'll test the points you mentioned.

I have to get a can of cleaning spray in the workshop, as I only have other fluids here which leave a oily coating. Or Brake Cleaner Fluid :D Thanks so far, I'll keep you updated.

Disabling the Lockscreen still gives me blackouts but okay, i dont have to swipe anymore - that will do for the moment. I haven't had similar problems in a while, so I tend to forget some points as repairing phones from time to time is only some sort of occupational therapy for me besides my other work ^^
[Nexus 7 (2013) Q&A] AeroplaneMode:
I was finally able to continue here. I cleaned the connection and applied some tape to thicken up the spacers. Still, I am not able to resolve the problem. I also tried to manually apple more pressure on the back, still not getting better unfortunately. :eek:
[Nexus 7 (2013) Q&A] k23m:
I know you're not happy about it but this is the best N7 hardware issue to resolve we've had so far this year :D

I opened up my N7 to check the sensor's connection to main PCB - it goes to LCM pin #41 - note the attached pictures. Disconnect the battery and use an ohmmeter to measure the two points - I get around 8 oHm. If you measure open circuit, then look for broken or corroded track somewhere along the way. If you measure proper connection, then the problem is on the motherboard and there is nothing else we can do - case closed unfortunately.

/EDIT

Here is a software workaround:

install ElementalX kernel

during installation select the "Disable magnetic cover on/off" option

:victory:
[Nexus 7 (2013) Q&A] AeroplaneMode:
I get 3 Ohms, so I flashed the suggested Kernel. It seems to solve the problem, won't get any better I guess. Thanks for your support!

Now is that a good thing? :silly:
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] parthavluv:
First Of All

I am Not Responsible

If your device bricked or any damage

Here i am,

Let me introduce myself

Forget it i m your known Developer

So Here is a Mod Which Allow you to Enable Quick Charge 3.0 in your redmi 3/S/X/Prime

I just Change Some Values In Thermal Library

So you get more power to charge your phone fast

Features :-

* Enable Quick Charge 3.0

* Make Your Phone Faster

* Custom Roms Support

Conc.

* Maybe little bit heat issue

Build 8 Updated

Magisk module added to test

Changelog :-

Test build 6 :

Stability (thats all i can do [emoji14])

Test Build 7 Updated : improve charging and limit heat issue... [emoji6]

Test Build 8 Updated : improve stability... [emoji6]

Magisk Module V2 Added : try to fix heat issue and improve charging...

Magisk Module V3 Addee

Presenting you magisk module [emoji14][emoji14]

Hit Thanks Button

And if You want me a Cup Of Coffee

Donate Here :- Donate Here By PayPal

Download Link :-

Google Drive Link For Miui Roms

Link For Miui Roms V2

For Custom Roms Test Build 4

For Custom Roms Test Build 7

For Custom Roms Test Build 8

Back to Stock

QC-3.0 Magisk Module(Need Tester)

QC-3.0 Magisk Module V2

QC-3.0 Magisk Module V3
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] bekcicandrej:
Flashed on crdroid difred, flashed successfully. Will see if any change
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] mannequiin:
This should not be in themes and mods?
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] parthavluv:
Maybe or maybe not... But it looks good here [emoji16][emoji16][emoji16][emoji16]

From my Redmi 4X using Tapatalk VIP
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] OMkaRRasaL:
any change?
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] parthavluv:
You can use it too i have provided restore zip too

So feel free to use this mod

From my Redmi 4X using Tapatalk VIP
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] bekcicandrej:
1850 mA instead of 1600mA
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] OMkaRRasaL:
That's quite nice. I've seen my phone charging more than 1700-1800mA without patching it.

P. S. I use QuickCharge 3.0 although I know it would've been charging with 2.0 technology
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] Muthu_IN:
Will it work on MIUI 9.5 I don't have quick charge adapter still will. iget any advantage?
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] parthavluv:
Yeah it will work without quick charger adapter

And work perfect in every miui rom [emoji6]

Install and check current flow in ampere app

From my Redmi 4X using Tapatalk VIP
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] parthavluv:
I've changed the mod link this one is latest

So have a try... it will work for you and give you more then 2000ma

From my Redmi 4X using Tapatalk VIP
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] Kiran02:
Bro Plz Make Only Quick Charge Mod

GPS,Ads,etc

Gaming

Some Features Remove Next Mod
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] sheshuvadrevu:
Is it only for MIUI?
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] Kiran02:
Only Miui Roms Supported
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] parthavluv:
Not sure only for miui but you can check in custom too...

But first take a backup of your current thermal-engine.conf file

Then install this mod and check current flow in ampere app

From my Redmi 4X using Tapatalk VIP
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] parthavluv:
Ohk i will

From my Redmi 4X using Tapatalk VIP
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] Kuchayhilal:
Does it work on custom ROMs ?
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] parthavluv:
Maybe... You can test it...

And dont worry about any messup

I provided Back-To-Stock zip file too

From my Redmi 4X using Tapatalk VIP
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] Kuchayhilal:
Yeah i'll test it later, my charging speed sucks; can u make any working fast charging mod for custom ROMs ?
[Xiaomi Redmi 3s ROMs, Kernels, Recoveries, & Other] parthavluv:
First check this one bro...

If it doesn't work for uhh then i will make another build...

From my Redmi 4X using Tapatalk VIP
[Galaxy S 4 Mini General] Mlartic2013:
Good day everyone,

For the past 10 years, I owned many smartphones but I just returned to the Galaxy S4 Mini i9195i because I like its weight and size.

Since it's an old phone...and many Android versions have been out, which version is best for this Galaxy S4 Plus ?

Which version run with less lags ?

And should I update from the original version (new phone) to this last in one shot ?

Best regards,
[Galaxy S 4 Mini General] thorium231:
IMO the nightly builds Lineage 14.1 are currently the best (and really good) option: https://xdaforums.com/galaxy-s4-mini/orig-development/rom-cyanogenmod-14-1-t3522169
[Galaxy S 4 Mini General] joeandjoe:
Just returned to 14.1 nightlies from 15.1 and I would also say 14.1 is best.
[Galaxy S 4 Mini General] k9r4n14:
AICP ran amazingly well on my one too! Not sure where their website is, but I'm sure if you search up AICP Rooting or Custom ROM, it should come up.
[Galaxy S 4 Mini General] ptr1968:
If you use gps/navigation a lot then cm13 is the best i find, compared with oreo/nougat are slow on gps lock due to no glonass fix.
[Galaxy S 4 Mini General] GGK_01:
My opinion...LineageOS 14.1 nightly works really good...also GPS/navigatin works fine...just missing flip to silent mode...
[HTC One A9] JohnVo:
Hi everyone,

My A9 originally has CID TELST001 and MID 2PQ910000 (S-off and unlocked bootloader). I followed this guide (https://xdaforums.com/one-a9/development/s-off-convert-to-htc-usa-unlocked-1-12-t3271861) to convert it to US model (CID: BS_US001 and MID: 2PQ912000)

I stopped at step 3, just go back to stock with RUU which I downloaded from HTC website (and I did lock bootloader when running RUU while keeping CID and MID as US model). However, the red text regarding to development purpose keeps appearing when I reboot the phone. Is it related to s-off status? From what I have read so far, as long as the kernel is stock then the red message should be gone. However, in my case, restoring via stock RUU does not erase the red message :confused:

Would someone please let me know if I did something wrong with RUU process? Cheers :D
[HTC One A9] Wonders_Never_Cease:
As long as kernel,system and recovery is all stock the message should disappear... There is no reason to relock bootloader if s-off when running an ruu. Did you revert back to telstra ruu or use the unlocked developer ruu? Possible if ran ruu for telstra and kept unlocked cid/mid,maybe cause of your issue... Not sure though... Could be wrong...