yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Accessories] Eric214:
It will just lift up. No residue left really. Think of it as more sticky and does not bond like a glue. Until you crank one and have to remove it... It's kinda hard to describe. But it comes up as easy as it is to put down
[Galaxy Note 3 Accessories] cooljonL:
Ordered it. Should be here soon. Do I still need a screen protector with it do you think?
[Galaxy Note 3 Accessories] Sardonik:
I haven't noticed any sensitivity issues. To be fair, I put the protector on only a few days after I purchased the phone, but I honestly never noticed any ill effects after installation.
[Galaxy Note 3 Accessories] Eric214:
On my S4 or this phone I've never had sensitivity issue with either phone. The Spen works flawlessly with THE MIME Ghost Glass (is only 32mm thick as to Spigens tr glass which is .40mm thick)
[Galaxy Note 3 Accessories] cooljonL:
Well my case turned up and I love it. Such a well made product.

It makes my phone look kind of Storm Trooper like. I wonder if I can get a vinyl for the front.
[Galaxy Note 3 Accessories] Rasool-Hamilton:
The best case are always made by spG , they are always my first choice. great protection nearby beauty surely makes a great classic version of your phone ...:)
[Galaxy Note 3 Accessories] idle0095:
Spigen does make a good case. Just wish they made all of them like they do for the iPhone 5.
[Sony Xperia ZL] bigshowjh:
I was on 4.2.2 rooted 6506 and tried to do the rogers 4.3 upgrade through ota and it downloaded the file rebooted and began to install and then failed. Any others having this problem. If so did u resolve and how? I want to use the ota method because supposedly it preserves root.
[Sony Xperia ZL] Crash338:
Are you kidding me, are you saying that Rogers released through OTA their modified C6506 4.3 firmware before Sony even pushed out the generic 4.3 via PC Companion for the C6506 model.

THIS REALLY BLOWS MY MIND....having a little trouble believing it :p
[Sony Xperia ZL] bigshowjh:
Not sure about companion because I want the ota update this time, but at 730 est I downloaded it, the update failed. Ten redownloaded it it failed again. It was firmware version 569.
[Sony Xperia ZL] Crash338:
Wow, impressive. Carriers are usually slow to release updates. I'm still going to wait for the generic 4.3 update from Sony. I really don't like the bloat-ware Rogers installs. I believe root will be able to be obtained with Nut's DualRecovery method just like the tablet Xperia Z.

Your way to preserve root is a 50/50 chance. It worked on previous firmwares but since your system files have been modified, it may be the reason why the update gets interrupted.

To root the tablet Xperia Z from 4.1.2 to 4.2.2 was via OTA just like you are trying to do (survival mode) but I don't think it works anymore on 4.3

Good Luck!!
[Sony Xperia ZL] ren2008:
Survival mode in SuperSU worked for me when going to 4.4.2 from 4.4 stock on my N7.

Not sure about 4.3.

I am now on a rooted generic US rom and on a Rogers ZL and I'm still waiting. Hard to believe Rogers released anything at all...
[Sony Xperia ZL] 23-10:
Lets see pics!
[Sony Xperia ZL] bigshowjh:
Here is the screenshot, tried again no luck stops install after download. I download the file, the phone reboots, I see the green android with a file status bar for about 20 second and it reboots and tells me upgrade was unsuccessful
[Sony Xperia ZL] bigshowjh:
Didn't know about survival mode for super su, How is this done?
[Sony Xperia ZL] ren2008:
There is an option if you unlock superSU pro (you can unlock the app from the playstore for free). You tick it and system tries to preserve root after an OTA update. Didn't worked for everyone but oh well, Nexus 7 is so easy to root anyway! ?
[Sony Xperia ZL] 23-10:
Sony Canada just posted up on FB that they have 4.3 on PCC.

I tried it with my ZL c6505 but no update popped up.
[Sony Xperia ZL] Crash338:
I just checked on PCC and it is still telling me I have the latest firmware. I'll keep checking throughout the day.

Fingers crossed!
[Sony Xperia ZL] KatokiShima:
I got my 4.3 last night and it came through the air without PCC :D
[Sony Xperia ZL] zombiej79:
Wow shocking for rogers. They usually suck I'm in rogers and I hate them but good to see updates.coming.fast for once
[Sony Xperia ZL] CharlesG70:
Has anyone been able to update a Rogers ZL to 4.3 and either

keep

root, or

get

root

(with the NOT-unlockable boot loader).

I have been seeing the OTA alert for a week now, but I don't want ot risk loosing Titanium and Xpose Framwork.

Thanks,

C
[Sony Xperia ZL] jafferman:
How can I get back on Stock Rogers 4.2.2? where could I find this FTF I want to get off this generic 4.3 and update it the proper route
[Nexus 4 Q&A, Help & Troubleshooting] at4r1:
Just curious if anyone else has T-Mobile and also a Magicjack?

Up until a few weeks ago this was working fine, and had been for 2 years. But recently we are no longer able to RECEIVE calls from a T-Mobile cell phone. When you call the magicjack number from the cell you get a message stating "all circuits are busy now, please try your call again later. Message NC26955".

I am, however, able to call the call a T-Mobile cell phone just fine. So basically, OUTGOING calls to T-Mobile cell phones work fine, but INCOMING calls do not.

I have already verified that Verizon phones work fine, as do land lines. The problem is isolated to T-Mobile cell phones.

I have also spent hours dealing with both magicjack and T-Mobile support, both of whom claim that there is no issue with their service.

I have also verified that the correct ports (5060 and 5070 UDP) are open to the magicjack. Anyway, nothing there has changed either.

Anyone have any other ideas of things to try?
[Nexus 4 Q&A, Help & Troubleshooting] Berrydroidcafe:
Obviously this should not be happening. It does sound like a magic jack issue. If you like you can pm me the mj# and I'll give it a try from here in San Diego. Are there any other ports you can use btw? Just to cover all the bases?

Sent from my Nexus 7 (2013)
[Nexus 4 Q&A, Help & Troubleshooting] at4r1:
I was convinced it was a magicjack issue, until my brother called me from his verizon phone. The only phones that can't call me are tmo cell phones. However, I can turn around and call a tmo phone just fine.

I spoke with tmo support again today and they are going to send me a cell signal booster. So hopefully I won't even need the magicjack anymore if I can get our cell phones to work inside the house.

As far as the ports go, those are the ones that magicjack uses for VOIP.
[Nexus 4 Q&A, Help & Troubleshooting] Berrydroidcafe:
Ok. My wife use to use magic jack. She's in the Philippines and we never had any problems with it. I'm with tmo, that's why I volunteered to call you if you wanted. I would suggest wifi calling, but I'm not sure if tmo still offers that!

Well, hopefully this cell signal booster works for you.

Sent from my Nexus 7 (2013)
[Nexus 4 Q&A, Help & Troubleshooting] at4r1:
Yeah, if WiFi calling worked on the nexus 4 that would be awesome.
[Nexus 4 Q&A, Help & Troubleshooting] topaz143:
Magic Jack error NC26955

Please advise on the procedure to solve this problem. Thanks
[Nexus 4 Q&A, Help & Troubleshooting] at4r1:
There is no solution that i know of.
[Nexus 5 Q&A, Help & Troubleshooting] asdf002:
Anyone have this problem? My phone just all the sudden won't allow me to use the rear camera. Any app I open that requires the camera it defaults to the front facing and doesn't have an option to switch to the rear camera.

Possible that my camera module has fried???
[Nexus 5 Q&A, Help & Troubleshooting] aooga:
Possible. But first try flashing the factory images. It might fix it. If not, then you would have to RMA.
[Nexus 5 Q&A, Help & Troubleshooting] asdf002:
Here is screen shot
[Nexus 5 Q&A, Help & Troubleshooting] asdf002:
Just in case anyone is curious...update: factory restored the device to 4.4 and 4.4.2 but camera was still broken. Camera didn't work in safe mode either. Also found out out that the flashlight app didn't detect the flash either. So something was definitely wrong with the hardware. In process of getting RMA from Google.
[HTC One X+] PippoX3:
Building Cyanogenmod

In the terminal, now we'll make a folder where to store the Android source code. Typically will make it in your home folder, within a folder called like your projected ROM, to identify from other stuff, open your terminal and type:

mkdir –p ~/Cyanogenmod
cd ~/Cyanogenmod

Now we are going to initialize your local repository, with the "branch" cm-11.0 (KitKat), in your terminal:

repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0

And now, the most long part of the story: you’re going to get the source. We have to download around 10-15 Gbytes. First of begin the process, you must to know that you can accelerate the process related to your processor and, obviously, to your internet band. You can choose the number of simultaneous processes to start. They depends from the "#" in the "-j" parameter. E.g. the option -j6 is related to a “normal” processor. If you have a performant processor and/or internet connection, try to increment putting –j10 or more. On terminal:

repo sync -j6

From time to time, check the situation on output, maybe occurs a pair of hours or a whole night. But when all will be done, you’re ready to build Android!

Once you finish your repo sync, you’ll ready to build. In your terminal, into your working folder type (pay attention at the initial “dot”):

. build/envsetup.sh

The commands are loaded, now you can build (tune your -j# parameter as you want):

breakfast enrc2b && make -j6 bacon

At the end of all, your fresh ROM to flash will be in Cyanogenmod/out/target/product/enrc2b. Happy flash!

Thanks [MENTION=1660234]Lloir[/MENTION] for supervision.

IMPORTANT: to flash a KK rom on enrc2b you'll need the Lloir's CWM recovery, available here.
[HTC One X+] PippoX3:
Building AOKP

Reserved 2
[HTC One X+] PippoX3:
Building Carbon

In the terminal, now we'll make a folder where to store the Android source code. Typically will make it in your home folder, within a folder called like your projected ROM, to identify from other stuff, open your terminal and type:

mkdir –p ~/CarbonDev
cd ~/CarbonDev

Now we are going to initialize your local repository, with the "branch" kk (KitKat), in your terminal:

repo init -u https://github.com/CarbonDev/android.git -b kk

After, using your file browser, go to your Home, CarbonDev (enable "show hidden files") folder and enter into ".repo" folder too. Create a new folder named "local_manifests" and create a new file named e.g. "MyRoomService.xml", edit it with GEdit (disable, into preference, "always make a backup copy...") and paste the follow content into:

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<remote name="github"

fetch="https://github.com/"

sync-j="4" />

<project name="STELIX/android_device_htc_enrc2b_CarbonDev" revision="kitkat" path="device/htc/enrc2b" remote="github" />

<project name="STELIX/android_device_htc_tegra3-common" revision="cm-11.0" path="device/htc/tegra3-common" remote="github" />

<project name="STELIX/android_kernel_htc_enrc2b_CM" revision="cm-11.0" path="kernel/htc/enrc2b" remote="github" />

<project name="TheMuppets/proprietary_vendor_htc" revision="cm-11.0" path="vendor/htc" remote="github" />

</manifest>

You have just create a local manifest, to add certain projects that this platform haven't yet. It git clone my sources, which are simply CM sources modified for the CarbonDev frameworks needs.

And now, the most long part of the story: you’re going to get the source. We have to download around 10-15 Gbytes. First of begin the process, you must to know that you can accelerate the process related to your processor and, obviously, to your internet band. You can choose the number of simultaneous processes to start. They depends from the "#" in the "-j" parameter. E.g. the option -j6 is related to a “normal” processor. If you have a performant processor and/or internet connection, try to increment putting –j10 or more. On terminal:

repo sync -j6

From time to time, check the situation on output, maybe occurs a pair of hours or a whole night. But when all will be done, you’re ready to build Android!

Once you finish your repo sync, you’ll ready to build. In your terminal, into your working folder type (pay attention at the initial “dot”):

. build/envsetup.sh

The commands are loaded, now you can lunch:

lunch

Choose the number corresponding to your "carbon_enrc2b-userdebug" (and press ENTER on your keyboard!)

When the prompt come back you're ready to "make carbon":

make carbon -j6

Tuning your -j# parameter as you want...

At the end of all, your fresh ROM to flash will be in CarbonDev/out/target/product/enrc2b. And Happy flash!

Thanks [MENTION=1660234]Lloir[/MENTION] for supervision.

IMPORTANT: to flash a KK rom on enrc2b you'll need the Lloir's CWM recovery, available here.
[HTC One X+] PippoX3:
Reserved 4
[HTC One X+] PippoX3:
Reserved 5
[HTC One X+] PippoX3:
Reserved 6
[HTC One X+] Cuzz1369:
I'm using mint 16. What should I do different?

Sent from my hammerhead
[HTC One X+] PippoX3:
Usually is recommended Ubuntu or Mint... I think there is no difference. Make attention if during packages installation it report any error.
[HTC One X+] Cuzz1369:
Awesome. Maybe you could add a guide on how to cherry pick commits next?
[HTC One X+] Cuzz1369:
It tells me I have java version 1.5.0

java version "1.5.0"

gij (GNU libgcj) version 4.8.1

Copyright (C) 2007 Free Software Foundation, Inc.

This is free software; see the source for copying conditions. There is NO

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Installed 1.6 and get this error

You are attempting to build with an unsupported JDK.

You use OpenJDK but only Sun/Oracle JDK is supported.

Please follow the machine setup instructions at

https://source.android.com/source/download.html

need some help here.

Edit: Figured it out, building now. Thanks
[HTC One X+] PippoX3:
Good. Hope you remove your open java. The first terminal remove any not supported java. Follow the guide step after step.

The cherry-pick is so simple to apply. Will see after. Thanks.
[HTC One X+] Lloir:
you can use OJDK with ALL the sources.

it will just come up with that "warning" and then will carry on building perfectly fine
[HTC One X+] MasalaMan:
thanks for the guide

can i use knoppix/debian instead of ubuntu ??
[HTC One X+] Lloir:
Yes, I use Arch. The instructions for Debian are essentially the same as Ubuntu
[HTC One X+] PippoX3:
Thanks mate. I haven't all this experience on different distributions. If I have a little of time, today I will add another slice to the pie...
[HTC One X+] skulldreamz:
Thank you so much for this guide [MENTION=2837935]PippoX3[/MENTION] I am about to have the most fun of my life now. Thanks again my friend :)
[HTC One X+] PippoX3:
You're welcome mate. To share should serve to make more people happy! ;)
[HTC One X+] Cuzz1369:
In this thread it say you need proprietary files from the device. I don't see that step on your guide. So which is the right way?

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

COMPILE From Source For Any Phone On Linux Distros [BUILD ENVIRONMENT TO COMPILE]

Sent from my hammerhead
[HTC One X+] Lloir:
Github.com/themuppets/htc all the prop files are uploaded there :)
[HTC One X+] Cuzz1369:
Thanks, I'm trying to build for hammerhead and I don't even know what to do with the blobs if I could find them. I'll keep googling though.

Sent from my hammerhead
[HTC One X+] Lloir:
Github.com/themuppets/lge ;)

They go into vendor/lge
[HTC One X+] Cuzz1369:
Ya I figured that lge part out. Thanks bud.

Sent from my hammerhead
[HTC One X+] Cuzz1369:
OK next stupid question. Are the proprietary files universal or just for cm? Say I want to build "slim" down the line. Can I use these same ones or am I gonna have to find "slim" specific ones?

Sent from my hammerhead
[HTC One X+] PippoX3:
If you're building for HammerHead, you don't need to add manually nothing, just let the scripts downloaded itself, repo init the slim sources, lunch the hammerhead and it does the rest...

Inviato dal mio Nexus 5 utilizzando Tapatalk
[HTC One X+] Cuzz1369:
Cool. Started a cm build to see how it goes. Seemed like the easiest place to start. Once I understand better what I'm actually doing g here rather than just copy and pasting stuff I'm gonna try some other stuff.

Sent from my hammerhead
[HTC One X+] PippoX3:
If you're interested to build for hammerhead follow my guide on Nexus 5 - General section. Here for your info, about "proprietary blobs" and device parts:

A device merged into a ROM source and its frameworks has always:

A device part specifical for its own (typically located into /device/"vendor"/"devicename")

A possible device part specifical for its processor (typically located into /device/"vendor"/"processor class/name")

A kernel part specifical for its device (typically located into /kernel/"vendor"/"device name")

A vendor blobs part generical with inside all or part of vendor devices (typically located into /vendor/"vendor"/"device name")

The (1) if specifical for the rom (Carbon is

slightly

different from CM, from AOKP or Slim).

The (2) maybe the same for alls.

The (3) maybe the same for alls.

The (4) maybe the same for alls.

I saw "maybe the same" for (2), (3) and (4), because often the teams make choice on every part to optimize the use and functionality of its rom.

In the specific (for the HOX+) we give this four parts from CM (that fortunately supports enrc2b) to insert them into another platform. Because our device isn't supported.

The (1) part will be modified in a number of make files, the (2), (3) and (4) instead will be the same.

While the guide grows, we can see for each flavour what changes.
[HTC One X+] aardappel12:
Woohoo, your guide inspired me enough to actually take my time and figure this stuff out.

So here it is; my first selfmade CM11 build including S2W, awesomecakesssss!

Now it's time to figure out how to build stuff that's not already around yet I guess ^.^.

Thanks anyway PippoX3 and Lloir!
[HTC One X+] sorceforge:
Thanks fora a good guide, and without your guide, I could not build CyanFox, which is a custom rom based on CM.

Because it is using the same based as CM, the build was successfully done.

However, the problem starts when I install it. When I get into the Setup Wizard, after it catches the 3G signal, Setup Wizard FCs and says 'Setup Wizard has been stopped.' Even full wipe does not help solving this glitch, so I think the build itself has the problem.

As one of the gurus, do you have any suggestions? Anything would be helpful.
[HTC One X+] PippoX3:
First of all, excuse me for not have completed the guide with others platforms tips (AOKP, Carbon, Slim). But device sources are in update yet, and see as I would to link you my github for it... I prefer to wait it is almost workin (stable is an utopia, for the moment! :laugh: ).

Regard your issue:

I imagine that CyanFox doesn't support enrc2b. Then, have you a local_manifest.xml to import devices/kernel parts? Which? Show us, please.
[HTC One X+] sorceforge:
It has the same build system as CM, so it was possible to build it with breakfast / brunch command. Therefore, I could built it with brunch enrc2b command, and I can say it downloaded the original cm system blobs in github of Lloir and TheMuppets.

Well.. Too bad I could not see logcat... I'll attach it if I can.
[HTC One X+] PippoX3:
Don't mind logcat. When you brunh/lunch the device, it create a local_manifest.xml (or similar) for you into the folder ".repo/local_manifests"

Take a look and post the content of the xml file that you find into.
[HTC One X+] sorceforge:
First of all, thank you for your kindness. I present you both my manifest file and roomservice file in here.

http://pastebin.com/XbTHh0Hy
[HTC One X+] PippoX3:
Hello! You're welcome.

First of all, delete your folder device/htc and vendor/htc and after, please modify your local manifests as:

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<remove-project path="vendor/htc" name="TheMuppets/proprietary_vendor_htc" revision="cm-11.0"/>

<project path="vendor/htc" name="TheMuppets/proprietary_vendor_htc" revision="cm-10.2"/>

<project name="CyanogenMod/android_device_htc_enrc2b" path="device/htc/enrc2b" remote="github" revision="cm-11.0" />

<project name="CyanogenMod/android_device_htc_tegra3-common" path="device/htc/tegra3-common" remote="github" revision="cm-11.0" />

<project name="CyanogenMod/android_kernel_htc_enrc2b" path="kernel/htc/enrc2b" remote="github" revision="cm-11.0" />

</manifest>

then you can repo sync again and wait.

Perform a "make clean" or "make clobber" before build again and let me know.

Note: for the vendor blobs, we're using the 10.2 branch yet. Don't ask me why... try to ask to Lloir! :laugh::laugh::laugh: enrc2b's prob.

And be sure to pick the branch 11.0 from cyanogenmod, for the device/kernel projects...
[HTC One X+] Lloir:
We are using the 10.2 branch? Since when?? I've been using cm-11.0
[HTC One X+] PippoX3:
:laugh: When we start build KK, you told me "use TheMuppets vendor htc blobs, branch 10.2, for now..." since I haven't news about, I follow to use 10.2 branch. I'm using them actually.

And about [MENTION=2715560]sorceforge[/MENTION] issue, I think his manifest git clone the projects with their default branch (cm-10.2), see as CM haven't yet change to cm-11.0.
[HTC One X+] Lloir:
Cm is using Cm11 vendor files have changed in themuppets for the enrc2b cm11
[HTC One X+] PippoX3:
Well, I'm building with a lot of new stuff. Included your new Muppets... What do you think to track them into cm.dependencies file?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[HTC One X+] sorceforge:
OK, thank you for your courtesy again. However, it doesn't work like other days. To tell the truth, I built a rom after I completely wiping the directory and modifying default manifest file like;

<!-- Like What PippoX3 told -->
<!-- project path="vendor/htc" name="TheMuppets/proprietary_vendor_htc" revision="cm-11.0" -->
<project path="vendor/htc" name="TheMuppets/proprietary_vendor_htc" remote="github" revision="cm-10.2"/>
<project name="CyanogenMod/android_device_htc_enrc2b" path="device/htc/enrc2b" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_htc_tegra3-common" path="device/htc/tegra3-common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_kernel_htc_enrc2b" path="kernel/htc/enrc2b" remote="github" revision="cm-11.0" />
</manifest>

Maybe, it happened because the rom is not the same as the original CyanogenMod. :( However, I still don't know why does the whole build process was finished successfully...
[HTC One X+] Lloir:
Pippo....it IS tracking from that...it's pulling everything in that, from CM-11.0 branches
[HTC One X+] Aust S5:
Hi guys,

Is there any real reason why I shouldn't use VM virtalbox software to boot up ubuntu? I am running a reasonable spec quad core processor and good memory but on a laptop. It is also on a cooling mat.
[HTC One X+] Aust S5:
You have all inspired me to take the leap of faith. Here we go. I'm going to try a carbon ROM using VM virtualbox. Any hints whilst I wait for the syncing?
[HTC One X+] PippoX3:
The reasons are: disc space, processor and memory. Compiling android take away a lot of memory (4Gb) and processor's tasks. And the sources together to out folder, needs at least 15Gb. Do your counts for a virtual machine... I tryed too in past...
[HTC One X+] Aust S5:
I have 16gb mem and core i7 with 2.8ghz, gave it a 140GB vHD so should be enough, either way we will see. So far the only differences have been the directory made and then the carbondev repo init from github. Still syncing, but will then follow the carbon dev terminal commands to build.
[HTC One X+] PippoX3:
You can always try, there's nothing wrong... after you'll assess if was good.

Take a look at post #4. Istructions ready for you.