yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S8+ Questions & Answers] vision33r:
Went to AT&T store this morning to take a look at both phones. The S8 looks like a longer Note 7 without the home button. I have sort of mixed feelings about the S8 after about 8 mins playing with it. Sure it's the most powerful phone right now but I don't think it's the only thing that matters. Playing around the rom itself, it wasn't that much different than the S7 Edge. I think Samsung is dumbing down the phone too much, it's loosing more customizeability unless we root and run custom roms on it. The screen doesn't look much different than S7 Edge except longer and the on-screen has a haptic sensor under neath just like the iPhone 7. The camera looks and perform just like the S7 Edge which is bit disappointing the next gen device with same current gen camera. Overall it's thinner, the side round edges are very thin so why bother having curved screen when it's just tiny edges. Makes the side bar notifications less useful just merely small tiny edge buttons. I took a few photo shots, the AF sensor behaves just like the S7 Edge. No noticeable difference. I tried to customize the navigation buttons, there are locked down no way to customize the buttons like LG could do to some degree and OnePlus phones.

On to the G6, it's vastly different than the G5 which is a good thing. It looks and feels sort of like the Samsung Galaxy A7 but taller and thinner. The screen has warmer colors than the S8, standard SLCD display. The ROM feels pretty well organized, more vibrant theme than the dark cool S8 theme. I think overall this is a pretty good phone too if the price is right. It feels pretty good quality compare to the G5. I saw Pocketnow's review of the G6 and I agree, this phone's camera is a winner. Blows away the S8 camera in quality, features, and performance. That wide angle camera rocks. The AF locking speed is amazing and not a single blurry shot even with the default ISO and constantly moving around. I took similar shots with the S8 and got more blurry pics due to the slower AF lock..

Now the question will be whether the S8 package beats out the G6. Probably because Samsung often packs good hardware with so-so bloated software. Don't care much about docking to get DEX. Have plenty of powerful laptops at home here.

So before anyone preorder, go and try it out for yourself if you have the S7 Edge right now you might want to wait for the Note 8 or something else. I don't see any huge upgrade over it. LG G5 owners should definitely upgrade.
[Samsung Galaxy S8+ Questions & Answers] cleopete:
Any idea how the LGs are root-wise? I'm not holding out much hope for Samsung. I can't go back to a locked bootloader. I just can't.
[Samsung Galaxy S8+ Questions & Answers] piscesjoey:
I had the G5 on Sprint & the bootloader was locked down. Someone did manage to get root access using a modified aboot but it was only for an earlier Marshmallow firmware & you had to do so much workarounds just to have basic stuff working & imo it just wasn't worth it.
[Samsung Galaxy S8+ Questions & Answers] Tiny Wiz:
The sensor is NOT the same on S8/S8+ as S7/S7 Edge...
[Samsung Galaxy S8+ Questions & Answers] Duncan1982:
It's true the S8 & Plus do have different sensors & much like on the S7 & Edge they will either have the Sony Sensor or the icocell, but both are equally as good according to reports.

View attachment 4099446
[Samsung Galaxy S8+ Questions & Answers] CadillacMike:
I have the LG V20, and had considered the G6 without actually seeing it, but then I saw the S8+ and knew it was for me. After that, I did make my way into Tmo store, and i saw the G6 and was quite unimpressed.

If i had to choose between the G6 and my existing V20, its the V20 all day.

between both of those and the S8+... well I pre-ordered the S8+
[Samsung Galaxy S8+ Questions & Answers] bkeaver:
My experience with LG has been worse reception than almost every phone on the market for some reason. That is why I tend to not go with them. The last LG phone I had was the v10. I know my brother had the same experience.
[Samsung Galaxy S8+ Questions & Answers] prfraczek:
I've also compared my S7E with S8+ today. In my opinion S8+ is a massive downgrade. The phone is much taller but bottom bezel+onscreen buttons together take more space than S7E bezel with buttons ca 2mm!!! The remaining part of the screen shows the same amount of data like S7E. Fingerprint scanner- I've got big hands but there is no way to use it without second hand- so if you are on the tube or similar and no free hand you can forget about using it. Aspect ratio 18.5:9 looks sooooo stupid!!!- Samsung took 'samsung' badge from the front- very well done but because of this aspect ratio ruined it massively. S7E black with chrome sides looks so cool compare to S8+ 'JETBLACK'- instead of stealing swipe left&right to go back and forward from apple they absorbed 'JET BLACK' crap colour-WTF. And the last thing- if you buy S8+ make sure you've got nail file so you can get rid of the stupid bixby button- what a crap!!! So like always nice phone every second release...
[Samsung Galaxy S8+ Questions & Answers] jayr04:
You can't go wrong with either one but one thing I noticed in the store is that the G6 didn't get very bright just like my V20. Samsung has been the king of screens for the past couple of years.
[Samsung Galaxy S8+ Questions & Answers] misiokicio:
go and moan somewhere else pal, op was trying to compare g6 to s8... not s7e to s8 plus, if ur happy with ur s7... stop messing abt in s8 forums
[Samsung Galaxy S8+ Questions & Answers] RevChappy:
The S8 has Canon duel pixel tech. It is not the same as the S7's camera, and LG G6 doesn't have nearly as many features. SD 821 vs 835....um... 835 please. Somewhat Decent VR.....Bixby thats has better features than Google assitant....

the S8 won this year, much like the s7 won me over the g5 last year. and I own both a g5 and s7....

Also...come in...LG's last 2 flagships had massive issues with boot failures. My LG G5 (and I'm a LG rep at my store) and it failed twiced.
[Samsung Galaxy S8+ Questions & Answers] SammyK998:
I was at a verizon store earlier today, and she said that they've only sold 2 of the G6's so far. That seems pretty underwhelming to me. Then again, "most" people go there to get iPhones, but I just thought it would sell better than that. Thusly, why I'm posting here now lol.
[Samsung Galaxy S8+ Questions & Answers] JesseMT4G:
I wish they would just go back to flat screens. I recently got a steal on a s7edge. It's a decent phone and the best battery life I have had on any phone. I do hate the curved screen. Thought I would get used to it, but nope. I heard it's less on the s8 hence me checking it out here soon, but I still have my N5 I use on wifi for home use and its to date my favorite phone. Unfortunately seems the note series is going mildly to the curved screen as well.

Maybe I'll check out the g6 while I am there. Or to heck with it, I might just get the blackberry Keyone! I do miss my physical keyboard, even after all these years.
[Samsung Galaxy S8+ Questions & Answers] mjs2011:
Not sure about dumbing down the customization. Have you seen the theme store?
[Samsung Galaxy S8+ Questions & Answers] CadillacMike:
when I went to the T-Mobile store to pay off my V20, so I could pre-order the S8+, they had a G6 on display, and that was the first time I had seen it out. I asked the lady if it was selling, and she said she has not sold a single one.

it was nice but, if I had to choose between my V20 and the G6, I would keep the V20. Now i just can't wait for my S8+
[Samsung Galaxy S8+ Questions & Answers] johnwayne27:
The on-screen buttons can be removed by installing nova launcher, turning the dock off, and handling everything with gestures. The screen area is only limited if you leave the default touchwiz launcher. Gotta think outside the box sometimes.
[Samsung Galaxy S8+ Questions & Answers] misiokicio:
haha well hard for some to do that xd, :)
[Samsung Galaxy S8+ Questions & Answers] jpinks:
I am worried about the curved screens too. The drop tests results on youtube arent too encouraging. But after the Note 7 went back and I am back to using my Note 4, I guess I will just have to put it in what I call a Brick case lol.
[Samsung Galaxy S8+ Questions & Answers] prfraczek:
---------- Post added at 08:16 AM ---------- Previous post was at 07:41 AM ----------

[/COLOR]

Buaaaaa I don't care about buttons on home screen, what about the buttons while mail is running or other apps? Is Nova working globally? What a ridiculous idea.

Thinking outside of the box hahaha
[Samsung Galaxy S8+ Questions & Answers] vision33r:
Don't buy the hype go try out the device out. The only thing I am seeing is this is an evolutionary​ step from the Note 7. They're trying to push it with a big PR to fix the note 7 debacle. Will they sell 70mil units? Hard to say since there are too many competition this year. Pixel 2, OnePlus, etc. I am gonna wait for Note 8 and hoping for none curve screen. It's a liability for me.
[LG G Watch R] Blueforcer:
Hello guys,

first of all, sorry for my bad english:)

now i have some strange problems too, and i need your help.

A year ago i flashed a moddet rom, but a bug has caused that the watch reboots when booting in the cradle.

finally my watch restart over and over for a whole night.

Afterwards she started to turn off randomly. Now i replaced the battery with a new one and flashed the newest stock rom and TWRP.

While in TWRP the watch keeps on and charge correctly until 100%.

When i try to boot normaly it boots up, says "Android is starting - X of 45 Apps" when all 45 Apps are done it says "Finish boot".

after that it says "Is shuting down" and switch off immediately .

After starting again, it shows the colorful loadingscreen and switch off again.

This is reproducible:

5 times shut down during colorful loadingscreen

"Updating Android" - shut down

and so on.

This is constantly repeated

I tried different stock roms, but have the same issue everytime.

Is that a Kernel or another softwareproblem? because in TWRP the Watch stay on the whole time. But right before starting the Android Mainscreen it shuts off.

Edit: one thing i recognize today:

The watch dont turn on automatically when i place it on the cradle

greetings

Stephan
[LG G Watch R] robimarko:
Try to completely wipe the system and then flash new one from TWRP.

I mean wipe the system partition from ADB
[LG G Watch R] Blueforcer:
i wiped the partition with

adb shell

rm -rf /system/*

and flashed the Rom via TWRP.

But same issue:(
[LG G Watch R] Blueforcer:
I do not know if it is a error:

i tried to sidoload superSU in TWRP and get the error:

Failed to mount /system (no such device)

In TWRP im unable to Mount system. Its not selectable

i cant find the SYSTEM partition:

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell cat /proc/mounts
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/mmcblk0p21 /data ext4 rw,seclabel,relatime,data=ordered 0 0
/dev/block/mmcblk0p21 /sdcard ext4 rw,seclabel,relatime,data=ordered 0 0
/dev/block/mmcblk0p20 /cache ext4 rw,seclabel,relatime,data=ordered 0 0

only in the mappings i can find system

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell ls -al /dev/block/platform/msm_sdcc.1/by-name
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 480 Jan 1 00:00 .
drwxr-xr-x 4 root root 560 Jan 1 00:00 ..
lrwxrwxrwx 1 root root 21 Jan 1 00:00 DDR -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 Jan 1 00:00 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 1 00:00 abootb -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 1 00:00 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 1 00:00 cache -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Jan 1 00:00 grow -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 1 00:00 imgdata -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 1 00:00 laf -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 1 00:00 metadata -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 1 00:00 misc -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 1 00:00 persist -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jan 1 00:00 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 Jan 1 00:00 rpm -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Jan 1 00:00 rpmb -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Jan 1 00:00 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Jan 1 00:00 sbl1b -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 1 00:00 sdi -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Jan 1 00:00 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 1 00:00 system -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 20 Jan 1 00:00 tz -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Jan 1 00:00 tzb -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Jan 1 00:00 userdata -> /dev/block/mmcblk0p21
[LG G Watch R] robimarko:
Which TWRP are you using?
[LG G Watch R] Blueforcer:
twrp-3.1.0-0-lenok
[LG G Watch R] robimarko:
Thats the issue,officiall TWRP was not working on 3.0.2 so it is probably not working on 3.1.

I use an unofficall image,if I am not mistaken this should be it

http://www.mediafire.com/download/rhfr5ps2c8ssxx5/twrp-3.0.0-0-lenok+squashfs.img

And it works
[LG G Watch R] Blueforcer:
this works thanks! Mounting works

Now i will try to sideload the rom (M1D65H) again, hopefully my watch will boot

btw: M1D65H etc is the versionnr? Or does it have to fit my watch?
[LG G Watch R] Blueforcer:
ARRRGH!

Still the same problem:crying:
[LG G Watch R] robimarko:
Maybe stupid question but have you tried to wipe cache and format everything except recovery from TWRP?
[LG G Watch R] Blueforcer:
i make a factory reset (wipes Data, cache and dalvik) via TWRP.

if i try to wipe System with TWRP it says: Unable to wipe /system -- unknown file system "auto"

Is there another way to format everything? With adb there is no command like wipe or format
[LG G Watch R] robimarko:
Yes,through TWRP.

In Wipe,through advanced
[LG G Watch R] Blueforcer:
Its unable to wipe /system
[LG G Watch R] Blueforcer:
Now i have flashed the old 5.1.1 and have the same problem. Maybe a hardware problem?
[LG G Watch R] robimarko:
Hm,I doubt it since it does not reebot in TWRP.
[LG G Watch R] Blueforcer:
And not during the Android update or Upgrade process. Only when it tries to load the homescreen i think. Is there a kind of safemode like in windows?
[LG G Watch R] Blueforcer:
No ideas anymore? :(
[LG G Watch R] smarak01:
Blueforcer I am having the exact same issues. Since my watch is on the new read only system OS I have not been able to get my watch to boot. I am able to use fastboot and adb but once it loads it just stays on the startup screen for a few minutes and then shuts down.

Does anyone know if there is a way to wipe the entire contents and reload from a working watch? I have tried multiple boot/recovery, but believe the issue stems from inside the systems folders.

Thoughts?
[LG G Watch R] philicibine:
hello all.

It appears I am suffering from the same or similar issues. My watch wont boot fully. It boots, and then on completion it immediately says "switching off".

I have reset it. And tried to wipe system. And im now at the same point where the system folder wont wipe properly. It errors saying "unknown filesystem 'auto'".

This to me looks like a software bug. In either twrp or the rom itself. The issue started for me when the battery ran too low. My rom was fully stock. Nothing changed.

Where can we report this to LG? My watch is well out of warranty so I am holding no hope for a fix. Seems my watch got bricked by this update to me.

EDIT: UPDATE!! Its fixed!! For now!

I used this recovery and used advanced wipe to wipe the system folder. Which resulted in no error about the filesystem. And I then sideloaded the twrp flashable factory zip.

I hope you guys can fix too!
[LG G Watch R] philicibine:
Well it seems I'm still in the same boat. Although it's not happening immediately after bootup, my watch is still randomly shutting itself down. :(

Got enough time while it's booted to get a logcat, but can't see what is doing it.
[LG G Watch R] miffymiffy:
I sent mine back to LG and they told me it was a motherboard problem with an update causing software corruption. It did not make sense to me...

They didnt repair it as I had the bootloader unlocked. So I have the watch back with the same issues.

Many have reported that replacing the battery has fixed their issues. I dont know how, seeing as though my watch stays on for days in bootloader and recovery.
[LG G Watch R] philicibine:
so I have taken a logcat. Can anyone see anything interesting here?

https://pastebin.com/6q6qFry8
[LG G Watch R] miffymiffy:
01-01 01:02:26.142 588 800 I ShutdownThread: Performing low-level shutdown...

Basically telling you that the watch thinks its low on battery so shuts down.
[LG G Watch R] philicibine:
Thanks

Currently trying to go back to the earliest factory rom i can but stumbling with writing to system. Out of warranty, so LG probably wont help me. Seems like their update bricked my watch :(
[LG G Watch R] philicibine:
Another update. I wiped thru fastboot

fastboot -w

and then fastboot flashed the earliest build I could. And let it setup (rebooting itself lots in between).

Once it had all gotten setup properly and after many of the symptomatic reboots. It has now taken a full charge and seems to be running ok. It has been up and running for a couple of hours without rebooting. I hope this is it fixed.

I have ordered a huawei watch classic just in case. :silly:
[LG G Watch R] philicibine:
So my watch has been on charge overnight. Running all evening yesterday on battery. Not one reboot in that time. It appears to be fixed

:D
[Galaxy S 4 Q&A, Help & Troubleshooting] jmo707:
Hello.

I'll first describe the secuence of events and then tell which solutions I've tried. Bear with me. I'll be brief.

I've bought a second hand Samsung Galaxy S4 (i9500) sold through a local carrier. By law the carrier can only give the unlock code to the original buyer of the phone, and the person from who I bought it from wasn't him/her.

I tried to unlock it by my means (basically this, trying lots of variants until "186" code dead-end), which resulted in rooting, flashing diferent modems and trying a CM based custom ROM (GearCM). Before going on any of this, I made an EFS, cdma-radio, radio, m9kefs1/2/3 backup.

As I couldn't do it, I took the phone to a repair shop, where they unlocked it with a box. Then they told me that the SIM tray was broken, and after trying a different one, they concluded that it was a software problem (I suggested it) and flashed a stock ROM from the carrier, which still didn't recognized any SIM.

This is when I took back the phone.

I've restored the EFS and flashed the correct modem (In fact I've found two which work: I9500UBUHPB2-CP and I9500UBUHOI1), but even if the SIM card is recognized, I can't connect to the network, I think, because the IMEI which displays the phone is different from the factory IMEI. In fact, is the infamous generic IMEI 0049... with IMEISV 01.

I've since tried this methods:

- Changing permissions of the EFS folder

- Flashing the stock ROM after completly wiping out the phone

- Manually deleting the EFS contents and restoring

And combinations of the above with RegionLockAway and with both working modem drivers.

I still have to try rooting an older stock ROM, maybe 4.4.2, but I wanted to ask more wise people if there is a logical, correct order to any of the above steps, or if you think I'm missing something here.

The only other answer that comes to me is that it's something done by the repair shop with the box, but still I've no conclusive proofs of that. I wanted to exhaust options.

Thanks in advance. Any answer will do good.
[Galaxy S 4 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
Restoring the EFS does nothing, as the IMEI is no longer stored in it. Thus none of the things you tried will help. You'll have to take the device back to the place who fixed it for you.
[Galaxy S 4 Q&A, Help & Troubleshooting] jmo707:
I would have thought that it was stored on it. Do you infer that from my failed attemps? Where should it be "stored"?
[Galaxy S 4 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
I don't "infer" anything. It's a fact. IMEI was stored in a file named nv_data.bin in EFS, but for some time now it's no longer been located there. It's been moved to three hidden partitions that a nandroid backup does not touch. You'd have to use Wanam Partition Backup and Restore to see the partitions in order to be able to back them up as well as restore them. Thus, your IMEI is gone, and the repair shop is going to have to fix it.
[Galaxy S 4 Q&A, Help & Troubleshooting] jmo707:
But I have a backup of those partitions, made with Wanam Partition Backup. I've restored them in this order: cdma-radio, EFS, radio, m9kefs1, m9kefs2, m9kefs3. Somehow, its not working.

That's why I think maybe it has to do with the order of the steps I'm taking, maybe even before restoring the partitions.
[Galaxy S 4 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
I edited my post while you were making yours.

My backup consists of much more than those three partitions. I have in addition to those efs.img, fsg.img, modemst1.img, and modemst2.img. The IMEI is in one of those partitions, NOT EFS.
[Galaxy S 4 Q&A, Help & Troubleshooting] jmo707:
Well then... I hope they can repair the IMEI then. It would be a damn shame if not... Thanks for your time.
[LineageOS Questions & Answers] BeastyUmbrella:
I just got a notification on my phone (HTC One m8) saying that there is a new update to LineageOS. When I open up the app the updater says that it's from the 1st of January 1970. Still says nightly and LineageOS 14.1 Android 7.1. Considering its the 1st of April I would think it's an April's fools, but I'm not sure. Anyone else in the same situation?

Thanks in advance
[LineageOS Questions & Answers] Ibuprophen:
[MENTION=8132041]BeastyUmbrella[/MENTION], They apparently released a corrected version on the 30th:

https://download.lineageos.org/m8

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[LineageOS Questions & Answers] BeastyUmbrella:
So I should just stick with the update from the 30th of March?

I have attached a screenshot of the update.

Thanks for the reply!
[LineageOS Questions & Answers] Ibuprophen:
I really do believe you! I did notice that this issue came up for a recent release on a few devices within the Lineage's Gerrit and Github.

That was an issue that i had to see with my own eyes and i did... I was amazed at this too...

What you see on the link i had previously provided is the Official source for the releases.

I believe that the 1970 release error, though was a good year, was pushed out only through the LineageOS Device Updates.

Remember that if you ever see any device updates that do not look right, DO NOT, under any circumstances update your device with a questionable update. When in doubt, defer to the LineageOS website for the update. You may end up messing up a device ROM install and end up losing everything and have to start it all over with a fresh install.

Until you see a newer, and date appropriate, update from within your device, stick with the LineageOS website downloads and, if you decide to, update using the LineageOS website.

To add, the device updates are the same as the one's released through the website.

I wish you the best of luck!

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[LineageOS Questions & Answers] BeastyUmbrella:
Thanks a lot!