yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Accessories] musz:
Can consider this wallet sleeve. ROCK Universal Wallet Case
[Nexus 6P Accessories] Maave:
I got one of these cheap phones cases off AliExpress for under $4. A knockoff of the kind that iuserman posted. It's a complete turd. It was way too thick, left-handed use sucks, and when it's flipped around so that you can use it left-handed it blocks the finger print reader. I woudn't get another flip wallet case ever. A non-flipping one would be OK but I think the finger print reader gets in the way of that.
[8525, TyTN, MDA Vario II, JasJam ROM Development] samw52000:
Not sure if this is a design function but everytime I turn the device off it returns to Today's screen.

Actually even when I toggle to screen in WMP and turn the screen back on the PPC throws me back to Today.

I initially thought it was a problem with my ROM (LSG then Custel 1.3) but after flashing to VP3G 3.0 on my 8525 (I have both an 8525 and TyTN) and without anything else installed it does that.

Any ideas if this can be changed? I'd like to open app to stay visible.

Thanks in advance for the help.
[8525, TyTN, MDA Vario II, JasJam ROM Development] Bensat:
I really don't have this problem on my ROM, see signature. I have especially tested it for you to be sure.....;)

Perhaps flashing 1 device to a different ROM. Can you see it yourself.
[8525, TyTN, MDA Vario II, JasJam ROM Development] samw52000:
that's what i figured so I had my 8525 that was running WM5.

I HardSPL, SuperCID it then flashed it with VP3G.

There is nothing else on the phone but my exchange and pop account setup, owner info and basic stuff like this.

I also have the clock shown on every apps and the extended rom unlock/mounted (though it does it with or w/o).

My TyTN is running Custel 1.3.

I just can't think what could be causing the device to always minimize open apps when the phone is turned off (standby).
[8525, TyTN, MDA Vario II, JasJam ROM Development] Mister O:
It seems that some plugins force a redraw of the today screen when coming out of stb. Nothing much to do but turn off the offending plugin.
[8525, TyTN, MDA Vario II, JasJam ROM Development] jompao:
Go to settings/today and on tab for objects remove the flag for timeout. Problem gone.
[8525, TyTN, MDA Vario II, JasJam ROM Development] HunterST:
Nice try, no prize - problem not gone.

This appears to be a WM6 "feature".

This discussion exists in another xda thread here, and in a Microsoft forum here.
[8525, TyTN, MDA Vario II, JasJam ROM Development] secuspec:
This is a really annoying "feature" of WM6. So far no answer in the Microsoft forums regarding this. Would be glad if i could return to exactly the screen where i switched off the device or in which the timeout forced it to suspend.

If it is not possible to fix this with a registry hacking, would it be possible to develop a small helper application which saves which application was open before the atual suspend takes place and upon a wakeup reads this information and switches to the last active window ? The app itself is still active, isn't it ?

Regards,

Secuspec
[8525, TyTN, MDA Vario II, JasJam ROM Development] ericc191:
Wait. So what exactly happens? I also used vp3G 3.0 and let's say I have Resco File Explorer open and my phone sits idle for 1 minute and goes into standby mode.. when I press the power button to make the screen turn on again, it still shows Resco File Explorer for me.. Is the bug causing it to go back to the today screen every time the phone goes into standby mode?
[8525, TyTN, MDA Vario II, JasJam ROM Development] samw52000:
if a program is left open when the device is turned off (or screen "muted") the program will be minimized when you turn the Pocket PC back on (you're kicked back to Today).

Glad I'm not the only once having issues. Thought it may be a design (flaw) but IMO it's a crappy one. Wish someone can find a fix.
[8525, TyTN, MDA Vario II, JasJam ROM Development] samw52000:
interesting, it looks like if you remove the device password it doesn't minimize the apps. kinda weird IMO.
[8525, TyTN, MDA Vario II, JasJam ROM Development] MikeChannon:
Isn't that what you would expect if you have a device password set!?

Mike
[8525, TyTN, MDA Vario II, JasJam ROM Development] HunterST:
ericc - that's exactly the problem. Are you sure you're really going to "sleep", and you aren't just seeing your backlight turn off? (you should have to hit the power button to wake it back up).

Especially annoying when driving with navigation software - I want to just turn it on and see what I saw before it went to sleep.

MikeC - that's a very interesting point. I have exchange push email going, and my system administrator pushes restrictions onto my phone... I use Zenyee Stayunlock to allow me to change the ridiculous 5-minute lockout to something more reasonable.... perhaps either the device lock or Zenyee is the culprit.
[8525, TyTN, MDA Vario II, JasJam ROM Development] samw52000:
Actually not really... my Windows workstation locks I expect to see the program I had maximized still on screen not all down in the toolbar minimized. IMO that doesn't make much sense (and even if it did they should have an option to select the default behaviour).
[8525, TyTN, MDA Vario II, JasJam ROM Development] jompao:
Works fine on my Tytn with WM6 official Swedish. I don't have a device lock enabled btw.
[8525, TyTN, MDA Vario II, JasJam ROM Development] samw52000:
yes if the lock is turned off the programs will stay open and full screen on resume/screen toggle.

Problem seems to only take place when the device lock is enabled, no matter how long the lock period.
[8525, TyTN, MDA Vario II, JasJam ROM Development] sojakim:
Thanks for the hint samw52000! That perfectly worked for me :-) And it also sped up a lot of programs directly after wake up -what makes perfectly sense since no other program is interfering anymore.
[8525, TyTN, MDA Vario II, JasJam ROM Development] taticneb:
Long time after last reply, but still no solution.

I notice if time in suspend mode is longer that programmed in settings/Lock/Prompt if device unused for... (if you have to tap your password) then screen is same as before suspend.
[ONE Q&A, Help & Troubleshooting] berdey:
Dont know which ROM starts to dev the 6.0 base one.

Hope to test and enjoy it.

Thx.
[ONE Q&A, Help & Troubleshooting] parker09:
Apparently this one but I'm sure a lot of others are trying as well.

It's only been out for a short while so you have to give developers time to do this sort of stuff, I'm sure they have other important stuff to do.

http://xdaforums.com/oneplus-one/orig-development/caf-aosp-aosparadox-project-1-0-20150906-t3195245
[ONE Q&A, Help & Troubleshooting] berdey:
Thx a lot for your information.

:D
[ONE Q&A, Help & Troubleshooting] maxmuiz:
It's 5.1.1 instead of 6.0, I've tried and replaced it immediately ... Finally I found and installed 6.0 but not from this one. The file was aosp_bacon-ota-eng.hamster.zip but I have to find the gapps ex Nexus 4.
[ONE Q&A, Help & Troubleshooting] Seagorilla2:
Running aosp_bacon-ota-eng.hamster.zip now as primairy on multirom (TWRP). Moved CM 12.1 nightly to secondairy. Had some difficulties with installing Gapps (mm) in TWRP, but Slim_zero_Gapps beta for 6.0 installed just fine. Supersu 2.52 beta too. I find it pretty smooth for a experimental version. I replaced launcher with latest Nova launcher. Not working: Xposed framework, Titanium Backup Pro, Double tap to wake-up, and advanced reboot menu. I don't use themes so no clue on that one. Muzei is fine for me. Stock camera gives error when closing, but other camera's work fine. No issues with gallery.
[Moto X Q&A] jbaumert:
Does anyone have an alternate download for: XT1055_GHOST_USC_5.1_LPA23.12-21-1_cid9_CFC.xml.zip - the US Cellular variant of the Moto X.

There was a link here: http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 - but it is now broken.

Thanks
[Amazon Fire Phone] ethereal123:
I dont understand what happened to my Fire phone. All I can see is Recovery mode options( reboot system now, apply update from ADB, wipe cache, factory reset) and No command red triangle below. What I did is following:

-connect via USB to computer

-copied photos and videos to PC

-left it connected to PC and went out for an hour to let it charge

-came back and I see this blue menu

-tried factory reset/wipe but after amazon logo loading it will come back to this menu

Phone was previously rooted using king root (super SU) without any issues.

What a ****ty phone! What shall I do. thanks for the help.
[Amazon Fire Phone] MrSalue:
So you see the recovery? if yes then just wipe factory/data / cache then reinstall CM11
[Amazon Fire Phone] samuraix21:
Well, the first thing you should do is to create this thread in the correct forum...
[Amazon Fire Phone] ethereal123:
thanks for the reply. How do I install CM12 or fire phone stock ROM. I don't have custom recovery installed. My computer cannot see phone via USB anymore. I also installed drivers and tried to push stock rom via adb but I get error device not found.

Is there a way to pull out battery. I had to left phone at recovery screen all night and is now completely drained.
[Amazon Fire Phone] MrSalue:
you need phone to be on to install CM11 and recovery :(

but if you want to remove battery this video might help " i never tried to do it my self "

https://www.youtube.com/watch?v=4U5oMcXDX0w
[Amazon Fire Phone] ethereal123:
is there a tutorial to install recovery and CM11. I can turn on phone into stock recovery but dont know how to install custom recovery and ROM.

thanks
[Amazon Fire Phone] jack9955:
Once you get your phone back up running Fire OS, you can follow romario3600 post Installing Root, Safestrap, CM11, if you want to try out CM11.

---------- Post added at 01:40 PM ---------- Previous post was at 01:32 PM ----------

I don't think you need to remove your battery. Recharging your phone and and reinstalling Fire OS should get your phone back working. When the USB driver is installed correctly and the computer cannot see your phone via USB, you need to manually update the USB driver. Following the steps below to install Fire OS and if needed to manually update the USB driver.

1) Download the Fire Phone software update for your phone and move it to your ADB folder. If you like, you can rename the file to update.bin.

2) Power off the phone. Turn the phone back on by pressing and holding the Power and Volume Up buttons until the Fire System Recovery screen appear.

3) Use Volume down to reach "Apply update from ADB" option, then press Power to select the option.

4) Plug your phone into the computer. The drivers for the phone should be installed. In Device Manager, you should see either "Android Device or Kindle Fire> Android Composite ADB interface>", if not, right click SD4930UR or the device (Unknown device) that shows up when you plug your phone into the computer. Select Update Driver Software> Browse my computer for driver software> Let me pick from a list of device drivers on my computer> select either Android Device or Kindle Fire> Next> Android Composite ADB interface> Next> Yes> Close>.

5) ADB should now detect your phone, if not, see How to Setup the Fire phone for ADB.

6) On your computer launch ADB and and type the command ADB sideload "type the filename of the update here" (Note: you can copy and paste the filename). When the phone display "install from adb complete", press the Power button to select "reboot system now". The phone should update to Fire OS
[Amazon Fire Phone] ethereal123:
thanks! I will certainly try tonight and let you know ! cheers
[Amazon Fire Phone] ethereal123:
You rock man!! thank you so much!:):):)

Thank you for the tips and guide especially installing drivers. My phone is up and running fireOS. I will stick with fireOS for the time being till CM11 gets more stable.
[Amazon Fire Phone] jack9955:
You're welcome, I'm pleased to hear the installation went well.
[Amazon Fire Phone] ethereal123:
Thanks it worked like charm!! :):):):)
[Amazon Fire Phone] madushan1000:
If anyone is wondering, Holding the power button for 10-20 seconds force power off the phone. Plus don't leave your phone in the recovery screen for long periods of time because that might damage your lcd.
[Nexus Player Q&A, Help & Troubleshooting] Steelsky78:
Hi I just got the nexus player and just had a few questions can you flash your nexus player and use any of nexus player factory images? Meaning I am on 5.1.1 know and I want to try 6.0 if I flash my nexus player and use 6.0 factory image to go to 6.0 and I find out I do not like it can I use the same method to go back to 5.1.1 ? Or even go to one of the lower nexus player factory images?
[Nexus Player Q&A, Help & Troubleshooting] hartleyshc:
Yes.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Kannz2:
Someone showed me the thread with the 12.1 cm rom and the .img for the recovery is it okay if I use flashify to put the recovery on my phone instead of using odin after rooting? Or does someone have a .tar recovery for the L520 in a drop box somewhere? :) also do I need to update my firmware before flashing a rom? I think I'm on firmware na7 on 4.2.2
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] zacktack:
it's fine, trust me use flashify. Odin doesn't flash .img files. No, you don't need to update your firmware, it's going to be flashed over anyways.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Kannz2:
Seemed to work fine. That cm 12.1 rom still working okay for you?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] zacktack:
There's a few little annoyances but it's working okay otherwise. I get an exclamation point by my bars sometimes and have to reset the apn to fix it. GPS has some issues so it's become more a roadmap than actual guidance and I can't send mms but that's not really an issue as I have unlimited data and can just facebook messenger as a workaround. I hope that these issues get fixed but I understand that alot of 5.1 roms have issues with the exclamation point thing and even some unrooted 5.1 phones have the problem. It would be nice to see a fix for these issues but I don't see anyone making any more roms for this phone and the guy that made this rom seems to have landed a job with cyanogenmod and is too busy to update this rom. What a shame but at least I have 5.1 now.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Kannz2:
Hmm I suppose I'll stay at 4.2.2 till I feel like flashing 12.1 thanks for all the info. You don't have any overheating issues or random restarts right? Also how does the GPS not work well?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] zacktack:
No overheating or random restarts. All things considered its a pretty smooth rom if just a little incomplete. I only tried using the GPS once and it came up with my location and the route for where I needed to go but when i was driving along the GLS was not updating my location. It may have been just a one time thing, idk, I havent needed to use GPS since.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Kannz2:
Cool do you know a way to go back to stock if I don't like the cm 12.1 rom? :)
[Security Discussion] danp12:
I was not thinking and I sold my phone on Ebay, whats worse is that it was bought by someone out of the country. I didn't think much about the consequences until the nagging question of why someone would buy a phone that will only work on a carrier here in the states, US Cellular. Now I am very concerned. The buyer has already paid for the phone and for shipping. My number one option could be to just cancel the sale and refund the buyers money and eat the shipping. I have began researching how to securely wipe an Android phone and the best answer I have found is to encrypt the phone before I do a factory reset. The problem is that I have already factory reset the phone. In fact, the phone was rooted and rommed and I Oddined the stock recovery back onto the phone. Here are details about the phone. It is a SM-N900R4 US Cellular Samsung Galaxy Note 3. Since I bought the phone new from the carrier I have installed and wiped numerous Roms. I'm not looking for anyone to stick there neck out there and give me guarantees, I just want to know if there is anything I can do to be reasonably sure that the phone is secure. What about apps like IShredder, are they worth the effort. Any advice would be greatly appreciated. thanks
[Security Discussion] danp12:
Update, its 5:00am, I encrypted the phone, installed ishredder, ran the app a couple of times. I rerooted the phone using cf autoroot, downloaded a simple data recovery app, and am finding old data :( Any advice would be appreciated, thanks.
[Security Discussion] csoulr666:
I think a factory reset is quite enough, you can wipe the internal storage as well. Just use Odin to flash a stock firmware and recovery and you should be good to go
[Security Discussion] nutpants:
If you are extra paranoid

Fill the memory with data.

Data and cache partitions are the most important.

Fill it with anything, delete it and fill it again. Seven times.

That will make it as hard as possible to recover any info.

But unless your a giant ass that has annoyed thousands around the world, put all your personal info on your phone. Advertise that fact.

Then be silly enough to advertise to all your enemy's that your selling your phone on eBay...

The standard wipe will likely be enough.
[Security Discussion] danp12:
So I made the decision to refund the money and cancel the sale. I am shocked at how easy it is to find pictures, contacts, documents etc. after I encrypted the phone, deleted the data, used iShredder and wrote the drive at least 20 times at 3 cycles per time. I run a simple app called Disk Digger and I can still find data on the phone. Unreal. I think the iShredder app is simply not writing data in all of the areas of the phones memory. In fact, the more times I run iShredder and the more times I run disk digger, the more data I find :( This phone is connected to so much info like Paypal, Amazon, email, Bank Accounts etc. What a shame, my recommendation for anyone is the first thing you do when you pull your android phone out of the box is to Encrypt the drive, that way down the road when you delete the keys your data is safe. I have unloaded phones in the past but I never really thought much about it until I just really felt like the person buying it was buying it for nefarious purposes.
[Security Discussion] nutpants:
Nothing from apps is stored on the internal sd card.

It's all stored on the data and cache partitions in the internal memory.

Partitions you can't touch without root.

There will always be data of some type left in the memory.

That's just how the memory works.

I have yet to find anything that will wipe the entire device properly automatically..

It has to be done manually.
[Moto X Q&A] Corsario_Negro:
After many months, I was able to find the right Lollipop firmware for my carrier (Movistar Chile). Installed without a hitch, took an OTA for the Stagefright bug, said yes to Google's 'restore apps', and then proceeded to root.

After that, I did what I always do, which is integrate updates to system apps with Link2SD. But it came to a point where I could not integrate any more, because the /system partition was full. So I started eliminating bloat like Google+ and turning some non essential things into user apps.

After a lot of tinkering, I ended up with about 103mb free out of the 1.38GB /system partition, which is only like 6% so I'm a little worried that this may cause problems in the future.

Did I do something wrong? Do other 2013 Lollipop users have this little free space as well? Is it because of the OTA update?
[Moto X Q&A] _that:
I'd guess it's because you moved stuff to /system? :)

The only problem that low space on /system can cause is that installing future updates may fail.
[Moto X Q&A] Corsario_Negro:
Exactly, and right now I'm not sure if I'll be able to install the Xposed modules I need (want to try the cell standby bug fix module but it says I need good amounts of space).
[Nexus 6 Developer Discussion [Developers Only]] chairshot215:
I know I have just asked some rather Simple Kernel Questions and honestly as stated as always worked as part of a dev team and was never the Kernel Guy but with that said have always wanted to build an AOSP Rom based on the Code Aurora source. Not caf like CM or anything with all kinds of features and what not but just pure AOSP. Thought I would ask if anyone else would be down.

The Rom would be pure AOSP based on Code Aurora repository’s only. Have always wanted to look into doing this and looking into how to go about it.
[Nexus 6 Developer Discussion [Developers Only]] doitright:
Ok, first off, some useful descriptions;

AOSP: The source code provided by Google. This is directly buildable for Nexus 6 just by following the instructions.

CAF: The source code provided by Qualcomm, which typically involves *some* degree of feature addition, but mostly HARDWARE bringup.

The odd thing about the relationship between AOSP and CAF, is that they are both each other's upstream. I think I would classify CAF as being somewhat more of "experimental" code.

CM: a complete and utter MESS. It takes bits from here, bits from there, and throws in a jumble of other bits... none of which really work well together or were intended to be merged in that way.

Basically, CM is not so much a build of CAF as they pull in certain *parts* of CAF. So if you did a build of PURE CAF, it would much more closely resemble a build of AOSP.

Now is CAF buildable for Shamu? Hmm, sortof.... maybe. They do pull in AOSP, but I don't think they actually work with Nexus devices so much as their own internal development devices, and certain specialty "dev" devices like Dragonboard 410c. What that means, is that you will probably want to start off with a *generic* apq8084 manifest from https://www.codeaurora.org/xwiki/bin/QAEP/ under the "release" branch. You will then need to mess around with the blobs and kernel, add a shamu device tree, etc., and what you end up with at the end, will strongly resemble a pure AOSP build, but probably have a few things broken or unstable.

IMO: For something like Shamu, you don't really do a pure CAF build, since google has already selected and stabilized the appropriate parts of CAF for you. But if you see some new or not-included FEATURE in CAF, then you consider pulling that specifically into an otherwise AOSP build.
[Nexus 6 Developer Discussion [Developers Only]] Yoinx:
It's funny... I've had people argue this with me in the past few weeks...

This is pretty much exactly my understanding of it as well.

The biggest difference between AOSP/GoogleSource & CAF for me, is that CAF is much more lively... typically. Google puts out source on their Public Repos, but it always reflects their latest release. I'm sure they have internal repos that are more lively... But the public ones are usually stagnant until a new release.

Of Course, stock roms (even for us) include a lot of vendor blobs that AOSP don't.
[Nexus 6 Developer Discussion [Developers Only]] doitright:
Yep, that is pretty much why I used the term "experimental".

You do know that google provides the vendor blob archives, right? That is, the parts required to make the AOSP build fully functional on Nexus hardware. Those vendor blobs don't include any of the googly bits in the userspace layer (i.e., gapps).