yashsingh1/xdaforums huggingface dataset:
[8125, K-JAM, P4300, MDA Vario General] lotion:
I've scoured the forums to no avail ...

My problem is this: I sync up at home and at work. When I'm at home, I've been able to connect to the net through passthrough until recently. I've determined the problem with why I can no longer sync at home is due to a local network issue (unavoidable). I've also been syncing up at work through a proxy. That is, up until the other day. I'm not entirely sure what I'm doing is right. Basically, I have my "programs that connect to the internet" set to a blank profile, while my "programs that connect to a VPN" set up to "My Work Network" that has my company's proxy in it. I have my activesync at home set to connect to the internet, and my activesync at work set to connect to work. Why can't I connect at work any longer? I'm very confused by the whole thing (what does setting your computer's activesync to "work" change on your PPC, how does "work" know to use "my work network" ... that sort of stuff) and I would greatly appreciate the help.

EDIT:

I've resolved the issue but not logically.

Basically, I played around with it to figure out what settings it uses when it connects each time. At first I could connect when I applied my proxy settings to the profile I use for "programs that connect to the internet." This seemed to make sense because, after some research, I've found out that the work profile should only affect intranet addresses. After some tinkering, that stopped working, so I applied the proxy settings to both that and my work profile. After some more messing around (stopped working for a time), I ended up clearing the proxy out of both profiles, and putting it back into my work profile. It is now working. I'm glad but I'm still confused. Can anyone tell me what is going on? Isn't the work profile only supposed to affect internal addresses? If so, why am I now connecting through the proxy properly even though my internet profile (in this case, a profile named "blank") no longer has any proxy information?

In addition to all of this, I'm having a problem that, it seems, is very common and that is that I always get the "unable to get server-assigned IP address" dialog whenever I connect via activesync even when I'm able to passthrough.
[8125, K-JAM, P4300, MDA Vario General] lotion:
bump

bump for post edit.
[Samsung Galaxy Nexus] brunobliss:
My phone is freezing and stutering all the time, it's most noticeable when i press the apps key (third on the right). I've tried several different ROMs (always wipping data,cache system) as it appeared to be a software problem but it starts right off as i'm at the initial configuration, keys are not even responding properly, when i press a key it takes about 3 to 4 seconds to respond :(

I'm also under the impression the phone is overheating, it's getting really hot on top back near the camera. Any suggestions of what i might try?
[Samsung Galaxy Nexus] latenightchameleon:
Are you using cyanogenmod or CM-based ROM by a chance? I've had horrible lags on it, especially on the latest nightlies. If that's the case, try something light and AOSP-based like slimkat.
[Samsung Galaxy Nexus] brunobliss:
I have tried slimkat, aokp, cm11 and they all seem to be getting slower everytime i flash a new rom :( I think this started to happen when i first attempted to do a full backup, the phone froze during the process because it was running out of memory. It was a pain to get it working again because it was sooooooooooooooo slowwwwwwwww.

Then i just booted to cwm did a full system, data, cache wipe and installed a new ROM, during the initial steps phone starts stutering, no matter what rom it is.

My guess is that there are still some files somewhere causing the problem.
[Samsung Galaxy Nexus] isajoo:
First thing, Always keep >4Gb of free space.

Install/run Lagfix app.

Backup all important/personal files to PC, delete all files/folder on GN, copy over only ROM/gapps zips and flash a clean install(wipe data 3 times in row) and after ROM boot up copy back your files.
[Samsung Galaxy Nexus] latenightchameleon:
Oh, in that case it is most likely a free space issue as isajoo pointed out. I suggest using clean master to free up some space and get rid of some big files you don't need.
[Nexus 7 (2013) Q&A] mbressman:
I'm hoping someone might be able to help me recover my Nexus 7 which appears to be bricked currently. It is the 2013 version, and it was never rooted initially and was running stock firmware. (By the way, I'm not the most proficient with messing with my Android devices or even with the terminology, so I apologize in advance if I might require clarification on some of the responses).

A few days ago, I woke up to discover that somehow my home screen had reverted back to the way it was upon initially getting the device. This wasn't a big deal since I didn't lose any data or apps, but I figured something might be wrong and even posted about it on Google's product forums. Then, last night, I attempted to update to 4.4.3 because it had been prompting me to do so for a week or two. It downloaded and attempted the update, but it failed. It then eventually restarted, but upon loading up Android I got an error message that stated:

System UID's Inconsistent

UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable

with a button to click that says "I'm Feeling Lucky" - I clicked the button figuring I could at least get back in to back up my data, but after about 30 seconds the device just rebooted again (all I managed to do was accidentally click the Chrome icon) and now it is just stuck at the initial boot-up screen displaying the Google text logo.

I have tried to hold down the volume button and hit power, and I get to a screen with 4 options I can cycle through: Recovery mode (which will just put me back the Google text logo), Power off (which turns off the device), Start (which puts me back to the Google text logo), and Restart bootloader (which brings me right back to this menu options page). I'm attaching a screenshot of this page.

I spent about an hour on the phone with Google support, but they were basically useless. I then did some research and downloaded Skipsoft Unified Android Toolkit and was able to get the device to be recognized when it was in that 4-option mode by the Skipsoft Toolkit. However, all fastboot options I tried didn't seem to succeed because the Bootloader was locked. I figured I would try to unlock it, and it told me that in doing so it would wipe my device (so be it I figured since I had already pretty much kissed my data on there goodbye at this point). However, it seems to try and wipe it (even giving me a prompt on the actual Nexus 7), but then just sits and does nothing that I can see (see attached screenshots).

Anyone have any ideas/suggestions? Thanks so much!
[Nexus 7 (2013) Q&A] xbi0s:
To be safe, with a stock device that was not rooted... I would go ahead and use the Skipsoft program to flash the stock image back on the device. This should alleviate any future issues with the OS on your device.

I believe it to be Option #9 on Skipsoft.
[Nexus 7 (2013) Q&A] mbressman:
Thanks for the reply - I attempted your suggestion, but it didn't work because the Bootloader is still locked; and attempting to unlock the Bootloader seems to stall on erasing userdata.

Any other thoughts? Thanks!
[Nexus 7 (2013) Q&A] mbressman:
Anyone else have any suggestions/ideas? Thanks!
[Nexus 7 (2013) Q&A] Aerowinder:
Download ADB from my signature.

Put the device in bootloader mode (power+vol down), open fastboot.exe and type fastboot oem unlock.
[Nexus 7 (2013) Q&A] mbressman:
When I try that, I get:

C:\Users\User\Desktop\ADB & Fastboot API 19 (19.0.1)>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...

And it just hangs there....

The Nexus 7 did prompt me whether I want to unlock the bootloader and I selected yes (with the volume and power keys), but then it just hangs at that selection screen as well...

Any ideas??

Thanks!
[Nexus 7 (2013) Q&A] Aerowinder:
I changed the wrong link in my signature. The ADB link correctly points to version 19.0.2 now. Try that one. Try a different cable if you have one, try a different USB port if you can.
[Nexus 7 (2013) Q&A] mbressman:
Tried two different cables on two different USB ports with the new 19.0.2 downloads you posted - still having the same thing happen. Could it be the computer I'm using, or the drivers I installed (I used the Skipsoft Unified Android Toolkit drivers)? Or is my device just totally bricked and unrecoverable?

Thanks!
[Nexus 7 (2013) Q&A] Aerowinder:
You can try different drivers. Uninstall current ones, and install the ones from my signature.
[Nexus 7 (2013) Q&A] mbressman:
Ok, so I removed the Clockworkmod ADB drivers from add/remove programs (or uninstall programs - whatever it is called now on Win7), then I went into device manager and deleted the driver for Google Nexus BootLoader Interface, and then I rebooted. After the reboot, plugging the Nexus 7 in showed no driver detected, so I downloaded your Koush Universal ADB drivers, extracted them, and used them to install the Google Nexus Bootloader Interface drivers again (that's what it detected for my Android when I pointed the device listed in device manager to the extracted folder).

I then ran "fastboot oem unlock" but it's still getting stuck at the same place: (bootloader) erasing userdata...

Anything else I can try?

Thanks!
[Nexus 7 (2013) Q&A] Gawson:
Hi,

I have the same issue since yesterday. When I pulled my nexus from my backpack (charged 12 hours earlier) its battery was drained. After charging it nexus stucked on google screen during normal or recovery boot. Oem unlock also hangs on erasing userdata. I'm looking forward for any solution to this.

Maybe some ****ty update? I've got the LTE version.
[Nexus 7 (2013) Q&A] mbressman:
Anyone have anything else I can try?

I'm currently working on getting ASUS to replace the device under warranty - but they want me to send it in first, and I'm concerned that while I can't access any of my data on it, the data might still be there and potentially accessible to others (and I'd prefer to not have all of my confidential data that I stored on there accessible to anyone else). Unfortunately, ASUS won't replace/repair it unless I send it in, so I'm between a rock and a hard place...

Any help or advice is greatly appreciated!

Thanks.
[Nexus 7 (2013) Q&A] Gawson:
I've tried every single way to unbrick my nexus. After 2 days of searching send it for repair. Without any questions they replaced mainboard. Problem solved hard way.
[Nexus 7 (2013) Q&A] mbressman:
Gawson - when you got it back did it still have your data on it, or was it wiped?
[Nexus 7 (2013) Q&A] Gawson:
When I got it was wiped. Flash is on the mainboard so there was no way they could save my data. They do not migrate your personal stuff.

Now its working like new. In fact it has all new guts except battery and screen.

Only problem is that now auto brightness sensor is giving crap instead of useful data. I don't know if its hardware related or just 4.4.3 issue.
[Sony Xperia ZL] r_s_dhar:
Have I bricked my xperia-zl?

(originally posted in the wrong place, one of the members directed to repost it here)

1. My Phone is xperia-zl C6502 build 10.4.1.B.0.101

2. Successfully unlocked the bootloader

3. Used Flashtool to Iinstall CWM

4. Now my phone

a. does not boot: tried all combination of switches, including the yellow button next to the SD Card

b. is not recognized by flashtool any more

c. not recognized by Sony PC companion

d. no light/indication when put to charge.

5. I cannot flash stock firmware and then reboot the device as the device is no more recognized by flashtool?

Want help, desperately.
[Sony Xperia ZL] St.Jimmy90:
I'm sorry to say that, but you're still in the wrong place, you need to go there:

http://xdaforums.com/xperia-zl/help

Anyways, did you flash the correct kernel? Or did you just try to flash a recovery?
[Sony Xperia ZL] r_s_dhar:
St.Jimmy,

I am a first time member, joined only yesterday (that is after my tail caught fire!); sorry to be still in the wrong place. Could moderators please relocate my post to the right location? Thanks a million to this wonderful site.

Thanks for the reply. I think installing CWR required flashing a "boot.img" file. The device gave up its ghost after flashing the boot.img file. As of now, there seems to be a slight improvement -- there is a red LED indicator that has come on when put to charging; it is faint, but it is there alright! Any chances of resurrection or is my phone really gone to its Heavenly Kingdomo?
[Sony Xperia ZL] kedar a.k.a. 3K:
I suggest u first charge it for 1-2 hours and then try using flashtool

Sent from my MT25i
[Sony Xperia ZL] r_s_dhar:
Kedar,

Thanks. I have charged my phone overnight (10 hours). Still LED glows red. For a while I could connect in flashboot mode (LED=blue). Any help?
[Sony Xperia ZL] r_s_dhar:
I can now sometimes connect in flashboot mode; flashtool initially recognizes the phone but when I try to flash a stock ROM, asks the phone to be connected (as if it has not already recognized the phone)! HELP PLEASE!!
[Sony Xperia ZL] androidtweaker1:
might have a solution for the recovery if the fastboot is working

download minimal adb and fast boot from here

place boot.img in minimal adb and fast boot folder after installation

Put your phone in fastboot( hold power up key and plug usb)

open minimal adb and fast boot application

it will open a cmd window

type fastboot flash boot boot.img

after that type fastboot reboot

your phone will restart now

PS: your phone is refusing to boot because the recovery is corrupted
[Sony Xperia ZL] kedar a.k.a. 3K:
What if you fastboot a custom kernel with inbuilt recovery and then flash a Rom with the recovery?

Since you have fastboot working

Sent from my MT25i

---------- Post added at 07:53 AM ---------- Previous post was at 07:49 AM ----------

What if you fastboot a custom kernel with inbuilt recovery and then flash a Rom with the recovery?

Since you have fastboot working

You may try the method by [MENTION=5541850]androidtweaker[/MENTION] mentioned above as it is similar :thumbup:

Sent from my MT25i
[Sony Xperia ZL] kingvortex:
First, what exactly did you flash to your phone and where did you get it from?
[Sony Xperia ZL] r_s_dhar:
Androidtweaker1: Thanks. Cannot connect in fastboot mode. The blue LED comes on but the device is not recognized (adb drviers etc. no problem, all correctly installed, all set).

kedar: cannot connect in the fastboot mode. See reply to Androidtweaker1 above. Thanks

kingvortex: Thanks. I was trying to follow the following tutorial:

After downloading Z_DooMLoRD_AdvStkKernel_FW-4.3-101_v12.zip, place it in external SD Card of your smartphone

Now extract Z_DooMLoRD_AdvStkKernel_FW-4.3-101_v12.zip on your PC’s desktop and copy boot.img

Paste this file inside the folder where you have installed Minimal ADB and Fastboot

Now turn off your smartphones completely

Plug in mobile’s USB in cable in PC port only

Hold Volume up button and plug in USB cable in mobile’s port

LED will turn blue (If it does not remain blue for long, then read Optional part in bootloader unlocking method explained above

Once you are successfully in fastboot mode, then you can continue

Now type Fastboot flash boot boot.img and press Enter

It will flash boot.img file on your device

Now unplug the device and boot it up

As soon as you see purple colored LED, start pressing volume up and down buttons repeatedly, until you are in CWM mode

In CWM Mode, select “Install Zip”

Now select the storage you have put that zip file in and just confirm its installation

There are two ways to navigate in this CWM recovery

You can navigate with volume buttons and make a selection with power button

Another way of navigating is by swiping your finger on empty area in recovery

Swipe up to move up, swipe down tp move down, swipe right to make a selection and swipe left to go back

After installation is complete, go back to main menu and reboot your smartphone

Congrats! You have successfully installed CWM custom recovery on your smartphones
[Sony Xperia ZL] remav:
I have a similar situation and I'm stuck.

Q: is working the minimal adb if in the settings was not checked the debug mode?

In my case I can go in fastboot mode each time but not help.

When I try to go in flash mode, there is strange because the flashtool say it it connected in flash mode , even the PCC say this, but the LED it's not green, is off, first is try to go green after get red and after off, but the software say is in flash mode.

I can try to flash any ftf, it's working without erors but my phone it's still dead after restart, even SONY logo is not appear, just vibrate once.

Other strange think, each time when I made a new flahing, there is a status message of device, it say that the version of ftf is 230 even if last time I was tring to flash 101 for ex and was finished without errors. Always show the same ftf version like nothing is changing inside. The only thing can change is the BL, lock or unlock and I can see this in the status device, this is made in fastboot mode and there I have the blue LED.

Can anybody give me some ideeas to fix this?

have the log of flahtool attached.

Thanks.
[Sony Xperia ZL] Aljecama12:
SOLUTION

Hey, have you already solved your problem? I had the same as you and I could fix it, I will try to submit a post here explaining the steps I followed
[Sony Xperia ZL] remav:
I solved but in other way. I bought another Zl with the battery dead and I replaced the motherboard. I have it now working from gew months without any problems. The old motherboard is still broken.
[G Pad 8.3 Q&A, Help & Troubleshooting] techinv:
Anybody with the GPE G Pad get the OTA update for 4.4.3?

If you did, let me know how it compares to the 4.4.2 ROM (speed, battery, etc).

Thanks
[G Pad 8.3 Q&A, Help & Troubleshooting] cam30era:
Not released yet for our device.
[Galaxy Tab 3 Q&A, Help & Troubleshooting] dsilx:
title says it all

:confused:
[Galaxy Tab 3 Q&A, Help & Troubleshooting] paranoidmarvin42:
On the Dev subforum depending on what Tab 3 7, 8 or 10.
[Galaxy Tab 3 Q&A, Help & Troubleshooting] dsilx:
where at

could u post a link i tryed posting it on the dev page where all the other roms are but it wont let me it says i dont have permissions
[Galaxy Tab 3 Q&A, Help & Troubleshooting] moonbutt74:
missing kink......sorry i couldn't help it

you have to upload your rom to a host like dev-host or androidfilehost first then provide a link

in your post here. but in order to do that you must first make a prerequisite number of posts on xda.

for what device is this rom? if it's for sm-t210 [tab 3 7.0] or gt-p5210 [tab 3 10.1 wifi]

once you've uploaded it to a host send me a pm with the link and i'll see if i can flash it and take it for a spin.

if it's good i'll suggest it here with link.
[Galaxy Tab 3 Q&A, Help & Troubleshooting] paranoidmarvin42:
Read the rules first. If you've followed it, click new thread. I'm not sure if there is a number of posts required before creating a thread in the dev page like the limit to replying. You can contact a moderator for help. You can see who beside the new thread button.
[Galaxy Tab 3 Q&A, Help & Troubleshooting] dsilx:
mind F******

iv uploaded it to mediafire because i dont like google drive and mega was taking forever but il upload the link android file host

aka i am aware of some of the bugged apps that wont open when installed
[Galaxy Tab 3 Q&A, Help & Troubleshooting] Nonta72:
Tab 3 Development forums, depending on your tablet's screen size i.e 7, 8 or 10.1.

Can't wait to see another rom, we're missing them, really !

Sent from my room mate's computer :p
[Moto X Android Development] jsnweitzel:
These are unified builds and will work on all variants of the X and the unlocked Droid Maxx too.

The following models are supported:

XT1052

XT1053

XT1055

XT1056

XT1058

XT1060

XT1080

The updater has been testing and works well on the X.

Update Notes:

06-16-14 - add option for proper 10MP camera, hover options under interface in settings (kill low priority and non-clearable notifications)

06-22-14 updated to 4.4.4, kernel has overclock to 1890 vs stock 1728.

07-13-14 The latest build will have the media profiles enabled so third party apps like open camera and perhaps others will record SD-HD video. Still working on trying to get the built in camera to work for recording. If you try the stock app it will crash and you must either f/c it or reboot.

08-03-14 Quiet hours will now work by time, no longer using devhost for alternate download see link in first post.

09-18-14 - New builds will now be named "ghost". You should be able to dirty flash over the latest nightly.

http://www.drdevs.com/devs/teamliquid/Nightly/Moto_X

Note Speakerphone may still be a little buggy.

[url="https://plus.google.com/u/0/communities/117452480298315341829"]LiquidSmooth G+[/URL]
[Moto X Android Development] metaljr81:
Safestrap/locked bl?
[Moto X Android Development] jsnweitzel:
Unlocked only.
[Moto X Android Development] infinit22:
Just got this set up. Running very smooth! Will be using this as my dd.

Will this be updated with the built in updater?
[Moto X Android Development] sorullo_xgrx:
I'm guessing since is official it should.. I'm back at smooth roms
[Moto X Android Development] kenosis:
Can It use it on XT1053? Last time on 4.4.2, i always face "Failed to sign-in hangout" problem.

By the way, msm8960dt is for which version? :D
[Moto X Android Development] gueszman:
Is this using original active display??...

Stock motorola camera or Aosp?

MotoX
[Moto X Android Development] DaRkRhiNe:
AOSP active display. Motorola active display hasn't been replicated yet
[Moto X Android Development] ad fu:
Nice work!
[Moto X Android Development] rebretz000:
Does the Active Display work like Motorola's?

When you move the phone it breaths and allows you to swipe the phone awake instead of the power button?
[Moto X Android Development] imparables:
Nice...thanks.

Sent from my Unlocked VZW M-O-T-O XxX
[Moto X Android Development] infinit22:
Only thing that doesn't seem to work properly is pocket mode under lockscreen. Everything else is great
[Moto X Android Development] kjjjnob:
First bug

Get FC when i try change the icon battery to number percent, only this problem. Incredible fast and smooth. Thanks
[Moto X Android Development] jsnweitzel:
We have a "shake to wake" feature but it requires a bit more movement than moto's version. You can also adjust how often ongoing notifications are redisplayed.
[Moto X Android Development] oeusr:
Is hover in the latest nightly? I saw mentions of it in the change log but I'm not sure if it's just preparing for future versions.

Can't wait to try this but I can't flash it until later today or tomorrow. Always loved liquid smooth rooms

Edit: has hover! awesome thanks
[Moto X Android Development] rocketsaucev2:
Sweet! Gonna flash this and try it out

Sent from my Nexus 10
[Moto X Android Development] kenosis:
Can anyone flash with TWRP 2.7.1.1?
[Moto X Android Development] jsnweitzel:
I haven't tested 2.7 still using 2.6. I'll upload a copy of it to the server (same folder as the rom).
[Moto X Android Development] kenosis:
I am trying to flash this rom and other Roms by using 2.7.1.1. I can't flash. I will downgrade TWRP and try again.
[Moto X Android Development] jsnweitzel:
Sound issue fixed, new build up.
[Moto X Android Development] lslacker:
Was there a dt build for it? Been waiting for this. Is anyone else having issues with wifi reconnecting (like leave the house and come back and wifi doesn't reconnect...have to reboot to get it working again)? It could just be me and my tasker jobs but I couldn't find anything in Tasker.
[Moto X Android Development] Blue_Churo:
Hi! This rom looks awesome, but for some reason I can't connect to the download server... are the links dead? :confused:
[Moto X Android Development] CsR0501:
Second post... Alternate for download ROM [emoji111]

Enviado desde mi Moto X mediante Tapatalk