yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Q&A, Help & Troubleshooting] MattBooth:
You're being obtuse by insisting that we're all public alpha testers.

You obviously have no idea about software development, nor about Android Open Source development. Not your fault, but running your mouth is.

You bemoan the memory leak fix took several revisions to fix. So, you think that Google dedicated the whole team to fixing that one bug? What then? No other bugfixes or features are introduced in the meantime? The likely case is (and this is from experience) that bug took some revisions to fix, in the meantime, Google were also pushing ahead with other fixes. Regardless to what the uneducated (about SW development), throwing 15 developers onto one problem doesn't solve it any quicker. 5.0.1 came, adn 5.0.2 came, then 5.1 came in the meantime. While that memory leak was being worked on, more releases come fixing other things. Be grateful they didn't listen to you and leave it at 5.0 for several months while they fixed one issue.

Whatever bluetooth fixes that you think are in 6.0.1 are pure fantasy, because none exist in AOSP 6.0.1: http://aosp.changelog.to/android-6.0.0_r5-to-android-6.0.1_r1.html <-- That's the FULL changelog of commits between 6.0.0_r5 and 6.0.1_r1.

It is not Google's job to fix a problem in anything other than their own devices. At all. Google's job is to make AOSP run smoothly on Nexus devices and release the source. Samsung, HTC, LG, Motorola et al all take the source code, just like CM, AICP, Slim and the rest do, and make modifications for their devices, using the sources given to them by their hardware partners and themselves. So if BT works in Nexus devices, but not others, then it's not Google's problem (usually). An AOSP issue will persist several devices, including Nexii devices.

Google also have taken on the quite large undertaking of monthly security updates for their devices, which I can tell you will be taking up some of the development teams time (it's what, 3-4 months into that project?).

No software ever released on this planet comes without bugs and issues. This is software development. You can check the status of AOSP development here: https://android-review.googlesource.com/#/q/status:open and feel free to download, code and submit your own features.
[X Style (Pure) Q&A, Help & Troubleshooting] Tinkerer_:
t

No new or useful information there. Thanks anyway, despite the ad hominem. I guess that comes with the territory (forums).

Yep, the Google-Android-(independent hardware makers) ecosystem is seriously flawed. Too much disconnect between the OS owner (Google), the hardware makers, the carriers, and the customer. And the first three in the chain (not including the customer) have different incentives/disincentives, and there are a bazillion hardware variations, of course it is broken. We know all this.

Reminds me of the original PC/Windows mess. Except worse because the carriers interpose an additional dysfunctional layer hindering OS updates/support. (Before anyone says "just DIY with one of the many available ROMs, I started this "Q" thread about stock MM, not third party ROMs.)

Still hoping for any useful information on anything happening to fix the MM defects, to get an idea when it might be past public beta and worth installing to MXPE.

TIA...
[X Style (Pure) Q&A, Help & Troubleshooting] MattBooth:
What ad hominem? Your uneducated state affects your ability to understand the nature of Android and software development. It's a perfectly legitimate response to your position. You lack the ability to understand and therefore your argument is flawed. I'm not attacking you, I actually tried to give you some insight into how it works, but you're not really interested and would rather insist on this "public beta" bull.

As far as fixing any "defects" you suppose, you haven't actually listed any so no-one is going to be able to help you with temporary work around without a list of what you feel is broken. I also showed you the changelog, so you can do your own homework to see if your supposed defects are fixed in 6.0.1.

The various hardware configurations doesn't even matter because Android is built to deal with it. So long as the hardware vendors of chips and modules support them properly and give out functioning binaries to OEM's, or proper source code, it's irrelevant. The exact opposite of what you said is true, Google has a very close relationship with it's partners (anyone signed up to their Google programs, to preinstall Google apps). The problem is carriers, who really shouldn't have a say in software on the phones, but that seems to be a chiefly North American problem.

Google doesn't need to have any connection to Android users as customers. Google does not sell Android, therefore you are not Google's customer unless you use a Nexus phone. Google sell the Google Experience, with the Nexus. You are Motorola's customer, and you are using Motorola's branched version of Android. Google doesn't owe Motorola any fixes or patches for their device. Motorola must maintain their own device tree and maintain their own relationships with their partners.

EDIT:

Also, Motorola's problem is resources. They have four version of the Moto X 2015 to deal with, three versions of the Moto X 2014, the new X Force, then the various versions of the G and E to deal with, along with two smart watches, and so forth. Their line up is increasing whist I imagine their development team is not. There was outrage (rightly so) when news broke that the Moto G 2015 wasn't getting the MM update, despite being a couple of months old, and Motorola listened and OTA's are rolling out.
[X Style (Pure) Q&A, Help & Troubleshooting] Tinkerer_:
I am asking if anyone can offer any info on anything being done to move toward MM revision with the many significant defects of 6.0 corrected. Read the forums, there are way too many defects with 6.0, it is patently a de facto public alpha, and we are tracking the usual pattern where it takes 3 to 5 revisions before an OS major rev is ironed out enough that upgrading will not cause more problems than it fixes.

There are always excuses made for why there are so many defects in software. There is a euphemism for "defect" everybody uses, "bug". Everyone has been making excuses for so long about shoddy workmanship and inadequate testing and correction of software, with the "bug" euphemism to minimize the reality that these are defects, that we are all just to suppose to accept systems ridden with faults without complaint. It's unacceptable. It can be done better. Part of why it doesn't get better is because everybody says "that's just the way it is, deal with it". With mountains of byzantine excuses and even ad hominem attacks (as here).

This thread was not started to start a tit for tat ad hominem back and forth, nor to post long essays detailing excuses for the pathetic status quo of the fragmented Android ecosystem with respect to defect causes and distributions. It was started looking for any info about work being done to fix the stock MM defects. Still seeking info.

TIA.
[X Style (Pure) Q&A, Help & Troubleshooting] MattBooth:
You should probably check the definition of ad hominem. There was no attack on you as a person, just pointing out that your uneducated state with regards to knowledge about software development affects your ability to call judgement on this.

But you haven't listened to a single word I've said and still maintain a shoddy position, so I would suggest to anyone else who reads this to simply ignore you as a troll.
[X Style (Pure) Q&A, Help & Troubleshooting] LenAsh:
I think we'll close this debate. There are no real "Android" insiders on XDA, so asking for update info which is privy to Google is perhaps somewhat futile.

On a related note, XDA have a few dedicated "Android Fora", such as this complete Category where non-device specific discussion and indeed conjecture takes place. Perhaps you could take a look there and see what transpires?

Thanks
[General Topics] finesse:
I have a T-Mobile MDA Compact III and i want to upgrade to the Fujitsu-Siemens Pocket LOOX N560.

My question is, the Fujitsu N560 comes in WM5, is it worth waiting till the phone is releases with WM6?

thanks
[General Topics] Rudegar:
it may never get wm6

it's 100% voluntary for the makes if they wish to release

newer roms for it
[General Topics] levenum:
Uhm, the N560 is not a phone. It is just a PDA with a built in GPS receiver.

(Thats for navigation in case you are not familiar with the term)

As far as I know Fujitsu never made a PDA phone of any kind.
[General Questions and Answers] kaku1992:
all videos are not opening by default player .uses software decoding in other apps like MX player etc..

Causing battery drain in SW mode

Wanted to reply in temasek redmi2 cm13 unofficial forum.

No I am not a complete noob
[G3 Q&A, Help & Troubleshooting] sdgksdgksdgk:
does someone knows how to root the stock marshmallow including recovery ?
[G3 Q&A, Help & Troubleshooting] SpaceRaider:
Not possible yet
[Android Q&A, Help & Troubleshooting] wolfboytech:
Model:	ASUS_Z00AD(ZE551ML)

RAM:	4G

Firmware/APP Version:	Latest

Frequency:	All the time

Rooted/Unlocked:	No

APP Name:	None/All/System

Hello, all!

I'm pretty sure I'm gonna have to send it back for an exchange, but I tried to wipe the cache partition on my brand new ASUS ZenFone and got impatient. On top of that I forgot to allow USB debugging. So here's what I did, and the problems I'm facing now:

I installed the latest OTA update that was sent

After three hours of trying to find a fix for the notification glitch, I arose to the solution that it was a permanent bug, however seen many reports of clearing the cache to help

Assuming it was the system cache, I powered the phone down and booted into fastboot, then into recovery using a tutorial found on YouTube

I got into the F:/Cache partition by moving the cursor down and selecting "Wipe Cache Partition"

The process was taking longer than expected, so I powered off the phone in what I feel is a catastrophic failure

Problems:

Bootloader is corrupt with only showing the "dead" android with it flashing slow and constantly

Unable to access recovery mode anymore (see above problem)

Able to access fastboot, but no USB Debugging is turned on

ADB can't access the device (most likely because of the USB Debug. turned off.)

I am NOT rooted and DO NOT have a custom ROM like CyanogenMOD

is there any helping the poor thing or do I have to send it back? Thank you for reading if you got this far.

sincerely,

J
[Android Q&A, Help & Troubleshooting] dapezzz:
Hello

I did the same thing and fixed it by plugging the phone in fastboot mode and typing the following command : fastboot erase cache

I was then able to go back to recovery and flash a full stock rom with adb sideload

Hope it does the trick for you
[Android Q&A, Help & Troubleshooting] wolfboytech:
Thank you for your reply.. TBH, I have no idea how it works, but it does all of a sudden. The first thing I did, tho, was enable USB Debugging. Goddess this was a long and tedious possess that I hope I don't have to go through again.. This is a great case and point where Apple wins in simplicity. But, yes, to that hater who's reading this: I did know what I was doing, I've rooted many androids before, I just got careless.
[Android Q&A, Help & Troubleshooting] ultramag69:
Only when Apple works, had my little brother pulling out his hair trying to get an iphone to downgfrade after the upgrade pretty much pissed all over the actual using of the phone for calls... To make matters worse, it was his work phone and he'd just got through updating everyone's phone at the company...

Simple way to go bald and loose a job....
[Android Q&A, Help & Troubleshooting] KillerNo2:
Actually it depends on how much you want to get out of your phone. The more you get the trickier it gets. Most people won't run into those troubles because they just got what manufacturers give to them.
[Android Q&A, Help & Troubleshooting] c_/\/\_k:
there is nothing like stupidity in this bro... this is all about curiosity..these problems makes you more aware of ur device and what andriod development actually is.. getting into these problems and solving it gives a great pleasure and confidence in urself.. which APPLE can never give. m sure every android geek is gone through this problem.. so be happy and proud bro.. happy new year.
[Android Q&A, Help & Troubleshooting] intelprakash:
Exactly bro! In learning about androids full potential, its all about trial & errors. By the way, speaking of Apple. IPhones are too simple for advanced users/geeks like us [emoji12]
[XDA Assist] Androidfixer2k16:
I recently bought a elephant m2 for myself but after a hour of use it stopped working can anyone help me. Thanks:)
[XDA Assist] :
I have a rooted moto e xt1022. After flashing and installing new ROM, sim card is not detected and even the IMEI number is not shown.

When I type *#06# to check IMEI number a blank IMEI screen is shown.

I have got cyanogen mod 12.1 installed on the phone.

Please give a solution to this problem.
[XDA Assist] OfficerJimLahey:
Hello, and welcome to XDA! :cowboy:

Appears to be corrupted EFS. Always bad news.

This should be useful:

> Motorola Moto E > Moto E Q&A, Help & Troubleshooting > No network/wifi/bluetooth

If not, you can post how your problem differs in the same thread (once you have an XDA account).

Hope this helps, and good luck!
[Windows Phone 8 Development and Hacking] Riyad_:
Here is the procedure to permanent unlock ur lumia device.

1st interop unlock ur device...Check This link - http://xdaforums.com/windows-phone-8/development/xap-vcreg-lumia-reg-editor-live-interop-t3135326

2nd now download the file...

Interop unlock archive.zip

Download Here - View attachment 3605285

U will need a pc/laptop to do this hack.(i hope u have one or managed one ;) )

Now extract the zip file..u will find 3 files ..

1) 7zip.exe

2)vcreg 1.2.xap

3)reg entries.txt

Now install 7zip in ur pc. No need to open the software.

Now connect ur interop unlocked phone with usb and deploy vcreg1.2 in ur phone with any deployer.

No need to install that again if u alredy installed the app earlier.

Now open the vcreg 1.2 app in phone...click on( ••• ) ...then press template .. Now mark the live full file system access.then press apply...

Ok it will show complete...

Now Restart ur phone and connect it to ur pc..

*******It will take some time to show/detect the phone.(keep calm)

(again keep calm.don't be mad if it took so long :p ) ********

Ok when ur pc detect the phone.go to (Ur phone>Phone memory>windows>packages>registry files) folder..now u will see many registry files.

Warning:: don't play with those files.

Now scroll down and copy the (software.reg ) file from the folder to ur pc.

Now the main work begins.

Right click on the software reg and open it with 7z file manager(not 7zip)

Now u will see (software) file in 7zip fm...again right click on it and select edit...

A notepad tab will open with some text.scroll down and goto the end of the text.

Then open registry entries.txt file i provided with zip.and copy the whole text from reg entries.txt.

And paste the texts under the software texts.

Now press ctrl+s.

Press ok...again ok...

Now copy the modified software.reg and paste to( Ur phone>Phone memory>windows>packages>registry files)

Press yes if u see any warning.

Done. Enjoy the unlock device forever. :D

Here is a Oemsettings procedure..thanks to [MENTION=7102782]rickk182440[/MENTION]

Hey , that's the way to have Interop forever on windows phone 8.1 and also the windows 10 mobile , get tested , it works !, even after upgrading to Windows 10 mobile and make hardreset , it continues with the Interop done, and a few more alterations . Only add these records in OEMSettings.reg and format that will be with Interop :D

View attachment 3608883
[Windows Phone 8 Development and Hacking] augustinionut:
You mean this ? OEMSettings.reg
[Windows Phone 8 Development and Hacking] megasounds:
This does NOT work for the Lumia 950XL

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

be carefull !!!

Link - http://bdupload.net/r80ow5343sjy

this link contain a Trojan virus

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Windows Phone 8 Development and Hacking] derausgewanderte:
not saying that the OP is actually working or maybe simply repeating old stuff. However, realize, that the 950XL runs W10M. The OP was posted in the WP8 section.
[Windows Phone 8 Development and Hacking] magical_ua:
why i cannot copy modified file software.reg to ]( Ur phone>Phone memory>windows>packages>registry files)

(you do not havve permision to creat this item) so can u show me how to open permision to can read and write file system ,thanks alots
[Windows Phone 8 Development and Hacking] AshleyT:
Thank you for this useful post!

The file is very difficult to download and is detected as malicious (false positive) by Google Chrome and Windows Defender.

I've attached the file with the needed registry entries to make the download easier.

Also, you can download 7-Zip here: 7-Zip Download

And vcREG here: [XAP] vcREG:Lumia Reg Editor+Jailbreak (interop unlocking ,fs access) No SD,WP8,W10M
[Windows Phone 8 Development and Hacking] matgras:
which virus scanner are you using? it may be a false positive.
[Windows Phone 8 Development and Hacking] Riyad_:
It's not a virus..this is false positive i think.. And if u have permission problem to move software.reg.then Try to copy the original software.reg file to ur desktop then modify that and paste it again in ur phone... Or for admin access to all folder u can download admin access app from net.. :)
[Windows Phone 8 Development and Hacking] Riyad_:
And sry for late reply... My exam is running..thats whay i can't come to xda. Sorry for that folks :)
[Windows Phone 8 Development and Hacking] AshleyT:
Hello!

Can I do this also on Windows 10 Mobile? If yes, I have no software.reg on my Lumia 930, can I use OEMSettings.reg instead? Thank you!

I was having the same permissions problem when I had to replace the reg file using MTP, so I used SFTP connection (possible only on W10M) to replace the file and it worked flawlessly!
[Windows Phone 8 Development and Hacking] Riyad_:
yes u can if there is no permission isuues.bcz some devices doesn't give access to edit oemsettings.reg..that's why i choose software reg
[Windows Phone 8 Development and Hacking] vali20:
Does this method allow you to interop unlock a device without an SD card on Windows 10 Mobile, and then revert back to Windows Phone 8.1 and still keep the interop unlock? Anyway, thanks for a great tutorial.
[Windows Phone 8 Development and Hacking] Riyad_:
its not the tuorial for interop unlock any device mate.it's just a method to permanently unlock ur device..bcz with the VCreg method if u unlock ur device..then reset ur phone the phone will lock again...so if u want to remain unlock ur device after reset this trick will help..and if u roll back to 8.1 from 10..u have to unlock ur device again
[Windows Phone 8 Development and Hacking] Riyad_:
Post updated...
[Windows Phone 8 Development and Hacking] rickk182440:
OEMSettings

Hey , that's the way to have Interop forever on windows phone 8.1 and also the windows 10 mobile , get tested , it works !, even after upgrading to Windows 10 mobile and make hardreset , it continues with the Interop done, and a few more alterations . Only add these records in OEMSettings.reg and format that will be with Interop = D
[Windows Phone 8 Development and Hacking] rickk182440:
Even after upgrading to Windows 10 mobile and make hardreset , it continues with the Interop done, and a few more alterations .
[Windows Phone 8 Development and Hacking] augustinionut:
What is this ?

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FileSystem]

"SymlinkLocalToRemoteEvaluation"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SecureBoot]

"AllowSigningPolicyExtension"=dword:00000001
[Windows Phone 8 Development and Hacking] rickk182440:
This is for the Interop , this is block issue for loop in the Hard reset

---------- Post added at 11:28 PM ---------- Previous post was at 11:27 PM ----------

This registry from the Rom WindowsMania.pl
[Windows Phone 8 Development and Hacking] rickk182440:
new registry OEMSettings , 1.1

hey , update my file for this file
[Windows Phone 8 Development and Hacking] augustinionut:
Please explain why...new capabilities to unlock?
[Windows Phone 8 Development and Hacking] alexche77:
HELP

I am not able to paste the file back to the system :/

NVM,

My problem was that i used vReg 1.5. 1.2 must be used
[Windows Phone 8 Development and Hacking] Satirus:
Can't access anymore MTP or filesystem on this build 10586. Any coincidence?
[Windows Phone 8 Development and Hacking] reksden:
this don't working on windows 10 mobile)
[Windows Phone 8 Development and Hacking] Satirus:
Well, i did this previously on earlier builds before this terrible 10586. My point is this awful build.
[Windows Phone 8 Development and Hacking] droidzer1:
I'm having a hard time understanding why after adding 177 kilobytes of text into the software with 7z file manager that when it saves the file is now a couple hundred kilobytes smaller than it was before adding the extra text? I'm afraid to use that software.reg file now under these circumstances. Either the 7Z file manager is using a much tighter compression algorithm or something is not right. Any thoughts on that? I'm fairly certain I'm doing it right as I understand that 7Z first decompresses the software.reg from a hex format to readable text, you then add the new text of reg settings below the rest and then save which turns it back into hex (compressed) and you have your new software.reg. Weird that it is smaller by a lot - from 736kb to 566kb. ???
[Windows Phone 8 Development and Hacking] droidzer1:
I decided to risk making both mods to software.reg and oemsettings.reg and rebooted with no problems. I see the lines in there that give the unlock. Weird thing is still that software.reg got smaller and yet adding text to oemsettings.reg it got bigger when all was done. I did make sure I was adding to the software.reg and not overwriting what was already there. I could see the 'software' file was bigger than before but after being recompressed to 'software.reg' it was smaller :confused:
[Windows Phone 8 Development and Hacking] augustinionut:
The problem is not reboot. Is hardreset :)
[Windows Phone 8 Development and Hacking] here_982:
This unkock is for the network lock?
[Windows Phone 8 Development and Hacking] zgomot:
Any way I can check if this was successful save for doing a hard reset? I used the OEMSettings method since my Lumia735 doesn't have the software.reg file.

My device shows these keys:

“CapabilityClass”=”capabilityClass_DevUnlock”

“PrincipalClass”=”principalClass_DevUnlock”

but I saw somewhere they also have that Internal at the end.

“CapabilityClass”=”capabilityClass_DevUnlock_Internal”

“PrincipalClass”=”principalClass_DevUnlock_Internal”

Does this mean I am not permanently unlocked?
[Windows Phone 8 Development and Hacking] dodobila:
Nokia Lumia - Mass Storage mode allowed me to paste OEMSettings reg
[Windows Phone 8 Development and Hacking] alexche77:
This works, but i cannot paste files on my Data/Users/Public/ directory.

Windows explorer just hangs and crashes.
[Windows Phone 8 Development and Hacking] Satirus:
Am fully InteropUnlocked with my phone and i cannot copy files sayin' that i don't have permission
[Windows Phone 8 Development and Hacking] Satirus:
It says in a message box that storage is protected against recording. Anyone has a way to bypass this kind of protection against recording?
[Windows Phone 8 Development and Hacking] Satirus:
Found the only solution: wpinternals!
[Windows Phone 8 Development and Hacking] nate0:
I did a search on this thread...is this only for Lumia models?
[Windows Phone 8 Development and Hacking] Weltenbummler:
How2 do this on linux i want to install android on lumia 535 plz help me thx for all
[Windows Phone 8 Development and Hacking] Riyad_:
u can easily do this trick on ur windows10 mobile by SFTP or CMD access..