yashsingh1/xdaforums huggingface dataset:
[G3 Q&A, Help & Troubleshooting] patrs63:
well I didnt flash a custom ( i flashed a wrong official marshmallow only-for the wrong device it seems) , and yeah i did that without a root or a custom recovery ... i did it through pc :(
[G3 Q&A, Help & Troubleshooting] my.ads0:
Wish I could help more, but that territory is beyond my expertise. Sorry.
[G3 Q&A, Help & Troubleshooting] patrs63:
no problem , thanks for trying mate :D
[OnePlus 3 Themes, Apps, and Mods] Nishidh:
I don't know about the other Ad blocking apps but AdAway has been my favorite for a long time due to its functionality and being open source.

Here is the flashible zip

https://drive.google.com/file/d/0B6FY-XKZtgn4bU1vUE9lWUVsYjA/view?usp=drivesdk

Instructions

Flash this directly via recovery (custom)

*Requires root

Enable systemless root in settings if u use systemless root

Hit the thanks button below if u like this
[Moto G 2015 Android Development] EsromTech:
SlimRoms is a custom android operating system. Our main goal is to offer users a slimmed down yet feature rich alternative to other android operating systems.

The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.

All of the sources can be publicly viewed through GitHub and you can stop by our public Gerrit to submit patches of any type.

Slim7 is the project name for SlimRoms based on Android 7.1.1 Nougat and offers the following original features:

Slim Navbar & Hardware key rebinding

​Single tap action,​​ ​long press action, double tap action!-We’ve got you covered.

Slim Actions & Chamber of secrets

​Customise your device to the fullest​​ ​-You’re a wizard!

SlimRecents

A Faster alternative to stock recents ​-Your device, your choice.

SlimLauncher

​An​ ​Open​ ​source,​ ​feature​ ​filled​ ​launcher!​​ ​-Make yourself at home

Status bar customisations

​Clock and Date? Battery? ​-More​ ​fun​ ​than​ ​you​ ​can​ ​shake​ ​a​ ​stick​ ​at.

Important links:

slimroms.org - Our official website and your source for anything SlimRoms related.

Downloads - Slimify your device!

Unofficial Downloads - Initial Build0.9!

Installation instructions - Follow these steps if you want SlimRoms on your device.

FAQ - Have a question? Consider reading our FAQ first, you might find your answer there!.

Report-bugs - Found a bug? Send it our way!

Kernel Source - The source of your device's kernel.

Get in touch! - You can contact SlimRoms at these places if you have questions, requests or feedback.

Google+

Twitter

Facebook

Disclaimer: We are not responsible for any damages to your device.

XDA:DevDB Information

SlimRoms Slim7 Android Nougat, ROM for the Moto G 2015

Contributors

EsromG5, prbassplayer

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

ROM OS Version: 7.x Nougat

ROM Kernel: Linux 3.10.x

ROM Firmware Required: Custom Recovery

Based On: Aosp, Slim

Version Information

Status: No Longer Updated

Current Beta Version: Build0.9

Beta Release Date: 2017-01-28

Created 2017-01-28

Last Updated 2017-03-20
[Moto G 2015 Android Development] EsromTech:
Reserved
[Moto G 2015 Android Development] jhenrique09:
nice work
[Moto G 2015 Android Development] firdous95:
You should update it...this rom has potential
[Moto G 2015 Android Development] Nudd42:
Good rom, I liked it, it has future, I hope there is continuity
[Moto G 2015 Android Development] SkylerZekrom:
Will keep updating this ROM? Im curious to know :p
[Moto G 2015 Android Development] krisbeowolf:
file not found
[Xposed Framework Modules] XVoiceChanger:
Wechat & Telegram voice changer base on Xposed framework

Screenshot:

i.imgur.com/ChE0tn8.png

Xposed repository link:

repo.xposed.info/module/gg.xvoicechanger
[Xposed Framework Modules] juancollado2003:
Has a heavy lag in sound like if I had a bad reception
[Xposed Framework Modules] XVoiceChanger:
What is your device？
[Xposed Framework Modules] juancollado2003:
Blu life one x 2016 android 5.1.1
[Xposed Framework Modules] bugggmenot:
Would have been great if supports Whatsapp, GBWhatsapp and Plus Messenger.
[Xposed Framework Modules] XVoiceChanger:
It now supports Plus Messenger.
[Xposed Framework Modules] Bombo1:
Great, but I can't find the right sound, I thing that I have the same problem as juancollado2003
[Xposed Framework Modules] bugggmenot:
Thanks but the recorded voice is weired, it is just some noises and nothing else.
[Xposed Framework Modules] Malcob:
not working - android 8
[Xposed Framework Modules] neearai:
Do you have the plan to make it support android 8 please?
[Xposed Framework Modules] anjarys:
Mirror is down for a while. Do you have backup?
[General Questions and Answers] umby75:
Hi, I have got mu Note 4 rooted phone.

I use external microsd card as internal card for some app to free the memory.

Now I have a Kingston 64Gb class 10 Uhs 1.

I wonder if I use a 128Gb class 10 Uhs 3 can I get some good results compared at my current situation?

I know that Uhs 3 is made for camera transfer, etc. but I don't use video in high resolution.

Second question: can my note 4 tead up to 128Gb as maximum size?

Thanks..

Sent from Note 4 device - Rome - Italy
[General Questions and Answers] Prateek(Patrick):
There are several devices with the name Note 4

Samsung Galaxy Note 4

Samsung Galaxy Note 4 (Duos)

Samsung Galaxy Note 4 (USA)

Xiaomi Redmi Note 4

Xiaomi Redmi Note 4 ( MediaTek)

Xiaomi Redmi Note 4G

Please specify the model that you are using.
[General Questions and Answers] umby75:
I'm sorry. My phone is SM-N910F (Samsung Galaxy Note 4).

Sent from Note 4 device - Rome - Italy
[General Questions and Answers] Prateek(Patrick):
You can use a card of 128GB

Yep, that's right.

But it should not be of UHS-3 reasonbeing the host device of this phone doesn't support it.

It's just like trying to play a DVD in a CD player, you can put inside it but it will not be able to read it.
[General Questions and Answers] steven81ir:
Guys I would like to have a question. What is the maximum size of microsd and what type for Redmi Note 4g?
[General Questions and Answers] Ashwinrg:
The maximum size of SD card is 512 GB. I think Redmi note 4g can support max to 64 GB class 10 SD card.
[Shield Tablet Q&A, Help & Troubleshooting] bob3rt:
Good afternoon everyone

I got my K1 for Christmas and I've been trying to root it for a few days but I can't get that far because I can't get the bootloader unlocked.

I've been following the guide based off of Nvidia's website

I've activated USB Debugging mode as seen here . Now once I've authorized the PC using the tablet. Once I run cmd in administrator mode I run

adb devices

I am able to get the serial and it says it's authorized. However if I go into Fastboot. if I check for devices it just goes back to the prompt, and if I try to run the unlock command it just gets stuck on <waiting for devices> (I've attached a screenshot here.)

At first I thought this was an issue with the OS/Drivers because I am on Win10 x64, and the shield drivers gave some error about driver incompatibility. So I loaded up a VM with win7 x32. However I am running into the exact same issue once I get to fastboot; the tablet just doesn't want to cooperate. I've booted into fastboot manually Where the options are:

[nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - locked

Continue
Fastboot Protocol
Recovery Mode
Restart
Poweroff

Nothing is recognized from there either. I've also tried multiple cables, since the Shield doesn't come with any. Anyways I've searched the older threads here for help but none of them have given me any luck. If there's something I can try I would definitely be open to hearing it and trying, I just don't know what the issue could be.

Thanks for your time everyone.
[Shield Tablet Q&A, Help & Troubleshooting] njhuiz:
You have boot into the bootloader before being able to use fastboot. Just reboot your device and hold vol- during startup. The tablet will show some console messages, offering some options. If you see that screen, you can use fastboot.
[Shield Tablet Q&A, Help & Troubleshooting] dzidexx:
Adb works in normal mode.

Fastboot works in Bootloader mode.

Reboot to BL and type "fastboot devices", if no device go to K1 and select "fastboot protocol". Select on/yes.
[Shield Tablet Q&A, Help & Troubleshooting] bob3rt:
Hey there, sorry for my late reply, I've been swamped with work. I've tried your advice with no luck so far.

I can reboot to the bootloader, but when I select "fastboot protocol" I don't get to choose Select on/yes. it just refreshes the screen with the same options that I listed above. If you'd like when I get home I can provide a screenshot of my tablet so you can see the options, but I'm not getting anything like you described. Am I missing something?

Thank you for your time so far helping me.
[Shield Tablet Q&A, Help & Troubleshooting] dzidexx:
Connect k1 to pc, type in cmd:

adb devices

adb reboot bootloader

fastboot devices

/Enable fastboot protocol on k1, type again/

fastboot devices

Give here screenshot from pc - all command/answers in cmd. [MENTION=6009584]bob3rt[/MENTION]
[Shield Tablet Q&A, Help & Troubleshooting] JALACB:
I had the same issue and lasted untill I tried different usb cable

Shield K1 connectivity is very sensible to cable quality

try others
[Shield Tablet Q&A, Help & Troubleshooting] bob3rt:
Hey Sorry again for a late response! However the good news is that I got it working!

What I ended up doing was hooking up the tablet to my Raspberry Pi with MATE and running adb/fastboot there. I originally ran into the same issue, but since I was able to sudo fastboot everything was recognized and seemed to work fine. I appreciate all of your help, and I apologize once again for the late replies!
[Shield Tablet Q&A, Help & Troubleshooting] 0mad:
For those that don't have a Raspberry Pi to follow the OP solution (like me), it's likely that your drivers aren't up to date on your PC.

Go here... https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm

And follow the initial instructions in the introduction paragraph and get yourself NVIDIA CodeWorks for Android. Once downloaded and installed you'll then see the shield in your fastboot devices list.

:good:
[Shield Tablet Q&A, Help & Troubleshooting] Nriku1:
Worked like a charm! Thanks.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] loaderboy:
I need help getting a logcat while my phone is shutting down and also while it is booting up.

Here is some history of my problems which will explain why I need to do this.

Note 3 sm-n900v

Currently running OF1 firmware and Alliance t-mobile rom

Rooted and unlocked bootloader TWRP recovery

I got this phone used for cheap and thought it would be an easy fix. I started with a clean odin of the stock OF1 firmware to put it in factory condition. Everything went great and had good signal and 4G LTE ran smooth and set up with no problems.

After the first time I rebooted the phone I had no signal. Checked About phone and my IMEI, baseband and serial number were gone.

I reflashed the phone in odin and everything was back. Another reboot and all is gone again.

I have tried different roms after rooting including some AOSP roms and always the same result.

I have checked to make sure that the phone wasen't a victim of the "NVbackup/restore" bomb and my NV partitions do not seem to be corrupted.

When I power off the phone it seems to take a long time to shut down (1-2 min.) so I suspect that something is being rewritten on the phone during a reboot. This is why I need to get the logcats so I can have some wizard/guru/hero/Android God read them for me and hopefully tell me what is happening to the phone and how to fix it.

I can work in ADB if someone would be kind enough to give me the commands needed to get the logs and where to post them or who to send them to for help.

I'm old but not stupid. Just an old fart that needs some help getting across the Android freeway. :)

Thanks in advance to anyone that can help.

Loaderboy
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] bftb0:
"got the phone for cheap" - did you call Verizon and inquire if the ESN was blacklisted?

If not, I would inquire before trying anything else.

(for shutdown; assumes you are rooted.)

adb shell

su
cd /data/local/tmp
cat > watcher.sh
#!/system/bin/sh
cd /data/local/tmp
logcat -c
logcat -v threadtime > watch_shutdown_logcat.txt 2>&1
^D

chmod 755 watcher.sh
./watcher.sh 2>>/dev/null &

exit

then reboot.

I know it's a pain in the butt to re-Odin the phone & re-root in order to run a single experiment, but you might also try the reboot cycle with the phone in airplane mode (or better yet in a location where you know you do not have a cell signal) to see if that has an effect.

Does the rooting process require a reboot? If so that would seem to be a chicken-and-egg problem - if your IMEI gets wiped on the first shutdown, then it would be hard to install a new ROM to find out whether it is carrier ROM software that is performing the changes.

Other possibilities: an intermittent hardware problem that is being mis-diagnosed as software behavior. If this were the case, occasionally the problem would appear even after a fresh Odin flash.

Other ideas include performing checksum (md5) signature comparisons on the stuff in /firmware and /firmware-modem before and after reboot to see if anything is changing, e.g.

find /firmware /firmware-modem -type f -exec md5sum {} \;

PS This advice doesn't mean I'm planning on helping you examine your logcats, but you should feel free to put them in a pastebin and provide the link here. You might want to scrub the file of any personal or device identifier information before you do that.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] loaderboy:
No the phone is not blacklisted, first thing I thought of. The problem happens on Verizon and Tmo roms alike.

The last time it lost the IMEI and baseband I got it back when I flashed Alliance rom but I havent rebooted since. The phone didn't lose root so I think I can experiment without odining the stock firmware and rerooting.

I will get the shutdown logcat and see if I can find anything before posting it.

Thanks so much for your quick reply.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] bftb0:
The observation that it is ROM-independant is significant.

That would suggest that it is less likely to be due to a piece of application software unless all the ROMs carried the same application/code, or the functionality was coming from the TrustZone, or perhaps code in a kernel shared in common between ROMs exhibiting the behavior.

You seem to be suggesting that it can be corrected by simply flashing a new ROM. Normally that only involves the /system, /cache, and /data (when you wipe) partitions not the /firmware or /firmware-modem partitions.

It's just one hypothesis, but my money is on flaky hardware that causes a failed initialization during boot up. Evidence for that might be:

(1) boot the phone several times after you lose IMEI, both warm reboots as well as shutdown/boot and shutdown/battery pull&reinsert/boot. If it comes back up during any cycle... flaky hardware. (Note also that if you put the phone on the charger when it is "off" it actually performs a "silent boot"... I think the bootloader does this by providing the kernel with an alternate (skinny) ramdisk. In any event, many pieces of hardware could be fully powered up & kernel initialized when doing this, so potentially this could affect flaky hardware. Just be aware of it so you are correctly appraised of "how many time did I boot this thing?")

(2) Alternatively, NOT recovering service in a reproducible manner (e.g. flash & boot a ROM 4 or 5 times using the exact same procedure and one of those times service is not restored) also would be indicative of intermittent hardware troubles.

(3) if you have TWRP installed and the problem was due to some stateful behavior (e.g. something recorded into a file on the previous boot), performing a full wipe of /data might alter the behavior as that is the most likely place for it (esp. since you say that ROM flashing cures the problem). Try wiping & booting several times - does the problem come & go?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] loaderboy:
well I rebooted and lost signal. I then booted to TWRP and wiped data and still no signal.

I did this 3 times and no signal. Then I wiped dalvik /art cache and cache without wiping data and signal is back.

Getting closer. I will reboot to lose signal and then reboot to TWRP and wipe each one seperatly to see if I can narrow it down.

Stay tuned.

Wiped dalvik/art cache and signal is back. Tomorrow I will restore my stock backup and see if it works on that as well.

Thanks for giving me the tips on where to look. If it works on the stock rom I will then have to try to find out what is causing this to happen.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] bftb0:
... and the result is?

.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] loaderboy:
Flashed stock backup and everything was there. reboot and it's all gone. Boot to recovery and wipe dalvik cache and baseband IMEI etc. all back.

Sorry for the long break but spent the weekend moving a friend.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] bftb0:
Looks like you have your work cut out for you. Somehow I doubt you are going to find something meaningful inside of /cache, but I'd look there first since that is likely to be the simplest in terms of effort.

I suppose you could try a binary division method of manually deleting half of the .dex files and the corresponding entries in places like

/data/system/packages.xml

/data/system/packages.list

/data/system/install

/data/system/users/0/package-restrictions.xml

/data/system/users/0/runtime-permissions.xml

and then iterating (the divide the right group by half) but thats gonna get tedious fast - and possibly just cause bootloops or hangs.

Frankly, I still think there is an underlying bit of flaky hardware - if the ESN was clean, what would be the point of software being intentionally coded to "turn off the phone" on an otherwise clean ESN device, and a completely vanilla ROM (i.e. no personalization by initialization of a Google account credential, no market apps, etc).

If you decide to use logcat and you discover that you need to launch on boot because the logs are rolling over before you can manually run a logcat (very likely because of the long Dalvik rebuild times), you will either have to choose a ROM which has a hook for auto-starting a script (e.g. CM13 userinit.sh files), or you have to re-pack the boot image to execute a one-shot service during late boot (customizing init.rc), making sure to put the logcat invocation into the background so the service doesn't block init. In both those cases, make sure you write the log to someplace like /data/local/tmp - you can't use /sdcard as the automounter tends to mount it quite late in the boot.

good luck
[Xiaomi Redmi Note 3 Questions & Answers] sasukay:
I was just reading through this article, "Advanced Kernel Tweaks for the OnePlus 3" and was really surprised by the improvement in battery life and performance by just making a few tweaks in the kernel profiles.

While the battery and SOT for our kenzo is already at par with most of the other devices, thanks to the massive battery, but still the thought of implementing the tweaks and further increasing the battery and performance to another level just amazed me. In this article the OP is talking about increasing the SOT upto 14hrs on OnePlus 3 without any significant trade off with the performance, with its 3000mAh battery. So, guys just think what these tweaks can do to our device.

Now, I'm not being too much greedy here but guys let's just give this a try. We have enough people here on our forum for testing.

Since, I'm not much active here and don't know much about the devs involved in the development of our device, so I ask everyone to tag the devs from our Redmi Note 3 forums, in this thread, so that they can look into it and work on highly optimising the different kernel parameters to get the most out of this device.

This is just a humble request from my side, which will benefit a lot of users. Its not that I'm commanding or forcing the devs to do it. Its just a humble request and the devs are free to neglect it.

Thanks anyways, let's hope the devs look into it at further improve the device's performance to another level.
[Xiaomi Redmi Note 3 Questions & Answers] Archmage1809:
The biggest problem is Snapdragon 650 is 28nm processor and Snapdragon 820/821 is 14nm. 650 will need higher voltage, higher power consumption to reach the stability and performance.

IF Snapdragon 650 were made with 14nm processing, I assume Kenzo will have around 12hr+ SOT straight out the box.

Second is processor architecture, 820/821 based on Kyro cores (heavily modified version of Cortex-A72/A73 core if I'm right, correct me this). Even small cluster of 820/821 will have the same or better performance to big cluster (2xCortex-A72) on 650.

10hrs+ SOT on Kenzo has reached hardware limitation. Miracle may happen, but don't expect it. Developers still looking for the best way to save your battery without trading too much performance.

IMO, Radon Kenzo is the "TWEAKED KERNEL" you need.

OT: Battery life is the only reason why RMN4 (SD) use 625 instead of 652 as we expected. RMN4 SD gonna have little worse CPU performance than MTK variant in trade of better graphic performance. And maybe battery life, I assuming it will have 12hrs+ straight out the box.
[Xiaomi Redmi Note 3 Questions & Answers] jordandroid64:
The clusters (there use the same archicture but the frequences are different) of s820/821 are at the same frequences less performing than a72, else same in 14nm the consumption of battery is too big with only big cores because there are not efficient for small usage .. so Qualcomm used their own cores mixed to perform correctly and battery consumption correct... but it's really not perfect (Geekbench 4 show well that kryo 100 are really not fantastic...)

If you want a big sot with 650, put down the big cluster... and launch them only on some bigs apps...

14h with an OP3 I think it's near to impossible, same with kernel tweaks... I know a OP3 user and generally it's not more than 5H SOT....
[Xiaomi Redmi Note 3 Questions & Answers] sasukay:
[MENTION=5328571]Archmage1809[/MENTION], [MENTION=6022515]jordandroid64[/MENTION] = The project was initially started for Nexus 5x which had SD 808, a hexa-core processer with 2xA57 and 4xA53 cores. Also it was built on 20nm architcure technology. So, that means there's hope for us too, if what I understood it right.

Nexus 5x Kernel Tweaking
[Android Q&A, Help & Troubleshooting] abhaykhira:
how to root coolpad note 5 with twrp......i not getting proper recovey image file...i tried a lot.....help asap......
[Android Q&A, Help & Troubleshooting] vikas kumar mudhiraj:
Me too
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Alcibiade:
Just wondering what you guys have been trying for radios in Japan

What is the best radio in terms of battery life / quality of reception ?

I am willing to upgrade (Currently using TNT latest ROM with the original radio from Softbank) and not so much into testing 1.47, 1.50 1.51 and 1.54 if you have alreday tried them :P

If I had to bet I'd take 1.51 which I tried before... But anyway I am willing to hear everybody's idea on this sensitive issue

Any advice ?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Alcibiade:
Come on there are lots of X01HT users here :)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] shunsai:
unfortunately, i think that the majority of x01ht users IN JAPAN are still stuck at 1.14.xx.xx (myself included). sadly it seems like its become a lost and forgotten cause...
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Alcibiade:
Mmh true for the recent versions of the X01HT. If you want I can sell you one which you can easily upgrade (I broke my radio, got a new phone but it came back to life (Miracle !!) so I can sell one of my phones. They are both "upgradable" X01HT)

That said the 1.14 is not that bad compared to some of the recent ones (At least it was better than my 1.37...)