yashsingh1/xdaforums huggingface dataset:
[Galaxy S6 Edge+ General] umbrokhan:
battery test Review show Note 5 and Galaxy S6 Edge+ Plus battery last longer then Galaxy S7 Edge battery!

so Galaxy S6 Edge Plus has a longer battery life then Galaxy S7 Edge.

Even Galaxy S7 Edge battery is bigger on paper. (spec sheet).

Real life test show the performance are about the same when opening app's.

Web browser about the same aswell. not a big difference.

in games Galaxy S7 is 1 second faster or same then Galaxy S6 Edge+.

you only need Galaxy S7 if you walking alot and it could rain anytime. or if your working out doors.

or Installing alot of games, movies, MP3 files.

Not really worth it otherwise.

https://www.youtube.com/watch?v=vw7BGfKBd9k

Note 5 has same spec's as (Galaxy S6 Edge Plus) Vs Galaxy S7 Edge Speed test.

this is bad news for the new phones coming out. performance is same or Half a second difference.
[Galaxy S6 Edge+ General] umbrokhan:
is this web site link below True?. showing Galaxy S7 snapdragon 820 battery worse then S6?

http://bgr.com/2016/03/08/galaxy-s7-...-vs-iphone-6s/
[Galaxy S6 Edge+ General] Santanazz:
After my S6 edge+ got 6.0.1 update, I am grateful that I have already chosen a correct device.. By comparing this two beast side by side, I noticed the S6 edge+ really impress me a lot.
[Galaxy S6 Edge+ General] dajumper:
I have exynos and battery is very good
[Galaxy S6 Edge+ General] gam3r20:
Did you face any deep sleep issues with your update?
[Galaxy S6 Edge+ General] Santanazz:
I didn't have such issues as deep sleep worked perfectly. My battery drains about 2-3% in 8 hours by closing all apps and activate airplane mode.. I was update via OTA and I assume it is official
[Galaxy S6 Edge+ General] cebs:
S7 or S7 Edge no worthless for me

http://www.xda-developers.com/galaxy-s7-bootloader-lock-explained-you-might-not-get-aosp-after-all/
[Galaxy S6 Edge+ General] justforlove:
My s6 edge plus under the Vodafone contract in Australia has still not received the 6.0 upgrade yet! : (
[Galaxy S6 Edge+ General] jutley:
I went from s7 edge to s6 edge plus and i find s6 edge us better suited for me.G9287 dues i just got ghe 6.01 update today great stuff.
[Galaxy S6 Edge+ General] jonny68:
yes in a few weeks ill sell this and put the rest towards S7 Edge
[G3 Q&A, Help & Troubleshooting] raoulbhatia:
Fixing the EMMC issues that manifested itself after upgrading CM 12.1 to CM 13 by showing EXT4 file system errors in TWRP, black screens like it as bricked, and crashes worked for me.

For the record, I've updated my LG G3 to firmware build number LRX21R.A1446038723 / software version V21a-232-01 and was able to install CM 13 as described without any issue.

Thanks for your help!

Raoul
[G3 Q&A, Help & Troubleshooting] towertsk:
My ls990 crashed while using it and after booting into recovery it fails to mount /system /data/ cache. Using BoardDiag v2.99a, shows "Failed to open partition from EMMC". Is this really a failed EMMC hardware part or the issues you're referring to?

My phone is currently unusable, "soft bricked" i thing. I can get into the following modes: Firmware upgrade and Recovery.

Someone please help!

Thank you!
[G3 Q&A, Help & Troubleshooting] tschmid:
An emmc brick wouldnt let you go into download mode. Then you have to follow a 'fix hardbrick guide with pin shortening'

Gesendet von meinem LG-D855 mit Tapatalk
[G3 Q&A, Help & Troubleshooting] towertsk:
From reading several posts the "pin shorting" method is to allow windows to detect the phone as "qualcomm HS USB QLoader 9008", correct? When plugged in with USB, windows detects the phone. I've tried loading with LG Flash Tool and adb sideload, but fail due to unmountable /system /cache and /data.

Is my phone salvageable? Thanks for the quick reply!

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

Does shorting the pins do more then enabling the Qualcom DLoader feature? Maybe executes some internal memory erase? Thanks again.
[G3 Q&A, Help & Troubleshooting] tschmid:
Yes, you can erase the whole emmc with boarddiag, so the pin shortening is not only to allow win to detect the phone as HS USB QLoader 9008 but also to use several tools to erase and rewrite the emmc

Gesendet von meinem LG-D855 mit Tapatalk

Look here:

http://xdaforums.com/showthread.php?p=61280085
[G3 Q&A, Help & Troubleshooting] towertsk:
I tried changing EEMC to erase but i still get see, "FAILED TO OPEN PARTITION FROM EMMC".

Is my emmc really bad? I can get into twrp recovery but every rom install fails. What should i try next? Thanks for the help!
[G3 Q&A, Help & Troubleshooting] tschmid:
Try this guide:

http://open-freax.fr/guide-unbrick-your-lg-g3/

Be sure you use a USB 2.0 port and original LG cable. Had this failure also, tryed 2-3 times then it worked

Gesendet von meinem LG-D855 mit Tapatalk
[G3 Q&A, Help & Troubleshooting] towertsk:
I think emmc is really dead. I can't erase the emmc after trying over 10 times. I can still get into recovery and firmware download but loading still fails. Is there anything else i can try?
[G3 Q&A, Help & Troubleshooting] tschmid:
Sorry im not sure, maybe you should ask in the fix brick thread also

Gesendet von meinem LG-D855 mit Tapatalk
[G3 Q&A, Help & Troubleshooting] DehoXeD:
Hi dude,

First, thanks for that start of thinking about the cause of this problem.

Do you have any return saying that there is still EMMC brick, even with Stock ROM updated (with all thing "need" to avoid brick), meeting the brick after a while?

Here are my facts to help your hypotheses :

- 1st Brick :

1 year ago, after 2-3 days of use of CM12.1 based Blisspop ROM / Solved with the fix tutorial ;

- 2nd Brick :

Still on Blisspop, after some times (weeks) of use / Solved with trick again, but switched to CandySix (AOSP based) ;

- Extra :

I realised after a while (6-7 mounths, yeah, I did not need a lot of storage at this time ^^) that I had 16gb instead of 32gb --> I assumed I had flashed the wrong firmware (ie the 16gb one) during second fix ;

--> Btw, I used my phone for 6 mounth without EMMC problem when I was on AOSP based ROM ;

- 3rd Brick :

Then I decided to redo all of the fix and switch ROM by the same occasion --> Came back to Bliss 6.X (Pure CM13 based) directly from V10E firmware --> 1 day to wait before I met that EMMC Brick again.

Next step : I'll try to update LG stock before flashing custom 6.X ROMs and see what happens in some days.

Just my 2 cents, for who want to compare with its own G3's life ;).
[Galaxy S3 Neo Q&A, Help & Troubleshooting] TheForgotten:
I wanted to know if someone could give us a link of the Blisspop 5.1.1 ROM for our phone.

I know that the official page has removed the links, but maybe we'll found a lucky guy that can give us like a Dropbox/Google Drive link or something like that.

I would be very thankfull to that person, and I'm pretty sure that I would not be the only one :)

Edit:

I FOUND A GOOGLE DRIVE LINK FOR THIS ROM!!!

Here it is: https://drive.google.com/file/d/0B_49ymqgWLYvWUZMcS1DdmZhaW8/view?pref=2&pli=1

Thanks to [MENTION=3080328]Marcos75[/MENTION]62 from Androidiani Forums!

Be happy :D
[Galaxy S3 Neo Q&A, Help & Troubleshooting] [TR]Neco:
Thanks Bro :) :D ı was search on 1 weeks. :)
[Upgrading, Modifying and Unlocking] onecom:
Hi i searh in all forums and this and test some solutions but not working or i not make good.

You have any idea for pw10a1 loked to movistar spain and in botloader mode i see this.

walaby botloader v5.15

and in down line i see gsm ok.

Any idea is apreciate.

regards:onecom.
[AT&T LG V10] LGMONO:
yeah ahh felt screen and is was hot to the touch this lasted 20 mins even after doing a factory reset thinking an app was causing this problem, i have no idea what lead to this i am using a portable 1000mAh charger that i was using but because the batt is 3000mAh i didnt think this was the cause of it. anyways its cooled down only after i allowed it to go into standby for 10 mins weird LG PLEASE DEBUG this issue because my 700 dollar phone gos pop. anyone else have this issue?
[AT&T LG V10] cansler:
When did you start experiencing this? Was it before or after the MM upgrade? Mine has been doing this for the last 3 days and yesterday the battery did not last more than a few hours where normally it goes almost 2 days. I got the OTA upgrade to MM last week and I noticed it getting hot after that. I also noticed that my Wi-Fi or lte is constantly dl/ul something. I think that's what is causing the heat. But I can't figure out what is causing the data dump.

Edit: I turned off my data and Wi-Fi and I see that my phone is now cooled and can charge. ( live been charging all morning and was only at 70%
[AT&T LG V10] rquinn19:
Check and make sure ATT Message Sync isn't on/syncing. I bought a Gear S2 and it turned on, on it's own and had the same problem.
[Android Apps and Games] F4i:
Hi!,

I'm currently training familiarize myself with app development. An app I'm currently dissecting has a lot of xml files I want to modify but there are hash files for each xml file. Whenever I modify an xml file the app resets everything. Can someone please help me overcome this obstacle..
[Android Apps and Games] pavlepiramida:
Tried deleting hash?
[Android Q&A, Help & Troubleshooting] EMEK:
Hi.

I have android bike navigation. Is this possible to pair navigation with phone to use standart HF profiles?

I want to answer calls incoming to my phone using navi. Next i want to get notification about incoming SMS on navigation.

I know that some cars BT devices have these options, but how can i do it with another android device.

Both devices have bluetooth module.

Any ideas?

Wysłane z mojego GT-I9195 przy użyciu Tapatalka
[Android General] newbit:
Welcome to the Runbo F1 Super Thread

As a new owner of a Runbo F1, I am looking forward to share with you my informations I collected for this rugged phone.

Please feel free to post your questions or any other thoughts in this thread. Thanks for reading - NewBit

Specs and Pics

Drivers / Tools

- View attachment 3655080

- MediaTek SP Flash Tool v5.1516.00

- MediaTek SP Flash Tool v5.1708.00.000 (MTK6753 support)

- View attachment 3655085

(MTKdroid 2.5.3d with Patched MTKdroidTools.ini for MT6752 support)

Enable { } Developer Options

- enter Settings -> About phone

View attachment 3657492

- touch 10x on Build number

View attachment 3657491

- and become a Developer

View attachment 3657490

- Choose your Developer Options

View attachment 3657891

Boot into Recovery (Stock and TWRP)

- phone is turned off

- Hold Volume Up and Power Button at the same time

- when the first Boot screen appears

View attachment 3657899

-> just release the Power Button and keep holding volume up

- recovery should boot

FTP Login for Runbo Update / Upgrade Servers CN / EN

Chinese Version:

FTP: upgrade-cn.runbo.net

Port: 21

User: ftpadmin

Password: bo369123

English Version:

FTP: 185.86.148.226

Port: 21

User: ftpadmin

Password: 95dq96bcF1

Found in View attachment 4063999 apk folder -> Res -> Raw

Also findable in View attachment 4064000 apk folder -> Res -> Raw

Decompiled with APK Studio

View attachment 4063992

View attachment 4063993

Full Backup Runbo F1 Phone (MTK 6752A Chipset)

MTK Scatter File Tool Kit by NewBit

Backup Preloader.bin and modification for Unbrick and Partition Resizing

Flashing Fullbackup / TWRP

Rooting

After flashing the TWRP, download a SuperSU-vxx.zip and install it over the TWRP.

Recoveries - Stock / TWRP

Stock Images and FTP Login for Runbo Update / Upgrade Servers CN / EN

Exchange Micro SD Card (to 128 GB)

Resizing Partition Userdata with internal SD

I am not responsible for anything bad that comes to your device when using the information posted in this thread. Everything here is dangerous,

may cause a brick, will void a warranty and has the potential to just plain wreak havoc. Do not complain you followed my instructions and met

with a dead device. Consider yourself warned

I've tested to the best of my ability, but I am one person with one device, I cannot catch all potential failure modes. If you find a problem and a fix,

or have information that should be added let me know and I will update the necessary information.

Big Thanks and Credits to:

- Kemonine96 and his team for their great work and help on the Samsung Rugby Pro (SGH-I547) Super Thread

- Chainfire, for his awesome root script [STABLE][2016.02.02] SuperSU v2.65 and [STABLE][2016.12.15] SuperSU v2.79

- Anatoly Smaznov aka javum from lenovo-forums.ru, for his TWRP 2.8.4.0 source patched and compiled

- TeamWin - TWRP, for their indescribable work on their open source project twrp.me

- Carliv, for his extraordinarily image kitchen [TOOL][UTILITY] Carliv Image Kitchen for Android - unpack/repack boot-recovery

This site is still in progress and will be updated step by step.
[Android General] newbit:
How to Full Backup Runbo F1 Phone (MTK 6752A Chipset)

You need:

- MediaTek USB VCOM drivers installed

- Switched Off Runbo F1 phone with minimum of battery charged to 50%

- MediaTek SP Flash Tool v5.1516.00 or similar

- Scatter file for a MTK 6752A Chipset

- Minimum of 5GB free space on your HDD for the backup

How to install MediaTek USB VCOM drivers

- switch off the phone and connect

- open your device manager

- connect phone via micro USB cable to he PC

- observe the device managers list for pop up an unknown device which driver cannot be installed

- double click that device and install/update drivers

- paste the the link to the folder "MediaTek USB VCOM drivers"

- let the system search for the right drivers and wait until it is finished

- once the driver is installed properly, it should be always shown without any issues

in your device managers list, but only for a few seconds, then it disappears again.

View attachment 3655155

How to backup the phone MediaTek SP Flash Tool v5.1516.00

- create your own scatter file or use mine: View attachment 3655154

- switch off the phone and let it disconnect

- open SP Flash Tool and load a scatter file

View attachment 3655150

- click on Readback and then on Add+

- double click on the new line and create a new folder BlindDumpFile and save

View attachment 3655151

- a new window will pop up, Readback block start address

- Type remains HEX

- Region remains EMMC_USER

- Start Address remains 0x0

- Length: copy and paste from the scatter file 0x150000000, fill in zero's between 0x and 15 -> 0x0000000150000000

(HEX values in SP Flash Tool are right side aligned)

View attachment 3655152

- click OK and double check your setup

- hit the Read Back button, and connect your phone

- SP Flash tool should start reading your flash image right after

- after reading back your image, SP Flash will notice you (duration approx. 20min)

View attachment 3655153

Congratulations, you have now a single full flash image file of your phone.

You can now experiment with your phone, you can do what ever you want,

except deleting or downloading your preloader, which is stored in Region EMMC_BOOT_1.

I can just recommend highly to backup your preloader once, either to share it to other who need it

for reverse engineering or just in case for a JTAG unbrick.

To backup your phone directly into single region files, use the View attachment 3655193 file.

Each partition need its own Add+ entry under Readback with an own start address and length.

With the BlindDumpFile you can also do this by your self. Just use a hex editor, HxD for example,

select and cut off your regions according to your scatter file.

To extract the binary files automatically you can use the MTK Scatter File Tool Kit by NewBit
[Android General] newbit:
Flashing Fullbackup / TWRP

You need:

- MediaTek USB VCOM drivers installed

- Switched Off Runbo F1 phone with minimum of battery charged to 50%

- MediaTek SP Flash Tool v5.1516.00 or similar

- Scatter file for a MTK 6752A Chipset

- TWRP Image file for your Phone

- Fullbackup from your Runbo F1 Phone and extracted into single files

(If you have to flash the preloader, make sure the bin file is correctly modified)

Flashing TWRP for Runbo F1 1st Gen

- switch off the phone and let it disconnect

- open SP Flash Tool and load a scatter file View attachment 4064053

- deselect everything

- click on Location from the recovery entry and select the recovery_TWRP_2840_Runbo_F1.img file

- check if the combo box says Download Only

- click on Download

- hook on the Runbo F1 phone

- wait until it is finished -> Download Ok Windows will appear

- hook off the phone

- start into recovery by holden Volume Up and Power On until the Runbo Bootscreen shows up

-> keep holding vol up and release Power On -> TWRP Splash Screen should appear

Flashing Fullbackup back for Runbo F1 1st Gen

- switch off the phone and let it disconnect

- open SP Flash Tool and load a scatter file View attachment 4064053

- check every single entry to be correct, all files should be already selected

if all the extracted files from Fullbackup in the same folder as the scatter file

- Double Check if your Preloader.bin file is correctly modified

- check if the combo box says Format All + Download

- click on download

- hock on the Runbo F1 phone

- wait until it is finished -> Download Ok Windows will appear

- hock off the phone

- start the phone by pressing the power button, Bootscreen should appear and the phone should boot up normally
[Android General] newbit:
Backup Preloader.bin and modification for Unbrick and Partition Resizing

From the Fullbackup you can not extract the preloader.bin file.

It is stored in a different memory area. It is in EMMC_BOOT_1, where all other binarys are stored in HW_STORAGE_EMMC.

You have to read it back directly from the phone.

How to backup the Preloader.bin with MediaTek SP Flash Tool v5.1516.00

- create your own scatter file or use mine: View attachment 4064152

- switch off the phone and let it disconnect

- open SP Flash Tool and load a scatter file

- click on Readback and then on Add+

- double click on the new line and create a new folder PreloaderFile and save -> Filename: preloader_readback.bin

- a new window will pop up, Readback block start address

- Type remains HEX

- Region changes to EMMC_BOOT_1

- Start Address remains 0x0

- Length: copy and paste from the scatter file 0x40000, fill in zero's between 0x and 4 -> 0x0000000000040000

(HEX values in SP Flash Tool are right side aligned)

- click OK and double check your setup

- hit the Read Back button, and connect your phone

- SP Flash tool should start reading your flash image right after

- after reading back your image, SP Flash will notice you

Congratulations, you have now a preloader backup of your phone.

Hot to mod the perloader_readback.bin for flashing it back into the phone

The preloader_readback.bin allways gets an additional header, added from the Flashtool during the read back.

Its size is exactly 2048 Bytes. Cut these bytes off. You can also cut off the none used zero's at the end

of the file. After this mod's, you can use it to flash it back into the phone.

Download Preloader Files: View attachment 4064038

After extraction of the zip, rename the file preloader_without_header_and_without_noneused_Zeros.bin to preloader.bin

and put in the folder with your extracted image files.

Make sure in your scatter file the preloader area is changed to:

- partition_index: SYS0
partition_name: preloader
file_name: preloader.bin
is_download: true
type: SV5_BL_BIN
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x40000
region: EMMC_BOOT_1
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BOOTLOADERS
reserve: 0x00
[Android General] newbit:
MTK Scatter File Tool Kit by NewBit

I've wrote a little Windows Tool Kit MTK Scatter File Tool Kit to edit scatter files a bit more handy and to easy extract images from a Raw Blind Dump Fullbackup Image.

You need:

- Fullbackup from your Phone -> ROM_0_Backup_3.2_Stock.img

- MTK Scatter File Tool Kit for Windows (View attachment 4064117)

- Scatter file which fits for your Raw Blind Dump Fullbackup Image

- MTK Scatter File Tool Kit, Scatter file and Raw Image in the same folder

- Minimum of 5GB free space on your HDD for the backup

How to Extract Binarys from a Raw Blind Dump Fullbackup Image

- Open the MTK Scatter File Tool Kit (MTK.Scatter.File.Tool.Kit.Source.Binary\MTK Scatter File Tool Kit\bin\Release)

View attachment 4064160

- Click on Select Raw Image File

- Select the Scatter File first -> ok

View attachment 4064159

- Select the Raw Image File second -> ok

View attachment 4064161

- Wait until the image and binary's are extracted

View attachment 4064162

- Look for a folder like -> ROM_0_Backup_3.2_Stock.img_ExtractedImages

All binary files described in the scatter file will be extracted.

How to Edit a Scatter File

- Open the MTK Scatter File Tool Kit (MTK.Scatter.File.Tool.Kit.Source.Binary\MTK Scatter File Tool Kit\bin\Release)

View attachment 4064160

- click on Select Scatter File

View attachment 4064163

- click on the combo box to select a partition

View attachment 4064165

- edit the partition by double click on the entry

View attachment 4064167

- every changes, changing directly to the file - no need to save

The MTK Scatter File Tool Kit is like it is. If you have suggestions or tipp's, you are welcome to tell me.

Source Project is attached, you can write or modify on your own. Compiled in VS Express 2013 for Desktop
[Android General] newbit:
Recoveries - Stock / TWRP

TWRP 2.8.4.0 for Runbo F1 - flashable with SP Flash Tool

Download Runbo.F1.TWRP_2.8.4.0.zip

View attachment 3656272

This compiled version of TWRP 2.8.4.0 comes originally from Anatoly Smaznov aka javum from lenovo-forums.ru.

I only use the "init" file and modded the the other files, like fstab, by myself.

Against TeamWin's FAQ - What is a data/media device?

This Device with Android 4.4.4 does not have the SDCARD mounted to data/media.

Unfortunately, I am not capable to compile a TWRP source myself or rather to get this code who Anatoly Smaznov aka javum wrote and patched.

So I cannot change RECOVERY_SDCARD_ON_DATA := true to RECOVERY_SDCARD_ON_DATA := false. But maybe someone who reads this

is willing to support me a little? Maybe Anatoly Smaznov itself, it would be a great honer to me!

Also against all these so called "Recovery Porting Tools for MTK Devices" aka PhilZ, TWRP, CTR, CWM and so on, terminated with

the same Error Report. The Recovery Partition is too large & causes region overlap! Even those Versions which claims to be able

to ignore that massage, terminated some steps later with the same Error Report. For me it looks like, all of this tools are having a

fixed maximum size they compare with it the actually build file size. Not even according to a scatter file, which tells exactly the

truth of the partition size. Also not according to the read back image size including the not used zeros.

So thats why I was forced to puzzle the TWRP manual, where Carliv Image Kitchen for Android came into the game.

I wished there is tool which just port all these fstab and init's entrys, and then you can use the image kitchen of your choice.

As a final test, I tried even only to take the init file from the canceled Recovery Ported Image, and replaced with my already bootable

TWRP. But it just didn't wanted to boot with it.

Byte Count Compare:

- Scatter File And Read Back Image says: 16777216 Bytes

-> 9287664 Bytes Are None Used Zeros => Free Space

- "my" TWRP 2.8.4.0 says: 15798560 Bytes

But maybe I did and misunderstood something major wrong?! I am looking forward to somebody who can explain this to me.

Except that data/media feature, TWRP works flawless for me and is essential to gain root!

Stock Recovery Image 3e ALPS.KK2.MP13.V1.16 (KitKat 4.4.4) from/for Runbo F1 - flashable with SP Flash Tool

View attachment 3656209

View attachment 3656210