yashsingh1/xdaforums huggingface dataset:
[Micromax A106 Unite 2] sling-shot:
This is likely to be the work of Micromax's own Software Update program. You will have to root and kick out some programs by Micromax.

http://www.xda-developers.com/micromax-remotely-installing-unwanted-apps-on-devices/
[Galaxy Grand 2 General] JAMESAMEES:
cm12.1 rom

any body tell me grand 2 spot OTG
[Galaxy Grand 2 General] VigneshS007:
only Y type OTG cable it supports in CM12.1 and Blisspop by Aapav............. i havent tried it.............
[Galaxy Grand 2 General] JAMESAMEES:
Kon se site se mile ge
[Galaxy Grand 2 General] Swp1996:
Amazon par search kar
[Galaxy Grand 2 General] yusuf.yusuf:
What is Y cable bro?

SM-G800H cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy Grand 2 General] Swp1996:
Google bro
[Galaxy Grand 2 General] JitDevHacker:
Y cable support cm 12.1 by mukulsoni??? just curious to know...
[Galaxy Grand 2 General] JAMESAMEES:
How to use this
[Galaxy Grand 2 General] NishRapper:
Not supp.
[Blu Pure XL] micmars:
These look identical to the TWRP themes to which you've linked...in fact, I am unable to see any original work here...and, with your donations link, I fear that the possibility exists that you'll be siphoning donations that may otherwise go to the rightful developers.
[Blu Pure XL] bemolx:
I don't want any donations from this thread. This is not my work - I haven't written anywhere as it could be mine. I've mentioned right developer and right official thread. Everything is just rewrited. It's only for sharing those themes.
[Blu Pure XL] micmars:
But you've done a few things that seem unhelpful...

1. You've linked directly to the downloads

2. You've provided a pretty sizable amount of real estate to pictures of these themes towards which you've made zero contribution

3. You've started a thread with your name on it, and your perpetual donation link in the sidebar (of course that's fine in-and-of-itself), but when coupled with the thread, it does yield the possibility to which I previously averred.

More to the point, it seems to me that if you want to help these devs, then do that...link to them.

To create a thread wherein you showcase these fantastic themes, and provide download links, strikes me as overkill.

Perhaps [MENTION=5476501]Train88[/MENTION] and [MENTION=2719389]z31s1g[/MENTION] may have differing opinions than I on the matter.

Irrespective, the thread has your good name on it, whatever that's worth to you.

Wishing you a terrific weekend.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Blu Pure XL] Train88:
Considering this isn't even my own work, I can't say much... But here's my two cents:

I doubt z31s1g1 is going to like this, unless you asked BEFORE making it. Also to give another parallel, I'd seriously be pissed if someone just made a copy of one of my threads to "share" it. We spent too much time on our stuff to be copied
[Blu Pure XL] z31s1g:
Actually I don't mind this thread or the possibility of donations going elsewhere.

The themes are already spread across different forums and included in custom twrp builds, there's no way to keep control of this stuff once it's in the open wild.

Train88 is right, asking would have been the right thing to do.

But the problems I see are, that when you decide to mirror the official threads, you should also be on your heels to keep it up to date.

And you should be able to provide sufficient support in case users run into trouble. I won't monitor this thread. And recovery trouble can become serious, because the recovery is the last resort to rectify issues on a device.

If you're willing and able to do both, I see no problem here.
[Blu Pure XL] bemolx:
Yes, you're right. I know every work takes some time, sometimes more, sometimes less..

Yeah, as it's "my" thread I'm responsible for this and I'm able to keep an eye on it. Sorry, I haven't asked you before sharing your great idea. I hope you aren't mad on me. Anyway thank you for your work on those themes.

Wysłane z mojego X2_Soul_Xtreme
[One (M8) Q&A, Help & Troubleshooting] mongoose96:
I have chosen encrypt my SD card in the android settings but when i copy files to the SD card then put the card in my PC I can see all the files and their names but can't play or read them. Is this normal or did the encryption not work? HTC m8 verizon stock firmware not rooted Android 5.0.1
[XDA Assist] XDA Visitor:
sw version lg855zv4, hw rev 1.0, kernel 2.6.35.7, build grj22, root obtained with kingroot, CWM v. 5.0.2.8 installed
[XDA Assist] OfficerJimLahey:
Hi, and welcome to XDA :cowboy:

Unfortunately, this device didn't get the kind of love like it's brother, the LG Optimus Black. Which is a shame. 1GB RAM and 4GB ROM would have got you as far as KitKat and still (in theory) be usable.

If you are on Boost instead of Sprint (if that matters - sometimes it doesn't), there's a web video of a Marquee running CM9.

Hope this helps, and good luck! :)
[General Questions and Answers] qwcarlowp:
Anyone who can help me? or can teach me how to root it? pls :confused:
[General Questions and Answers] patsurat:
how to root it honor bee y541-u02 anyone knows ?

how to root it honor bee y541-u02 anyone knows ?

The actual thing i m telling that in some build no. version kingroot,it works but in some with latest build version it does not work..

One frnz i m having same mode but with different build no version...it works in it but in my of the same model it does not work...its amazing. :(
[Moto G 2014 LTE Q&A, Help & Troubleshooting] rafaelrgi:
Hello,

Maybe its a noob question, but I'll ask it anyway: is there some way to get rid of that pop when there's a incoming call and the device is unlocked?

I would preffer to see the same screen (full screen ) that shows up when the device is locked, like in KitKat....

The Lollipop popup is harder to read than the good old obtrusive screen of KitKat... any advice?
[PDA2, XDA IIi, 2020i General] MasterIce:
Sorry, I posted this in the wrong forum before (I thought the XDA11i was a himalaya duh!

My apologies if this a bit longwinded.

I was recently given an O2 XDA11i.

It was totally screwed and had a battery problem.

With a new battery in it, it still didn't function so, with nothing to lose, I downloaded the O2 rom upgrade program V111171.exe. (rom version 1.11.171WWE)

I ran it and was, I'm pleased to say rewarded with what appeared to be a fully working unit.

Except that is as for the phone/gprs/gsm side of the thing.

I put a new O2 payg simcard in but although the phone acknowledges there is a card in it does not find a network.

I ran the unlock v1.6_138.exe from the root directory and (as most people seem to have got) was told that the phone was now unlocked and also that there was a problem.

I have tried the phone with two O2 sims (both of which work in my older xda11) and two Orange sims but the phone still does not find a network.

The signal here is fine so I haven't got a problem there.

The unlock log is as follows

xdadev_all_unlock started

device=PH10C

key found

ril ioctl 0xc2: 00000000

simlock answer: %SIMLOCK= 00

0

current lock status: 00

security answer:

000

security answer2:

at%LISTNETWORKCODE answer: 0

at%LISTNETSUBCODE answer: 0

at%LISTSPCODE answer: 0

at%LISTCORPORATECODE answer: 0

at%LISTSIMCODE answer: 0

at%LISTIMSIRANGECODE answer: 0

at%CLEARNETWORKCODE answer:

at%CLEARNETSUBCODE answer:

at%CLEARSPCODE answer:

at%CLEARCORPORATECODE answer:

at%CLEARSIMCODE answer:

at%CLEARIMSIRANGECODE answer:

simlock answer:

invalid sim lock answer

xdadev_all_unlock done

ril ioctl 0xc2: 00000000

ril ioctl 0xc6: 00000000

If I select the network selection to manual it tries to search for a network and then gives a message "Unable to read setting from the network. Try viewing settings later, or disconnect data connection and try again"

The top display bar shows the "!" mark and says there's no network.

Neither a cold or warm reset makes any difference.

Has anybody got any idea what the problem may be

Thanks very much in advance
[PDA2, XDA IIi, 2020i General] deedee:
For what it's worth i had no luck unlocking my Alpine with the latest version of the tool, i had to use the older version, and this was successful.

Download the earlier version here

Whether it has any effect on your problem i don't know but it may be worth a shot.
[Nexus Player Q&A, Help & Troubleshooting] htchd2fix:
Anibody tryed any of this android remote connected trough usb dongle?

is listed as keyboard remote with mouse options i think it should work but need somebody who is using it confirm this.

Thanx
[Nexus Player Q&A, Help & Troubleshooting] SkOrPn:
I'm using the Air Mouse C120 with mine now and plan on upgrading to the "MeLE F10 Deluxe" soon. Air mice work really good with all Android boxes, especially if they have their own usb dongle...
[Nexus Player Q&A, Help & Troubleshooting] htchd2fix:
thanks for sharing you experience......i have tried FLIRC not good at all unless you have ligitec remote (very expensive).......tried also this one from Bay

Wireless 2.4GHz Air Fly Mouse and everything works but back button (thats very annoying when you have to go back as only option i have to use remote app from phone) so still looking for a fly remote that got everything working.....

your air mouse c120 got the back button working??????
[Nexus Player Q&A, Help & Troubleshooting] SkOrPn:
The C120 works good enough for me I guess. The back button does NOT work on my Nexus Player, but it works ok on my Beelink m18. I have a Wetek Core on the way and will be trying it on that but only if I need a keyboard. The Wetek already comes with a good air mouse.

I never did get the F10 Deluxe and don't think I need to now.

EDIT: The C120 also works good on the Wetek Core, including the back button. So my guess is the C120 does not fully support Android TV, although for me only the back button failed to work on the TV OS, which can be annoying. It's working perfectly on all my tablet based media players, such as the MXQ Pro, Beelink M18 and the Wetek core. Just not on my Nexus Player.
[Samsung Galaxy Mini] Shadow Of Leaf:
CYANOGENMOD 11 FOR MINI2

First i want to thank [MENTION=4148720]TheWhisp[/MENTION] for his sources

this is Final stable cm11 for s6500 and s6500d

- What not Working

Camcorder

NFC(S6500 only)

- What Working :

Everthing

Install method for s6500d only:

-Download and install CWM6.0.5.1

-Download the rom

-Download google apps

-Copy the rom and gapps to external storage

-Wipe data,cache,format system

-Install the rom and gapps and the fix

-enjoy

Install method for s6500 only: plz follow the instructions

Im not responsable for any damaged phone so do it on your own risk

-install twrp and reboot in recovery

- go to wipe and Advanced wipe and then wipe cache , system

-in advanced wipe choose data and go to repair or change file system

- go to change file system and choose EXT4

-Install the Rom

-Reboot recovery

-Install gapps

-Enjoy

- Downloads for S6500

Rom : https://drive.google.com/open?id=1F8z95LPiMmiCfMwv4Eblyqa6Ea0__vRt

Gapps :https://androidfilehost.com/?fid=95864024717070880

TWRP 3.0.2.0 Odin : https://drive.google.com/open?id=1TUNcLo12YGYAH3B5rHv_m0MfaaxWtspr

- Downloads for S6500d

Rom : https://drive.google.com/open?id=1orqH1nyIQAyygcnMRb1NiMkqz6xhFG5V

Gapps :https://androidfilehost.com/?fid=95864024717070880

TWRP 3.0.2.0 Odin : https://drive.google.com/open?id=1Uvx-YdMAKlHbFrQonA4pnC1JS2B6AKTM

For the S6500 Install Video , this is the Link :https://www.youtube.com/watch?v=ACLEn63Nvi8&feature=youtu.be

Credits :

-TheWhisp

-Samsung :laugh:

-bleached for some motivation

-lorn10 "special thanks for you"

if you consider Donating thanks​
[Samsung Galaxy Mini] QGM:
Ok i will test that ;)

--

Cool rom, but visiting XDA or other sites with normal browser lags like the hell, system is really fast, is not slowly.

Wysłane z mojego GT-I9505 przy użyciu Tapatalka
[Samsung Galaxy Mini] lorn10:
Many thanks for this most recent cm11 rom simokb1996!

Question, - which milestone has this release? Is it at same M12 level as midzan21's last cm11 rom? Is the "low RAM feature" of Android 4.4 KitKat enabled in this cm11 build here?
[Samsung Galaxy Mini] Shadow Of Leaf:
because the m12 is the final release of cm11

low ram feature is enabled in this version
[Samsung Galaxy Mini] lorn10:
Hi QGM, - the following workaround may help to reduce / fix these browser lags:

1) Type or paste chrome://flags in the URL bar in Chrome for Android

2) Find the Maximum tiles for interest area (#max-tiles-for-interest-area ) flag in the list

3) From the dropdown, change from Default (value) to 256 (note, original source says 512 but that is most likely to high for our Mini 2 phone)

4) Tap on the Relaunch Now button to commit the change.

I don't know if this fix is really designed for Android 4.4 & cm11, - you will see. (I will try this when I get my test GT-S6500 phone.)

Source: http://www.androidauthority.com/chrome-android-scroll-lagging-363080/
[Samsung Galaxy Mini] QGM:
But im using AOSP Browser not Laggychrome for android
[Samsung Galaxy Mini] lorn10:
Yes, - I forget. Google replaced in KitKat stock AOSP Browser rendering engine with Chromium based WebView. And cm11 still have (also) their own browser...

Well, the problem of these lags are most likely RAM related, - I don't know where to set this value in AOSP / cyanogen browser, sorry.

simokb1996 may help. ;):)
[Samsung Galaxy Mini] QGM:
Interesting thing is that why they replaced to a bit worster not optimised thing? Why they dont keeped normal webview?
[Samsung Galaxy Mini] Shadow Of Leaf:
i will build a cm11 with old webview (webkit)

and for nfc i will look in s6310N it has nfc support if mini2 can handle it
[Samsung Galaxy Mini] YarpenZ:
Will it conect to "hidden" WiFi (not emittting SSID)?

This doen't work in 10.1-20150902-UNOFFICIAL-jena
[Samsung Galaxy Mini] Shadow Of Leaf:
Test and see if he working
[Samsung Galaxy Mini] lorn10:
That would be great, - webview is much more "lightweight" then heavy & fat Google chrome. So any other browser is therefore much more practical for our S6500.

Regarding NFC, - the S6310N has complete different SoC design, - so no Snapdragon S1 MSM7227A. :( Unfortunately I also found no custom rom, no Cyanogenmod. All normal S6310 custom roms are incompatible. Only a modified stock android 4.1.2 rom exist: http://xdaforums.com/galaxy-young/development/rom-glassrom-n-installer-t2882891
[Samsung Galaxy Mini] Shadow Of Leaf:
s6310 has cm11 but he is in devpt stage

i take s6310N NOT FOR THE SOC Design i just want the updated files nxp p544 nfc controller from the kernel that all
[Samsung Galaxy Mini] IAmLucky:
I am flashing thiw with CWM 6.0.5.1 from 2.5.6 gingerbread. Did factory reset and cache reset. After flashing is done, phone stucks in samsung logo. Any fix?

Edit: second time trying i get error status 7
[Samsung Galaxy Mini] Shadow Of Leaf:
You have s6500 or s6500d

Because this version is just for s6500
[Samsung Galaxy Mini] IAmLucky:
s6500 also CWM 6.0.5.1 is very unstable on my phone. Hardly gets into recovery. Also has blank black screen sometimes and I have to reboot it till it gets working. Anyways I dunno why It stucks in Samsung logo and after few secs reboots . Can there be a reason that I'm updating directly from gingerbread 2.3.6? should I update it to jelly bean and try again? I dunno Im not expert sorry. As I couldn't believe something making in 2016 for that old device... lol.
[Samsung Galaxy Mini] Shadow Of Leaf:
just a stupid solution flash cwm 6.0.3.3 with odin and then install cwm 6.0.5.1 and see if this working
[Samsung Galaxy Mini] IAmLucky:
okay I will try it because I had installed via odin 5.0.2.8 and then flashed 6.0.5.1 zip
[Samsung Galaxy Mini] hack91:
future versions will support camera, camcorder and nfc ? and what about internal storage ? is there any fix ? thanks in advance :)
[Samsung Galaxy Mini] Shadow Of Leaf:
when the internal storage work the camera work

Im looking for a fix for nfc

Camcorder will be miracle if it working
[Samsung Galaxy Mini] thedogx021:
i have the same problem on my 6500D , the internal memory didnt mounted

and i do the direct install the S6500 rom on my S6500D like this step, but no good

maybe i need to install TWRP too and reformat data partition to ext4?

ill report later after installation attemp
[Samsung Galaxy Mini] lorn10:
[MENTION=5880534]thedogx021[/MENTION], thanks for your feedback. Well, these S6500D problems are totally strange.:(

It is important to note that the latest CM 11 build and also the CWM 6.0.5.1 was developed by Shadow Of Leaf primarily for the original non-D S6500 mini 2 model. (The most people in this thread uses the S6500 and not the S6500D.)

However, what should S6500D users try to do? Well, after all these reported problems here, I strongly recommend to install first CWM-6.0.3.3-b2 with Odin. Why? This version was developed by former mini 2 devs for both models, it is confirmed to work stable for the S6500 and S6500D. After successful installation the upgrade to CWM 6.0.5.1 can be processed over the zip file. This will result in the following procedure.

Install method for S6500D:

0) root your phone with CWM-6.0.3.3-b2.tar.md5 and Odin 3.10.7 (if locked, it's recommended to unlock the phone first with a compliant stock rom)

1) boot into CWM, disable the Signature Verification and install CWM-6.0.5.1-v3-jena.zip from zip

2) boot again back into CWM and wipe both data & cache

3) go into menu mounts and storage and select format /system

4) go back to main menu and select install zip, install (from SD card) the jenad (or jena) rom, GApps, and the boot fix (the boot fix maybe not needed)
[Samsung Galaxy Mini] Don Pedro!:
Sorry, the runme.bat is described in the link you posted yourself:

https://xdaforums.com/showthread.php?t=1953420

But you're right, rooting in fact comes together with CWM here. I think there's a lot of confusion concerning the rooting of the mini out there. As said, if you search for "root GT-S6500" on XDA or google you'll find dozens of different recommendations about how to do it.

Well, I found out that the the recommendation of wverkist2 in fact does work also on my phone:

https://xdaforums.com/showpost.php?p=71226701&postcount=174

Press *all* buttons, vol up, down, home and power. As soon as the Samsung logo appears quickly release the power button and keep all other buttons pressed. This in fact will boot also my phone into recovery. A big THX goes to wverkist2!

One additional interesting fact I found out:

In one of my (meanwhile many) attempts I forgot to format /system and /data prior to flashing CM11. IMHO this should make no big difference here, as I formatted it several times before, so the changes in fstab should have been there already. Just the data in /system and /data hasn't been wiped. After another vain attempt to boot CM11 I reflashed bleached CM10.1, and guess what? I could boot this and found all apps I had previously installed under CM10.1 did survive this double flashing, fully functional, including their settings. For me this is a hint that that the booting of CM11 gets hung in a very early state. I would really be interested in finding out what the phone is doing there!

Cheerz

Don
[Samsung Galaxy Mini] thedogx021:
report after installation attempt:

so yeah u need the data partition to be ext4 format

i do this with TWRP and reformat the data partition to ext4

and then install the S6500 rom and Gapps and reboot,

boom, my internal storage is fixed now,

TWRP is kinda buggy thoo, reboot by itself after a period of time
[Samsung Galaxy Mini] Don Pedro!:
Yes, I already know all this stuff and I did it like that. And yes, you're right, TWRP automatically reboots (due to crashing?) after a variable time on my phone, too. This can hapen even during a flash, leaving a queasy feeling in your stomache...
[Samsung Galaxy Mini] lorn10:
Thanks for this feedback, - maybe these CWM and TWRP issues will be fixed sometime, - I hope. ;)

Regarding the rebooting of TWRP, I thought that this is a feature and not a bug. Well, it could be both.... :D

However, to use TWRP also at the S6500D model is a bad idea. This is the absolutely opposite of what developer Shadow Of Leaf has stated. TWRP is only necessary for S6500 phones because of it's internal storage problem. The S6500D was never affected by that grave problem. So don't be surprised if you notice some strange behavior with this config.

As of 2017 this old tweak is NO LONGER necessary / valid. At least in all MY CASES, for all my Central European mini 2 versions. ;) However, as mentioned, there may exist other mini 2 variants (in other parts of the world) that need a special method.

So far I get the chance I will buy a cheap S6500D and test this oneself somewhat deeper. ;)
[Samsung Galaxy Mini] xEmre66:
I installed it on my S6500 it's very fast and stable its just greaaat.
[Samsung Galaxy Mini] lorn10:
Yes xEmre66, and with your CAF HAL mini 2 (snapdragon optimized) kernel also this CM 11 will run even more efficient, including better AnTuTu performance. ;):o
[Samsung Galaxy Mini] xEmre66:
Yeah I'm hardly working to get it working.
[Samsung Galaxy Mini] lorn10:
That's great to hear [MENTION=7429196]xEmre66[/MENTION]! :)

By the way I have a little question, how can I replace the "libpn544_fw.so" in the current CM 11 install / build with a different one? It seems that the current NFC fw file is the wrong for our very early NXP 44501 C1 controller. Why I think so? Well, as mentioned there are phones with IDENTICAL old NXP 44501 C1 chip out there, - good examples are the LG Optimus L5 E610 and the Samsung Galaxy S II I9100P. (The LG L5 has furthermore also near identical snapdragon SoC hardware.) However, their NFC is working on newer Android 4.x versions. :D

The "libpn544_fw.so" file for these two devices is smaller in size, - it seems that there exist (many) different versions of that file. Different NXP 44501 chip steppings needs different libpn544_fw.so file. The file which Shadow Of Leaf uses in this build here is a more recent one, it has 70'776 Bytes. The file for the LG L5 has 58'640 Bytes, the file for the Galaxy S II I9100P only 58'488 Bytes. The original stock file for the mini 2 (with Android 2.3.6) has also only 58'488 Bytes but has

different content

.

And finally, the Snapdragon S1 based LG L5 has furthermore also a nfc.msm7x27a.so file (in system\lib\hw\) which is missing at our CM 11. We have just a strange nfc.default.so, - it my have just a different name.:confused: Whatever, in the attachment I upload here now some examples.;)
[Samsung Galaxy Mini] Shadow Of Leaf:
I Agree with you [MENTION=7045712]lorn10[/MENTION] i upload a new version of libpn544_fw.so

nfc.default.so is just a vendor file maybe i will build a nfc.msm7x27a.so from scratch

but the problem is not the this files the problem is about the kernel,when i did a Dmesg (kernel logcat) it give that pn544 can't be enabled that all