yashsingh1/xdaforums huggingface dataset:
[Amazfit] chrisrozon:
Due to rapidly aging eyes, I'm having a lot of trouble reading notifications on the Bip without digging out my reading glasses - which isn't really convenient when walking around! I'm a few years away from needing bifocals, so I need a fix in the meanwhile :)

I've updated the system font a few times, but those are minor adjustments when what I really need is the text to be 2 or 3 times bigger! After changing the watchface to a black hands on white background and seeing a huge increase in readability at a glance, I'd like to try to same with notifications. Anyone have any promising leads on this I can chase after?
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] rober788:
You can install February update later this mounth ??
[Xiaomi Mi A2 / 6X Guides, News, & Discussion] Funk Wizard:
This thread does not hold any value of discussion. Please don't create redundant threads and help us keep the forums clean.

Thank you for your cooperation.

Thread Closed.

Funk

Forum Moderator
[P3600 ROM Development] ervius:
Finally I got it, me and udK!!!!
[P3600 ROM Development] icest0rm:
ok...let's begin waiting :D
[P3600 ROM Development] FInixNOver:
Niiice!!!

Thank you both for this.;)
[P3600 ROM Development] luigi.ing:
Hi, Ervius

I already inserted him two weeks ago.

Good!!!!!!!!!!!!!!

By BY BY
[P3600 ROM Development] icest0rm:
hi Luigi,

unfortunately your rom is free only for payers, so we couldn't check it ;)
[P3600 ROM Development] cavallino:
and repass articles and english grammar! BY BY BY
[Android Q&A, Help & Troubleshooting] Xrev Undetect:
NEED HELP
[Galaxy Note 3 Q&A, Help & Troubleshooting] elerouxx:
Hi. I am aware there is no such thing as The Best Rom for model X. I have installed ROMS before in other smartphones and I've always admired all the effort put on every rom version by their authors.

I'm just asking for personal opinions / experiencies regarding the latest ROMs released for the Galaxy Note 3 (N9005) to help me decide according to the goals below.

I know there is a lot of information in every ROM thread and I have read many of them, but the particular difference with the Notes against other smartphones is the S-pen functionallity. Many roms don't mention the S-pen so It's a little difficult to tell which ones really suport these features, which are important to me.

In my case, I would be very happy if:

- The ROM has pen support (the reason I have the Galaxy Note).

- I think the ideal ROM would be close to the Note line, say, a port of N7, N8 or so.

- Battery Life is good (and/or settings can be tweaked to have better batery. life than stock Lollipop 5.0, if possible.)

- I really like latest Android versions, the newer the better (Android 9), but I can live with an older one (6, 7, 8...) if it's really more stable, fast, or battery life is better.

I apologize to those that don't like this kind of posts. Just a short story: I owned a Note 3 Neo Duos (N7502) for some years, and I was really frustrated because there is just no development, no way to update it from kitkat. And I tried hard. I think I read every possible thread about the N3n duos here and outside. Many apps stopped working with Kitkat, and most notably MICROSOFT ONENOTE, one of the apps I use the most. Plus the battery was getting bad.

I ended up selling a bunch of used equipment last month and decided to give up and say farewell the N7502 for good so I sold it cheap.

To my surprise, two weeks later I was selling a (very) old notebook and out of nothing a buyer offered me a Galaxy Note 3 N9005 as a trade!

I gladly accepted and now I am very happy. The phone is in excellent condition, including the battery.

Now I see myself in the opposite situation. I had so little information and no ROM options for the N7502 and now I have so much and so many for the N9005 it's being very hard to decide. I've been reading the ROM threads for a week or so and I seem to have more doubts than answers.

So, I would like to count with the opinions or impressions of who has already tried some of the custom ROMS.

Thank you!

-E
[Xiaomi Poco F1 Questions & Answers] Udaya.kr:
Even though 4g+ is giving good coverage my ping goes very high while playing online games. Where my OnePlus 3 give very good ping.

Please help me.

Thanks in advance.
[Xiaomi Poco F1 Questions & Answers] Hectorify:
Hey bro i am aslo facing the same issue pls share me if u found a solution
[Xiaomi Poco F1 Questions & Answers] Hunteres:
Type

*#*#4636"*"* and choose what ever network suits...note its reset after reboot. I am using it all the time.

Enjoy
[General Topics] $_Vladislav:
[img="Front"]https://xdaforums.com/attachment.php?attachmentid=4699845&stc=1&d=1549346815[/img][IMG="Back"]https://xdaforums.com/attachment.php?attachmentid=4699846&stc=1&d=1549347048[/IMG]​

Versions: SM-J260M/DS (LATIN); SM-J260Y/DS (Philippines); SM-J260G/DS (India); SM-J260F/DS (CIS)

*CIS - Union of Independent States (Russia, Kazakhstan, Tajikistan, Uzbekistan, Armenia, Belarus, Azerbaijan, Kyrgyzstan, Moldova)

NETWORK

Technology GSM / HSPA / LTE

2G bands GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2

3G bands HSDPA 850 / 900 / 2100 - J260Y/DS, J260G/DS, J260F/DS

HSDPA 850 / 900 / 1700(AWS) / 1900 / 2100 - J260M/DS

4G bands LTE band 2100, 1800, 850, 2600, 900, 700, 2600, 2300, 2500 - J260Y/DS,

LTE band 2100, 1900, 1800, 1700/2100, 850, 2600, 900, 700, 700, 700 - J260M/DS

LTE band 2100, 1800, 850, 2600, 900, 800 - J260G/DS

LTE band 800, 850, 900, 1800, 2100, 2300, 2500, 2600 - J260F/DS

Speed HSPA 42.2/5.76 Mbps, LTE Cat4 150/50 Mbps

GPRS Yes

EDGE Yes

LAUNCH

Announced 2018, August

Status Available. Released 2018, August

BODY

Dimensions 143.4 x 72.1 x 8.9 mm (5.65 x 2.84 x 0.35 in)

Weight 154 g (5.43 oz)

SIM Dual SIM (Micro-SIM, dual stand-by)

DISPLAY

Type PLS TFT LCD capacitive touchscreen, 16M colors

Size 5.0 inches, 68.9 cm2*(~66.7% screen-to-body ratio)

Resolution 540 x 960 pixels, 16:9 ratio (~220 ppi density)

Protection Corning Gorilla Glass (unspecified version)

PLATFORM

OS Android 8.1 Oreo (Go edition)

Chipset Exynos 7570 Quad (14 nm)

CPU Quad-core 1.4 GHz Cortex-A53

GPU Mali-T720

MEMORY

Card slot microSD, up to 256 GB (dedicated slot)

Internal 8 GB, 1 GB RAM

MAIN CAMERA

Single 8 MP, AF, f/2.2

Features LED flash, HDR, panorama

Video 1080p@30fps

SELFIE CAMERA

Single 5 MP, f/2.2

SOUND

Loudspeaker Yes

3.5mm jack Yes

COMMUNICATIONS

WLAN Wi-Fi 802.11 b/g/n, Wi-Fi Direct, hotspot

Bluetooth 4.2, A2DP

GPS Yes, with A-GPS, GLONASS, BDS

Radio FM radio

USB microUSB 2.0, USB On-The-Go

FEATURES

Sensors Accelerometer, proximity

Messaging SMS(threaded view), MMS, Email, Push Email, IM

Browser HTML

BATTERY

Removable Li-Ion 2600 mAh battery

MISC

Colors Black, Gold, Lavender

SAR 0.61 W/kg (head) * * 0.61 W/kg (body) * *

SAR EU 1.39 W/kg (body) * *

Price About 100 EUR
[General Topics] alameery13:
(ذ)
[General Topics] galaxys:
It's a February 2019 2 Year old thread...
[General Topics] Vanxploit:
How to fix safetynet in my device j260g ?
[General Topics] EyzTOP01.L:
This thread would be almost unattended, for me it's a fresh start, interested on building the TWRP recovery project for SM-J260M ( The common Latin-American variant I think, 2018 version) and have seen your posted trees on GitHub, given the fact that this user: https://github.com/Vladislav4KZ belongs you. In the case that you can advice me a little nuances for this device --being a noobie on this matter-- please are you able to describe how you grasped the kernel tree? I´ve picked a kernel tree from: https://github.com/MT6797/kernel-3.18 . Due to I've looked on my phone's settings that it's Linux kernel version was 3.18.14 (See Attachment below) .

About the vendor tree, which one have you used? I'm currently picking this universal exynos7570 Android8.1 vendor tree from: https://github.com/OpenExynos/android_vendor_samsung_slsi_exynos7570/tree/android-8.1.0_r1 .

The device-tree, I've leveraged from SebaUbuntu's device tree generator: https://github.com/twrpdtgen/twrpdtgen . After that, I've chosed the repository from https://android.googlesource.com/platform/build/+/refs/tags/android-8.1.0_r51 to perform the build. I've got some errors, specially when compiling the kernel, I've worked-around the common erros that were most related to an outdated programming language: python2 on files that were being built with python3.

When I've finalized clearing that files, they were few, I've decided to take the kernel and vendor tree out of the build. So i've chosen the omni_device_tree that's for default created when creating the google-Android building repo and syncing it. Got a successful recovery image, until I've tested it and got the problem of the classical blinking-screen when I've booted the device at recovery.

🗨🗨 Questions:

⭕How you grasped the kernel-tree?

⭕Which vendor-tree have you used?

⭕How can I compile the kernel adequately for this model that is a little bit different than your: SM-J260F ?

⭕Have you compiled a recovery image for your device? If yes, were you succesful? What problems you've faced as the main rocks hindering the build process's completion? What you changed, in case you've flashed it but got a blinking screen?
[General Topics] notnoelchannel:
Hi, I just built TWRP 3.6.2-9 for your device. Can you test it? Here's the flashable file
[General Topics] EyzTOP01.L:
Thank you, first sucessful TWRP image that past beyond the blinking screen, in fact it booted-up smoothly, unfortunately it's not recognizing the touchscreen and that limits it's ability to test and point more flags about it. What have happened when I've tried to reboot to the system is that it didn't worked, when an odd-recovery image is flashed on this device model seemingly it doesn't return to normality unless you're able to do that from the recovery itself i.e not forcing it by withdrawing the battery or pressing button combinations for restarting; I've fixed that issue by flashing the stock recovery back to the device via Odin ( the only resource for rescuing this device) and worked up to the normal state, no problems after that. Here I show you below, sorry for my phone's state, it has suffered a fall that slapped it's external surface, fortunately hardware still intact, and relative to it's touch sensitivity it works seamlessly as you can note in the next attachment.

There for that particular problem, by changing or adding some flags on your BoardConfig.mk file that lies on the device tree folder you can fix it. It's mentioned on other XDA threads and some TWRP-compiling channels found youtube. I would be pretty grateful in case you show point me out the device, kernel and vendor blobs that you've used for compiling the recovery. As I've previously stated: the blobs I've used led me to the blinking screen failure and I am figuring out about what I've made wrong, I'm a beginner and would appreciate the epiphany that you'd cater me in case you teach me about the code and what you've made, particularly on the blob trees. Thank you very much in advance.
[General Topics] notnoelchannel:
I compiled TWRP on android-8.1 branch too. That might be the solve of the no touch problem.

About compiling, you'll just have to get these:

Minimal TWRP manifest twrp-8.1 branch here

And a device tree from here

In the device tree, we already have a prebuilt kernel. So we don't need any kernel source. Same for vendor.

I'll try to fix touch by building on higher branches.
[General Topics] notnoelchannel:
Here's a smaller PORTED twrp version:
[General Topics] EyzTOP01.L:
Same issue with the touchscreen, can't swipe to unlock, the only noticeable change was the color and of course it's smaller size. Have you tried adding some flags at the BoardConfig.mk? Could you please try developing with the 9.0 Branch, I only have the 8.1 one and low space on disk. Thanks
[General Topics] EyzTOP01.L:
Sorry, Sir, excuse me for asking advice there, but I got stuck and found no way to get out of this issue when compiling the recovery-image fror the J260M: on my build directory: bionic/libc/bionic/grp_pwd.cpp . This file deploys a bunch of errors that are related with the C++ language, such as = bionic/libc/bionic/grp_pwd.cpp:137:46: error: unknown type name 'android_id_info' or undeclared identifier on some other lines. Finally outputing the following hurdle for continuing the process:

fatal error: too many errors emitted, stopping now [-ferror-limit=] 20 errors generated.​

What could I do, it's my mistake or it's one from the android-security-8.1.0_r81 branch code? ( which was the one I've initialized and synced the repo for building). What have you made to compile the image without those errors?. No matter if I build with/without kernel source this error always stucks my progress.
[General Topics] notnoelchannel:
Build with the device tree and manifest i linked
[General Topics] EyzTOP01.L:
No matter what I've tried, followed your steps closely, even switched to the 9.0 branch but it seems to not work up due to so many erros on the code of the whole android source. What would have I messed up for the Building Platform to deploy so many issues and hence leaving me unsuccesful from completing the recoveryimage compilation :( . How can I work this? If i haven't wrote the android source code...
[General Topics] Noobmaster205:
any updates?
[General Topics] Parthib:
The touch driver doesnt load when you are in recovery mode as you can see here - synaptics_i2c_rmi.c#probe. You should try installing the recovery image in boot partition and see if it works.

If it works then rebuild the kernel with that check disabled, so it works while in recovery mode.
[General Topics] EyzTOP01.L:
Thank you for your reply, a few months ago I managed to build a TWRP with almost all partitions, except "cpefs" partition, working, I've used the kernel source for it, however I've excluded on the main kernel makefile manifest the following files which I've ported from other exynos7570 devices such as the J5 Prime: exynos7570_acpm_draminit_s.fw ; exynos7570_acpm_pedo.fw . By that I've got this result, I'm going to build what you've suggested to look if I can make now the touchscreen driver work, despite that, if you use OTG cable for connecting a mouse, then you can confirm that on this recovery image all of the partition except the one I mentioned above get mounted.

Flash it via Odin.

Wasn't easy, nor impossible. This prototype will hopefully become the effective one.
[General Topics] notnoelchannel:
good luck for getting twrp working for this device, if you are tired of building, i can build freely :D
[General Topics] notnoelchannel:
Okay, i'll try to build the kernel with patched touchscreen driver, wish me luck
[General Topics] notnoelchannel:
Sorry for disappearing for a long time, now i'm really building the kernel

Edit: it failed
[General Topics] Skorpion96:
just tried to port twrp with Hovatek Samsung Auto TWRP recovery Porter 1.1, give it a try:https://www.mediafire.com/file/92ri...J260YDS-A9-Test-by-autotwrprecporter.img/file

Another thing that can be tried is to take fstab from this build and merge it with old builds and so twrp should be able to mount partitions, this if hovatek build does not boot
[OnePlus 6 Accessories] radeonxt:
I couldn't find one specifically for our oneplus 6's dash charger but found one for VOOC charger which is used on oppo f9 which can also be used to rapid/dash charge our oneplus 6.

http://www.chongdiantou.com/wp/archives/1228.html

https://archive.fo/ovQY2
[OnePlus 6 Accessories] KJYap:
Nice sharing, didnt know what all it was even though i know chinese haha. It would be nice if can share how dash charging works
[Huawei P20 Questions & Answers] MomentaryPixels:
Hey guys, when watching videos on webpages in full screen, I often see this icon appear on the top right corner.

View attachment 4699851

Any of you guys know what it is? Sometimes it's not there so I'm just morbidly curious. :D
[Huawei P20 Questions & Answers] hwandroid:
That might be some app causing or extension that you have installed on your device.
[Huawei P20 Questions & Answers] MomentaryPixels:
Not sure. It was there since day one and it's present in Dolphin Browser and Chrome.
[Huawei P20 Questions & Answers] Rachid17:
It's for those who have a notch. You have to tap it, and it will shift the video, so the notch won't disturb you when watching the video.
[Chromebooks] GFeldmen:
im a producer and i recently recieved a chromebook from my brother, is there any way to get l studio 12 on this thing?
[LineageOS Questions & Answers] flixman:
Yesterday I updated my Nexus 5x Lineage OS. As sometimes happens, the first reboot went through TWRP doing nothing. After rebooting into the system and launching the update installation again, this time TWRP applied the update (it went through the usual storage decryption and applying the system image). When LineageOS booted up, after entering the PIN, it stayed for one hour displaying the lineage OS boot animation, time after which I rebooted the phone.

Since then: when I start the phone it just goes to the "google" display, then to the LineageOS boot animation, and then reboots... indefinitely. Is there anything I can do to recover use of my phone?

Thank you everybody :-/
[Xiaomi Mi 8 Lite ROMs, Kernels, Recoveries, & Othe] Kaconk:
reserved

---------- Post added at 02:33 PM ---------- Previous post was at 02:31 PM ----------

where can i download the latest build? thx
[Xiaomi Mi 8 Lite ROMs, Kernels, Recoveries, & Othe] rsyhan:
Download Link:

https://sourceforge.net/projects/havoc-os/files/platina/
[Xiaomi Mi 8 Lite ROMs, Kernels, Recoveries, & Othe] nosakaryota:
If the function of enabling Camera2 API needs magisk or root?

I press it many times to turn on it, but no respond... and I nearly can not open Mi Tweaks again until reboot the phone.
[Xiaomi Mi 8 Lite ROMs, Kernels, Recoveries, & Othe] rsyhan:
Thanks for reporting that bug.I knew this bug.So just wait my next build bro:)
[Xiaomi Mi 8 Lite ROMs, Kernels, Recoveries, & Othe] hlcm151:
Volume rocker wake not working

Anyone help ???

Edited : it's working after i enabled music control
[Xiaomi Mi 8 Lite ROMs, Kernels, Recoveries, & Othe] Kaconk:
the bug found so far :

-boot up take little longer than any other rom

-force close in battery info

tho everything is smooth, thank anyway mate for the rom :D:good:
[Xiaomi Mi 8 Lite ROMs, Kernels, Recoveries, & Othe] umutcezarap:
i Really like the rom. I couldnt find face recognition. Also i wanna say the customize everything is really good. Thank you!
[Xiaomi Mi 8 Lite ROMs, Kernels, Recoveries, & Othe] Kaconk:
Every rom has face unlock, it depend on gapps u use, try micro
[Xiaomi Mi 8 Lite ROMs, Kernels, Recoveries, & Othe] umutcezarap:
Actually I wasn't talking about Google's Trusted Face. I was talking about Miui Lift Up Auto Unlock Face Recognition. I thing just stock miui rom has this feature
[Xiaomi Mi 8 Lite ROMs, Kernels, Recoveries, & Othe] PotiU:
Notifications

The rom is perfect, but sometimes i dont receive whatsapp notifications, good job!!
[Xiaomi Mi 8 Lite ROMs, Kernels, Recoveries, & Othe] lukemorales:
Audio through USB not working (haven't been able to test it with the adapter, but my car player didn't received the audio as it did with MIUI, the audio kept playing on the phone speakers)
[Xiaomi Mi 8 Lite ROMs, Kernels, Recoveries, & Othe] intuition739:
New build shows info about not matching vendor image
[Xiaomi Mi 8 Lite ROMs, Kernels, Recoveries, & Othe] RenãNunes:
Front camera stopped working on latest release, anyone with the same bug?
[Xiaomi Mi 8 Lite ROMs, Kernels, Recoveries, & Othe] Sovietano1:
Hello, constantly runs out of cellular signal, the funny thing is that it is only with a company (Telcel Mexico) is corrected by dialing, but when someone calls me, the call does not enter. How to solve it ?
[Xiaomi Mi 8 Lite ROMs, Kernels, Recoveries, & Othe] trfcygvbhjkjno:
shows info about not matching vendor image and front camera stop working

plz fix

---------- Post added at 02:38 AM ---------- Previous post was at 02:17 AM ----------

me dude
[Xiaomi Mi 8 Lite ROMs, Kernels, Recoveries, & Othe] trfcygvbhjkjno:
I got it.

When you enable the Camera2 API in Settings, you front camera will died

and now you can use gcam but only main camera

Close it and reboot , you front camera will back

but you cant open gcam anymore
[Xiaomi Mi 8 Lite ROMs, Kernels, Recoveries, & Othe] RenãNunes:
Exactly the same here.
[Xiaomi Mi 8 Lite ROMs, Kernels, Recoveries, & Othe] blikered:
Thanks for this ROM. It's the best one available for the Mi 8 Lite, imo. It's also the only one that allows me to install the 'Amazon Shopping' app.

Very stable. I've not experienced any issues.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] alissonlauffer:
This is ViperOS​

Disclaimer:

We are not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.

"This is a user friendly thread. All feature requests will be heard and considered. I am not against anything that doesn't stray too far away from the original idea of the ROM! Helping one another is also encouraged! Please be respectful and you will always be treated the same way, we are all here for a good experience."

About:

We are a Brazilian team, ViperOS aims to bring stability and useful features. If you are looking for a stable ROM with true tested features, minimal bugs and no Lineage bloatwares, then this is the place to be.

Features:

Added OTA Services updater

Statusbar

QS settings

Clock statusbar settings

Battery style

Carrier label

Network traffic

VoLTE icon toggle

4G/LTE icon toggle

VPN toggle

Rounded corner settings

QS for Reboot/Recovery

QS Screenshot full and partial

Recents

Style recents AOSP and QuickStep

Button clear and Membar for recents AOSP

Lockscreen

Face auto unlock

Fingerprint authentication vibration

WheaterClient

Battery info Charging

Ambient music ticker with new style

System

Color engine

theme QS style

Styles switch

Styles clock lockscreen

Buttons and navbar settings

LED battery Charging

LED notifications colors

Power Menu advanced

Fonts packages

Pulse Navbar

OP Gestures

Thermal Controller support

VPapers new

Many other customizations, install and take a look

Download:

Official website: Download

GApps:

OpenGapps: OpenGApps

​

Credits & Thanks:

All ViperOS Team

LineageOS team

And all other open source Devs/Teams I may have missed!
​

Other links

Telegram channel

Telegram chat discussion

Wallpapers channel

ROM source

Devices source
​

​
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] guineks:
A big thanks to devolper.

The Rom is Very smoth and fast

Thanks from Brazil
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] rom3osv8:
viper settings need translations!
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] alissonlauffer:
To which language?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] rom3osv8:
Spanish...united states
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] pierrezaoo:
parceiro, vc teve problema com o sinal de wifi? se sim, resolveu com essa rom? como tá o consumo da bateria?

dude, did u have problem with wifi signal? if yes, fixed with this rom? How is the battery consumption?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] rom3osv8:
And i have a issue(stuck) when i reboot the system in "initializing android"
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] rom3osv8:
How i know if this ROM is a stable build?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] alissonlauffer:
Version 6.1 available! Download It from here: https://sourceforge.net/projects/vi...r-sanders-20190207-v6.1-OFFICIAL.zip/download

Changelog: https://raw.githubusercontent.com/Viper-Devices/official_devices/master/sanders/changelog.txt

(The update will be available on ViperOS website soon...)
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] rom3osv8:
How to update ?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] alissonlauffer:
Simply download it from the SourceForge link and flash it over the old version. (But I always recommend a clean flash)
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] alissonlauffer:
And starting from this version, the ROM will have a OTA app (see the screenshot below):