Bridge for Mac Issue > Please Report Here - Sony Xperia P, U, Sola, Go

There seems to be some synchronisation issue with the Bridge for Mac and XPS. And reporting to Sony Mobile seems to be taking a long time since they can't isolate & identify the problem at their end.
To get this issue addressed/solved faster, we need to gather more information on the problems. If you are using Mac and having issue for Bridge for Mac and XPS, please report your problems here with the following info:
1) Phone Info
a) Build No: ( Go to 'Settings' > 'About phone')
b) Bootloader Status : locked/unlocked/relocked
2) Mac Info
a) OS Version: ( Click the Apple on top left of screen and select 'About this Mac)
3) Issues
a) Problems Type: Sync Issue / Phone Browser
b) Media Type: MP3/Photos/Video (state format)
c) Problems when copying single or multiple media?:
d) For multiple media: Playlists or Albums
4) Try this:
a) When the Sync hangs, go to your phone and check how many media is being copied before it hangs.
b) Try to copy the failed media with the Phone Browser manually and see if it works.
c) Identify the failed media that wasn't copied over and the details of the failed media and any successful media that was copied over. (Right click and select "get Info"). In the "More info" section, are there any non alpha-numeric characters? This means anything that doesn't belong to numbers and western alphabets.
5) Other info
a) Any other information that you think may help identify and solve the issue faster.
I know it's troublesome, but this would really help to identify the problems.
Regards,
Zann H

Related

Blackberry Problem Fixed (Receiving Emails But Not Sending)

A couple of people I recall have had this problem whereby using 1.72 RIM/BB version that they can receive emails but (frustratingly) not be able to send them
I've had an open call with O2 Blackberry support for a couple of weeks & today it was sorted.
These are the instructions
****DO NOT RUN ON THE BES****
1) Remove the device from the cradle and close down desktop manager on the users PC.
2) Remove the user from the BES.
3) Delete the service books (go into Options, then service book) on the BB device. (ALP/CMIME)
4) On the users PC – go into documents and settings, users profile, application data and then delete the RIM folder you see in there.
5) Run dbclean on the users PC as follows:
i) Store dbclean on the root of C
ii) Go into command prompt at the root of C
iii) Type dbclean
6) Then re-add the user to the BES.
7) Re-cradle the BB device, open Outlook and then open BB desktop manager.
8) Re-generate the encryption key.
Worked absolutely fine first time EXCEPT dbclean crashed (caused exception) with a .dll conflict, so it may be that this aspect is not always needed.
Anyhow, end result is my XDA working properly with BB client Hope these instructions help others & if still needed, ring BB support for the file.

[REF] █▌█▌█▌█▌THE ANDROID WALK>THROUGH - Guides, Explanations, Fixes & Tips █▌█▌█▌█▌

[REF] █▌█▌█▌█▌THE ANDROID WALK>THROUGH - Guides, Explanations, Fixes & Tips █▌█▌█▌█▌
Find here and EXTENSIVE collection of every single information available on Android : Kernels, Builds, Updates, Fixes and much much more...
Posts Guide​
Post 1 : Android Encyclopedia
Post 2 : Complementary Guides
Post 3 : Problems, and Fixes
Post 4 : How-to's
WARNING : This post needs updating, formating, typo-checking. Please be patient, as i'll need to collect a lot more data, and rest a little as well
Mods, I made a typo in my post ^^ Can somebody help there? Can't find how to edit a poll Thanks!​
A big THANK YOU to all the contributors of this thread, who are helping me, and the others!
​
This is a GUIDE/LINKS Thread. Suggestions are welcome, but :
PLEASE DON'T ASK QUESTIONS HERE Please check this (How to post a good question and maximize answers)
USE THE THREAD LINKS PROVIDED INSTEAD ON POST 3
You will save yourself double the time : On DEDICATED THREADS you will have more experienced users and more traffic, thus a faster and/or better answer!!!​
Why this thread​I've been reading a lot lately, but still haven't found an updated thread for basic questions, or just a welcome stop-by.
I'd add I'm not a cook neither a developer, but came to understand a few things by myself that weren't precisely told
(A common flaw of computer advices : Do this to solve that - You don't need to know how or why)
This brings pros, as I'll be more oriented towards the end users, but cons as I'll sometimes lack the necessary skills to go further. As a whole, I do believe this may still help understand the basics, and help get rid of a few misunderstandings. This is why there'll be a lot of "seems" and "mays" but in the end, most of the "basic" data here is accurate, and i'll get better as time goes by.
My current hardware and software
- HD2 Europe FR
- Hastarin 7.6 on PhireMod Sense 1.5
- Dutty CDC V11 COM2 FR
- Radio 2.15.40
However, this post covers Android as a whole, and lots may apply to other devices, be it with or without Haret "emulation"
Legend:​
-
Simple Explanation
->
A parameter or file you may change/trigger in order to enhance/solve problems/your Android build (yes, this works both ways)
[file]
An actual Windows Mobile/Windows XP/Seven file. You can see them using a SD Card reader/usb cable/etc
root/
This is Android C:\ drive
A file or directory present/visible ONLY when under Android on the phone.
/
Same as root/, but with some laziness included
(exe)
Means this is a Windows XP/7 Program
(apk)
Means....!
A. Android itself​
There are a few things you need to know on android on HD2.
What an Android build is made of :
- A "sound enabler" [CLRCAD.exe],
- An Android Bootloader for WM6 [HARET.exe],
- A startup command [startup.txt], Touch-screen Calibration Instructions [ts-calibration], a boot logo [initrd.gz]
- An Android Kernel [zImage],
- An Android Root Filesystem [rootfs.img]
- A ROM image [system.ext2]
- A data container [data.img]: This holds your texts, contacts and everything else. Sometimes provided BLANK by some chefs to avoid high boot times (cf Updating Android)
All of these should be on the "Android" folder of your SD card.
Note : For an easy launch of your Android, I recommend Exceller Multiple Boot Loader (link here), that you can set on autoboot (or not)
When you launch Android via EBL on WM6:
- [CLRCAD] enables sound
- [Haret] is launched, then totally closes Windows Mobile (all resources shut down)
- Kernel+Drivers, ROM and Data are loaded
What to learn about this:
- There are hardware/software interactions happening when Haret "closes" WM6 and it's own drivers take place.
-> It may be useful to activate "Airplane mode" in Windows to avoid pieces of the radio chip to stay indefinitely on without Android being able to shut them off (cf Power consumption problems)
-> Full charging may not be achieved under Android, this because of Android drivers not being able to correctly write the battery status (yet). To get to 100%, charge when the phone is off or under WM6 (although i do manage to have a 100% under Android under certain circumstances)
-> It may as well be useful to launch Android with Keypad lights on in order to ensure that lights are working properly. This depends on hardware and software, and varies from people to people.
->Flashing a radio under WM6 has the same impact over Android, as the radio chip instructions are shared between Android and WM6 (cf Robo Voice)
->The WM6 ROM used, while seemingly not worthy of attention (as it is "shut down" by Haret), seems to handle some important work when closing itself or interacting with the hardware. That's why changing from "Stock rom" to a "custom one" may resolve a few problems too.
B. Android's Internals​
First, at the current state of development, Android is ENTIRELY run through the SD card.
-> Class 2 cards have been reported to being a source of annoyance, still being able to correctly run Android, but slowing a lot of problems. T-MO USA users have different experiences with the bundled microSD card provided. However, i'd advise using AT LEAST a Class 4 microSD, with correct formating.
- File explorers under Android are reporting a "root/" directory with several files and folders, and a "root/sdcard" folder. In fact, the [data.img] of the SDcard IS (some part of) the "root/" (unzipped for you to see) whereas the SDcard is...the SDcard. That's why removing the SDcard with android running may freeze the whole file-system.
- The actual NAND work is approximately for the devs to put the [rootfs.img and system.ext2] inside the phone flash, to ensure that Android still runs when removing the Sdcard. The problem is : the [data.img], that holds Android's data, may still be on the SDcard (as EU HD2 only have 512mo of ROM, and Android already takes 300 just for booting)...To be continued.
Kernel, Libraries, Modules, File-system, and the like...
Ok, I know little about them, as I'm not a developer or a cook, but here are the basics
Kernel bundles
-> [zImage] : It is the main kernel file, it seems to contain the primary drivers using for controlling the phone. You can update this file by downloading a "Kernel" like Hastarin 7.6, by powering the phone in WM6, and replacing the [zImage,Haret,initrd.gz] in the Android folder of the SDCard
- [Initrd.gz] seems to be the logo launched when Haret is loading Android (needs confirmation)
- [rootfs.img] : It handles the basic file-system
Android Builds Bundles (further explanation)
- [system.ext2] : It contains the Android files described there-under, also provided in a build
Modules
Located in /system/lib/modules, they are here to handle the Bluetooth and Wifi. They sometimes need to be replaced manually (aka "pushed" via the shell/terminal)
Libraries
Located in /system/lib/ or /system/lib/hw, they handle other elements, like lights and so on. They can also be uploaded manually when needed.
File-system Organisation
- root/acct, root/bin, root/cache, root/config, root/dbgfs, root/sbin, root/dev, root/mnt, root/proc, root/sys, root/tmp seems to contain files used for Android. Never went there.
- root/data/etc and root/data/system holds some system files. Don't mess!
- root/data/app/ is the main location for user installed apps (.apk)
-> root/data/data/ is the location for each apps' storage (like some sort of registry), like scores for games, etc
-> root/data/data/ seems to also be the place where the "hosts" file of android is located (The other ones across the file-system are usually empty ones)
- root/system/app/ is the main location for cooked (pre-installed) apps. Removal is at your own risk!
-> root/system holds the build.prop file, responsible for some of the phone behavior. This folder seems to be physically hosted in Android's [system.ext2] file, and is dependent of the chef providing it. You can configure alternate DNS in this file (BACKUP first).
Kernels' flavors (MichyPrima Kernel Thread)(Hastarin Kernel Thread)
- There are two branches : EVO and Nexus1. They mean different libraries, drivers and modules. Nexus1 is the most stable, but the least capable. EVO, although less stable, is the most able, and thus has been selected to be at the base of the NAND development.
- There are two data approaches : RMNET and PPP. Both have their pro's and con's: Speed(PPP) vs Stability(RMNET). (Learn more here)
- There are several kernel chefs, and several available tweaks for each branch.
- There are several capabilities, such as Overclocking or Not, etc. Usually, each Kernel chef delivers its Kernel with or without these additions. Find the one that suits you best.
To summarize / To Update Android :
- A downloaded "Build" provides a FULL working Android system, you need NOTHING ELSE
- A downloaded "Kernel" provides : An updated [Haret, initrd.gz, zImage] that you just "paste" over an existing Android "Build" and sometimes updated "Modules/Libraries" that you need to manually push
->Note : There seems to be a workaround, like a [root] folder, containing many sub-folders, that is placed in the [Android] folder. The files included in this [root] folder seems to be copied by Haret into the root/ folder of Android on boot. That is why, when you "update" an entire "build", chefs ask that you deleted everything on your [Android] folder, to ensure nothing from an old "build" or "Kernel" will be copied to the new "build" upon booting Haret.
->Note on updating "Builds" : I personally erase everything but the [data.img] on my android folder, then unzip the content of a new "build". WARNING : Some chefs include [data.img] in their "builds", so be sure to CHECK to avoid an override!
How to choose a build/a kernel:
- Check what are your needs : Sense implementation, Basic but blazing Android, HTC Sense.com services.... Each come with a price
- Again, choose what do you want from your phone, cutting-edge but unstable or basic but sure...(You may have both )
-> I personally don't recommend going out of binded paths. Each chef, in each build, uses a specific Kernel dev, and adapts its ROMS to it. I chose to only update a similar Kernel, when the cook or chef just didn't have the time to implement it yet (usually, unless Kernels are really faulty, new ones come with new builds, so just wait for a wholesome upgrade)
C. Basic Android Tools (Survival Starter Kit)​Some tweaks will require "Super-User Access" or stuff like that. Again, here are the basics.
First, "Droid Explorer" (exe).
No, don't look on the market, it's a WINDOWS XP/7 PROGRAM.
(Why the capitals? For the story, a few months ago, it took me HOURS to figure that, as there is also a "Droid Explorer" on the market, free as well. When you're told, "Go into ADB mode with Droid explorer and push that file in the rootlib" you're starting to think you took the wrong spaceship )
-> ADB Mode : Short for "Android Debugger Mode". You can switch this in "Parameters/Application/Development, Check the USB Debug). You need to enable ADB mode to use Droid Explorer.
- Droid Explorer basics : If already on ADB, click on "Connect device" at the right corner, and select the only device shown.
- Warning : I've personally got increasing problems accessing/pushing files to Android using Droid Explorer. I'm currently using the "root folder update" method. (Handle with caution!)
Other useful programs (most are free, some very useful may not, and some are included in builds):
System Apps
- Root explorer (Apk) : A useful Android program, to access files currently not available trough ES Filexplorer or Astro, although some other file explorers may possibly retrieve SU privileges to access the entire file-system. "root/data" is a typical folder not accessible with "traditional" file explorers.
- Super-User (apk): It's an Android Program, provided with your build. It enables programs to access some privileged code/areas...(To investigate)
- Terminal Emulator (apk) : It's Android's cmd.exe, used to input commands like in DOS-Mode
Usually Bundled Apps
- Astro (apk): Beautiful File Explorer
- Drocap2 (apk): Screenshot app. Push start, and shake HARD
- DSP manager (apk): Manages that crackling speaker bad bass rendition
Must-have Apps
- Adfree (apk) : Similar to winhelp2002 for windows, this block some ads while on the Internet. Doesn't block GoogleAds (developers need to survive through free apps too!)
- BatteryLevel (apk): Inputs a permanent notification, which shows the battery percentage. Lightweight and useful, albeit not always properly refreshed
- DroidWall (apk): The only? firewall for Android. Need Busybox (cf TitaniumBackup) in order to function properly. Warning : May block genuine apps from accessing Internet. And no, your cracked apps won't be prevented from calling "home", as license verification goes through the Android system itself.
- GPS Status (apk) : Handles the A-GPS, compass and other stuff
- SetCPU (apk+widget) : This is used to tweak the CPU. (see Hastarin's recommendations, a shame I can't export my settings). Install the apk, then place a widget in order for it to work (mandatory? need to investigate...)
- Shazam (apk)
- SMS Popup (apk) : Great program, pops sms and enables quick management. SMS notifications have to be handled solely by either the program, or the system. Disable one or the other accordingly.
- Startup Cleaner Program (apk) : Manages starting programs. Handle with care.
- SwitchPro (apk+widget) : Almost similar to Cookie's switches for WM6. Can't live without. Weird implementation though.
- Taskiller (apk+widget) : Selective task killer. Has been reported to cause wake-up lag when set on "autokill on sleep" (and I do, but use it on other occasions)
- TeslaLED (apk) : Ke$ha's favorite tool for impromptu parties!
- CurrentWidget (widget) : report power consumption. Helps reporting battery drain problems (I got 3ma on standby ). Don't set to "update" on less than 1 minute. Use it to log when on sleep, then check power consumption on standby.
- DolphinBrowserHD (apk) : Very configurable, personal choice.
Very Nice Addition
- Swype (apk) : Provided on the forum, or sometimes implemented on Builds, can't live without either.
Is there a developer in the room?​- Taintdroid (needs implementation/compiling?)
Unusual stuff coming from me, but this program recently came to my attention. It detects every ID/IMEI/etc Internet leakage and reports to the user. It visibly need some kind of integration into the kernel in order to work. With a firewalling program, we could prevent our phones from spying hard on us (I have a dream, i know ^^)
>>>Hastarin, MichyPrima, ElBartoMe and the others, anyone there? <<<
Thanks for all the devs, chefs and forum users, i'll link when available and when free
Complementary guides
This is post 2 :
Complementary guides
Complementary guides:
> How to flash an android build, and boot issues/solutions
http://forum.xda-developers.com/showthread.php?t=732380
>A good explanation of the different terms
http://forum.xda-developers.com/showthread.php?t=774859
>Frequently asked questions (although pretty much technical to me) (Tips and Apps)
http://forum.xda-developers.com/showpost.php?p=7088391&postcount=3
Main Problems, Concatenated Solutions, Original Threads
This is post 3 :
Main Problems, Concatenated Solutions, Original Threads (When available):
Main Problems and Solutions (compilation)​Some filenames aren't correct, i'll check that later
(One general thread)
Battery Drain (One thread there) (Another Thread here)
May be the main problem out there, although Touchscreen freezes are competing for #1 as well
- Try tweaking WM6 power management (Thread here)
- Use CurrentWidget log mode to verify
- Remove root/data/system/batterystats.bin
- Try the Airplane mode in WM6. For daily Android users, set to airplane, then switch the phone off and on without a reboot app. The airplane mode should stay indefinitely on. For constant switchers, launch haret after airplane mode. On next reboot, WM6 shouldn't have airplane mode on.
- Try checking the "lightslib.q8sk"(?) file/problem. Try replacing it with the newer "lights.htcleo.so" provided on the forums
- Try flashing a different radio or WM ROM (test radio first of course)
- Try booting Haret with the keys' lights on
Robo Voice
This issue seems to be hardware+software related. AKA It is different for everybody, and same build+rom+kernel may produce different results on similar phones.
- Current state of resolution is : FLASH RADIO and CHANGE WM ROM ^^
PPP Stuttering (no Edge/HSPA icon warnings)
- Try the libhtc_ril_wrapper.so fix provided by noellenchris (Another thread there)
- Try updating your kernel
- Try removing Taskiller Autokill feature (not the kill on sleep feature)
PPP Freezes (icon going on and off, etc)
- Try tweaking the build.prop (GSM or WCDMA prefered via "ro.telephony.default_network=" parameter ) (See "Tweaks" Section)
- Try changing the DNS inside "root/system/build.prop" (Link of your mobile provider DNS here)
- Try tweaking the APN in "root/system/etc/apns-conf.xml"
Screen of Death (Thread)
As Robo Voice, this issue seems to be hardware+software related. AKA It is different for everybody, and same build+rom+kernel may produce different results on similar phones.(Proof)
- Try flashing a new radio
- Try formating your SD with the largest FAT32 Allocation Unit Size possible (Thread Here)
- Try changing your SD-Card
Touch-screen Freezes
- Try disabling g-sensor in Parameters/Display/Auto-rotation
- Try offset change. Still haven't understand... (Thread Here)
Music Stutter
- Try updating or Changing Kernel (Thread Here)
- Try this workaround
Background Noise
See this thread
Camera "Moon picture" Preview
- Temporary fix : Disable preview
Camera : HTC 5Mpx (EVO/Desire Roms ONLY) (No Desire HD, No Desire Z...)
See thread here
011 International Dialer issue
Fix can be found here
T-MO USA MMS Issues
Thread Here
Tweaks i'm aware of​
Boost DATA Speed
-> Edit your "root/system/build.prop" and check for correct values (These ones seems "overboosted") -> (Thread Here)
- Here are the "HSPA network" values explanations (See here), these seems more moderate
Build.prop Configuration
ro.telephony.default_network=
-> "0" is WCDMA/UMTS Prefered, even when network is very low
-> "3" is GSM/WCDMA Auto Mode, switch 2G/3G according to highest network
How-To's
This is post 4 : How-To's
HOW TO REQUEST FOR HELP ON XDA​Again, personal point of view here, but there are a lot of "unsaid" things around there....
1. Nothing more annoying than a "noob" (and we've ALL been through there, but...) that didn't (at least) try looking for himself.
-> Use wisely the "Search on this thread" button. It's WORKING. Tip: If you're not on a specific thread, but rather in the Development of General sub-forum, tick the "Post" button to avoid going through entire threads for a single answer.
2. Do remember: you're not alone.
-> DON'T BE RUDE, BE POLITE, SAY HI, THANK PEOPLE, we all have to be patient. It's XDA Community. Plus, some threads are moving real fast, and may have flooded your question. Ask again, and just don't complain!
-> EDIT YOUR SIGNATURE. Insert your ROM, Radio, Phone model, etc etc etc. Most common answer to noob problems: "WHAT'S YOUR ROM"
->Try asking GOOD QUESTIONS, starting with (Hi!) "I've been looking for this, found this, understood this, but need help about that" (Thanks) and you'll see how people will be more inclined to answer ^^
Flash a WM6 ROM (compatible with Android)​> Need-to-Know : HSPL, RUU, WM6 Roms
1. Install the HSPL
- A HSPL is needed in order to "flash" custom roms, as well as new radios, and then Android Builds. Most up-to-date HSPL is HSPL 3 (found here).
- Plug your WM6 phone to your computer using the USB cable provided on activesync mode (SDCard Flash method here)
- Launch the "Mobile Manager" in Vista/Seven, or wait for activesync in Windows XP, and establish a connection (Connection failure : Look here)
- Launch "HSPL3_PKG.exe", and follow the instructions
- Reboot phone
2. Download and Install a WM6 ROM
- Hint: Choose and download a recent WM6 rom (advices here)
-> Your phone needs its battery to be charged at a minimum of 50%, else flashing won't occur
- Again, plug your phone in USB-Activesync mode
- Unzip the archive, and launch "CustomRUU.exe" ("ruu_signed.nbh" is the WM6 rom file)
Flash a new Radio (under WM6 only)​- Choose a recent radio, minimum required is 2.08, 2.12 recommended (radio thread here)
- Again, plug your phone in USB-Activesync mode
- Sometimes, only the radio (ruu_signed.nbh) is provided in zip files. "Pick" the "custom_ruu.ex"e of a WM6 ROM, and copy it in the unzipped radio folder, it'll work just as well.
- Launch and follow the instructions
Install Android on a SD Card​
Update an Android Build (with a new build)​
Update an Android Build (with a new kernel)​
Yes, I did find this useful - Thank-you !
RedWave31 said:
A.Android itself
There are a few things you need to know on android on HD2.
>What an Android build (like mdeejay NextSense.zip) is made of :
- An Android for Windows Mobile emulator (HARET),
Click to expand...
Click to collapse
HaRET is not an emulator. It is a Linux bootloader.
A Really good guide, actually explains quite a lot about the filesystem that I wasn't aware of. Well written and a great idea.
msoler8785 said:
HaRET is not an emulator. It is a Linux bootloader.
Click to expand...
Click to collapse
Thanks, updated!
Feel free to submit ideas or whatever!
Wow, good idea on putting it all in one thread, few things, however:
As another poster suggested, haret is not an emulator (handheld reverse engineering tool)
As far as the filesystems: rootfs.img is the linux rootfile system, startup.txt are commandline arguments for the linux startup, system.ex2 is the root android filesystem, etc. So to avoid confusion, think of it this way: system.ex2 would be closer to the android "rom image", where as rootfs, startup.txt, ts-calibration, and initrd are for the linux kernel side, so you can boot up android. (Very oversimplified I know, just trying to help)
When you install a linux box, typically it's installed on more than one partition (keeping the /home directory on a seperate one is always good practice, and some people even keep /var on a seperate one for log files as well.) data.img and system.ex2 would be like different partitions of the android filesystem. When you buy a phone that isn't "rooted", it means you don't have access to the root file system, aka in this case, system.ex2.
*edit* oops you already saw the thing about the haret. Didn't notice.
You may also want to add that for where apps are located after install, /data/app is for user installed apps, /system/app are for pre-loaded apps that are installed with the system. If you wanted to remove any app that came with the system (like the amazonmp3, for example), you'd delete it out of there. (Delete files out of the system/app at your own risk, don't delete it if you don't know what it is)
Added HSPA Values and DNS and APN files location. Enjoy
This is a very nice guide. Has a lot of the necessary stuff that the other guides leave out.
Good job. Maybe I will just link folks to this guide in the future instead of directly answering them. (probably just do both though - I was pretty noob at one point)
Oh, and .apk = Android Package (android apps are .apk / android package file)
Added 5mpx Fix, hope the HD Roms will have camera too
- Try the Airplane mode in WM6. For daily Android users, set to airplane, then switch the phone off and on without a reboot app. The airplane mode should stay indefinitely on. For constant switchers, launch haret after airplane mode. On next reboot, WM6 shouldn't have airplane mode on.
Click to expand...
Click to collapse
For my phone, turning on Airplane mode in WM6. then booting into Android with Haret without restarting, then coming back to WM6...it is still in Airplane mode.
Great Job man...keep this thread up to date...We appreaciate your hardwork....thanks a lot...
Top work dude!
Spelled "through" wrong in the title
OCedHrt said:
For my phone, turning on Airplane mode in WM6. then booting into Android with Haret without restarting, then coming back to WM6...it is still in Airplane mode.
Click to expand...
Click to collapse
Damn I spent a lot of time trying to figure this one, as I'm not using WinMo anymore. Are you using Cookie HomeTab's switch? Or directly in the Com Manager?
>I remember using Cookie Switch didn't stay at next reboot
- BTW, maybe it has to do with your launcher, or even the rom
jetsetwilly said:
Top work dude!
Spelled "through" wrong in the title
Click to expand...
Click to collapse
LOL This is the "Walk-true-shame"
Thanks for reporting
Added "How to post a Good Question", personal joke of the day, but REAL INFO
A question and a few suggested tools-
First, where in the Android file structure are the logs stored?
Second, another way to access the phone from Windows, one I use for working on Linux systems-
1) install QuickSSHd from the market. It will open an SSH (secure) tunnel into the phone
2) Install on your windows system Winscp and Putty (both Windows XP and up applications and both free. Winscp allows you to transfer files to and from the phone and Putty gives you a root shell and your desktop/notebook keyboard.
While these tools are not real simple, if you have an understanding of basic Linux and get this far you can then log into the phone over your home WiFi network with full root access and get into a lot of trouble if you aren't careful. It also seems more stable than Droid explorer.
Excuse this potentially silly question...
How do you quit Android? I'm running the Runnymede/Rhyme/Bliss one and long holding power doesnt do anything.
Is it just a battery pull?

Why Can't I Use Multi-screen Collaboration?

Recently, some users have said that they are unable to use Multi-screen Collaboration after installing certain applications on their laptop. Whenever this occurs, a dialog box pops up indicating that the hardware decoder is faulty, and that Multi-screen Collaboration does not work. Even restarting the laptop multiple times does not resolve the issue.
What went wrong?
First, let's take a look at the two main causes of this issue.
The first is the launching of certain third-party applications using the administrator permission, which causes the dynamic-link library (DLL) name of the operating system under the path (C:\windows\system32) to be modified, which can affect the running of Multi-screen Collaboration, and the system's video player.
The second involves the potentially faulty source mirror, after installing Windows system on your own, on a Linux system laptop.
How can this issue be resolved?
To use Multi-screen Collaboration, simply perform the following steps:
1. Set the preferred graphics processor to auto-select in the NVIDIA control panel.
2. If you are still unable to use Multi-screen Collaboration.
Check whether you have modified "msmpeg2vdec.dll" and "msmpeg2adec.dll" to "msmpeg2vdec.dll.bak" and "msmpeg2adec.dll.bak" under the path "C:\windows\system32".
3. If yes, delete the suffix bak.
Press the Win key and enter "CMD" in the search box on the taskbar, and right-click Command Prompt and select to run it as the administrator.
Enter the following commands:
regsvr32 C:\Windows\System32\msmpeg2vdec.dll
regsvr32 C:\Windows\System32\msmpeg2adec.dll
regsvr32C:\Windows\System32\evr.dll
4. If you still cannot resolve this issue, check whether this issue happens due to the second cause. It is recommended that you download the official source mirror from MSDN, and confirm that you can use this feature. Alternatively, display CMD and enter "winver" in the search box to check your system version. If your system version is lower than 1903, update your Windows system. If this issue is still unresolved, re-install the system.
I hope that you found this helpful. If you're still having difficulty using Multi-screen Collaboration, feel free to contact me!
More questions to ask? you will definately get some help here
Can you describe your problem in detail?
Freemind R said:
Can you describe your problem in detail?
Click to expand...
Click to collapse
So I've encountered the situation (and heard people saying as well) that the multi-screen collaboration does not work well after installing certain applications: a dialog box might pop up indicating that the hardware decoder is faulty, and that Multi-screen Collaboration does not work. Even restarting the laptop multiple times does not resolve the issue.
My post here is meant to provide a possible solution.

Default USB config. from Dev. Options ignored by SystemUI

the USB Default Config. in Development options is ignored by the System UI.
When connecting the device to PC, the phone asks for USB Behaviour (Charging only / File transfer / etc), even if the default USB behavior is set to File Transfer in Dev. Options.
tried with USB debugging "on" and "off".
- Model: RMX2001
- Build number: RMX2001_11_A.38
- realme UI version: v1.0
the idea is to add the possibility to transfer data (photos, videos, documents) to pc in case the screen gets broken...
The system won't allow that due to security reasons because if that was possible then anyone would copy your phone's data
Aag64 said:
The system won't allow that due to security reasons because if that was possible then anyone would copy your phone's data
Click to expand...
Click to collapse
Understood, although I still have some questions about the whole thing:
- if the option was still available, one would require physical access to the device. What I believe most of us carry in the pocket or so.
- in case the display becomes unresponsive due to damage, how can the owner get to his data then?

Oppo A52/A72/A92 Android 11 update via VPN

Hi,
I managed to get the Android 11 update with a bit of stuffing around and thought I would share for everyone else, I did this on a unlocked Australian variant bought from Optus, you're mileage may vary.
This will activate dual sim mode on the phone with a single IMEI, I left my location set to Europe so it is upto you if you follow the last step to remove Dual Sim Mode.
You will need to backup anything you don't wish to lose as a full factory reset is required.
I did some digging and this will work with the same rom on A52, A72 and A92.
Could I get a moderator to cross post this to the other device forums please?
Requirements:
OPPO A72/A52/A92 - My bootloader is locked, My simlock is off
CPH2067_11_A.54 Latest European ROM for the device - Download Here: https://support.oppo.com/nl/software-update/software-download/?m=A72
Oppo Free Unlock Tool - https://forum.xda-developers.com/t/...de-to-coloros-11-and-enable-dual-sim.4191787/
A Google account to download ExpressVPN (This is the second last step so leave for now)
A Windows PC with a internet connection
WIFI or Mobile data on phone.
Latest ADB Drivers - https://adb.clockworkmod.com/
Instructions:
1) Backup all settings and user data.
2) Remove all accounts and screen lock security settings on phone.
3) Format all data, factory reset phone.
4) Download Oppo Free Unlock Tool from the link provided to PC.
5) Follow these instructions to install Microsoft Loopback Adaptor -
6) Open Device Manager and expand the Network Adapters category.
7) Find your Loopback Adaptor and double click it to open its properties.
8) Go to the Advanced tab and find the Network Address option in the Property pane.
9) Under the Value pane, select the radio button next to the text box and paste in the following: 704D7B61ABCD.
10) Install ADB Drivers.
11) Extract OPPO Free Unlock Tool, You're antivirus may give a false positive so you will have to manually add an exception for the tool.
12) Go to where you extracted the unlock tools. Open Sec5.exe.
13) Plug in phone via USB and select "Transfer Files".
14) Enable developer options on phone and activate USB Debugging.
15) Press Allow when prompted to give PC ADB access.
16) Open Sec5 window.
17) After about a second, a string of numbers and letters should show up in the left pane, Press Start Unlocking and few seconds later, "OK" should start flashing in the right pane.
18) Press stop unlocking and disconnect phone.
19) Open the phone app on your device and dial *#3954391#. Then dial *#391#. A screen should come up with a whole bunch of regions listed. (Take note of the one highlighted in green as you will need this in the final step).
20) Choose this one: "Europe EUEX" and click Ok you're phone will restart.
21) Download the rom from provided link to the phone and install through recovery mode.
22) Add your google account and download ExpressVPN from Play Store.
23) Open ExpressVPN and start 7 day trial then set to Netherlands server.
24) Goto Settings then Software Update and you will see Android 11 available to download.
25) Click Download then when complete Click Install
26) Remove Google Account from phone and factory data reset again.
27) Use instructions 12-20 to set your phones location back to your original setting.
That's All Folks
@MuntedJester THREAD CLOSED as duplicate of
Android 11/ColorOS 11 OPPO A72 Update with VPN
Hi, I managed to get the Android 11 update with a bit of stuffing around and thought I would share for everyone else, I did this on a unlocked Australian variant bought from Optus, you're mileage may vary. This will activate dual sim mode on the...
forum.xda-developers.com
The thread has also been moved from the development section into this sub-forum.
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse
Also review the sticked "Device Forum Rules (Read before posting)" with special focus on the conditions what threads qualify for the development section.

Categories

Resources