yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Mini Q&A, Help & Troubleshooting] indralang:
I'm not rooted yet.

But Du Battery Saver said Android OS is draining my batteries.

Even in battery saver mode.

I will give screen shot after if it happening again.

Do you know why Android OS consumed much power?
[Galaxy S III Mini Q&A, Help & Troubleshooting] lifeiswisdom:
Blootware.
[Galaxy S III Mini Q&A, Help & Troubleshooting] Aport:
Benz rom, golden kernel and setcpu.When you install the first two, set the minimum cpu clock to 200 mhz and max to 1000.Select pegasus governour and check "set on boot" option.I had poor battery life, but now it can last 24 hours with medium usage.
[Galaxy S III Mini Q&A, Help & Troubleshooting] AssToast:
Kinda not relevant since he is on stock rom
[Galaxy S III Mini Q&A, Help & Troubleshooting] indralang:
I checked another thread and I found the answer without using any custom ROM.

He answered = "Developer option, background process up to 4 process" and it works! :fingers-crossed:
[Galaxy S III Mini Q&A, Help & Troubleshooting] encik_racun:
But can u tell me what is 4 limit? Is it all your app like fb working well after that?
[Galaxy S III Mini Q&A, Help & Troubleshooting] oldslowdiver:
I was pretty curious about this option too, some time ago, so I googled it and finally came to the opinion that it is like using a task manager, = useless on Android, because it has its own RAM manager.

This option to limit process is what it is: for developers, to test how their eventual app handle once it goes in background, and what if once killed. (read http://www.extremetech.com/computing/112013-how-multitasking-works-on-android-and-ios/2)

My personal advice/choice for a longer life for your battery:

1 - root your device and freeze/delete bloatware (system apps: first freeze them, see how it goes, then, delete them (after making a backup)

2 - use

A) Juice Defender (balanced or aggressive), set 2g connection when the device is in your pocket,

B) Use Wakelock Detector to check what most consumes your battery (https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector&hl=en)

3 - use wifi and 3g only when needed, - don't count on the smartness of automatic mode 2g/3g under data

4 - switch off syncronization if you don't need it 24h (whatsapp / viber will work anyway)

5 - settings / display /

A) Auto adjust display tone ON

B) Turn off softkeys (I know exactly where 'back' and 'option' keys are..)

6 - Power saving mode ON for screen and cpu (http://www.youtube.com/watch?v=XTLTBo2DRQA)

7 - Disable double tap on home button for S-Voice (http://www.youtube.com/watch?v=OmU8hXUXNFE)

8 - Keep normally a mid-low brightness level, you can adjust it quickly if needed, can't you?

9 - Disable Auto-update in Google Play (you can update manually)

10 - How To Disable Samsung Push Service and Samsung Ad Utility Services (http://www.eyes4tech.com/2013/03/ho...e-samsung-push-service-and-samsung-ad-utility)

11 - Turn OFF vibration (actually, I like it and I use it for SMS and incoming phone calls)

12 - Set airplane mode when you go to sleep (or just switch it off if you don't count on it for morning alarm or to use it as an eventual light)

13 - Never use a Task manager ;)

Assuming you're enough smart for keeping Bluetooth OFF if you don't need it, by this way, according to my daily use (phone calls, texting, internet, no gaming), I recharge it each 1d 15/22 hrs.

Hopefully this helps. :cyclops:
[Galaxy S III Mini Q&A, Help & Troubleshooting] indralang:
working as usual. :)

I'm using fb, twit, whatsapp and line as 4 background process and working as usual.

Here is my RAM Usage and my battery up to 18-20 hours with 3G connection always ON.
[Galaxy S III Mini Q&A, Help & Troubleshooting] indralang:
thanks, but i need my 3G connection always ON and you don't need to root to freeze bloatware. application - force stop - disable. :)
[Galaxy S III Mini Q&A, Help & Troubleshooting] encik_racun:
U using one power guard right?
[Galaxy S III Mini Q&A, Help & Troubleshooting] indralang:
Just for batterry status. I'm not activating any power saver. :)
[General Questions and Answers] amlan12:
Please tell me how to root Salora pro tab HD?

Kernel version 3.0.36+

EM2926-738A@V01M#255

BUILD NUMBER--

RK292X_ANDROID4.1.1-sdk-v1.00.00

rk2928SDK-ENG 4.1.1 JRO03H

Please Help me..Thanx in advance
[General Questions and Answers] SanjuM:
Rooting

i have Salora Fontab SFT071.i have tried numorous methods to root my tab but in vain. please help :crying:
[General Questions and Answers] 9441Rahul9441:
Try Shuame and moborobo if it doesnt help then try cydia impactor

new to the world of rooting but please thank me if i helped u
[General Questions and Answers] SanjuM:
Salora Fontab Root

i have successfully rooted my SALORA FONTAB SFT071...just follow the instructions in the following link provided

thetechnosquad.com/root-android-sphs-on-hsdroid/

i have rooted my tab,but still couldnt find adb usb drivers for my tab. if anyone finds compatible usb drivers please let me know!! thanks!!
[General Questions and Answers] SanjuM:
Any method to install either CWM or Cynogen MOD on salora fontab SFT071

the Stock ROM is very laggy and slow...crashes all the time

:(
[General Questions and Answers] ratnesh1992:
download baiduroot work 100% for protab

Root Without Pc Through Baduroot.
[T-Mobile, Samsung Galaxy SIII] Dantenios:
I'm not sure if my issue is complex or not. It's just a matter of me not being able to update my phone. Well, my phone was and is still working fine, but after an update, I believe it was CM 10.1 april 20th nightly build, or near that day. I started getting issues with my phone, where it would randomely reboot, and do it much more often when music was playing. That's when i guess i did the stupid thing, I went and downloaded the April 11 Experimental M3 update and updated using that, which worked fine. After that my phone was good as new. And still is right now, not really having any issues. But ofcourse, usually newer nightly builds come with bettered features, so i thought i would update. Here's the problem, when i update, I would get an assert failed and three lines of getprop ("ro.bootloader") T999UVDLJA and the 2 other versions the T999 models, then my model number i believe, followed by Status 7 installation aborted. Any help would be greatly appreciated.
[T-Mobile, Samsung Galaxy SIII] GenericAsianGuy:
You will need to update to the latest bootloader (which is different from modem).

If you're on T-Mobile, you'll want UVDMD5: http://xdaforums.com/showthread.php?t=2282603

If you're on WindMobile (or SGH-T999V), you'll want VLDLL1: http://xdaforums.com/showthread.php?t=1949687 (you'll have to ODIN)
[T-Mobile, Samsung Galaxy SIII] Misterjunky:
re: error 7 - odin flash

This guide will get your phone back up and running properly, doing anything else will just prolong your problem.

Easy and sure way to fix error 7 and other issues or problems - Here is the step by step guide:

After doing this you will end up with a stock-pre-rooted T999 Tmobile Touchwiz 4.1.2 rom which works properly.

You will not loose any of your pictures, videos or music by doing this.

Download the newest pre-rooted Samsung Galaxy S3 T999 Jellybean v4.1.2 rom: T999_UVDMD5

After downloading make a folder on your computer's desktop and unzip the

file using Winzip or 7zip so the .TAR file is in the new folder you just made.

Download and extract Odin into the same folder you made containing the TAR file

Here is the link for Odin: http://d-h.st/Q14

Download ODIN which is required for flashing the stock rooted firmware (a windows app)

Download the Odin Flash firmware for T999 Tmobile then copy it to the same folder as Odin

Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted

Turn off your phone and boot into

DOWNLOAD MODE

(Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)

Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.

You should now see a COM** port listed toward the top-left of Odin (under ID:COM)

Click on the PDA button in the middle-right area of Odin.

Browse to and select the Firmware you downloaded (TAR file)

Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.

TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.

If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.

Click Start to begin the flash. This will take a while, so be patient!

Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.

You may unplug the phone and close Odin if you wish.

Wait at least 5-10 minutes for the system to boot the first time and then build its cache!

(It may seem to hang during boot, this is normal and you must be patient!!!)

Good Luck!
[T-Mobile, Samsung Galaxy SIII] Dantenios:
to Be honest, I'd rather keep using CM 10.1 and not the TouchWiz JB. And what would be the latest bootloader? Apologies, i'm some what new to this. :p
[T-Mobile, Samsung Galaxy SIII] Misterjunky:
re: jellybeans

I never said you should be running JB Touchwiz roms, all I was trying to explain is the best and easiest way to get

your phone back up and running whichever way you like it to run.

If you follow the step by step instructions and the phone is working normally then you can re-flash whichever rom

CM10.1 or any others without any issues unless their is something wrong with the rom you are trying to flash.

The main thing is that it's best to start fresh when someone is having issues like you are having with your phone.

Doing anything else besides what I suggested will only prolong all those issues you are having now.

People will be telling you that your cwm or twrp recovery is not the latest one and you need to update it,

other people will tell you that you must have had some error downloading the cm10.1 rom and they will

tell you to re-download it, then others will tell you to check the MD5 checksum of the download and all

kinds of other things which will just prolong the problems you are having.

None of those things I just wrote will help you to fix the error 7 and other issues you are having.

That's why I posted the step by step which works each and every time to fix errors such as yours and

give you or anyone else a clean and fresh start.

Good luck!
[T-Mobile, Samsung Galaxy SIII] Misterjunky:
re: you are right

U R so right! I could not have said it better!

---------- Post added 19th May 2013 at 12:00 AM ---------- Previous post was 18th May 2013 at 11:18 PM ----------

I forgot to mention, since you are kind of new to this you should not even think of or mention anything

about bootloaders if don't want to end up with a shiny brick.

This has happened hundreds of times in these XDA forums when people mess around with bootloaders.

Flashing bootloaders intentionally or by trial and error is the number one way to end up with a bricked phone.
[T-Mobile, Samsung Galaxy SIII] Dantenios:
Alright, I understand now, thank you. Just curious, this will probably trip the flash counter right? Or does following that method allow to reset the flash counter? Or is that just something i need to worry about if i'm going to send the phone in for repairs (which i hope I wouldn't need to)
[T-Mobile, Samsung Galaxy SIII] Misterjunky:
re: flash counter

The odin flash to stock rooted will trip the flash counter, but then each time you flash any rom trips the flash counter too.

You can get the "Triangle away" app to reset the flash counter at the play store.

Actually there is no need to reset the flash counter at all unless you need to

exchange a defective phone which is still under warranty.

Good luck!
[T-Mobile, Samsung Galaxy SIII] Dantenios:
Apologies but one more thing, your post was a link to a pre-rooted JB for T999, My phone is the T999V, if you'd happen to have the pre-rooted version for that would be greatly appreciated.
[T-Mobile, Samsung Galaxy SIII] Misterjunky:
All of these roms are stock pre-rooted roms, I am not certain which one is for your

T999v phone. Perhaps the "V" stands for videotron so select that one.

Mobililicity_VLDLL1

Updated JB Firmware

Mobililicity_VLALH2

Updated ICS Firmware

Wind_VLDLL1

Updated JB Firmware

Wind_VLALH2

Updated ICS Firmware

Videotron_VLDLL1

Updated JB Firmware

Videotron_VLALH2

Updated ICS Firmwar
[T-Mobile, Samsung Galaxy SIII] GenericAsianGuy:
Great post Misterjunky!

One of these; it depends on what carrier you're with.
[T-Mobile, Samsung Galaxy SIII] Dantenios:
I just finished using Odin to the Mobilicity VDLL1 with the pre-rooted JB. Just waiting on my phone to boot up. I have the tab open to install CWM Touch via the terminal emulator. After that I can install the latest CM 10.1 update correct?
[T-Mobile, Samsung Galaxy SIII] Misterjunky:
re Ok

Yes, once odin is done and you flash custom recovery the phone will be ready to be flashed any compatible cwm/twrp custom rom zipfile.

You would be much better off if you go to the playstore and download "Goomanager" which is a free app.

After its installed, open it and press the menu key and select "installopenrecoveryscript".

Doing that will flash the latest TWRP recovery.

When Goomanager is done flashing, reboot the phone into recovery mode and go from there.

TWRP has a built-in file manager and terminal, plus an option for ADB sideloading.

It has all the options which CWM has and more.

Give it a try, you can always flash the cwm back if you like.
[T-Mobile, Samsung Galaxy SIII] Dantenios:
Sure, though i'm having a new issue now haha My phone has been stuck on the Samsung loading screen ever since after Odin said pass. How long does this usually take, right now for me it's been almost half an hour...And i know i followed the instructions to the T
[T-Mobile, Samsung Galaxy SIII] Misterjunky:
re: reboot

reboot the phone into recovery and do a "Factory reset" then restart the phone.

Chances are excellent that it will boot normally if you flashed the correct rom.

Don't wipe anything in recovery.

Good luck!
[T-Mobile, Samsung Galaxy SIII] Dantenios:
Thanks a Bunch, It worked! Now to install the recovery, then i may try using Touchwiz JB for a bit, but to be honest, I still think i like CM 10.1 better haha this one feels..some what clunky to me.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
It would probably be best to edit your title with SOLVED in italics or something so other users are aware and can revert to this thread for assistance rather than starting up a whole new one :)
[T-Mobile, Samsung Galaxy SIII] Dantenios:
Done. I just wanted to ask, I installed the latest CM 10.1 update, and wondering, when i facotry reset it, it didn't take me through the welcome procudure and under my Mobile network options, i didn't see any LTE options, just EvDO and Global and other GSM/WCDMA ones which even after selecting didn't change the one selected by default.
[T-Mobile, Samsung Galaxy SIII] GenericAsianGuy:
If you don't see the Gmail app (and other Google apps) installed, you may need to flash the latest Gapps: http://goo.im/gapps/gapps-jb-20130301-signed.zip
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Gapps no longer includes the Gmail app.
[T-Mobile, Samsung Galaxy SIII] Dantenios:
Thanks, i got the that google apps done, but i'm still wondering what's wrong with the Mobile networks options, they don't seem to actually work and always says WCDMA preferred even if i choose GSM Only, plus no LTE option anymore. Also, i can't get on to the Mobilicity network nor get the option of editing the network profiles for MoWap and such. Oh and when i go into my recovery, it's not showing me the the content from my CM10 update, but the content that was there when it was on Touchwiz JB
[T-Mobile, Samsung Galaxy SIII] Misterjunky:
re: CM10

After you Odin flashed the stock rooted firmware and before flashing the CM10.1 rom I would bet that

all those settings including the setting for APN under mobile networks worked.

In fact if you were to flash any T999 Touchwiz Jellybean 4.1.2 or 4.1.1 custom roms like "Wicked v10"

or "Darthstalker X2" roms you might even find that you would like them even better than any Cyanogen

aosp/aokp or ported roms.

All these issues and problems you have described have to do with the CM10 rom, that's why a lot of the

CM10/AOSP/AOKP and the ported rom threads here in xda clearly state that they are "experimental" and

mainly intended for developers.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
What I would give for you to stop spreading this misinformation.
[T-Mobile, Samsung Galaxy SIII] Dantenios:
Yes, you are right, before flashing CM 10.1 it detected my network and in fact everything did work. But the thing is, they were working when I had CM 10.1 as well, before the status 7 issue even happened. I do understand that they are "experimental" roms, it's just that, they were working fine until a certain point haha. I'm just wondering why my recovery is displaying the content of my sdcard before flashing the CM 10.1 build, because after putting another file into the root of the sdcard, and going into recovery, it doesn't show up, instead it shows the CM 10.1 build i flashed which i already deleted and had replaced with something different. The other thing is, i have a Pin on my Sim card, and each time the was restarted or turned on, i'd have to input that first, after the CM 10.1 flash it wouldn't seem to detect the sim card because it didn't ask for the PIN, it does though on the TouchWiz JB. I'm sorry for the long post, i just want to understand what could be happening.
[T-Mobile, Samsung Galaxy SIII] neysito:
I responded to you question on the nightlies thread, but it actually belongs here better. Here's the same answer.

When you reboot the first time after installing a cm-10.1 nightly coming from TW mobilicity's network wants you to activate your phone again but it won't ask for it right way, only when you reboot once more , that's why that first time it goes roaming and it does not connect to their network.

-Do a full, clean wipe in recovery.

-Install nightly.

-Install gapps.

-Reboot and setup your phone (it goes roaming)

-Reboot and you will get the activate phone prompt.

-Activate it and it will connect without need to modify apns.

-Dialer will force close, don't worry about it.

-Reboot again, profit.

GS3 T999V
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
I forwarded the steps to him as I've been trying to help him myself. I've been giving him the same steps only I was unaware of Mobilicity's procedure as I am not on their network.

Since you were the first for me to see this,

All credits go to you
[T-Mobile, Samsung Galaxy SIII] :
which one would i download? im using a mobilicity carrier but the phone was unlocked from wind..any help? thx
[T-Mobile, Samsung Galaxy SIII] Da Kine:
If the phone is from wind, then you download the wind firmware.
[T-Mobile, Samsung Galaxy SIII] :
but im using mobilicity sim card...that the confusing part
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Those are all T999V models.

The V is not just for Videotron. If the phone is from Wind then use that firmware. The others probably wont even flash.

You could try to flash Winds firmware then flash the modem that came from your carrier.

No gaurantees, but why not try it?
[T-Mobile, Samsung Galaxy SIII] :
Would it hard brick if I flash wind firmware and mobillicity modem?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Others have done it. Worst ive ever heard of is lost connection and needing to flash back.

---------- Post added at 05:03 PM ---------- Previous post was at 04:54 PM ----------

The partitions are the same. Bricks usually occur from flashing stuff to the wrong partitions.
[T-Mobile, Samsung Galaxy SIII] :
So how should I go about this? Odin wind firmware and flash mobillicity modem?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Correct. Odin the root66 version of the firmware so you will be rooted, then flash the modem.

---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------

Hang on though. Are you certain yours is a model T999V?

In your posts it says you're using the T999.
[T-Mobile, Samsung Galaxy SIII] :
how do i check?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Best way is look at the sticker under the battery.
[T-Mobile, Samsung Galaxy SIII] :
yep, it is 7999v
[T-Mobile, Samsung Galaxy SIII] :
What is the point of updating bootloader? I found a way to install latest nightly without updating bootloader
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Yeah, by editing the update script. Did you stop to think that the check might be there for a reason? The reason this time is stability.
[T-Mobile, Samsung Galaxy SIII] :
it is the correct version. i triple check
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
What model phone do you have? Maybe the CM team forgot to add some asserts?
[T-Mobile, Samsung Galaxy SIII] Da Kine:
Delete.
[T-Mobile, Samsung Galaxy SIII] Dantenios:
Just wanted to add this for anyone else that has gotten this problem. For me i just went back to root66 ICS and then flashed an older CM10.1 M3 version and had been using that. Decided today to check if there was any update on the issue, and after some browsing found this:

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

Just flashed that, and now i can update just fine, runniny RC5 right now, may update to the newer nightlies some time. And everything works like a charm. Just need to find a mobilicity VLDLL1 modem now lol. Glad this is now properly solved, thanks for all who tried and have helped. If anyone wants to know what my issue was for reference, let me know.:good:
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Yea.. old news bro lol but thanks for posting anyways. Could come useful to noobs unaware of this or those who don't like to search.
[T-Mobile, Samsung Galaxy SIII] Dantenios:
Yup, that's who i intended it for lol and to just put a proper finish on this, considering it caused me some good amount of grief too haha
[Nexus 4 Q&A, Help & Troubleshooting] veritas2000:
I just updated to the N4 from the NS. I loved the simplicity of nstools but is there one for the N4 that works in the same way? I've been using trickster bit I'm fond on the setup. I'm looking for simple lol
[One (M7) Q&A, Help & Troubleshooting] ss_snail:
moved
[T-Mobile, Samsung Galaxy SIII] itzzbenx3:
My S3 belongs to Wind Mobile. The device was rooted and had the stable Liquid Smooth v 2.2 rom installed. Today, I decided to flash this http://xdaforums.com/showthread.php?t=2282603 to flash pacman rc1 later. Unfortunately, my phone hard bricked as soon as I pressed reboot system after successfully flashing the T999 UVDMD5 Firmware / Bootloader. My phone does not turn on. What should I do? :confused:
[T-Mobile, Samsung Galaxy SIII] KingKostas:
you're probably bricked. try to get into download mode and if you can odin back to stock

---------- Post added at 01:13 AM ---------- Previous post was at 01:09 AM ----------

BTW i just saw a thread saying how t999 modems (so im guessing firmware too) and t999v (your phone i believe) cannot be flashed interchangeably. so i recommend you odin back to stock
[T-Mobile, Samsung Galaxy SIII] Misterjunky:
re: bricked

I just checked on that link of the rom which you decided to flash, you must be some kind of developer

to want to experiment that much with your phone, that rom even modifies and changes your bootloader.

All of those CM/AOKP/AOSP and ported roms can be an excellent project for developers or people like

you who really like to experiment a lot.

In the future I would suggest to purchase a jtag so each time you brick your phone you won't need to

send it to an online repair shop to get it jtag'ed and get it un-bricked.

eBay has some really good jtag'ing deals for people like you who bricked their phones, check it out.

Good luck with it!
[T-Mobile, Samsung Galaxy SIII] itzzbenx3:
So, I'm guessing the only way to un-brick my phone is to jtag it? O:

Well, my phone isn't managing to get into download mode. Thanks for the advice.