yashsingh1/xdaforums huggingface dataset:
[Moto G Q&A, Help & Troubleshooting] padhu1989:
Did you play any movie and check.. Or this issue only related to apps?
[Moto G Q&A, Help & Troubleshooting] PumaPerez:
just tried to stream movie to mx player and it works as suppose to :) so it looks like only apps :/

for example in this game a see black backround, but instead of icons i see those dots. this is how it should behave before kitkat. since kitkat we should have true full screen, right?

https://lh5.googleusercontent.com/-...62-h821-no/Screenshot_2014-05-02-08-38-43.png
[Moto G Q&A, Help & Troubleshooting] padhu1989:
These dots indicate the navigation buttons.. If you don't want these, you can install modules like "force immersive mode" in xposed framework...

It's not the issue..
[Moto G Q&A, Help & Troubleshooting] PumaPerez:
ok, then tell me reason why did i have true fullscreen mode since i buy the phone to like 3 days ago... was my phone defective and now suddenly is everything ok?
[Moto G Q&A, Help & Troubleshooting] padhu1989:
Check mine... See few apps, games won't go full screen mode.. Developers designed like that.. If you want full screen.. Use xposed modules..
[Moto G Q&A, Help & Troubleshooting] PumaPerez:
few days ago that app was in full screen.

also about angrybirds go. do you think developers let there that navigation bar on side, so when i want to turn right i actually quit the app? :)

i already told you, those apps where in full screen since i bought my phone. suddenly few days ago those apps wont go to full screen. something happened to system.
[General Topics] CalebQ42:
Beta!

This area is for BETA!!

Soon updating will become more regular as school is letting out this week. If you want to see my source code, I'd be glad to post my vb solution, but at this point it would just take up time I don't have much of.
[Oppo Find 7 and 7a] Allanitomwesh:
Here are the OPPO Find 7a Kernel Sources if anyone needs them from their github.

https://github.com/oppo-source/Find7-Kernel-Source-4.3
[Nook Touch General] jasonmehmel:
Hey all,

I've been working at getting USB-enabled adb working for my Nook Simple Touch. I've got adb working on my Linux laptop, and I've got an adbwireless app working on my nook. (It was part of the app bundle when I rooted and flashed the Nook with extras.)

So I can connect via adbwireless, but not via USB. My main desire to get USB working is in the eventuality that my nook gets locked. (Getting jostled in my bag can activate the PIN and cause a lockout if it happens often enough.) But I'm also taking this as an exercise in learning more about ADB.

To be clear, I've got adb installed already on the laptop, I just want to be able to detect the nook when it's plugged in.
[Nook Touch General] MildBill:
As I understand it, you have a choice with the Nook Simple Touch, you can have ADB over wireless, or USB, but not both. It is based on a setting in init.rc (which is contained inside uRamdisk)

setprop service.adb.tcp.port 5555

If this line is present, it sets the TCP port for ADB, and your NST will connect via wireless. If you comment it out (place a "#" at the beginning of the line), your NST will connect via USB.

I see that Renate gave full instructions for you on this in another thread, you should check there.

MildBill
[Nook Touch General] jasonmehmel:
Yeah, I posted this before I saw their reply. That said... I'm having a hard time following Renate's instructions clearly; I feel like I'm too new at this to fully understand each point though I am researching the questions as I have them.

So, uRamdisk and init.rc... if I've got the ES File Explorer on the nook, would I be able to track down that file and open it that way? I'm assuming uRamdisk is part of what I've used to root the nook?

(I followed instructions online to root the nook and partially understood them, but I'm still fuzzy or non-expert on a lot of what I'm using.)
[Nook Touch General] MildBill:
uRamdisk is used to boot the nook, it is actually an archive of many files, and is the actual filesystem used in booting the Nook. There were longer, more complete instructions I have seen, and followed myself, in another of Renates posts. it can be found here:

http://xdaforums.com/showthread.php?t=2122046

You would not need to do anything with with the default.prop file, as NookManager will already have done what is needed. But, you can either use noogie.img as suggested, or use ADB pull via your wireless connection to get the current uRamdisk, then follow the instructions to extract init.rc from it, modify the one line in the file, then insert the new copy back into uRamdisk and use ADB push to replace the copy of uRamdisk on your device.

NOTE that once you do this, and reboot your NST that ADB over WiFi will no longer work, you will be using ADB via USB.

There is a utility that you will need to download from Renates page (Click on her signature block, it will take you there) to extract and reinsert the init.rc from uRamdisk. Otherwise, the instructions in that post should be all you need to do the job. Read them over, be sure you have everything ready to go and that you have a basic understandng of what you are doing before you actually try it.

One more suggestion, you may want to keep 2 copies of uRamdisk on your computer, one set up for ADB WiFi (a copy of the file you will be starting with!) and one for ADB by USB (The one you will create after you modify init.rc). That way all you will need to do in the future to change over is an ADB push of the appropriate file to your device, then reboot it.

Hope this helps,

MildBill
[Nook Touch General] lcd047:
If you have ADB working over wifi and all you want is to enable it to work over USB on Linux you can probably forget about uRamdisk. You're fine, you don't need to change anything on Nook's side, all you need are a few changes on Linux. Specifically:

1. Enable permissions for Nook's device in udev. In order to do that, create a file (or edit an existing one) /etc/udev/rules.d/51-android.rules, and add a line:

SUBSYSTEM=="usb", ATTRS{idVendor}=="2080", ATTRS{idProduct}=="0003", MODE="0666", OWNER="<your_username>"

2080:0003 is Nook's USB ID, and <your_username> is (surprise!) your username on Linux. Reboot to force the changes to takes effect.

2. Create a file (or edit an existing one) ~/.android/adb_usb.ini and add a line with Nook's vendor ID:

0x2080

3. Connect the USB cable to your Nook. At that point, Linux will probably detect your Nook as two USB drives. Eject those drives.

4. Start the ADB server:

adb start-server

5. Check that ADB sees your Nook:

adb devices

If you get back something like "<big_number> device", you're good to go, you can run ADB commands. Otherwise kill the server and start it again:

adb kill-server
adb start-server
[Nook Touch General] Renate:
... and the new white Nook is 2080:0007

The latest ADB version has B&N in the list of known manufacturers.

This will not be necessary if your copy is new enough.
[Nook Touch General] lcd047:
Sorry, there's one more thing needed before ADB can work over USB: enable USB debugging. Get NookColorTools, run it, and go to "All Settings" > "Development" and check "USB debugging". After that the ADB server should be able to see your Nook.
[Nook Touch General] MildBill:
Odd, I used Renate's instructions from http://xdaforums.com/showthread.php?t=2122046 and ADB works fine either over USB or WiFi (either/or, both will not work at one time, depending on whether or not you define the port with

setprop service.adb.tcp.port 5555

).

I never had to do anything other than that to get ADB root access, but then, I don't want all the junk that the leading root managers want to add to my Nook.
[Nook Touch General] lcd047:
I just flashed my Nook to factory and went through all this from scratch, and the setprop above was not enough. Whether USB debugging actually does anything on Nook is still subject to debate among the supposedly knowledgeable people, ;) but it was needed for me to enable the ADB server to see my Nook over USB. It was also required on all other (newer) Android devices I used, so it makes at least some sense. Still, It might have to do with the version of ADB.

As for not being able to use both TCP and USB at the same time, that's a limitation of the server (it can't talk to more than one device at a time), which is why you have to kill it before switching. But you don't need to do anything on Nook to switch from one to the other (at least that's how it works for me).
[Nook Touch General] MildBill:
No, by itself it is not. But, if you read the post I linked, you make changes to both init.rc and default.prop, both contained in the uRamdisk filesystem archive, and that is all it takes to achieve root shell access via ADB on the Nook ST v1.2.1, or, at least, that is all it took for me to achieve it.

Keep in mind that the setprop as listed forces WiFi access to ADB, for USB access to it, you must leave that line commented out, again as shown in the linked post.

MildBill
[8125, K-JAM, P4300, MDA Vario General] helowsa:
After install/deinstall of two SMS-managing programs ( Smart Inbox and SmartLock ) there is no more sound and graphical notification of new text message. Any idea?

Thanks for help!

D.
[LG Optimus Black] howlog:
My phone's feather-touch buttons are not working but touch screen is working flawlessly but I am unable to close an App because of this issue. :rolleyes: Hence I am looking for a Launcher that has ON-SCREEN virtual BACK and HOME buttons (at-least). Please suggest any launchers. :D
[LG Optimus Black] tantrums:
You can use this mod by RomWiz : http://xdaforums.com/showthread.php?t=2122098

btw, you should post this in q&a.
[LG Optimus Black] Arcanium:
lash rom that surports navigation bar
[T-Mobile HTC One (M7)] colorsharpkid:
is there a way to stop this infernal vibe on call connect

i hate it plus its annoying can i repeat i hate it i do not want to live with it or get used to it

im a weirdo and this type of annoying thing is the type that eventually drives me nuts to the point of getting rid of a device its soo stupid why i cant take it off

and befor eyou say disable vibrate in sound menu

i have looked in sound menu disabled every vibe related thing i can find and in the phone settings

no wi may have missed somthing correct me if im wrong but omg i hate this it feels like its tearing my phone apart from the inside

i have never used vibrate features since i had a windows pda 10 years ago it to me is only usefull in high volume environments which i am never in i hate this i hate it i hate i i hate it

not to mention i had a iphone that eventually the vibe thingy tore up inside and would make clicking as it vibed and also on a hd2 eons ago i dont want this happen to my htc one

i see a mod but its posted in legacy devices

i am rooted and have cwm 4.3 tmobile 1.55hboot software 3.24.531.3

baseband 4a.21.3263.03_10.38m.1157.04l

kernal 3.4.10-glcbcae4root@abm010 #1 smp preempt

im keep looking but seems there is no way that i have to live with this i cant beleive it
[Xperia Z2 General] Strangeland16:
When I first got my phone when it was fully charged and taken of charge with stamina mode on it would estimate there was 5 days 8 hours battery left. Although I never got that out of it. Now whenever it's fully charged it estimates just 20 hours. Why has it done this anyone else the same?
[Xperia Z2 General] doministry:
Stamina estimates how long the phone will work on one charge based on your usage.

When it was charging the estimation was based on IDLE state, so it gave 5 days result.
[Xperia Z2 General] Strangeland16:
Ah OK so what your saying is if I'm a heavy user the battery estimates what's left for my usage. So if I factory reset it and don't use it it will be at its full potentional. That's very clear thanks for the quick reply
[Xperia Z2 General] doministry:
Factory reset? WTF. Just use it. It is at the full potential.

Do you understand the matter?! If you use it more it lasts shorter, if you use it less it lasts longer.
[Xperia Z2 General] jayc1980:
Battery estimation compared to how the LG G2 is a waste of space in my personal opinion. However I dont care as I charge my phone everynight. And it lasts me a full day
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rohanr014:
So I flashed cm 10.2 on my Galaxy S3 AT&T, and forgot to flash the right gapps, so I did that, except I forgot to do a factory reset when I flashed them. When I went to reboot, my phone would not turn on, nor get into recovery mode. It keeps showing the Samsung logo with the little CyanogenMod figure underneath it, and keeps vibrating repeatedly while trying to turn on. This is not a boot loop (I think) because my phone doesnt even get as far as the arrow animation that keeps going in circles. All I can do is access download mode. Can anyone help me? I have tried taking the battery out multple times and waiting for the battery to charge and then trying to turn it on, to no success.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Larry2999:
If you can get to download mode, try flashing a stock file via Odin to reset your phone to working conditions. Thereafter, you can go back to a custom ROM. Would you recall what firmware version you were on prior to flashing CM? If it was anything older than 4.3 (e.g. 4.1.2, 4.1.1), you can Odin back to 4.1.1. If you already had 4.3, you would need to Odin back to 4.3 following the instructions posted in the thread below ..

http://xdaforums.com/showthread.php?t=2722660&page=3. Scroll through carefully for the file you need for 4.3. Otherwise, you can find the Odin flash-able 4.1.1 stock file on sammobile.com
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rohanr014:
I have looked at the thread but I am new to all this stuff, how do I flash using Odin?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Larry2999:
First you will need to download and extract the Odin tool. Odin is Samsung's tool for flashing (installing) firmware. You can download Odin v3.07 via the link below ...

http://www.mediafire.com/download/772dlmuaxfgm0x2/Odin307.zip

Once you have downloaded it, extract the files and look for the executable file (*.exe). That's the one you will need to run to open Odin.

We also need to identify the appropriate firmware to flash. You did not answer the earlier question on what Android version your device was on prior to flashing the custom firmware. This is important to let us know which official version you can safely revert to (4.1.1 or 4.3). If you were an older version than 4.3, you should flash 4.1.1 but if you were already on 4.3, then you should stick to this. Either way, you can download the 4.1.1 file via this link .. http://rapidgator.net/file/681a28a5...ATT_I747UCDLK3_I747ATTDLK3_Original.zip.html?

Download the files to your PC and extract.

To flash via Odin, open Odin.exe on your PC

Click on the PDA tab and navigate to the file you just extracted. Select the file ending in *.tar.md5 (For 4.1.1, this would be I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5). Make sure this file is showing in the PDA tab.

Boot your phone into download mode and connect to your computer with a good quality micro-USB cable. Make sure your phone is recognized by Odin. You should see the message Added in the left pane.

Do not check or uncheck any boxes other than the defaults.

Click on start and waiting for firmware flashing to end and you see Pass. Your phone will reboot at this stage. You can disconnect from your PC

However, for 4.3, it looks like the Odin flash-able file has been taken offline so you would need to this via custom recovery. That's a different process so please revert on your Android version first so we'll know whether this is required or not
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rohanr014:
I was running JB 4.3, and I am planning to flash 4.1.1 as you've said. I am downloading that rom from the SamMobile site, however it is taking quite a while...

I understand that it shouldnt be a two minute download, however its been 2 hours and only 210 MB has been downloaded.

Also, I have Odin v3.09, which in the place of a PDA tab, there is an AP tab... should I place the file in the AP tab?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Larry2999:
Please do not try to flash 4.1.1 if you were on JB 4.3 otherwise you could hard brick your phone due to the secure bootloader in 4.3. You need to revert to stock 4.3 via custom recovery. You may go to the thread below for instructions...

http://xdaforums.com/showthread.php?t=2658486

1) Flash custom recovery (I would suggest TWRP because of the GUI). In Odin v3.09 use the AP tab in place of PDA. You can download TWRP for your device via the link below ...

http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar

2) Download the stock restore zip file in the thread above and copy to your (micro) SD card. The (TWRP) stock restore zip is also available via the following link .... http://www.mediafire.com/download/30idxwhg2hidxx2/ATT_I747_UCUEMJB_StockRestore_2282014.zip

3) Flash the custom recovery file via Odin. Remove battery immediately the flashing is complete to stop reboot.

4) Place the SD card with the recovery file in your phone

5) Reboot into recovery mode by simultaneously holding down the Volume Up, Home and Power buttons. Hold all buttons until you see the blue flash across your screen, then release power button but keep holding the volume up and home buttons until the Android image appears.

6) Select install and navigate to the stock restore file. Swipe across screen to flash and wait for installation to be complete.

7) Clear cache/dalvik and reboot to system

If you are unable to boot to recovery, then you may still try flashing using Odin v3.09. You may follow the instructions in the thread below and load all the respective partitions. You would need to use the version that has separate flashable files as the single *.tar file has been taken down.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rohanr014:
Just to reaffirm since I am not very experienced and do not wish to break my phone:

1) Download the twrp 2.6.3.1 d2att.tar file and flash it to my phone in download mode via Odin.

2)Download zip file on my computer, and take out the microSD from my phone, and copy the file to my microSD.

3) I am confused here because you stated to flash the custom recovery in step 1... anyways when flash is complete I immediately take my battery out to stop the reboot.

4) I insert the microSD with the zip file containing the stock rom

5) Now I should be able to reboot into recovery mode on my phone, though I could not beforehand.

6) Once in Recovery, go to Install and flash the custom stock.

7)Wipe dalvik cache and cache, and reboot to system.

Please clear up any confusion, I am very cautious and inexperienced. Sorry.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Larry2999:
Yes, you are correct. What you are doing in step 1) is flashing custom recovery to your phone. Custom recovery allows you install zip files to your phone and is more functional and versatile than stock recovery.

The zip file referred to in 2) is the stock restore zip. This is the file you will be flashing from (custom) recovery and is the one from the following link (http://www.mediafire.com/download/30...re_2282014.zip). Once you have downloaded it to your computer, save to an SD card so you can insert it into your phone to flash.

The battery pull is after flashing the TWRP file. You then have to boot into (custom) recovery mode to flash the stock restore zip from the SD card.

You are OK on the other steps. Trust this clarifies. Let me know if you encounter any issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rohanr014:
I have done everything you said, I flashed the TWRP file via Odin, and then i copied the stock zip file to my microSD and put it back into my phone.

I am able to boot into recovery, and everytime I go to flash the stock rom, midway through the flash my phone starts rebooting. Even if I try to clear dalvik cache and cache first, once they are cleared my phone automatically starts rebooting. What do I do now? The zip file is there and I can reach TWRP recovery, but the flash wont complete because my phone starts rebooting. I am at a 100% battery right now so I do not know what the cause of this could be. Please help, I cannot tell what I did wrong if I did do anything wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Try installing the latest version of Philz Touch for the d2lte. Some people have good results with TWRP. I found Philz Touch, which is based on CWM, better for my purposes. Philz can be installed via Odin as long as you down the tar version.

http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rohanr014:
Ok, something very strange has occured.

Since my phone would not flash the original stock rom, I decided to go ahead and flash CM10.2 and its gapps to see if it the problem was with my phone or with the file. Everything worked fine and my phone booted and ran CM10.2, but then I had absolutely no signal anywhere. I could confirm something was wrong because there were multiple AT&T users near me that had good signal. So then I went to flash the stock rom, and it worked. I cleared dalvik and cache like normal after all these flashes and performed factory resets, however when I flashed this stock rom, it worked but 1) I could not connect to Wifi 2) I could not use apps with root requirements, and Root Checker said I did not have root access, even though I had definitely rooted my phone earlier when I first ran CM11 and CM10.2

Should I root again? Please help, my phone is working and I can go into download, stock recovery, and normal mode.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Larry2999:
The whole idea was to get your phone back to working state. Thereafter, you can build up on the food chain. The stock file you flashed restores the phone to near factory settings including a complete stock (official) firmware, stock recovery, resetting the flash counter. Unfortunately, it also removes root as well. You can, however, re-root in a number of ways. You may also do as Audit advised and reflash Philz Touch custom recovery which would allow you flash any custom ROM of your choice. You do not necessarily need to root to flash custom ROMs if you have custom recovery. However, if you need to use apps which require root, I would recommend you try SafeRoot (http://xdaforums.com/showthread.php?t=2565758). Very easy to use and worked quite well for me.

Finally, you should be able to restore your Wi-Fi from settings. Wi-Fi setup should have happened during the set-up process upon reboot after the firmware installation but sometimes this step is skipped. If you go to Settings, you should be able to enable and set up Wi-Fi.
[Sony Xperia Miro, Tipo (Dual), J, E] dhruvil09:
After rooting my phone,I decided to unlock the boot loader.I unlocked it by sony flashtool but something went wrong and it was not booting up9only showing sony logo and then the booting screen).After reading some similar articles on xda i flashed the .ftf file from the flashtool but now it has worsened. It is not showing the sony logo and only the led light is blinking green.PLEASE HELP!!:crying:
[Sony Xperia Miro, Tipo (Dual), J, E] Azene:
hey dude :D

dont worry

im also had that situation when i was first time with flashtool

i think i flash the ftf about the tenth time, then it flash successfully

i think you should use the latest flashtool

also check the flashtool and fastboot driver

or use other laptop or pc

this is becuase my laptop have problem with flashtool

i dont know why

when it flashing the system.bin, my lappy will go crazy (not responding) and the progress aborted

but when im using my friend laptop, it was okay

it flash the ftf completely and my phone boot up but it take a while ^^

dont panic okay :fingers-crossed:
[Android Q&A, Help & Troubleshooting] joke19:
Hi, how I can add the option for a expandable desktop to my xperia stock rom? Thanks

Gesendet von meinem Xperia SP