yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV General] saquib:
Could all UK T-mobile users provde feedback on how they are finding the reception on the T-mobile network? As an ex-Kaiser user, I'm finding reception is quite poor, the Diamond usually showing a couple of bars less than the Kaiser. Additionally, HSDPA performance is poor and intermittent.
[Touch Diamond, MDA Compact IV General] aidanbree:
Mine shipped with 25.03 and I am not impressed with the signal or data at all. I am finding it is dropping calls where my Vario II was fine.

The battery usage is quite high too so I am recharging at the moment and I think I will take the radio to 25.05 tonight....Not sure whether I should try another OS ROM.. seems too many to choose at the moment

Cheers

Aidan
[Touch Diamond, MDA Compact IV General] kidd78:
I have tried all of them and now on 25.11 which seems to hold a 3g signal longer but not very strong (2bars ish) better than 25.06 but not a huge difference. I am prob thinking of moving back to 25.06 because it got more better signal for gps purposes, as i said not a huge difference in phone signal.

In all honesty Im what dissappointed i couldnt get a strong 3g signal on motorway. Oh well just wait for the next new radio to test :)
[Realme X2 Pro Questions & Answers] Ak's World:
Any one please guide me proper way to flash stock ROM and lock bootloader over custom ROM(Mokee OS) using TWRP Recovery... Actually I flashed this Custom ROM over Realme UI and I am encountering so many bugs now that's why I wanna go back to Stock ROM without any bootloop and bricking issues....
[Samsung Galaxy S 5 Unified Development] IKGapirov:
Bootleggers ROM is an aftermarket firmware based on AOSP with some patches and fixes from LineageOS and various other projects. The idea is to bring custom features and some of the most useful apps on your device, with the goal of Making you feel like 家.

With an almost stable source, this ROM is also packed with some custom wallpapers (avaliable on ShishuWalls), ringtones, fonts, and themes to bring to your device into a more fresh look and give you always a good experience.

Also, we got our Telegram Group to talk about the ROM, share some love, ideas or even have fun with us!

Some of the features that are included on this ROM are:

* QS Rows and Colums
* Volume Keys: Wake up, skip tracks and switch according to rotation
* Show song album cover, visualizer and battery info on Lockscreen
* Power Menu Items
* Battery LED light settings
* Suspend Actions: Make your device disable GPS and switch to 2G when you're not using it
* AppOps: Manage your apps permissions in an advanced way
* Recent Styles: Dig the new Pie Quickstep recents, go back to the classic layout or use the Android Go layout
* Network icons: Show or hide the cross, switch between 4G or LTE, use the classic icon layout before Pie or toggle roaming icon too!

Also, you can check a full list of Features available here.

Thanks to this people, this ROM could be possible, so, i have to give a big thanks to:

* Shishu (For being there)
* Ground Zero ROMs Team
* AOSPExtended
* ABC ROMs
* NitrogenOS
* AICP
* DirtyUnicorns
* Lukas Koller (Camera Roll dev)
* fxckingdeathwish (for the amazing photos for wallpaper/headers)
* OmniROM
* CyanogenMod/LineageOS
* PixelExperience
* PureNexus
* merothh
* Resurrection Remix
* AOSiP
* CrDroid
* CypherOS
* PureKat
* theimpulson
* MatiHalperin
* Project Xtended
* Pixeldust Project
* AquariOS
* Alejandro Ponce (Quetzal/Calypso dev)
* PixysOS
* The Memedo Testers team
* Every maintainer who decided to give our project a shot
* You for your interest on our project

Also if you got some ideas,bug fixes, stability improvements or want to help to support features for your device, you can do it by sending a Pull request on Bootleggers Github (check downloads and sources part) or tell us on our Telegram group (Check about us section), will be really appreciated. Got some questions about some terms we use? Check our FAQ or feel free to ask us. We appreciate your feedback and help.

SOURCEFORGE

ANDROIDFILEHOST

OPENGAPPS

Device Sources:

Device tree

Klte-common tree

Kernel tree

Vendor tree

ROM Sources

Bootleggers Github

ROM Specific bugs:

* You tell me

Device-Specific bugs:

* You tell me

Screenshots
​

Thanks to:

Haggertk (LineageOS team)

ElDainosor (Bootleggers ROM Team)

Dinosnore (Bootleggers ROM Team)

Khalvat

Jprimero15

Afaneh92

If you like my work, you can support me:D

SGS 5 Unified Development Group on Telegram

XDA:DevDB Information

Bootleggers ROM 5.1, for the Samsung Galaxy S5

Contributors

IKGapirov

Source Code: https://github.com/BootleggersROM

ROM OS Version: 10.x Queue

ROM Kernel: Linux 3.4.x

Version Information

Status: Beta

Created 2020-04-29

Last Updated 2020-07-19
[Samsung Galaxy S 5 Unified Development] Drhedphuk:
Thank you mate. ?
[Samsung Galaxy S 5 Unified Development] MauricioGD:
Hello, the problem is that, on many occasions, the mobile freezes and tells me a UI system error, which has stopped (KLTE)
[Samsung Galaxy S 5 Unified Development] IKGapirov:
Please ensure that you are running stock ROM and kernel. No Xposed or other hacky crap. Create a logcat.
[Samsung Galaxy S 5 Unified Development] Noob9496:
Stable??
[Samsung Galaxy S 5 Unified Development] pmduper:
Bugs? What exactly is the problem?

What variant S5 do you own?

Gapps?

Kernel?

Version twrp?

Dirty or clean install?

Formated?

Your list of bugs?

Please respect the developer and help him with lots of information and log/s :svetius:
[Samsung Galaxy S 5 Unified Development] vlad3647:
really good rom but my phone get to hot and the battery drain pretty fast
[Samsung Galaxy S 5 Unified Development] Noob9496:
Try install newest tuned kernel. On lineage OS 16, phone i always cold.
[Samsung Galaxy S 5 Unified Development] vlad3647:
Thanks bro
[Samsung Galaxy S 5 Unified Development] SnowOwl20:
how is batteyr life,

screen flickering in it?

can mixer_paths be modified from twrp without failure?

I hate lineagos 16 as its glitchy
[Samsung Galaxy S 5 Unified Development] SnowOwl20:
good rom,

something that would be cool would be a power opition (power saving efficiency balanced gaming etc.)
[Samsung Galaxy S 5 Unified Development] reza_khof:
Sim card sliders don't work for both of them.

How can reduce hw keys light? And active battery percentage
[Samsung Galaxy S 5 Unified Development] IKGapirov:
UPDATE BUILD

Changelog

Bootleggers:

* Source rebase from may security patch

* And maybe more
[Samsung Galaxy S 5 Unified Development] mixyzptlik:
Sometimes UI freezes when pulling down status bar
[Samsung Galaxy S 5 Unified Development] SnowOwl20:
It's a problem I also get, better going back to android 9 till android 10 is perfectly built by a developer
[Samsung Galaxy S 5 Unified Development] IKGapirov:
UPDATE BUILD

[B]Devices: [/B]
* Fixed some known bugs

[B]Bootleggers:[/B]
* July SP
* Small improvements
* Added some more QS tiles
* New shishuwalls app
* Add launch music player on headset connect(wired headphones only)
* More QS tiles
* Show seconds in clock
[Samsung Galaxy S 5 Unified Development] EuK_V:
Disable 2nd sim on klteduos

Hi, is it possible to disable second sim card by editing /system/build.prop?

Does this way work on this rom?

Thanks in advance!
[Samsung Galaxy S 5 Unified Development] dametsuna:
I've noticed that sometimes, after unlocking the screen, the brightness is too low and I have to move the slider for a bit so it becomes normal. Is there any "fix" for this? This "bug" is quite annoying, it only happens after unlocking it, I think it may be related to ambient display? Anyone faced it before? It happens with adaptive brightness on or off.
[Samsung Galaxy S 5 Unified Development] DhiaXDA:
you may try a custom kernel... it should fix that
[Samsung Galaxy S 5 Unified Development] dametsuna:
Thanks, it works normal with Tuned kernel!
[Samsung Galaxy S 5 Unified Development] Anewkine:
Hi,

Awesome work :)

Thanks for our beloved Klte

Just to find out, will you do an update? 😉
[Samsung Galaxy S 5 Unified Development] IKGapirov:
Hi!

Soon... :cowboy:
[Samsung Galaxy S 5 Unified Development] Anewkine:
Hi,

Too awesome, given the news on Telegram, I'm looking forward to testing your work

Thanks for keeping up to date our beloved S5.
[Samsung Galaxy S 5 Unified Development] EuK_V:
@IKGapirov

Hi, in bootleggers rom 4 (android pie) there was an option to record calls directly from the Dialer app (pretty cool feature):

Why there's no such option in 5.1?

Thanks in advance.
[Samsung Galaxy S 5 Unified Development] Anewkine:
Hi all

I see on the Bootleg telegram channel that the work on Android 11 is progressing fast. 👍

I hope that our beloved S5 Klte will be there and that we can enjoy this great ROM...

If you ever need testers, I'm up and running. 😉

Again thanks for the 5.1 that works like a charm.

See you soon and KEEP BootLeg
[Samsung Galaxy S 5 Unified Development] HomieEnzo:
There will be no more updates for Q? :(

I will love the adding of native rounded screen corners feature, and the other features in the 5.2.

Also I could not find the recent apps changer feature (from oreo style,to go style...etc).
[Samsung Galaxy S 5 Unified Development] HomieEnzo:
The rounded corner feature and recent apps style feature is present on this ROM?
[Samsung Galaxy S 5 Unified Development] JuninhoBMX:
thanks for this rom i in klteduos <3
[Samsung Galaxy S 5 Unified Development] Anewkine:
Hi @IKGapirov

I saw on Telegram Channel Bootleggers that the Alpha 5.8 build is out. 🤪

Are you going to work on it?

This is just a question and not a build request. 😉

For me it's still the best ROM I've tested on my good old GS5 and that thanks to you and the Bootleggers team !!! 🤪
[Samsung Galaxy S 5 Unified Development] methythebozo:
The hardware key backlight change setting is missing in the rom. I'm stuck with the keys lighting up whenever I don't want them to be lit up with no way to change that
[Samsung Galaxy S 5 Unified Development] methythebozo:
No USB wakeup toggle either. Other than that, pretty good rom.
[Samsung Galaxy S 5 Unified Development] IKGapirov:
Once upon a time there was an build....
[Samsung Galaxy S 5 Unified Development] vlad3647:
I still using bootleggers
[Amazfit] Malli2602:
Hi [MENTION=9350973]All[/MENTION]

I have some issues with my Amazfit bip.

First some informations:

Firmware: 1.1.6.48

A-GPS: up to date

Now to my problems:

1. If I start a workout like Outdoor running my amazfit ne approx 7-10 min to get GPS connection. And I'm not inside my Appartement.

2. I have no Idea what I have to configure to use Amazfit original app and Notify& Fitness for Amazfit together.

I like Notify a lot but I think that the Firmware Update Process from the Original App is just better.

I also don't want the permanent Notifications from both apps in notification bar.

Can you help me please?

Best regards

Stephan
[Amazfit] ebsebs:
N & F can be used together with MiFit or by itself by pairing the BIP with it.

While I prefer N & F for pretty much everything and use it without MiFit, there is one problem - N & F can't update the AGPS, so you would have to use MiFit for that.

However, I also don't understand why your GPS connection takes so long, since it's up to date.

If you run both apps, I don't think there's any way to get around the need for persistent notifications for each, to make sure they aren't killed by Android.

Sorry I couldn't actually be of much help!
[Amazfit] Malli2602:
Is there someone who can help me with my major problem?

Best regards,

Stephan
[Amazfit] Malli2602:
Push
[Samsung Galaxy S20 / S20+ / S20 Ultra Guides, News] tomhouf:
Hello guys,

I own an Exynos S20 for a month now and I'd like your opinion on tests we can see on the web that seems legits.

They all show comparisons with other phones etc, and it seems that the recent ones show great battery life on our Samsung s20s.

In fact they show 7 or 8 + hours of SOT and S20 results almost even iPhone 11 pro results.

As far as I'm concerned, I don't have anything near these results as I never went above 4-4h30 SOT on my S20, even if a optimized my settings, got rid of some bloatware, or even set up routines to save some battery. Plus, I'm stuck at home so 100% of the time on wifi.

Do you think these tests are false ?

Thank you for your answers or advices.

Best regards,

Thomas

Here are some links of tests I speak about :

https://www.youtube.com/watch?time_continue=727&v=QP9LxoBe6pE&feature=emb_logo

[youtube]KRrsIp1kNtc[/youtube]&feature=youtu.be

https://www.reddit.com/r/Galaxy_S20...exynos_pcmark_battery_test_results_for_60_96/
[Samsung Galaxy S20 / S20+ / S20 Ultra Guides, News] Rask2015:
Here is my battery consumption on my S20 Exynos Variant. (no gaming and no YouTube - only light usage like Facebook, Instagram, E-Mails, Browser)
[Samsung Galaxy S20 / S20+ / S20 Ultra Guides, News] tomhouf:
All right, thanks. But this is not on a full charge is it ?

You charged the phone on the middle ?

Still, 7h30 SOT estimated would be great for me. ^^

Could you pls share your optimizations/settings ?
[Samsung Galaxy S20 / S20+ / S20 Ultra Guides, News] Rask2015:
No this isnt a full charge of course. I don't use the device such frequently, it's only a calculation from the app "AccuBattery" which is based of my usage statistic since the last 7 days. What I can say is that it needs 5-7 days till the battery life was okay. Also with the last two firmware updates my estimated SOT raised from 6.3h to 7.1hours. (maybe it is a coincidence)

Realistically I would say (without gaming) I will get 6/6.5 hours out of the device if I stay at home. (So the screen brightness isn't as high as outdoors)

My settings:

- FHD 96hz (you can find the app here in the forum)

- GPS off (don't now if it makes any crazy difference)

- Bluetooth, mobile data and wifi on

- energy setting set to optimized and adaptive

- put all apps to deep sleep (except WhatsApp, Gmail, smartwatch app)

-> you can find it in the battery saving section

I think it will not make a big difference if you have your screen constantly on)
[Samsung Galaxy S20 / S20+ / S20 Ultra Guides, News] termdj:
I to wonder about the sot some people get....I get +- 4 to 5.5 hours sot on a good day....most days 3.5 hours....I did notice that 4g/lte drains a lot more power then wifi....the bad sot days are the days when I'm at work and only on 4g/lte....AOD etc is on and I use most of the functions the phone has...120hz etc....Why buy a phone and not use the stuff...:) I can get through a normal day fine, so I'm okay with the battery...The standby drain on my s10 + was bad...during the night 2-4% per hour....the s20+ I get .5% per hour during the night....
[Android Head-Units] jrobbom5:
I've seen a few posts recently about how to set up Viper4Android on an Android head unit, so thought I would start this thread so that we could share some ideas. The configuration that I posted below is what I came up with in 15 minutes of experimenting yesterday. It's not a definitive or optimum config, it's just what I came up with, but I am very happy with the result. The purpose of this thread is to share ideas and configurations, due to there being a complete lack of this kind of information anywhere else that I could find.

First, a disclaimer: I'm half deaf, have constant ringing in my ears, and I am most definately not an audiophile, so take anything I say below with a grain of salt. Having said that, I do appreciate clarity when listening to music, so that is always my priority.

So I installed an android head unit in my car last week, installed the Hal9k ROM which came with Viper4Android (V4A) pre-installed. I've played around with V4A on my phone before with goods results, it's mainly geared towards phones with earphones, so don't expect too much from it using it in the car. But I played around with it yesterday and came up with a setup that I am really happy with, it gives in my opinion a richer, fuller sound, with no loss of clarity.

So here is what I did:

1) Select the speaker icon down the bottom. The headphone setup certainly has a lot more options available, but I went with the speaker setup as that's what I'm using.

2) Turn on the Master Limiter

3) I turned on Playback Gain control for a specific reason. My head unit has a bit of hiss with no signal at very high volumes. I can't hear it while the engine is running, but it's there. Bumping up the playback gain control let me turn down the gain on the head unit (look in Factory Settings) which reduced the hiss, but without any clipping or distortion that I can hear. I set Strength to 2, Max Gain to 9x, and output threshold to -1db.

4) I turned on the FIR equaliser. I was using the equaliser in the Amplifier app that came with my head unit, but I would rather just have all of these settings in one place, so I set the Amp equaliser to flat, and made all of my adjustments within the FIR equaliser. My setup tends to be a bit bass-heavy to my ears, so I just use the equaliser to gently taper off the bass, and I leave everything else flat. But just adjust it so that it sounds right to you in your car with your choice of music.

5) I turned on Reverberation. I dare say many will scoff at this, but I like the effect. It makes the sound more "full", without any loss of clarity that I can hear. I used fairly minimal settings to achieve this effect. Room size = 25m2, Sound Field = 6m, Damping Factor = 20%, Wet Signal= 20%, Dry Signal = 50%.

And that's what I came up with in 15 minutes. I'm really happy with the result though. Hopefully that will give others a starting point to do some more experimentation. And if you have your own ideas, please share them here :)
[Android Head-Units] 67comet:
I downloaded Malay Mod {and got the Full Version}. It also came with V4A but I hear no difference no matter what I've got selected. Mine has "Headset - Phone Speaker - Bluetooth Device - USB/Dock" tried them all ..

My headunit pushes amps via RCAs, so maybe it doesn't work through those channels?

Good ideas on your tuning {I've for tinnitus too}.
[Tilt, TyTN II, MDA Vario III General] defriend:
Hi,

I am planning to buy extra USB sync cables for my Tilt. I plan to use it as a car charger with a USB car charger ( http://www.meritline.com/car-travel-charger-black-593.html )

Will any USB A-B cable work or do I need to pay attention to which cable I buy (4 pin, 5 pin etc).

Regards

Nick
[Tilt, TyTN II, MDA Vario III General] Kaze0110:
Any regular USB cable'll work.
[Tilt, TyTN II, MDA Vario III General] AthenaLod:
i read somewhere some ppl where warning against this, make sure u do some good reading b4 plugging it in
[Tilt, TyTN II, MDA Vario III General] kilrah:
Forget that car charger and get an official HTC one. If you search a bit you'll see that more than enough people have fried their USB port/charging circuit with no-name chargers wanting to spare $10...
[Huawei P30 Pro Questions & Answers] i3arty:
Hi all.

So when I first bought the phone, when I was recording and zooming in the cameras changed to the better quality one x10 zoom. However since few months it does not change at all, stays the same. I was thinking with emui 10 it will get fixed but it didn't.

How can fix this issue?
[Huawei P30 Pro Questions & Answers] i3arty:
For anyone having similar issue i found solution. Empty your camera app cache, empty data and force stop the app then reopen (i think cache is the main problem) but now it all works!
[Huawei P30 Pro Questions & Answers] rubiicon59:
Glad you got it sorted.

And thanks for posting your solution - too often people can't be bothered.
[Shield Tablet General] xdpirate:
Great work! Does this mean you could in theory push payloads made for the switch to the K1, as they are both tegra-based devices?
[Shield Tablet General] Lord_Rafa:
Well, yes that is partially right but bear in mind that these payloads relies sometimes on the switch peripherals, so for example if you want to show something on the LCD it will not work because the shield and switch LCDs controllers aint the same, the code will run on the boot CPU but the LCD will not work because they don't work in the same way... It is something like use the wrong driver for a device.

Also you need to understand that the payloads normally are used as first stage loader for something else, if that something else is wrote for the switch app CPU it will not work at all. Switch Tegra app CPU is an arm64 CPU and shield app CPU is a 32bit armv7 so they are not compatible. E.g. this is why I cannot run the Switch Linux directly on my shield.... and even if they could work, again you will find the problem of the peripherals and many others customized things for Nintendo... that is why a Shield TV is not a Switch... same same... but different.

This can be more useful to those people that are interesting to do some research around this device.
[Shield Tablet General] Tonio1987french:
Is it possible to unbrick a Shield Tablet killed with this ?
[Shield Tablet General] Lord_Rafa:
With some additional development I think that it could be posible. Unfortunately I don't have a killed device to work on this.

Someone that would like to work on this, would need to check where the kill switch is enabled and where is verified.

If I understand correctly this would be the boot chain: bootrom -> nvtboot ( boot cpu code ) -> nvtboot ( app cpu code ) -> second stage bootloader( uboot/fastboot??? ) -> Android.

I would be tempted to think that nvtboot at boot cpu is the responsible to check if the kill switch has been enabled, or maybe the kill switch just modifies the bct header to break the boot chain... If I am right then maybe it would be posible to use shoelf2 to restore a backup to the emmc.

A payload would still need to be developed to being able to read/write the emmc using shoelf2. This is something that I am considering to implement as part of the works porting mainline Linux.

Also it would be nice to see if all devices shares the same private key that would be great because anyone could read a working shield emmc and share it to restore a killed one... if anyone could share the fuse dump, that my shoelf2 generates I could answer this question....

Anyway I would require a killed switch to being able to work on this... My main focus now is run mainline Linux....
[Shield Tablet General] Conti93:
I do have a killed Shield Tablet LTE. Where are you from?

The OTA that kills the tablet has been dissected here: https://xdaforums.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489

Once flashed the tablet doesn't give any signs of life, and goes only in APX mode when connected:

[IMG="device manager"]https://i.imgur.com/7lWRAdU.png[/IMG]

Is it possible to use ShoEL in APX mode? I don't think?

Gave a quick try compiling crosstool-ng on Debian 8 but it's hanging at make, will have a look at it later.

On a side note, one user (Drims75) from Ukraine restores motherboard for a modic cost, you can find a couple of user who sent their motherboard to him: https://xdaforums.com/showpost.php?p=71516196&postcount=139
[Shield Tablet General] FunDev:
Thanks for your work!
[Shield Tablet General] stronthoop:
I can confirm the exploit is working.

Thanks so much LordRafa, you're a legend!
[Shield Tablet General] forti77:
How do i get the SBK Key? Is the FUSE_PRIVATE_KEY i get via READ_FUSES the SBK? And is it possible to dump the BIS keys? The biskeydump payload seems only working for switch. Anyone has a biskeydump payload for t124?
[Shield Tablet General] wertus33333:
Did you have any success running/porting mainline linux?
[Shield Tablet General] valdeinsamkeit:
Would this dump the key required to nvflash u-boot?

Edit: I think I understand enough now to know why this is a dumb question. One would use tegrarcm, not nvflash.

Fuses - Nintendo Switch Brew

switchbrew.org

Edit: From NVidia's bct-overview:

Has anyone done any testing around what that means for devices with both PKC and SBK? As in does it validate both, either or a does one take precedence over the other?