yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] xzyk:
thanks for the suggestion but i think the problem is deeper than that. I've tried many different apps that offers wifi access between your PC and the N4 and none of them work.

I cannot even ping from the PC to the N4 when they're active, so something is stopping this from working and it's probably not the app. I suspect either something to do with the N4, since all my other android devices (6 other phones) work flawlessly or something strange with the network.

EDIT: I thinks it may have something to do with WPA2 (my normal way of connecting to my wifi). I've set back to WPA and all is working fine. I'll investigate further but i've seen this sort of behaviour on other android devices where WPA2 between router and devices don't behave well.
[Motorola Droid Bionic] mbarry55:
Ok so in an attempt to get around the headphone whining issue, it seems bluetooth headphones are the way to go. However, would a USB headset work? Has anyone tried? I don't want to buy one and then have to return it if someone has already tried. Didn't find much in a google search.

what are the best options with the lapdock to avoid the headphone whine?

Anyone know?
[Motorola Droid Bionic] silversonic1:
There are several options, but the only USB audio devices I own don't work with the Bionic. Still, that doesn't mean none do work. After all, the docks channel audio through the USB port.
[Motorola Droid Bionic] mbarry55:
what is the most cost-effective solution? I found a bluetooth headset that has an adapter which lets you plug your own headphones in online, I was going to try that.

What are the other options?
[Sony Ericsson Xperia Neo, Pro] Human_Fly:
Hi, guys!

I tried searching the forums but didn't find anything similar so, here's my question:

Is there a working port of the Xperia Neo stock camera app for the CM10 ROM? Or, maybe, somebody working on that? The camera app that's built in in CM10 doesn't come near the stock app :(
[Sony Ericsson Xperia Neo, Pro] thunder888:
There isn't now. But maybe you can follow this thread : http://xdaforums.com/showpost.php?p=35957070&postcount=351

Hope he gonna make it. :o
[Sprint HTC EVO 4G LTE] datatype_void:
First of all, I'd like to thank you guys for everything you have posted on these forums. They have provided me with all the answers I've needed so far. But I'm finally stuck. I recently flashed a Sprint Evo 4G LTE to the Boost Mobile network. When I first completed the flash I had both error 16 and the data call failure error. I got rid of the error 16 by contacting Boost and complaining that my donor phone couldn't call out. They quickly amended the problem by doing whatever on their end. I played with the HA and AAA keys, and got the data call failure to go away by using the hex code from nv item 466, which was 34 digits long, where I just dropped the first two numbers. I also had to drop the first two digits of my second AAA key because it was 14 digits long. Using these numbers, I no longer get error 67 or a data call failure popup. When I enter ##debug# > EVDO Engineering, at the very bottom it just always says 1 = authenticated.

For the record, I have the Boost Mobile 61009 prl, but have tried various Sprint prls as well, because I read on this forum that might help. I currently have the Sense-based MeanRom installed in order to use the ## codes, and this forum has suggested to try to update profile and update prl, neither of which work. When I choose update profile, I get an error 1012, when I choose update prl, I get an error 1233. Any suggestions are much appreciated :)
[Sprint HTC EVO 4G LTE] datatype_void:
As of right now, I am installing a different Sense based Rom, called MeanBean v2.3. I'll see if I have any luck.

For the record:

Baseband: 1.12.11.0809

Build number: 2.13.651.1

Donor phone: Samsung Rant

Plan: $50.00/month Unlimited Plan

Update: Changing to this ROM has not yielded any results.
[Sprint HTC EVO 4G LTE] datatype_void:
I'm going to relock the bootloader and update my firmware with the 2.13 RUU, and then unlock the bootloader and reinstall MeanBean 2.3 to see if that helps. In the MeanBean documentation, it states
[Sprint HTC EVO 4G LTE] Savio Dantes:
Data Fix (Profile Switch)

Open QPST and connect to ypur device,

Open QPST Service Programming

Go to M.IP Tab, click Read tab, enter your SPC/MSL Code,

On the right side under ACTIVE USER, (not in profiles) change it to "1" instead of 0,

(0 is only meant for Evo 4g not LTE )

Click "write to phone"

Restart the device and you should have data.

There are additional ways to increase 3g speeds as well, but they need to be performed AFTER this process.
[Sprint HTC EVO 4G LTE] SavioDantes:
Error 67 Fix

Note: Make sure you're on a Sense ROM or the ESPT codes you need will not respond or function (##3282#, ##3424#, etc).

Also, if you have questions about how to use the programs listed, then you're too far ahead and need to do a quick read/ trial and error of the basics so you know how to use them.

If you are having a hard time getting data back up and running, for the

Evo LTE

then I suggest the following using the following items:

work.

CDMA Workshop

QPST - Service programming

DFS

- Connect your donor phone and open DFS

Click on the Programming Tab (Main Tabs),then read in the values from your donor phone and take screenshots of The Following Sub Tabs: NAM, Data, and Mobile IP

Within the Mobile IP Tab there are 2 radio buttons for Profile, click on each and make sure to get good screenshots of each.

First Check and Compare your Data Info in with what you have saved in your Donor Phone Items/Notes, if not save both your old and new notes to compare and change later.

Connect your EVO LTE and open DFS, and your screen shots. Compare and make any changes that do not match from your Screenshots, to your EVO LTE.

- Close DFS.

- Open QPST - Service Programming, read in your EVO LTE's info, enter your SPC (MSL). Click on the M.IP Tab and compare the information

with your and check for any errors, also be sure that Profile 1 is the

active profile

.

(Profile 0 is for non-LTE phones)

- Close out of QPST - Service programming.

- Open CDMA Workshop.

Click the Security Tab and send your SPC (MSL). Next click on the NAM tab and load and write your NAM 1 and NAM 2 files for their respective profiles

(hopefully you saved this as well as your NV Items from your donor phones profile).

Next, click on the Memory Tab and write your NV Items to your phone (465, 466, 1192, and 1194)

Finally click on the Other tab and write your donor's PRL (or one you've downloaded) Choose LG not Universal. and choose NAM1.

After which DO NOT disconnect, simply attempt to close the program and it will ask if you would like to restart the phone to apply modifications, click OK or restart your phone manually and you should be good to go.
[Nexus 4 Q&A, Help & Troubleshooting] jmejiaa:
I've seen people mention this game(Need For Speed MW) on some threads and I wanted to buy it but the play store says it's not compatible with my phone..

Are people doing some sort of workaround?
[Nexus 4 Q&A, Help & Troubleshooting] iCalculate:
It might be a country restriction because here in London it fully works from the play store directly
[Nexus 4 Q&A, Help & Troubleshooting] kdog808:
what kernel are you using because i live in usa it was working till i put franco kernel now it says the same thing as yours
[Nexus 4 Q&A, Help & Troubleshooting] jmejiaa:
I'm on franco, so that may be it.. weird..
[Nexus 4 Q&A, Help & Troubleshooting] Twau:
Also noticed this problem, saw that my Nexus 4 even missing under "My Devices" on https://play.google.com can anyone else see if your N4 is gone?

Edit: Cleared cache on Google Play app, now its back on Play.google.com.
[Nexus 4 Q&A, Help & Troubleshooting] netsyd:
Same problem - only Matrix kernel.
[Nexus 4 Q&A, Help & Troubleshooting] spaceman860:
I'm using Franco on my n7 and it shows up OK not on my n4 though (you can side load it)

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] kcls:
I'm getting the same thing on Franco kernel. Odd though, because I have it installed on my phone from the play store, but I just realized I was on the stock kernel when I first downloaded it.
[Nexus 4 Q&A, Help & Troubleshooting] Michealtbh:
The latest update has made it incompatible with the N4 for some reason
[Galaxy Note II Q&A, Help & Troubleshooting] ITKingdom:
I discovered this on my galaxy note 2 during coffee break time, it's fun.

Just use any kind of material such as plastic, cotton, paper, cover your s-pen, and see what happen!

[YOUTUBE]oxKs5mPLVOA[/YOUTUBE]

Have fun :laugh:
[Galaxy Note II Q&A, Help & Troubleshooting] ITKingdom:
Fixed link :)
[Galaxy Note II Q&A, Help & Troubleshooting] UtkarshGupta:
It was discovered long time ago by just using fingers
[Samsung Galaxy R i9103] saroj405:
Does the battery performance vary when charged the phone with usb cable, or wall charger provided for galaxy r or some other samsung charger?

I noticed that when I charge through usb cable, it takes long time to charge and the phone discharges soon.

I used another charger and it charges sooner and gives more backup.

With galaxy R's wall mount charger it gives 12-13 hours on data network.

Is this a normal behaviour??

One more thing i wanna know is when does the "on battery" statistics gets reset? Is it only after 100% charge?
[Samsung Galaxy R i9103] DeepankarS:
Buddy as i have experienced yes. :)

The voltage provided by the chargers matters i think.

Correct voltage at a consistent level is a must for any device :)

The non branded chargers at times made my touchsreen unresponsive too.

And charging from a usb cable makes my battery vanish faster.

i think any high end phone charger supplied by samsung should do well or equal to that given with our device.
[Samsung Galaxy R i9103] D™:
I think, Adam will explain it better coz he is doing something(i have forgotten) in electric science.
[Samsung Galaxy R i9103] The-Droidster:
Adam has already explained this in one of the threads...plz use search.;)
[Galaxy Note II Q&A, Help & Troubleshooting] frankieGom:
Hi all,

I recently got a HK N7105 and because it lacked the possibility to use a french keyboard I upgraded to a stock unbranded ROM from Sweden (XXDLL1) and succesfully rooted with the relevant CF_autoroot through Odin. Also installed TWRP 2.3.3.1.

Then, I connected the Note 2 to my corporate exchange server which enforced a full encryption policy (device and external SD card) so I had to type in a password at each boot time (with a "nice" swedish prompt that took ma while to decypher), plus a password to unlock the screen. All was well as the root survived the process.

Next I upgraded to a later stock ROM from France (XXDLL4 from SFR) to try and get rid of the swedish prompt. That worked fine (and root was loast in the process, as expected) but I hated the branded stuff so much I reverted to XXDLL1 until a proper unbranded "english" or "french" ROM is available.

At this point I decided to root again. I was running XXDLL1 like the first time and used the same autoroot tar from Chainfire. Except my Note 2 was still encrypted and after that it would not accept my boot password (a four digit PIN) anymore so I was guted and had to factory reset and root then reinstall everything before reconnecting to the exchange server.

Question 1: Does anyone know of a safe, proven way to root a fully encrypted Samsung device so I can go another upgrade without having to wipe the device first?

Why reinstall everything? Why not backup everything first so you can restore after the wipe? Well, it so happens that no recovery (at least neither CWM or TWRP) can read any encrypted media on the Note 2 at the moment. And no Recovery can actually fully backup the device as well.

Question 2: Does anyone know of a proper way to handle this situation with minimum hassle?

So far, the best I can think of is doing a Titanium backup and FTP the files to my NAS so I can retrieve them later. But (Question 3) will this be enough to restore my phone to the expected state after a stock firmware upgrade?

Thanks in advance,

François
[Galaxy Note II Q&A, Help & Troubleshooting] pasil.pt:
I think using Exynos Abuse apk will do the work ;)

http://xdaforums.com/showthread.php?t=2050297
[Galaxy Note II Q&A, Help & Troubleshooting] frankieGom:
Thanks for the heads up, I'll look into it. But to be clear, that answers question 1, correct?
[Galaxy Note II Q&A, Help & Troubleshooting] pulser_g2:
Yes that's a way to root the device.

Regarding encryption, very few people on xda seem to use it. So for that reason you'll have trouble finding out what works... I do use it though through choice so I can help you a bit.

When you encrypt the device, just consider /data to be off limits to anything not booted fully. That's why it asks you for your key in swedish - it can't see what language is in use until you unlock /data.

You will have issues using recovery with the device, since they can't read /data. You can use an external sd to perhaps load data to the device though.

I believe that TWRP might soon support the Samsung encryption on the device, meaning you could use it as recovery. Once you have a recovery that supports Samsung encryption, you should be able to consider it a fairly normal device.

Just be more cautious to backup your data as it is hard to recover if something goes wrong...
[Galaxy Note II Q&A, Help & Troubleshooting] vash_h:
If your using stock rom 4.1.2, exynos abuse method of root will not work. It's been patched
[Galaxy Note II Q&A, Help & Troubleshooting] frankieGom:
Fine, I understand. As long as I have a way to recover my data if I need to wipe I'm okay... I just have to hope Titanium backup gives me that until TWRP can manage encruption on the Note 2.

I'm really waiting for a stock rom that boots in English or French now.
[Galaxy Note II Q&A, Help & Troubleshooting] frankieGom:
Not the case with xxdll1. When was it patched, xxdll4 or xxdll7?
[Galaxy Note II Q&A, Help & Troubleshooting] chokxxi90210:
I am on Stock 4.1.2 and Exynos Abuse did work on my device, it's successfully rooted using the Exynos AbuseAPK on 4.1.2 :good:
[Galaxy Note II Q&A, Help & Troubleshooting] frankieGom:
OK, now I have been experimenting a bit with backups and upgrade and have trouble restoring my device fully. Let me explain...

I got hold of a TWRP build that seems to handle Samsung encryption fine through one of the TWRP devs (thanks!), so I decided to go back and try to update my device.

Current ROM: N7105XXDLL1_N7105TLADLL1_N7105XXDLK7_HOME.tar (obtained from Samsung Updates)

New ROM: N7105XXDLL7_N7105OLBDLL2_N7105DXDLL1_HOME.tar (obtained from Samsung Updates)

First I performed a complete Titanium Backup on the device and pulled the files to my laptop using ADB.

Then I restarted into TWRP 2.4.0.0 (got a prompt for my password), performed a full backup and pulled the files to the laptop using ADB.

(for some reason, I could not install the new ROM from TWRP (unable to open ZIP), but the ZIP looked OK, as well as after a second download which TWRP since did not like, so I had to use Odin instead).

Next, I flashed DLL7 with Odin. It worked, asked for the password at boot, but the device was unrooted at this point (I expected that).

Then, I flashed CF-Auto-Root-t0lte-t0ltexx-gtn7105.tar from Odin, but the boot up password would not be accepted anymore as I already knew.

Tried to flash DLL7 again from Odin, same thing

Flashed TWRP back on recovery partition, but on startup it would not ask for password anymore and the external sdcard looked empty to it.

I then copied my backup to a different, non encrypted sdcard and could restore from TWRP but the password would still not work after reboot.

I did a factory reset, restored backup, same result.

At this point I decided to factory reset, wipe Dalvik and format /data. The format did the trick and after TWRP restore of my original back up the device booted up, did not ask for password and all my data was there. Except the Exchange account I use for Corporate email wants me to restore encryption in order to work (I expected that too).

Back at DLL1, so I flashed DLL7 again with Odin (OK), rooted the phone, triangled away the flash counter and reflashed TWRP to recovery.

I was where I wanted to be except for one thing: I need to restore Corporate access. But when I let it encryp the phone it does nothing. I let it through the night and nothing). And if I reboot the phone no password is needed at boot time, yet the phone seems to behave as if it thought the device was still encrypted...

I reflashed my original, full, backup (i.e DLL1) succesfully but Exchange still wants to encrypt my device. Isn't restore supposed to restore the encrypted /data I backed up?

At this point I'm left with possibly tryinjg to go back to full factory settings, not use the backup at all, encrypt the device then restore my data from the Titanium backup I made.

Is there a better option?
[Galaxy Note II Q&A, Help & Troubleshooting] frankieGom:
[edited jan 18 - TWRP/TB behaviour]

My comments apply to encrypted devices only! I am not trying to talk down TWRP or TB here, as they provide splendid performance on non encrypted devices. I have come upon hard time trying to upgrade/restore an encrypted device using thoise tools, that's all

For those considering upgrading & re-rooting

encrypted

devices, don't!

I am finding the hard way that this is a one way street. At this point, my TWRP made full backup does not restore the device to the expected status. Each time I apply it, subsequent bootup takes several minutes and I end up going through the initial setup procedure. It seems the device for some reasoin goes through a complete reset procedure. :(

[edit]

Clarification: The TWRP build I use, 2.4.0.0 is an alpha build and I was not current when I restored my backup. I so happens that it was overwriting the encryption header on the partition, which messed things up bad, and had issues writing back the data partition, ending up in a factory reset status!

Using the latest drop as of today (jan 27) I was able to restore my original backup and am now back to my original state. All is well.

[/edit]

Titanium Backup is none better. It keeps telling me that my Android ID has changed, a host of system applications start to fail when I try to restore and generally speaking I have now spent between a good 20 hours trying to simply restore my data.

[edit]

this behaviour is probably linked to encryption. I know for a fact that TB works very well on non encrypted phones. The 20h figure is overall, not just with TB.

[/edit]

The end story is: root before you encrypt, and either don't upgrade or don't re-root if you do! If you do, be prepared for some rough times...

Unless someone has a cleat idea of how to do this properly without losing all your data, that is.

François
[Galaxy Note II Q&A, Help & Troubleshooting] pulser_g2:
I have had no issues despite doing upgrades, with and without wipes.

Titanium is fine, just stop restoring system app data. Seriously, what data do you have in a system app that you want to restore.

Restore your user apps, their data, and the xml based call, sms, Wifi backups. It will work fine.

Device ID isn't a problem - it's just trying to help you.
[Galaxy Note II Q&A, Help & Troubleshooting] frankieGom:
Sorry if I came across dissing Titanium Backup and/or TWRP. This was not the intent... I am sure both tools work real nice in general cases (and I have had success restoring data on a Jetstream before).

My main issue here is _full device encryption_ enforced by my company's corporate IT to allow me on the corporate exchange server. Do you have full device encryption on?

On my device, even after a full wipe and flashing a fresh stock rom Titanium Backup just did not work as I hoped. When I had to confirm individual popups of apps closing unexpectedly while it was proceeding and got nothing back in the end, what was I supposed to think? It could be that I don't understand how TB works... I was neither able to restore missing apps after the flash (missing apps: 0) nor installed apps data (they would close unexpectedly when started after restoring the back up). So I say: until full operation of TB on encrypted devices is documented, I will stay away from it, even though I am a registered user (and I do not plan to seek reimbursment)!

Anyway, I got to a belated happy ending (previous post edited).
[Galaxy Note II Q&A, Help & Troubleshooting] pulser_g2:
Yup I use device encryption :) Enabled manually, but it's the same encryption.

You should find that titanium shouldn't even be aware of it - the encryption is transparent!

I wonder... I'm sure lenny had that issue on a recent 4.1.2 "stock" ROM... And he doesn't use encryption...

I personally have had no issues with titanium on an encrypted device anyway :)

I notice you were using the newest rom - that's the one lenny had issues on.
[Galaxy Note II Q&A, Help & Troubleshooting] frankieGom:
Exactly like I thought, encryption should be transparent to Titanium Backup since it runs within the OS.

I have had problems restoring into 4.1.2 DLL1 (the build I came from) and DLL7 (the one I was trying to go to)

The point is moot anyway since the DLL7 I tried was actually branded (Singtel stuff all around the launcher) and did not include French, which is why restoring my TWRP backup was a tempting proposition.

Good to know TB runs fine with encryption as well. What ROM are you running?

François
[Galaxy Note II Q&A, Help & Troubleshooting] pat357:
About a backup : have you tried Online Nandroid (Playstore) (or similar, based on Onandroid) ? This makes a CWM or TWRP compatible backup while the device is running (everything should be unencrypted at this moment).

See http://xdaforums.com/showthread.php?t=1620255

About rooting : you can try the same trick as above, by using ADB-shell and pushing the needed files to root to the device while it is running.

For my S3 there is a Toolkit that automates all this (http://xdaforums.com/showthread.php?t=1703488), maybe there is something similar for your device ?

If not, you should still be able to do it using manual ADB-pushing.

I'm sorry I can't give you detailed instructions about the rooting as I'm not familiar with your device. Search here on XDA and you'll find more details.
[Galaxy Note II Q&A, Help & Troubleshooting] frankieGom:
Thanks for the suggestions, and no I had not tried Online Nandroid as I was not aware of it. Anyway, my main issue is now resolved since TWRP has include support for Samsung TouchWiz based encryption in 2.4 and that works well.

For those interested, the only remaining issues I have with TWRP regarding encryption are that if you want to format /data from TWRP (say, to remove encryption) it will fail unless you _do not_ enter the password at boot, and the TWRP formated /data cannot be re-encrypted (you must use stock recovery to factory reset/wipe the device or else the encryption step will sit deat in the water doing nothing). I suppose the second one is a bug that will be fixed in a later version.

I will check Online Nandroid out anyway, being able to make a backup from a live system sounds good!

François
[Galaxy Note II Q&A, Help & Troubleshooting] ludovicianul:
I have a similar issue. I had the device encrypted and decided to ROOT (using CF-AutoRoot). Unfortunately I cannot bypass the password screen now, although I know that I'm entering the right password. You are saying that if I flash TWRP everything will be fine?
[Galaxy Note II Q&A, Help & Troubleshooting] frankieGom:
Two separate things:

Root messing up encrypted touchwiz devices and twrp not handling touchwiz encrypted partitions properly.

The 2nd one, as much as I can tell, is fixed since before 2.5 so if youwork with the latest (2.6) you should be fine.

The first one I haven't played with in a while, but my finding is that you don't want to root a device once it's been encrypted. I've tried several different methods including rooting as you flag as is possible with twrp and all end up the same:the password is not recognised anymore! :(

The only thing that works for me is rooting before encrypting or only flashing pre-rooted ROMs.