vendredi 30 janvier 2015

Microsoft Remote Desktop topic






With the Note Edge I can't display the whole Remote Desktop, it looks like the Microsoft App thinks the screen is bigger than the viewable area. I have to scroll a few lines up or down. With Note 3 I had the full screen in view. There are all the time a few lines missing, either on the top or the bottom of the screen.

ScreenShot 3 shows, how it should be ...

Anyone knows, how to fix this?








Attached Thumbnails


Click image for larger version<br/><br/>Name:	Screenshot_2015-01-30-22-41-54.jpg<br/>Views:	N/A<br/>Size:	201.5 KB<br/>ID:	3141934
 

Click image for larger version<br/><br/>Name:	Screenshot_2015-01-30-22-42-18.jpg<br/>Views:	N/A<br/>Size:	196.7 KB<br/>ID:	3141935
 

Click image for larger version<br/><br/>Name:	Screenshot_2015-01-30-22-54-07.jpg<br/>Views:	N/A<br/>Size:	68.2 KB<br/>ID:	3141956
 

















Instructions reviving ME170C/ME170CX from bricked topic






After 3 days tried to find out how to recovered or fix bootloop/brick ME170C, here is the way which was succeed for me.

1. Download latest firmware from ASUS website
2. Extract (archive in archive) and throws to the SD card. Rename the file to K017_sdupdate.zip and Insert the flash drive into a tablet. (Use good one SD card)
3. Download flashtools and USB driver at the bottom of this thread
4. Enter the DROIDBOOT, for this purpose on the tablet off push and hold button volume + and power then connect USB cable to tablet and PC.
5. Open your firmware archive and copy the firmware from the boot.img, fastboot.img, splashscreen.img in Fastboot folder
6. go to fastboot folder and then push button shift and right click together and choose “Open command windows here”
7. Test your device by typing fastboot devices on that cmd
8. Enter the queue codes:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot boot.img
fastboot flash fastboot.img
fastboot flash splashscreen splashscreen.img
fastboot reboot-bootloader
8. Disconnect the USB cable and select the SD update or Recovery.
9. Take your coffee and sit, walaaaaaaa I see you are smiling :o:o:o










[Q&A] [KERNEL][ALL '11 MDPI] MESA v4.8 (STOCK ICS/CM9/CM10) [31 DEC 2013] topic






Q&A for [KERNEL][ALL '11 MDPI] MESA v4.8 (STOCK ICS/CM9/CM10) [31 DEC 2013]

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [KERNEL][ALL '11 MDPI] MESA v4.8 (STOCK ICS/CM9/CM10) [31 DEC 2013]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)






[Q&A] [ROM] [SM-N915 S-K-L Exynos] 10Jan [Aroma] TW KK 4.4.4 [NL1] SkyHigh v1.2 | Mu topic






Q&A for [ROM] [SM-N915 S-K-L Exynos] 10Jan [Aroma] TW KK 4.4.4 [NL1] SkyHigh v1.2 | Multi-CSC

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [ROM] [SM-N915 S-K-L Exynos] 10Jan [Aroma] TW KK 4.4.4 [NL1] SkyHigh v1.2 | Multi-CSC. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)






Kernel that allows SELinux=permissive for N915T KN3 topic






Hi. I thought I'd give out this kernel which allows one to set
SELinux=permissive for a rooted T-Mobile Note Edge with base NK3.
This setting is needed if you would like to run Linux on Android and,
I believe Viper4Android if you are so inclined, as well as some other
specialized apps (for future reference, let me know what apps you use
that needs this setting). Once you have loaded this kernel you can use the
app SELinuxModeChanger, found in the play store,
to set SELinux=Permissive and back to Enforcing. Note, this setting
is maintained until you change it back in the app (rebooting will
not change the setting). Anyways, what I am providing is a gzipped tar
file that you can download, gunzip and then load on your phone using
ODIN (version 3.07 worked fine for me, goes in PDA).
Remember, this kernel is ONLY for the T-Mobile N915T NK3 rom. Actually, I have
only tested it on the Lab Rats rom so hopefully it will work on other
roms for T-Moble N915T with NK3 base.

As most folks like to have a name for their kernel I've decided to call this the
"Low Lying Fruit Kernel" (LLFK) because it only has a minor change made
to it. Indeed this kernel is about as low as it gos (lol) as not a single
line of code is changed. I only changed an option in the Makefile
from true to false. Details are given at the following github site.

https://github.com/mscion/Permissive-Kernel-N915T-EDGE/

Anyways, I've been using this kernel for over 10 days with no problems,
but, of course , for those that try LLFK, the usual warnings apply! I am not
responisble for anything that happens to your device as a conseqence of
using this kernel. Indeed you have to be crazy to try it as I have
zero experience at this!
You also might want to read this before you try this:

http://en.wikipedia.org/wiki/Security-Enhanced_Linux

One more thing, while my preference is that an experienced dev make a kernel worthy
of the N915T EDGE, I am open to suggestions to make some more modifications
assuming the request are somewhat consistent with the philosophy of LLFK.

Don't forget to do a full back up! Good luck!

Kernel Download link:

http://www.4shared.com/archive/oH5fE...issivetar.html






For those one 5.0, can you change your ring volume? topic






I can't any more. Its been this way since the update. Every time I try to change my ringer volume it changes my in-call volume, even when I am not in a call. I always have to go to the settings menu to change it.






PC hates nook (ohci_hcd error) topic






I want to fix my bricked Nook (8g), in order to fix it I loaded cwm into a microsd card and my plan was getting adb to work while the Nook is in cwm recovery. The problem here is that my pc (Debian Wheezy) doesn't seem very happy with the tablet and I couldn't get it recognized.

Using Android SDK Manager I got the following in the usb.ini

Quote:









# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2080




worth saying (probably), I also edited /etc/udev/rules.d/51-android.rules as follows:


Quote:









SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"
SUBSYSTEM=="usb",ATTR{idVendor}=="2080",ATTR{idPro duct}=="0004",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="2080",ATTR{idPro duct}=="0004",SYMLINK+="android_fastboot"




When I finished doing that and still didn't work, I looked up what happens when I plug the tablet into the usb port,


Quote:









[ 9634.796053] usb 2-9: new full-speed USB device number 39 using ohci_hcd
[ 9634.980037] usb 2-9: device descriptor read/64, error -62
[ 9635.268035] usb 2-9: device descriptor read/64, error -62
[ 9635.548038] usb 2-9: new full-speed USB device number 40 using ohci_hcd
[ 9635.732041] usb 2-9: device descriptor read/64, error -62
[ 9636.020041] usb 2-9: device descriptor read/64, error -62




so this seems to be the error. Is it possible to fix it? I tried a few things I found (like killing the usb services and start them again) but you can tell it wasn't exactly successful. Is there anything I can try?