yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] s197:
It's been said a few times over in IRC. For the record, I said the restore tab in QPST doesn't work. There may be another way to utilize that backup QCN file but I don't think it's as easy as going back in the program, clicking on the restore tab, and loading the file.

I know peoplearmy has a tutorial that says as such but it may not work on Verizon, I've been trying to help he and PureMotive by providing them with NV Data and he mentioned he was worked on a fix for Verizon but to my knowledge, there is none that solves the roaming issue right now. If there is, I'm all ears.
[Verizon Samsung Galaxy S III] cortland1998:
Get one yet? If not ill send it to you.

---------- Post added at 06:23 PM ---------- Previous post was at 06:22 PM ----------

I have a roaming S3 that I'm shipping back tomorrow, and a replacement that hasn't been touched yet. I can send you all kinds of info from a working and non working phone. Let me know what you need.
[Verizon Samsung Galaxy S III] Hero:
A nandroid from a working phone would be great.
[Verizon Samsung Galaxy S III] cortland1998:
Okay, give me a few minutes.
[Verizon Samsung Galaxy S III] TechSavvy2:
Wanted to add my experience here.....

Followed to the T and everything went good, got my IMEI back, except at the end I got no signal. Data connected and ran fine, 4G solid and all but it was like I had zero reception bars and said no mobile network available still (wtf?). After messing with it for quite a while I remembered I had actually backed up my efs.sbn before so I tried the manual way of just pushing it back to location with the other thread instructions. That basically did its thing and as far as I know, was in the same state now as I was after your instructions here.....and still no reception or calls. Then at the end of the other thread it said to do the *2767*3855# to re-provision your phone which I did, it reset, and now is all back to 100% fully functional.

I don't know if it was already posted cuz I only read first 10 pages or so. I also didn't see anyone else post similar experience so I assume something just went wrong with mine? Dunno, but just thought I would add for future info that using the *2767*3855# to re-provision your phone thing worked like a charm for me.

PS - you're right, what a long process for me to go through when I already had my efs.sbn backed up, lol.....
[Verizon Samsung Galaxy S III] aj8600:
is there a guide on how to backup with QPST? im only seeing restore
[Verizon Samsung Galaxy S III] spiderj:
curious, is this still an issue now with the unlocked bootloader?
[Verizon Samsung Galaxy S III] d1ez3:
This is what I would like to know as well
[Verizon Samsung Galaxy S III] Budwise:
BL and IMEI are different issues.
[Verizon Samsung Galaxy S III] spiderj:
Ok, was curious because i thought I read somewhere that the IMEI issue was caused by AOKP roms or something and that once the BL was unlocked, it wouldnt be the case anymore. Might be I just misinterpreted.
[Verizon Samsung Galaxy S III] cortland1998:
I managed to lost my IMEI without an AOKP ROM. I was using a TW ROM when it happened. I was doing a restore in recovery back to the stock rooted ROM. Once the phone booted up, no signal and 0 for my IMEI.
[Verizon Samsung Galaxy S III] DROID3R:
Where are the BACKUP instructions

VERIZON GALAXY S 3
[Verizon Samsung Galaxy S III] con247:
search
[Verizon Samsung Galaxy S III] ercDROID:
I read that it is best to back up when you are on a stock rom. I wanted to ODIN back to stock and I read that people were successful on the root66 ODIN file. I originally used the first file that had some sprint elements in it and then flashed other roms through cwm. I never downloaded the updated root66 tar file. I wanted to odin back but the link for the updated root66 tar file isnt working. Anyone have a link to it? Or do you think I would be fine using the original version of root66 for this?
[Verizon Samsung Galaxy S III] DROID3R:
i backed up with the revised version of root66 ..it was failing with beanstock rom
[Verizon Samsung Galaxy S III] Peoplearmy:
Have you ever flashed an AOSP ROM before? CM9, CM10, or AOKP?

DX
[Verizon Samsung Galaxy S III] dknell:
I did everything exactly as shown. But i get an error everytime i try to put the "a" in the second text box. Error says < unsigned 1 byte> Array 1 is not a decimal number. Can someone please help????

---------- Post added at 09:47 PM ---------- Previous post was at 09:35 PM ----------

I tried it without the "a" and now my IMEI reads: 59000

Anything i can do? Any suggestions??
[Verizon Samsung Galaxy S III] brockkk:
did you check the hex box and put an 8 in the first box?
[Verizon Samsung Galaxy S III] ddggttff3:
Thanks for this guide, I thought I was SCREWED when the efs.sbn file didnt repair my IMEI, but then after following this, everythings good!
[Verizon Samsung Galaxy S III] dknell:
Yes I put an 8 in the first box, just as shown.

---------- Post added at 07:42 AM ---------- Previous post was at 06:49 AM ----------

So i ran through the process again, And it took!! Thanks! IMEI is back!

Still no mobile data :confused:

Any ideas? I tried the sim removal, reboot, etc

---------- Post added at 08:24 AM ---------- Previous post was at 07:42 AM ----------

I 're-provisioned and was able to get data back in roaming mode only.
[Verizon Samsung Galaxy S III] Jay Evans:
Welcome to the club.... :(
[Kindle Fire Q&A, Help & Troubleshooting] Cupidhunters:
Hi Guys ,

This is absolutely kickass forum for android lovers .I recently bought Kindle fire and rooted it with latest KFU and found when installing some apps its saying "THIS DEVICE ISN'T COMPATIBLE WITH THIS VERSION" .I m kinda annoyed with this messages and also wanna install some cracked apps ad games avaliable from forums and different torrent sites .

So could someone guide me how to install cracked apps and games ?

How to I get rid of those dumb messages .I would like to install new ROM if its good just let me know which one is stable and good to go ??

Thanks in advance for advices .
[Kindle Fire Q&A, Help & Troubleshooting] GameGuru41:
This is piracy my friend. Argh!
[Kindle Fire Q&A, Help & Troubleshooting] Iced666:
I think can delete this thread

Galaxy S - CM9
[Kindle Fire Q&A, Help & Troubleshooting] veeman:
You don't need to crack free apps though.

---------- Post added at 11:47 AM ---------- Previous post was at 11:46 AM ----------

This is most definitely piracy. Thread reported to mod. Please read forum rules and don't do this again.
[Kindle Fire Q&A, Help & Troubleshooting] Arjen:
Thread closed, it smells a lot like asking for piracy.
[Sprint HTC EVO 4G LTE] mrjasenr:
Ok so my camera used to work, im s-on rooted running a rom, camera app shows up, no preview and the buttons do

nothing. So, has any one had this and was able to fix it? What did you do? Any help would be appreciated.

And im a week beyond the 30 day warranty so no trading for a new one, and I don't really feel like sending it in to HTC

just yet.
[Sprint HTC EVO 4G LTE] cesarcerros31:
You do know its one year warranty.
[Sprint HTC EVO 4G LTE] mrjasenr:
Yeah but I don't want to send it in. I was looking for a quick fix.
[Sprint HTC EVO 4G LTE] Rxpert:
"Rooted running a rom"

That doesn't exactly help us help you.what Rom is it
[Sprint HTC EVO 4G LTE] wuestsider:
Usually that is indicative of a non compatible kernel.

WUESTSIDER X

Sent from my EVOLTE! The family JEWEL....
[Sprint HTC EVO 4G LTE] mrjasenr:
Running rejuvenated 2.1. Also rotted s-on
[Sprint HTC EVO 4G LTE] mrjasenr:
Unrooted and relocked bootloader, still no camera. Even did the latest RUU and no rear camera! :) will my htc warranty still

work since I did the htcdev unlock????????????????
[Sprint HTC EVO 4G LTE] wuestsider:
If your still within your warranty time frame you should be fine. My last EVOLTE had major antenna issues and Sprint gave me a new one, even though it was rooted. And yes the tech knew it was rooted.

WUESTSIDER X

Sent from my EVOLTE! The family JEWEL....
[Sprint HTC EVO 4G LTE] mrjasenr:
Ok but i'm out of my 30 day, so I'm stuck with the htc warranty. I called Htc and they said my warranty was fine. If they try to go into recovery, since I used HTCDEV will they just kick it back to me?? I don't know if some one will know this for sure, thought I would ask.
[General Topics] phonetech101:
I have put together these NRL bootanimations with spinning logos all are 480x800 i can resize on request. All have been tested and are working. If you have trouble with links copy and paste to your browser of choice. If you decide to use them please leave feedback and remember to hit the thanks button :)

Simply rename zip to bootanimation.zip. example. "Bulldogs.zip" would be "bootanimation.zip"

Enjoy :cool:

Broncos

http://db.tt/jkATPFfa

Bulldogs

http://db.tt/EBVf3TJu

Cowboys

http://db.tt/gayHRp1h

Dragons

http://db.tt/7h6qURPd

Eels

http://db.tt/CemQefjV

Knights

http://db.tt/AHeytv6X

Panthers

http://db.tt/0z870PxN

Rabbitohs

http://db.tt/s6BAZPg8

Raiders

http://db.tt/OJoTtq7J

Roosters

http://db.tt/9XqMQlBl

Sea Eagles

http://db.tt/I7QGyJsl

Storms

http://db.tt/XKQm8NML

Tigers

http://db.tt/fdDF3JT9

!!!!!!!!!MORE COMING SOON!!!!!!!!!!
[General Topics] Elioman:
great job men, waiting for more.:laugh:
[Networking] angelofmusic:
This is the follow up thread to:

Fast Dormancy -- Save Your Battery from 3G Drainage

http://www.youtube.com/watch?v=O8L50sCY7CI

This is a thread to discuss your findings and concerns about Fast Dormancy.

Feel free to leave questions for me, I will be constantly monitoring this thread.

****NOTE*****

There is an original app by Gokhanmoral, which effectively disables Fast Dormancy on the Galaxy S3 (ONLY TESTED ON i9300). Please refer to the description on market app link below for future compatibility.

https://play.google.com/store/apps/details?id=com.gokhanmoral.fastdormancytoggle.i9300

Supercurio is creating an app that disables FD, but also ads separate diagnostic functionality. :o
[Networking] supercurio:
Yeah so Erica spoke about an application we developed when studying the Fast Dormancy and RRC states.

In order to experiment and understand all about FD, we had to developer a new tool also allowing to enable/disable Fast Dormancy on several Samsung phones, and apply changes in real times, including when tuning Fast Dormancy timers.

Requiring root depending on the device itself, its main purpose it to help you analyze if the network you're using supports fast dormancy or not, then allow you to set reasonable settings providing satisfying battery performance while keeping the network latency low.

Be sure you watch Erica's video as she will explain the technical challenges behind 3G power management better than I could.

Phase 1:

Today's application is very simple:

It provides an easy access to the useful Samsung proprietary ServiceMode page displaying RRC states and also advanced network SNRs.

Download preview app from Google Play

Voodoo RRC Tool source code on github

Note: the app kind of suck and as you'll notice it benefits from no UI design at all yet :D

Contributions are indeed welcome.

Phase 2:

Automatize the FD detection process in order to help you telling us which kind of network behavior you experience with your carrier.

Phase 3:

With fast dormancy carrier database, recommending automatically optimal settings.

Add support to enable/disable and choose Fast Dormancy timers on non-Samsung phones.

Phase 4:

Reverse-engineered Service Mode in order to build statistics of RRC state used, maybe to guess automatically if a network supports FD or not.

I'll probably not go this far but it might be interesting to develop this, not only on Samsung phones but on many more.

Once again contributions will be welcome here too.

I hope you'll like this joined XDA TV & development effort, which aims to investigate a topic, share knowledge and provide tools for everyone's benefit.

Hopefully its only the first collaboration among many. I'd like to encourage other developers as well to consider XDA TV as an extension of everything we're doing here, and interact with videos producers.
[Networking] ephraim:
Guess i'll be the first to reply. Thanks for the info, i really learned alot. Keep up the good work erica.

Cheers!
[Networking] rehmankhan101:
video is no longer avalible WHy?
[Networking] supercurio:
There was an unexpected glitch in one of the demo, the one explaining how to diagnose if Fast Dormancy is implemented or not by your network.

Concretely the actual demo was exhibiting a different behavior from our previous observations, so to be completely sure to guide you in the right direction we're re-investigating.

Except this part where there was doubt everything was perfectly accurate: Erica video shall be back soon on XDA TV once we figure it out :)
[Networking] zodiaxe66:
Thanx sc,nice tool and great work,even though I was expecting another app from u,hopefully that will come eventually

Good to see you're back.
[Networking] Irvysan:
Not working??

EDIT - the app by Gokhanmoral on the OP works perfectly now! (on my sgs2)

ignore the text below :)

The app doesn't show any output for me, is this :

1: Because FD is not available with my Carrier? (UK Vodafone)

2: Because I'm in the UK?

TIA

Irv

*Either reply in this thread or PM me if you need any further info/testing

EDIT : See - http://xdaforums.com/showpost.php?p=28107797&postcount=8 and : http://xdaforums.com/showthread.php?t=1742813

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Codes don't work on AOSP/AOKP ROMS's (apparently) :(
[Networking] veyka:
I have always wondered if AOSP on for example the galaxy nexus supports FD, There is a general lack of information, it looks like it should, but I don't know.

It would be great to find a way to gather this sort of data on AOSP or other devices, no idea if it's doable though.

Great video series, FD is under documented and there is a lot of misinformation and unbacked assumptions :)

As far as networks go, unless the documentation is incorrect, my network (3UK) have FD enabled, I am unable to back this up with data, as I sold on my sgs2 a while back now :(
[Networking] SwimmerBoy:
I can't get any information about FD in my Galaxy Nexus with JB
[Networking] supercurio:
Yes good question about AOSP.

It's possible Samsung RIL is still reading fast dormancy activation status and timer values from somewhere in pure- Google devices.

Samsung devices running AOSP instead of Samsung firmware must still read the FD configuration parameters, as they're rocking the same RIL binary code.

This is definitely something to investigate, I'll take a look but feel free to report your findings, that might be useful features to add to RRC Tool.

Tip: you can search for strings in libsecril*.so in /system/lib and attach strace to the rild process : both give a lot of clues :)
[Networking] nCoder:
On my Galaxy Note the code do access the service menu is *#*#0011#*#*

Does this depend on the radio version? model? network?
[Networking] rehmankhan101:
Awsome Three uk support Fast Dormancy:)
[Networking] veyka:
I have been poking the rild with strace, at the moment the output is refusing to be piped to a textfile, which is annoying, will work on that later.

Funny thing is that it runs for a bit then crashes it, have to toggle airplane mode to get network back, its most likely me not running strace with the right parameters though.
[Networking] andysoserious:
if i enable FD in the app and set the timer to 15 sec then nothing changed in *#9900#. there ist the curent status of my FD stil disabled.

okay so i enabled both and charged phone to 100% and toggle mobile data and was watching the battery. in half an hour I lost 2% of Bat.(did nothing .. only get few emails via push and wrote an message via whatsapp)

than i checked BBS and in the section kernle wakelocks i get an wakelock named : "sercril_fd-interface" with an time of 22m ( FD was anebled for 30 min) witch take an total wackelock of 50%?

now i kinda dont it what should i do ? :D will watch again 30 mins and will check than without FD .

/andy
[Networking] YLNdroid:
Hello angelofmusic, I have a Samsung Galaxy Note GT-N7000 currently running on CheckROM Revo NoteHD v5. Upon accessing SysDump, there is an option - Enable fast dormancy(Current State : Disabled).

Thus, I suppose I would not require the prescribed app, would I?

:silly:

What is the appropriate stepwise testing procedure/methodology that you suggest I follow?

:o

Thanking you and awaiting your response.

:)
[Networking] JGuinan007:
So will FD save me some battery life if I enable it? What about black crush how do we fix that?
[Networking] lokhor:
You might want to note that Gokhanmoral's app was based on the guide here: http://www.androidnz.net/2012/06/at-your-own-risk-how-to-disable-fast.html
[Networking] inks:
Telstra RRC states/timers

Telstra does the following on 850MHz (MCC/MNC 505/01):

DCH (T1 1s) -> FACH (T2 30s) -> URA-PCH

Three/Telstra does the following on 2100MHz (MCC/MNC 505/06):

DCH (T1 5s) -> FACH (T2 10s) -> URA-PCH

Didn't time the T3 timers (long).

If you're on Telstra, the fast dormancy timer will force the IDLE state (for both networks above), and you will miss out on the benefits of the PCH state.

Background info on Australia 3G networks:

Three + Telstra had a reciprocal network sharing agreement for years (Telstra 2G 900MHz + Three 3G 2100MHz)

Three + Vodafone merges.

Three network shares with Vodafone 2G (and wiith Vodafone 3G this month).

Three/Telstra network sharing agreement ceases end of this month.

I think Three network would likely stay as a seperate network (rather than merged), in which case the states/timers would likely be the same.
[Networking] zetnord:
Confirm..yes me too on my Galaxy Note code is *#*#0011#*#* to enter the Service Mode

maybe it gonna be awesome if possible to direct from the Voodoo RC tool..btw that app is awesome for starting

keep a great work for you Supercurio :good:

as long as your carrier provider support that FD ..

black crush ? hmm i think that a different problem..this thread is discuss about networking not the Screen Colour ;)

....

finnaly ..

before trying your Voodoo RC tool i check the RRC state behaviour with default setting ( enable fast dormancy from *#9900# )

and the result is:

DCH to FACH pretty random timer ( some times 8s, 15s ) .. and very quick from FACH to PCH -/+ 5 sec and stay on PCH never goes to IDLE state

then i try voodoo RC with guide from erica video (thanks erica)

1. when i enable and first try the 1 sec FD with policy then back to test

DCH to FACH still ramdomly but never reach above the 10s ..and still very quick switch from FACH to PCH and stay on PCH state until the same process repeat PCH to FACH then DCH

2. then i try the 10 sec FD with policy and tested

DCH to FACH still ramdomly but sometimes lil bit longer the 10s ..and still very quick switch from FACH to PCH and stay on PCH state until the same process repeat PCH to FACH then DCH

.. then i decide to stay in that setting and see what happen..until more or less 5 h i check with BBS that secril fd_interface on kernel wakelock is 2 h more or less is about 51% and yes my phone cannot enter the deep sleep by that ( i forgot to capture it sorry :( )

my question is : is that mean my carrier provider deffenetly didn't support the FD or i did something wrong with the step .. coz last time i disable the fast dormancy ( with FastDormancy toogle by Gokhanmoral ) i never saw that secril_fd process so high..

but i'll try looking for and test again

again thx Supercurio and Erica :)
[Networking] johanlh:
This is a great thing Erica is triying to do!

I wrote a guide in Spanish for people in South America or Spain:

http://loqueselocomparto.blogspot.com/2012/08/fast-dormancy-en-s3-colombia.html
[Networking] Redneck Trash:
So this only applies to GSM networks?

Set from my toroplus
[Networking] davidwar:
Nice work!!

Movistar Spain:

WCDMA 2100 Band 1:

(average)

T1: DCH to FACH: 8 secons

T2: FACH to PCH: 13 seconds

T3: PCH to IDLE: never

try with FD 15 secons, same results.
[Networking] spupuz:
not showing anything in nexus s gsm italy.
[Networking] kerman19:
Hello,

Figured I'd add my experience here.

I've got a UK SGSIII, completely carrier/sim free on stock LG8 which by default has FD Disabled, my carrier of choice is Three UK which supports FD.

Using the VooDoo RRC and enabling FD my phone means that it goes from DCH and skips FACH, going straight to PCH in 7 seconds, where it remains. It does not go to IDLE... I believe that PCH is more or less as decent on battery as IDLE, but with the added benefit of initialising a lot faster, around half a second, vs a couple of seconds or more.

With FD off, my phone performs identical, DCH to PCH in 7 seconds, with no mention of FACH.

Here are the speed test results, which shows something is happening.

First one is FD on, Second is FD off.

Phil
[Networking] davidwar:
Wifi Off and WCDMA or 3G set?
[Networking] MPKO:
Just a note related to "fast dormancy"

Fast dormancy as we know it at the moment is implemented only into Mobile. Mobile manufactures are implementing fast dormancy in two different ways in their mobiles - Fast dormancy and fast dormancy by support of network controlled fast dormancy.

Most of the Smartphones are using normal fast dormancy implementation (e.g. Calaxy S2 international) and some of them are supporting network controlled fast dormancy (E.g.high end Smartphones implemented by Qualcomm chipset and iPhone4 and 4S). from Mobile parametrization point of view there is no difference.

Normal Fast dormancy: Mobile Manufactures has implemented a feature which is measuring data activity in the UE.When data inactivity is detected, internal FD timer is triggering RRC connection release request towards network and network has to release the connection ( based on 3gpp specification and Network has to obey this).

Fast dormancy by support of network controlled fast dormancy: when Network providers found out that Mobile manufactures started to implement a new way of releasing the RRC connection without following network implemented timers, they started to implement feature called Network Controlled Fast Dormancy. Network Controlled Fast Dormancy is working only in Networks which are supporting RRC state called Cell/URA_PCH state and it has to be also supported by the Mobile. Only Difference between "normal Fast dormancy" and "Network controlled fast Dormancy is the cause code in the RRC connection release request message sent by the Mobile device. In "Normal Fast Dormancy" the cause code is SCRI release (signalling connection release) and in Fast dormancy which supports Network controlled fast dormancy feature,

the cause code is PS data session end.

When network receives a RRC connection release request with cause code "SCRI release", network has to move to UE to idle state

because it is defined like this in 3GPP specification.

In case where network and Mobile supports network controlled fast dormancy and mobile sends RRC connection release request towards network (with cause PS data session end) UE is moved directly from Cell_DCH state to cell/URA_PCH state and not to idle.Power consumption is almost identical in case of Idle and cell/URA_PCH state.

Most of the Networks which are supporting Network controlled fast dormancy are also using really short inactivity timers to save UE battery life and also avoiding network congestion due to too many DCH connected users.

And as mentioned already, FD is applied only in 3G/HSPA technology.

Cheers!
[Networking] spupuz:
yes but actually i have a bad signal.

I mean i cant see nothing else the the network id in the Voodoo RRC tool
[Networking] MPKO:
To kerman19.

Fast dormancy don't affect to your download/upload speed. Which phone you used?

And it is better to restart your phone after toggling fd to be sure new parameter values are used.
[Networking] frenchglen:
omgosh you guys are awesome. long live xda. i been here since the htc tytn days (my first smartphone), so to see if grow to these heights is awesome. perfect video.

reflects android: powerful, customisable, yet simple/accessible if need be!

i have a galaxy nexus so looks like I can't get FD anyway?.....eh well.