yashsingh1/xdaforums huggingface dataset:
[Droid Turbo 2 Q&A, Help & Troubleshooting] Zeljko1234:
Then Force is not the best device for you, unfortunately (lack of LTE 13) :(
[Droid Turbo 2 Q&A, Help & Troubleshooting] mklop013179:
I also LOVE the inability of people to Freekin Read... Turbo 2 T W O not Moto X Not the same phone ROM... Not the same phone. Not the same radios... NOT THE SAME. Turbo 2's model number is xt1585 Kenzie... All other Kenzies reffer to the Appearance of the phone famliy. And possibly the nickname of the coder who wrote the ROM... For the Love of God or whoever... Let's start a "Root for xt1585" thread and KEEP it xt1585. This situation is how Bricked Phones are made.

---------- Post added at 02:23 AM ---------- Previous post was at 02:22 AM ----------

If y'all don't (more like refuse) to sort these issues by model number of device... The combimed Intelligence of the entire community is a failure...

---------- Post added at 02:25 AM ---------- Previous post was at 02:23 AM ----------

So PLEASE devs... Please make time for the xt1585 and use the model numbers. And boot comments about irrelevant devices. Thanks
[Samsung Galaxy Core Prime Guides, News, & Discussi] 2xMakina:
Out of curiosity, how does this affect the "phone unlock" feature? In case I want to change providers?
[Samsung Galaxy Core Prime Guides, News, & Discussi] bogarty:
It won't affect it at all as long as you don't delete the "Device Unlock" app. More info on unlocking your device here:

http://xdaforums.com/showthread.php?p=63729887

Also, you can just install SlimPickins if you want an already debloated rom. :)

http://xdaforums.com/showthread.php?p=63868639
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] vitortakeda:
I've been using Gnabo v_7 version for quite a long time, and a very simple and beautiful day when I woke up my Samsung GT-N8000 was stuck on bootscreen. I wasn't able to do much so I got this "Brazil stock rom" that I found in a website, and it flashed all right, except for the detail that there is something at the screen that I haven't got a bloody clue how to remove. hahaha

And still, whenever I try to install another room, I got stuck at bootlogo and so on. I'm kinda lost here, mind a little help?

I traveled around the forum but well, I'm a little dumb so I couldn't find any proper information about, how to solve this. I would like to know if there is a way to remove this thing from the main screen, and post here the image for you guys to see it please.

I tried to post the image here to make it easier understanding, but since I got this login recently I can't =\

Thanks
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] burduli:
Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] vitortakeda:
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\

I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] burduli:
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] vitortakeda:
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.

P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\

Thanks!
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] burduli:
Here is tutorial about how to install ADB and Fastboot drivers and use them. Unfortunately, I don't know how to use it to restore efs. Sorry.
[Eee Pad Transformer Q&A, Help & Troubleshooting] kpoppema:
When I hold the power button in and release it, all I hear is a single click, then nothing happens. What could be the issue?
[Eee Pad Transformer Q&A, Help & Troubleshooting] *Detection*:
The click is the camera module iirc

Nothing on screen could mean it's been knocked or dropped, and the display cable has been pulled out

Open it up and look for the cable that wraps around the battery, when it's dropped, the battery shifts and pulls the cable out

Just push it back in (If that is the problem)
[P3600 General] chunga168:
Hi all,

I'm wondering if it's possible to use my handsfree button to activate the voice speed dial program?

The button can answer phone calls no problem, I'd like to get it to make calls too.

I'm currently running PDAViet's WM6 ROM.

I'd assume that this can be done since that's quite a common function even with old phones. :)

Thanks,

Anthony

hmmm... stupid me... it actually does work, I just gotta hold the button for more than 2 seconds... is it possible to delete this thread? :D
[Verizon Samsung Galaxy Note5] natypes:
I did this this weekend trying to watch the CoC vr video on YouTube. Well it was a tight fit and the screen turned black and I could see the colorful font so I ripped the Note 5 as quickly as I could. Too late, it had went into the bootloader (I'm guessing)and performed a factory reset in less than 2 seconds. I think it was bootloader bc I go into recovery on Samsungs almost daily at work. It takes a lot to perform a factory reset. Had it been recovery all the volume presses required to factory reset it would have saved me. Quite a pain in the butt.

I have the cardboard set b/c I bought it when I had my S6 and it is a good cardboard set, just not for Note 5.
[One (M9) Q&A, Help & Troubleshooting] Widafer:
I am using Straight Talk, and I can receive pictures from everyone, and group messages from everyone except one person. This includes iphones and androids. That one person has an iphone 5s and they use Verizon. This issue only started about a week ago, before that it was working fine. I have used an OPPO N3 and am now using an HTC One M9 and am having the same issue. I even have a new sim card.
[One (M9) Q&A, Help & Troubleshooting] shivadow:
If the same problem exists on 2 devices it makes sense to blame crap software.

I wish I stole my HTC M9.
[One (M9) Q&A, Help & Troubleshooting] Widafer:
Are you saying it is an android issue?
[One (M9) Q&A, Help & Troubleshooting] mike.s:
So, you've used 2 different phones. Both worked fine when getting messages from everyone except one person. That one person has an iPhone 5s.

I think you're in the wrong forum, and the thread should be titled "Problem sending messages from a Verizon iPhone 5s."

Really. It's an iPhone problem.
[One (M9) Q&A, Help & Troubleshooting] Widafer:
The problem is my phone, because that one person can send group messages to everyone, including other android phones no problem. I think it has something to do with me using Straight talk wireless.
[One (M9) Q&A, Help & Troubleshooting] PrizmaticSmoke:
It definitely sounds like a carrier-specific issue - you've already ruled out device-specific and OS-specific issues by using different phones and reproducing the same results, and by verifying that the person you can't get messages from has no problems sending messages to other people using android on different carriers.
[One (M9) Q&A, Help & Troubleshooting] dlads:
Turn off imessage on the iPhone and see if the problem persists
[Galaxy Note 10.1 (2014 Edition) Original Android D] Shawn5162:
Reserved

NOTE:

I am not blind...I can see the DL link doesn't work yet. Nightlies should begin rolling out within the next 24-48 hrs. for this device. Once that happens the link(s) will work.

Also HUGE thanks to [MENTION=3463426]RaymanFX[/MENTION] for the original CM tree for this device.

The maintainer for this device are:
[MENTION=5323673]Shawn5162[/MENTION] (if that wasn't obvious already)
[MENTION=4144316]joshndroid[/MENTION] (that should have been obvious too cause he is BOSS)
[MENTION=6176472]Orion116[/MENTION] (#STFUWiley ;))
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
First?

If you follow me on G+ you would see why [MENTION=5323673]Shawn5162[/MENTION] added that hashtag[emoji23]
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
The wiki says that our device name is "Lto3wifi", however it should be It03wifi. I look forward to trying this out once the download link works. Thanks for your hard work for our device!

---------- Post added at 10:08 PM ---------- Previous post was at 10:04 PM ----------

Read the op before posting (the second part, last line)?.
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
The nightlies should be f2fs ready I have added all the files
[Galaxy Note 10.1 (2014 Edition) Original Android D] benand:
That's a great news to have a team working on Our Device !

Thanks a lot
[Galaxy Note 10.1 (2014 Edition) Original Android D] machhho:
when I click on the download link , I get this message " Internal Server Error " . is it only me or the download link is dead !

thanks
[Galaxy Note 10.1 (2014 Edition) Original Android D] Shawn5162:
Is it only you who can't read the second post...
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
One word wow
[Galaxy Note 10.1 (2014 Edition) Original Android D] 88fingerslukee:
I'm vibrating off my seat for this! GIMME GIMME GIMME :D:D:D:D:D:D:D:D:D:D:D
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
I'am sorry for my bad formulation. I only wanted to ask why you starting to put more efforts in cm 12.1, if everyone waits for cm13.

It wasn't my Intention to be rude or ungrateful relating to your hard work on this project.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
Yes, there is reason. I don't have to tell you how rude this sounds. Enjoy the ROM and wait.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Shawn5162:
You got to remember out tablet shipped with Jellybean (4.3). It's old. We wanted to get official CM support ASAP and we had a stable cm-12.1 base. So we thought, why not get nighties going while we can. CM 13 (android 6.0) is putting up a bit of a fight right now. Once we get even a semi-stable build we will release it.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Shawn5162:
[MENTION=535343]all[/MENTION]

Nightlies begin tonight :)

Enjoy and once again thanks to all the people mentioned in section post!

Shawn
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Ok, i think i understand the difference. Now an official cyanogenmod Team also supporting our Rom. That sounds really good. If they could manage it, that screen mirroring will work stable on our device, i will definitively change back from touchwiz 5.1.1 rom to cm 12.1. Thanks for it.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mising:
The download is only 6mb. Is it a delta, and can it be flashed on top of Temasek's current build?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Apparently the wiki was deleted. Also, flashing this won't replace twrp with the cm recovery right?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Tiemichael:
Seems to be just a 'recovery'
[Galaxy Note 10.1 (2014 Edition) Original Android D] mising:
There are actually two downloads. One is the build and the other is the recovery. The checksums are good on both, but the full builds are normally around 200 + mb and the deltas were around 50ish mb. I'm just curious as to whether or not the upload completed.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
Boot into download mode. Home + volume up + power.
[Galaxy Note 10.1 (2014 Edition) Original Android D] TruThug407:
Yea boot in to download mode an reinstall twrp than flash da ROM your wanting to use it should be fine in my exp wit Samsung as long as it turns on it can be fixed....
[Galaxy Note 10.1 (2014 Edition) Original Android D] ddyxda:
I've spent hours trying to install TWRP or any recovery with ODIN without any luck. Always just end up the the Galaxy Note 10.1 2014 splash screen.

-Doug
[Galaxy Note 10.1 (2014 Edition) Original Android D] Starek:
Hello

What about CVE-2015-3636 kernel vulnerability

They are any schedule to patch the kernel?

Using CyanogenMod 12.1 - 20160302 - NIGHTLY - lt03wifi

https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-3636

Thanks for your hard work.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
If you have problems to install twrp with odin, try twrp v. 2.8.6.0. That should normally boot without issues. Then you can flash with twrp a newer version of twrp like 3.0.0.0 by joshndroid. If you still have problems to boot twrp, then i would recommend to restore your system. In that case use this tutorial.

Tip: After flashing a new rom with twrp the boottime could be up to 10 minutes.

Is it possible that you're coming from Samsung Touchwiz 5.1.1 stock rom without root permissions? Because in that case you need to flash the patched boot-file with twrp to be able to boot custom roms. But flash the patched bootfile only if you want to install a custom stock rom like beta6 by enotar. Otherwise use the tutorial to repair your system, install twrp with odin and flash directly the aosp rom you want to use.
[Galaxy Note 10.1 (2014 Edition) Original Android D] TruThug407:
Flash da cf auto root for our device first than boot back in to download mode an install twrp uncheck auto reboot first, than turn it off an hold power, volume up, an home button as soon as da note screen pops up let go of da power button while still holding down da volume up an home buttons for a second longer it should boot to recovery than....:confused:
[Galaxy Note 10.1 (2014 Edition) Original Android D] ddyxda:
Thanks for that, that did the trick. Now that you mention it I recall the twrp v. 2.8.6.0 thing from before.

-Doug
[Galaxy Note 10.1 (2014 Edition) Original Android D] .Sun:
Hi.

Your build (clean, no modifications, no apps, 20160529) is crashing while xposed-installer 3_0 alpha4 is installed. No framework, just the installer.

I got 2 variants of a crash:

1. reboot

2. black screen - have to wait ~2min. Then i can wake up my device and start from the lockscreen again. After i unlocked the device i got a message: *launcher* is not responding. *launcher = trebuchet and also Action Launcher 3.

If you need logs, tell me. I do not attach it, because of a clean build.

All of my other devices works fine with 3_0 alpha4 and 5.1.1. Temasek's android6 build for p600 works also with 3_0 alpha4.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Good thing this ROM doesn't support Xposed!?
[Galaxy Note 10.1 (2014 Edition) Original Android D] .Sun:
Source? Cant see this hint in startpost.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
I can't find where it says that they don't support it, however they never said that they do support it, and they disable the built in bug reporter if you use xposed. It's also well known that you shouldn't discuss xposed in ROM threads.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
I have stated multiple times in this and other threads that bug reports while using Xposed and without logs are useless to us. Try again.
[Galaxy Note 10.1 (2014 Edition) Original Android D] .Sun:
And i said that there are only crashes using xposed. -> -> It is senseless to post logs without xposed.

There are no errors in xposed-installer-log.

However, xposed works fine with other builds.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Perhaps the cm team has taken extra precautions to make sure that people don't report bugs while using Xposed. All joking aside though, the maintainers of this ROM don't seem to care if xposed works or not, and for good reason (it is an insult to every ROM dev that has ever worked hard to provide a stable ROM). If you want this issue to be fixed go to the official Xposed thread and report the issue there.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stevethegreat:
There is another reason too. It nullifies the existence of custom roms. All we now need is a stable AOSP roms and the rest of the features we get from xposed.

Xposed does not cause instability on stable roms if you don't go crazy with modules. Never had such a problem.
[Galaxy Note 10.1 (2014 Edition) Original Android D] AndyYan:
Strange, how come the bug is still there in the latest nightlies...

I tried locking the tablet into wakelock using an app, and it wakes up quickly every time, however battery consumption is abysmal with wakelocks active. Really don't know what's wrong...

Sent from Google Nexus 6P @ CM13
[Galaxy Note 10.1 (2014 Edition) Original Android D] pn1fon1:
Hi, does anyone has cracling audio problems with this cm12 rom. I did a little research and I thing I have to flash samsung audio policy zip but I couldn't find it anywhere. All the links I found had expired. If anyone has it please post a link.

Also if anyone knows I have kitkat bootloader and I flashed this cm12 rom. Is it ok or should switch to lolipop bootloader.

Thanks
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Stay on the KitKat bootloader, which KitKat bootloader are you on?
[Galaxy Note 10.1 (2014 Edition) Original Android D] pn1fon1:
I think I am at ap swrev a3 bootloader? If I am correct because I don't really now how to find out. This one I found at the odin download mode screen.

Any idea about the crackling audio bug? Should I flash samsung audio policy? I found the zip but is for Samsung Galaxy Tab S 10.5. I don't know if it's the same for p600.

Thanks
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
The tab s is very similar to our tablet, so it's safe to flash the audio policy zip, but it's possible that it won't improve it, just make a nandroid first. Type this into a terminal emulator to the bootloader version:

su

getprop ro.bootloader

Edit: there's also a zip for the p601, try it first http://xdaforums.com/showpost.php?p=68422442&postcount=143
[Galaxy Note 10.1 (2014 Edition) Original Android D] pn1fon1:
My bootloader is P600XXUCNH3.

p.s. The crackling was very small while using mx player. I flashed the tab S audio policy I mentioned and I think it did improve. So far it looks like it dissapeared. Am I the first who has this problem? By the way I flashed the new nightly today and it came back. I had to reflash the audio policy again to fix.

Thanks
[Galaxy Note 10.1 (2014 Edition) Original Android D] pn1fon1:
Hi,

Is there a way to reinstall the latest stock lollipop samsung keyboard. I really liked the del button and the clipboard function. If anyone can help I would appreciate it.

Thanks
[Galaxy Note 10.1 (2014 Edition) Original Android D] Tiemichael:
Oh, you are right!

Just downloaded the image ..., /system seems empty ...
[Galaxy Note 10.1 (2014 Edition) Original Android D] diabl0w:
that PsychoI3oy boy seems like a total dbag... i hope hes not in charge of our device

according to his own twitter hes not even a dev so idk what hes doing goin around deleting a cyanogenmod wiki even if it was only tbd
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
We are not sure why it came out as 6mb but we are trying to figure it out.
[Galaxy Note 10.1 (2014 Edition) Original Android D] SamsungGalaxySamsung:
Thanks for all the hard work! Keep it up.
[Galaxy Note 10.1 (2014 Edition) Original Android D] jmark13:
Do I need to flash Cyanogen Recovery or can I continue to use TWRP and just flash the build?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
No you don't. OTA I think works through either recovery.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mising:
Is there an alternate download location that has the full build in the meantime?

Thank you!
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
Nope because test builds are doing the same thing.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mpyka91:
Are we okay to dirty flash if we're already on CM, or should we do clean installs for this nightly?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mising:
Do not flash these nightlies yet, as they do not seem to be complete. They are currently looking into why the builds are only 6.15 mb.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
Builds fixed. After the fiz is push nighties will resume.
[Galaxy Note 10.1 (2014 Edition) Original Android D] 7786:
Looks like the newest nightly still has the same problem, 6.15mb zip.
[Galaxy Note 10.1 (2014 Edition) Original Android D] diabl0w:
maybe im being ignorant but what is making it so dificult to upload a comoleted build?

can you just host it simewhere else?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
We don't upload the builds. CM uses there build servers if they haven't merge are fix then it is their issue. Local builds are fine.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
Fix merged nighties should be fine from now on.
[Galaxy Note 10.1 (2014 Edition) Original Android D] SamsungGalaxySamsung:
Still at 6.15
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
Zip date?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
The latest nightly (cm-12.1-20151210-NIGHTLY-lt03wifi.zip) is only 6.15 megabytes.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
Wtf
[Galaxy Note 10.1 (2014 Edition) Original Android D] ruud:
yes they still are 6.5 mb
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
I again have been in contact with cm to get vendor sorted. Cm.dependencies does not list vendor in any device but for official builds vendor has to be listed somewhere. Even if it's behind the scenes. That's a big reason why it is not working, every other repo that is supposed to be there is there.

If u were to self build with the source and then add in vendor yourself it will work. As all my merges have been tested before pushing them to gerrit
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
found the issue, f2fs in device was causing havoc with official cm (cwirl thought maybe due to the block based file system intially). probably 1 word/line/something out of place. On reverting it, the file size is back up to around 250mb where it should be. Nightlies have been resumed, NO F2FS support at present
[Galaxy Note 10.1 (2014 Edition) Original Android D] Tiemichael:
Being a current user of 'lt03wifi-temaseks-unofficial-build', am I right to say that 'data', 'system' and 'cache' need to be reformated from F2FS to EXT4 before installing the CM-build?
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
yes, you are correct you must change those back to EXT4 to use this rom, once nightly has been built
[Galaxy Note 10.1 (2014 Edition) Original Android D] diabl0w:
I could have sworn that CM formats /data to f2fs by default, am i wrong?
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
Yes you are wrong. Most roms format to ext4. Devs add support for f2fs in cm or aosp based roms
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
The latest nightly (cm-12.1-20151213-NIGHTLY-lt03wifi.zip) is 232.19 megabytes!?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
Did it flash?