yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] boeder9:
Bump, can anyone please help me?

Will reflashing the Siyah erase all my internal data? or is there a reflash method via odin that'll keep my internal data?
[Galaxy S II Q&A, Help & Troubleshooting] Saber:
No, reflashing siyah will not wipe your internal data. You can flash siyah under ODIN, CWM or TWRP. Siyah is not under development any more so I'd advise you to use a different kernel. If your android version is stock jelly bean, go with apolo kernel 4.14. If on kitkat, go with apolo 7.1.
[Galaxy S II Q&A, Help & Troubleshooting] boeder9:
Thanks. I'll just reflash siyah because its what I have and I'm not proficient with GS2. I need to remember what ver I had. Can't use cwm because the phone doesn't boot at all, can't go to recovery. Odin is my only choice here.
[Galaxy S II Q&A, Help & Troubleshooting] boeder9:
OK, I tried to flash via Odin v3 but the phone isn't recognized. I tried the power+home+ vol up, nothing. I already have the Samsumg drivers and KIES isn't running.

Can someone please help me as a matter of urgency? Thanks!
[Galaxy S II Q&A, Help & Troubleshooting] nhmanas:
1. What version of android did you use before your phone dead?

2. Stock or AOSP?

3. Does your phone offline chargable?

4. Can you see the Galaxy SII black screen when you turn your phone on?

5. If yes, what happens next?
[Galaxy S II Q&A, Help & Troubleshooting] boeder9:
Still trying to fix this:

1. ICS; Siyah Kernel, it rebooted once or twice suddenly and then it no longer boots at all..doesn't start.

2. Stock

3. I think it does charge

4. Nothing happens. Feels dead.
[Galaxy S II Q&A, Help & Troubleshooting] nhmanas:
this is a known bug on ics. this aka superbirck bug. there are ways to fix this search on xda
[Galaxy S II Q&A, Help & Troubleshooting] boeder9:
I did search, seems like the JIG is the only hope but the chances are pretty remote. :crying:

Any other options?
[HTC Droid DNA] dkris2020:
Hello,

So despite how well the DNA has ran for the past 2 years, I had to replace it due to hardware issues regarding the antennae and battery. I got a replacement and so I need to unroot my current phone and root the one that I'm getting. My two questions are:

How do I unroot my phome and return it to factory default settings?

How do I go about rooting my new phone (if I can)? Do I unlock the bootloader and flash TWRP and that's it or is there more to it?
[HTC Droid DNA] Uzephi:
Unroot and return to stock: http://xdaforums.com/showthread.php?t=2293919

It depends on what firmware your phone ships with. Earlier firmware was revone, moonshine, rumrunner or firewater depending on firmware... Latest OTA cannot get root at the moment. Give it a few and you may get root with an updated sunshine.
[HTC Droid DNA] dkris2020:
My replacement has 2.07, so "moonshine " (I have 0 idea what that means) will work.

For the Unroot thread: TL: DR. I have NO idea what that thread is trying to say about moonshile/revrun/facepalm etc. all that is doing is confusing the hell out of me.

My old phone was rooted 2 years ago so IDK what process I used to root it. And I sure as hell don't know which out of the million ways to unroot it I need for my phone. It's running Viper Sense 5.5, so do I need to return to a stock rom first before unrooting?

EDIT: Tried Rooting, ADB DOES NOT WORK IN BOOTLOADER!!! When my phone is on ADB recognizes my phone perfectly but not when it's in the bootloader! I get an error in Windows (8.1) saying "USB Device Not Recognized" http://i.gyazo.com/dbeeddc4070f2cfca3e9bd588b333637.png. I tried the methods that involve installing drivers but they do not work. When I get off of work I will try the 3.0 method that doesn't involve the Samsung drivers, but other than that is there a way to fix this issue?
[HTC Droid DNA] Uzephi:
I don't have Windows 8 or 8.1 I heard there is driver issues with those versions. Windows 7 and Linux work like a charm
[HTC Droid DNA] dkris2020:
Unfortunately this doesn't help me...

EDIT: For the rooted phone I found out I used Facepalm for S-Off. Had to did in my forum history to find out
[AT&T Samsung Galaxy Note 4] tampaboy1984:
Can anyone share these 3 lines from the AT&T Note 4 build.prop?

ro.product.model=

ro.product.name=

ro.product.device=
[AT&T Samsung Galaxy Note 4] xlr8shun:
ro.product.model=SAMSUNG-SM-N910A

ro.product.name=trlteuc

ro.product.device=trlteatt
[Networking] terryd1980:
Hi Guys,

I've been reading a lot of forums discussing internet access through O2's PAYG system, many think it cant be done and although you will be restricted there is a way.

On any O2 PAYG connected PPC you must add the settings for the internet in "My Work Network" - this gives you access to port numbers which aren't easily accessible through "My ISP" settings.

Add these details...

O2 GPRS settings (WAP):

Note: These settings were taken from http://www.filesaveas.com/gprs.html with some slight modifications from myself.

Homepage: http://wap.o2.co.uk/

APN address : payandgo.o2.co.uk

Gateway (IP) address : 193.113.200.195

Username : payandgo

Password: password

Session type: Continuous / permanent

Authentication: Normal

Security: Off

Port number: 80

The Port number "80" is the most crucial point, O2 has blocked port 8080 which is a standard for internet access but 80 will give you 90% of all web pages too.

You will unfortunately still be blocked from MSN messenger and POP email accounts, I havent tried any exchange servers yet but I would expect to be blocked from them too.

O2 dont want you to know that internet access is available through PAYG with the right settings, I hope this may help some of you.

Good Luck

Terryd1980
[X 2014 Q&A, Help & Troubleshooting] doronster195:
So the IR sensors on the phone, the ones that are on each corner of the phone and detect movement so that it lights up the active display. Has anyone noticed this? When i wave my hands over the bottom ones, the screen doesn't light up, but if i wave my hand over the top one, it does. Does this mean my bottom ones aren't working? It hasn't really been a real problem, and I'm exchanging my phone for a different color anyway, but wondering if other can recreate this or if it is actually an issue.
[X 2014 Q&A, Help & Troubleshooting] doronster195:
Should only take a quick wave of your hand over the bottom bezel of the phone to see if the display turns on. Someone please take a second to let me know.
[X 2014 Q&A, Help & Troubleshooting] nimper:
You have to be a certain height above the lower sensors for it to activate. I have the same issue.
[X 2014 Q&A, Help & Troubleshooting] sonomazr2:
I also have to look at the screen just right to make the screen stay on. Many times it starts to dim while I am reading and I have to adjust the phone. I also have to wave fairly high up to turn it on.
[X 2014 Q&A, Help & Troubleshooting] qwerty12601:
I could be wrong but I believe you have to wave your hand completely over the display for it to function properly. So its not unintentionally turning on with every movement near it. The command is a hand wave over the display, not the bottom of the phone. So I believe its working as designed.
[X 2014 Q&A, Help & Troubleshooting] nimper:
I can make it activate by waving over the bottom half, but only when I do it a few inches above the screen.
[X 2014 Q&A, Help & Troubleshooting] tayyab_hussain:
i have the same problem.

i can activate the sensors when approaching from the upper part of the screen.

But not from the lower half (sensors below the display).

when seen in very dark room i see all the sensors (upper two and lower two) light up red.

i know that when the upper part of the phone is covered ,the sensors don't work because if the proximity sensor senses dark then it means ur phone is in ur pocket.

should i get a replacement . :( (really worried)

i did reinstall the moto app, it didn't help.
[X 2014 Q&A, Help & Troubleshooting] gearysr:
My Moto X has the same issue.

Edit, covering the top sensor may make the phone think it is in a pocket. I can wave over the bottom of the phone with no response though.
[X 2014 Q&A, Help & Troubleshooting] _MetalHead_:
There's nothing wrong with your phone- the "sensors" at the bottom are just flashers and the actual IR receiver is in the top of the phone, so if you wave your hand too close to the bottom the receiver won't be able to pick it up.
[X 2014 Q&A, Help & Troubleshooting] mefxes:
Only the top right one wakes the device on mine.

I really doubt it's the IR. I believe it's the camera waking the device.

Enviado de meu XT1097 usando Tapatalk
[X 2014 Q&A, Help & Troubleshooting] _MetalHead_:
Why would you doubt something that is explicitly stated by the manufacturer? The IR sensor's sole purpose is for gestures, one of which is to show the Active Display.
[X 2014 Q&A, Help & Troubleshooting] CUBENSIS:
Only top right corner wakes my phone
[X 2014 Q&A, Help & Troubleshooting] guibcguidi:
I don't think you have a problem. Try this:

If u simply wave at the top sensors, from any direction, the screen turns on.

For the lower sensors, try a bunch of different movements and you'll realize that when you reach for your phone (that means, moving your hand down and approaching the phone from the bottom part) the bottom sensors work.

My theory: the top sensors detect any movements, specially wave (from side to side) movement. The bottom ones detct the "reaching for" movement... If i remember correctly, the little demo you get inside Moto app tells you you can view notification by waving right above the screen or right before you grab the smartphone... isn't it exactly that which we are discussing?
[X 2014 Q&A, Help & Troubleshooting] Jettic:
Taking a shot in the dark here, but try going to the "Moto" app, hit the little gear icon top right and select actions. Then select "Wave to silence".

Now test it out, try swiping just above the top sensor (leaving the bottom sensors unused). Now try vise-versa (swipe across the bottom sensors while leaving the top unused). Notice how the wave action DOESN'T work when you isolate the sensors in this way. Now try swiping just above both of them with either your hand or with two fingers, one swiping the bottom and one swiping the top at the same time, you'll notice that DOES work. I think the only time all the sensors are used is for the action of waving to silence calls and things of that nature. When it comes to Moto Display and showing notifications, I'm pretty sure it's programmed to only use the top right sensor, as it wouldn't need three sensors to detect movement. Though I'm not sure why all three sensors come on when the display is off.

-Jettic
[X 2014 Q&A, Help & Troubleshooting] _MetalHead_:
Again, there is only one actual sensor, the rest are just flashers, like little LEDs. The flashers send out IR, and the sensor picks it up. What this means, is if the sensor doesn't see your hand (ie, when your hand is only near the bottom of your phone) it's not going to activate anything. The IR flashers essentially bathe your hand in IR light, and the sensor is the component that actually sees it. Make sense?
[X 2014 Q&A, Help & Troubleshooting] Lorenzoz:
:good: +1.

I've read the same statement in some technical review.

Can't really remember which ones.

Don't replace your moto X. He's fine. ;)
[X 2014 Q&A, Help & Troubleshooting] kloan:
I've noticed on mine, the bottom two are easily visible in the dark, whereas the top right is barely visible, and the top left isn't visible at all.

I'm not sure if this is affecting the performance or not.
[X 2014 Q&A, Help & Troubleshooting] Nexus-S:
Read the post from MetalHead above yours.
[X 2014 Q&A, Help & Troubleshooting] neocryte:
I can activate my screen by waving my hand over the bottom or top portions of the screen.
[X 2014 Q&A, Help & Troubleshooting] kloan:
i did. The top left one doesn't light up at all, unlike the bottom two. This leads me to believe it's non-functioning.
[X 2014 Q&A, Help & Troubleshooting] qwerty12601:
This is exactly how its working for me. If you act like youre going to grab your phone, not even touching it or moving it, the screen activates. However if you wave yoyr hand over the bottom sensors it doesnt to anything.

Ive been doing this for 5 minutes and its been very consistent. No movement or action near the top sensor it still activates the screen if i act like im going to grab the phone.
[Moto X Q&A] beefamato:
I love MightyText and used to use it all the time on my Galaxy Nexus. I pull contacts from two accounts: my gmail and my Exchange server. It all worked fine, numbers and names came through just fine.

When I switched to Moto X a long while ago, MightyText could no longer find the contact names of my Exchange contacts. Gmail contacts were fine, but no Exchange contacts. I followed their advice and wiped the cache on the web client, then refreshed, but it didn't help. MT support said that they only pull contacts from the phone's local storage. But why does it work for gmail, but not my Exchange contacts, which seem to be stored locally as well? Why did it work for my GN, but not my Moto X?

Plus, Motorola Connect can find all the names on my phone. I'd use it, but it's so finicky and can't do groups or mms.

Has anyone else experienced this? Any solutions or ideas?
[Nexus 6  General] dave2metz:
I have the Nexus 5 now, but I haven't messed around with switching from Dalvik to ART runtime. Do you think there will be a noticeable difference with the Nexus 6 running ART by default?
[Nexus 6  General] 7TimesCursed:
Yes.
[Nexus 6  General] msal:
This phone will run ART be default. I don't even think Dalvik is an option any longer.
[Nexus 6  General] tgyberg:
I know I'm ready!
[Nexus 6  General] Dr Faustus:
This

In Kitkat ART was still in development and was far from finished. Once testing and building proved stable developers for L removed Dalvik and placed the final build of ART as their primary and ONLY Runtime now.

I just hope we see Xposed support for it not before long!
[Nexus 6  General] joshm.1219:
The ART we've had in KitKat is not the ART we'll have in Lollipop. The new ART runtime is also fully compatible with Dalvik properties , stability issues should not be a problem
[Nexus 6  General] Dr Faustus:
Dalvik properties or not we will not know how much work it will be for some developers to port over mods for Proper ART. Xposed Framework is one of those key mods and we have still not heard anything since the summer on the matter.

I know that the developer was waiting for when Proper ART was released, but I am just worried that the developer might have ditched development due to being badgered all the time.
[Nexus 6  General] charesa39:
This. I've been spoiled by all my Xposed modules on my N5.

---------- Post added at 11:02 PM ---------- Previous post was at 11:01 PM ----------

Dear God. I hope not... :crying:
[Nexus 6  General] dazed1:
The difference is night AND DAY! i refuse to buy any phone which does not have ART option in the dev options!
[Nexus 6  General] bart.found:
I use ART since my update to 4.4.2.. no realated stability issue.. only some apps doesn't work at all with new runtime.. but now they have to update..
[Nexus 6  General] LNJ:
I used ART since the day I received my N5 on November 6th last year. My N5 never ran on Dalvik!

HTC One M8
[Nexus 6  General] bradputt:
Does it means expose modules is dead?
[Nexus 6  General] eksasol:
In late October 2013 was when Paranoid Android leaked a prerelease version of KitKat for the the Nexus 4. I installed it and switched on ART, from that day onward I never went back to Dalvik.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] lieffring:
I got my note 3 a few months ago and rooted out of the box and stayed on jelly bean because people said kit kat had very bad battery life and a few bugs just want to know your thoughts on if I I should take the 4.4.2 update or stay on 4.3?

Thanks!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] murmur70:
I would not take the update. Kitkat killed my phone. Not really but my signal has been terrible since.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] SMR-DINO313:
I agree the kitkat update got issues with reception
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] xdadevnube:
I think it depends on the manufacture date. KK borked my reception, but I'm planning on getting warranty replacement. I had a Note 3 from a month after release, so it is definitely an early version.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] murmur70:
Even some of the later ones have problems. I bought a new one in August and it was exactly the same signal-wise as the one I bought last November.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] lieffring:
Thanks guys I think I'll just stick with JB till we see 5.0L
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] MACHEK:
I did a warranty exchange and there is a significant difference in reception. I couldn't make calls from work indoors in some of my buildings, now I have no problem. Driving through canyons I would also have dropped calls, but since replacement I can actually stay on a call through the same place
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Runz84:
Modem

Trying flashing your modem back to an older version using Odin. Its really simple and can be done quickly. This seems to have helped my issues. I am trying MI9 today to see how much better.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] MACHEK:
I don't have any problems anymore. I got a replacement phone and it's perfect. That's what I'm trying to say, on kit kat with replacement phone and awesome reception
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] MrDroidz:
Hi I opened SuperSu and asked me to update binary. I did.

Question is, where does the updated binary files go in the system folder?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] DarkStryder:
System/xbin or system/etc somewhere If I remember correctly
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] MrDroidz:
you mean the original binary is overwritten?
[Dell Venue] roadrage777:
This is a thread on how i rooted my device. I recently bought a refurb of this nice little tablet and navigated these threads. While the end result was what i wanted, a rooted device running an unsecured bootloader and the open source release was achieved. I did manage to brick myself in the process and come back from the ashes. So below are the steps and some links to what worked for me and will possibly work for you given youre runing the 3830 release with WIFI and no 3G.

NOTE: I AM NOT RESPONSIBLE IF YOU TURN YOUR TABLET INTO A DOORSTOP, YOU ASSUME ALL RISK IF YOU CHOOSE TO PROCEED.

1. Visit opensource.dell.com, browse the repository for the Dell Venue 8. DOWNLOAD EVERYTHING, because why not.

2. go here, read everything and download the necessary packages for your system. Get your drivers installed, etc etc

3. Open the dell guide from Step 1 and follow it for installing the unlocked bootloader and unlocked OS onto your tablet. Reboot, make sure you dont have a paperweight. If you do, keep reading the dell guide as it has a nice unbricking section to follow

4. Once you are up and running kick off mybatch from Step 2 again and this time use the option to root your device. Let it works its magic as described in the thread.

5. Reboot for good measure

6. Kick back and you should now have root access.

7. Wanna install CWM dont you? yes you do so go here follow Vampirefos nice guide and download the CWM image and flash it. Test it and you should be good to go

Notes: My tablet shipped with Stock 4.2.2 JBS so if you have the same it should keep you from avoiding the few pitfalls there are

Dell has provided the links and documentation on compiling the kernel and getting the AOKP sources in their guide as well. If i get some free time or if anyone is so inclined to continue where other devs have left off we may be able to get rid of the stock OS in favor of a lighter one.
[Dell Venue] pennywisdom:
Hello, great guide I just got this tablet so I will be using it shortly. I am assuming that step 3 will wipe the device, correct? Also is the Dell unlocked OS Kitkat 4.4.2? Or would you later use CWM to flash a 4.4.2 ROM? I don't see many ROMs available for this tablet which I'm assuming is due to the Intel processor. I'm fine with AOSP and Xposed Framework as that can add nice features to any ROM.
[Dell Venue] GeeKerGurL:
Hello all, this is the tab I have and I have been hoping to find a way to root it without a PC. I am wondering how big a risk it would be to flash the dev edition file without a PC handy? According to these instructions step one is making sure adb see's your tab but then you unplug it and do not need a PC for the rest of the process (if you just unzip the file to sd card on tablet itself) So what's the purpose of making sure adb see's it? Is it REQUIRED to flash dev file or is it just to repair a soft brick for example? Any reason I can't skip this step and just unzip the package and flash the file?
[Dell Venue] roadrage777:
Step 3 may or may not wipe your data settings, i had a blank JB install and just rooted out of the box so cant say yes or no on that one. No not many ROMS at all. Great little tablet though i have had great battery life and its been pretty stable on the dev edition. only had one random reboot.

Geeker -> you could technically get away with doing it without a PC but then again i always like to have it connected in case anything goes wrong. I would highly reccommend making sure you can connect with ADB so if anything goes sidways after rooting and flashing you can at least get into fastboot and flash the jb image from the mybatch install instructions.
[Dell Venue] GeeKerGurL:
Ok cool, thanks for the info! I have a backup tablet is why I am considering the risk. Now does this mean that if something did go wrong with flashing the dev image that I could possibly be perma-bricked if adb will not connect? Or would I still be able to find a PC, install relavent drivers and get things going again? Also I don't think I have seen confirmation anywhere if it is OK to use dev edition if you are upgraded to 4.4.2 or not, anyone know for sure? Instructions doesn't say anything about being upgraded or not.
[Dell Venue] roadrage777:
Im always of the opinion i want to connect and make sure i can before i start tinkering with my droids. technically you could even connect during a softbrick following the instructions but it would just be a little more work. I cant say if the downgrade will have any issues as i started at JB. As long as the bootloader is not upgraded and is the same version as JB then it should downgrade as long as you are rooted.
[Dell Venue] GeeKerGurL:
Well, trying to get root so I am not rooted now if that is what you mean. As far as the bootloader it is not something I have manually upgraded but IDK if the OTA updates would change that or not. OTA upgrade out of the box to 4.4.2 is all that has been done to it. Knowing it can still be saved im the event something DID go wrong with the flash makes me wanna go ahead and attempt it, I guess my only concern now is with the dev package downgrading the tab. I reckon I should try to find out if anyone else on 4.4.2 successfully did the dev edition flash without any other tricks.

---------- Post added at 06:29 PM ---------- Previous post was at 06:13 PM ----------

Ok, I just seen the rest of the instructions AFTER the part explaining how to fix brick. Guess I should have read farther but I was under the impression simply flashing "venue8_version-1.22-ota-signed_full_rooted.zip" would give me a rooted tablet, so this is not the case huh? I would still have to unlock the bootloader and flash the other images from a pc?