hi,
Today morning, i tried changing the following registry key .
Once i restarted the mobile, i got the updates notification for 7740 instantly.
MobileOperator: VOD-DE
MOName: Vodafone
OEMDeviceName: Atlantic_VDF_DE
anyhow, there is no Wifi tethering in this update.
What's new in this update?
Notice battery life improvements or anything?
It was said to fix the exchange server problem and some improvements in voicemail.
Not even 24 hrs since i installed the update.
Will keep posted if i see any battery improvements.
7740 supposed to have some improvement for battery according to this:
http://www.winrumors.com/nokia-promises-second-windows-phone-update-for-battery-issues/
Just did the changes as the OP suggested and I triggered the 7740 update. Interestingly, it says there is also "LG Update for Windows Phone", OP did you see this too?
Hoping it is for tethering .... updating now, will report when done.
Just in case anyone needed debranding instructions:
1. Enable the MFG application by going to the dialer and dialing ##634# then pressing call.
2. Launch the MFG application and enter 277634#*# when prompted for a password.
3. Select the Engineer Menu item.
4. Select the Other Setting menu item.
5. Select the Edit registry menu item.
6. Set the input boxes on this menu as follows:
Select ROOT_PATH: HKEY_LOCAL_MACHINE
Input SUB_PATH: \System\Platform\DeviceTargetingInfo\
Input KEY: MobileOperator
Data Type: STRING
7. Select Query and write down the result in case you need to re-brand for some reason.
EDIT:
Installation failed after rebooting phone, error code 8018001e, did not update to 7740.....did not do LG update...
EDIT 2:
Tried to update it a couple more times, but always getting the error... OP what kind of Quantum do you have and what carrier ROM? C-900? c-900B? c-900k?
can you tell me the registry changes you did ?
What mobile operator did you put in ?
I finally managed to update.
I think battery might be slightly better but that could be placebo lol
Anyway keeping current is always good anyway
I tried vod de and also vod it. Both showed there was 2 updates, but always failed. Op and scoobysnacks, what model of quantums are you using?
dont do ir his way, use the update cab sender here
http://forum.xda-developers.com/showthread.php?t=1306415
Much easier
Thanks, the cab sending method worked. I'm still interested in what carrier your phone was originally with
bobzero said:
Thanks, the cab sending method worked. I'm still interested in what carrier your phone was originally with
Click to expand...
Click to collapse
mine is a bell phone I'm using with telus
yakaaithiri said:
hi,
Today morning, i tried changing the following registry key .
Once i restarted the mobile, i got the updates notification for 7740 instantly.
MobileOperator: VOD-DE
MOName: Vodafone
OEMDeviceName: Atlantic_VDF_DE
anyhow, there is no Wifi tethering in this update.
Click to expand...
Click to collapse
Just a note -- if you truly 'debrand' by changing the MobileOperator to " " (blank), then you don't get the upgrade right away. It seems to be region specific.
Official 7740.16 update notices have been getting sent out over the last week to Bell phones.
No firmware update accompanied this OS update.
Just for reference in case anyone wanted to brand their phone to Bell or ATT:
AT&T
[HKLM\System\Platform\DeviceTargetingInfo\]
MobileOperator = ATT-US
MOName = AT&T Wireless
OEMDeviceName = PACIFIC_ATT_US
BELL
[HKLM\System\Platform\DeviceTargetingInfo\]
MobileOperator = BEL-CA
MOName = BELL
OEMDeviceName = PACIFIC_BEL_CA
Other keys that can be adjusted and have an impact:
FirmwareRevision
RadioSoftwareRevision
MODeviceName
The purpose of this thread is to have all information regarding the Weloop Tommy, gathered, fresh and to the point.
(i am not affiliated with Weloop)
Please read both post number 1, 2 and search thread before asking questions thank you.
FAQ
Q:What is the latest firmware?
[Release] black watch v3.19 firmware update notifications [Copy link]
This update to the firmware update, the client does not update the current firmware version v3.18 firmware watches friends can try to use the old client detects the firmware update.
Update:
Solve watches restart, restore factory settings watches language will change.
Download Link:
iOS client 2.079: http://fir.im/iosobt
Android client 1.29.3702b: http://fir.im/andobt
Unofficial file archive of WeLoop Tommy. APK-Files with ending "b" are BETA http://www.wtf.li/
Q: When is the next app update
A: Weloop v. 3.0 will be released as closed beta 7the of March 2015 we don't know when there will be an open english release....
the extensive update 3.0 have,
better health monitoring
profiles
sleep monitoring
more alarms weekdays/weekend
and more.
(see attached pictures for app version 3.0 UI improvements
Q: What does the settings do?
- Backlight
24H: Backligth always turns on when button is pressed
Nite: Backligth turns on when button is pressed at night time (from 17–8)
Off: Backligth Always Off
- Motion
24H: Motion detection always on (backlight turns on when motion is detected)
Nite: Motion detection on at night time (from 17-8)
Off: Motion detection Off
- Night
On: Notification vibration disabled at night (from 23–8)
Off: Notification enabled at night
- O Clock
On: every whole hour the watch will vibrate. 12'O'clock etc.
Off: Off
- Fitness
On: Fitness functionality on
Off: Off
- Language
Chinese
English
- Anti Loss
On: Alarm when Phone is out of BT range
Off: Off
Q: Is there Cyrillic support
A: Yes
Q: The GoClever Ecos Chronos is the same watch right?
A: Yes it is on the hardware side, and you can with a "hack" install the firmware from the ECOS on the Tommy. (see next post for How to.!)
Awesome Weloop Review by VECTRON
http://forum.xda-developers.com/smartwatch/other-smartwatches/weloop-tommy-smartwatch-looks-best-t2864444
Troubleshooting
Q: i can not update my watch/its stuck/acting weird
Have you tried to reset the watch? there are 3 ways to do it
Restart watch from app. under update there is a restart button (it says reset but it restarts and keeps all your settings)
Reset from watch (Last menu point, this resets everything)
Hard reset (connect charge cable and press up and down button to reset)
Force OTA update:
Connect your watch to the charger. (watch must be charging)
Press all 3 buttons on the side simultaneously
Release the 2 side buttons, and keep the middle button pressed until you get the upgrade connecting display. (this might take some seconds)
Delete connection from phone
Connect and pair from app and upgrade
If you are on an Android device and it cannot connect, try an ios device, and vice versa
Q: The watch keeps switching back to chinese
More people have experienced that if the language is non english the watch will reset to chinese. Changing the phone OS to english stops the watch from switching to Chinese.
"Hacks"
How to make your own watchfaces:
user fcsabika has created a cool tool to create your own watchfaces
WeLoop Tommy Watchface Creator
attached are also some watchfaces made by user ruicoel filename "project rui.zip"
How To install GoClever Chronos ECO firmware on Weloop tommy (android only)
Download latest ECO firmware to phone
Disconnect Watch from phone, install ECO app
Go to “Check For Upgrade”
Tap on the middle circle six times
“Select a firmware file___ [Browse]”
Watch must be in forced OTA
Update watch.
You can flash between weloop and Goclever firmware (always be careful and follow instructions when flashing, i take no responsibility for bricked or exploding watches...)
To install weloop firnware, follow same instructions but use weloop app instead.
PROJECT OPEN FIRMWARE (please make sure you understand what this is and what it does before you attemtp to flash your watch)
Make a Weloop Tommy an open source sport watch that can be used without a mobile phone. Want to see a heart rate when running, cycling speed and cadence when cycling or number of laps while swimming? Help to make it possible! LINK
This project is divided into six phases:
Phase 1: find out and document watch pinout so it will be possible to communicate with screen, accelerometer and a flash memory from a custom firmware. DONE
Phase 2: write a custom firmware that will print sample text on a screen and expose a BLE service. Firmware will be flashed using SWD connector. DONE
Phase 3: make it possible to upload a custom firmware using OTA. This will save the waterproof case from destruction. DONE
Phase 4: update softdevice to the newest version (S110 8.0.0). Add possibility to switch to other softdevice (S120/S130) DONE
Phase 5: create a "terminal" firmware that allows to control what is displayed on a watch from an android/iOS app. IN PROGRESS
Phase 6: create a "standalone" firmware using S130 softdevice that can connect to external sensors (HRS, CSCS etc) without a phone. TODO
Go support developer Krzysiek
Goclever APK & FW file is attached to this post.
Latest Chronos ECO firmware 3.18
http://www.chronos.goclever.com:8080/fileServer/firmware/CHRONOSECO_V3.18_1.bin
Chronos ECO app (android)
https://play.google.com/store/apps/details?id=com.yf.foreign.goclever
Chronos ECO IOS app
https://itunes.apple.com/th/app/goclever-chronos-eco/id955306578?mt=8
BUGS & Annoyances
Notification not always deleted from phone when deleted on watch
Watch freezes sometimes
Being able to set the night time manually would be great (This can be done with the Goclever fw)
I'm no Dev so I'm not sure if this is of any help. While updating the watch I wanted to ensure my screen stayed on so I was tapping the screen.
If you tap the center of the percentage 6 times a pop up appears for you to select your update file. If you select browse it gives you access to a bunch of folders that appear to be inside the app or maybe the watch itself. I tried it several times and 6 is the magic number to make the option appear or disappear. It doesn't work if the watch isn't upgrading it's firmware.
Hope it can be of some use
skiiermike said:
I'm no Dev so I'm not sure if this is of any help. While updating the watch I wanted to ensure my screen stayed on so I was tapping the screen.
If you tap the center of the percentage 6 times a pop up appears for you to select your update file. If you select browse it gives you access to a bunch of folders that appear to be inside the app or maybe the watch itself. I tried it several times and 6 is the magic number to make the option appear or disappear. It doesn't work if the watch isn't upgrading it's firmware.
Hope it can be of some use
Click to expand...
Click to collapse
Thanks was this working on ios or android?,
will add to FAQ
taleboblen said:
Thanks was this working on ios or android?,
will add to FAQ
Click to expand...
Click to collapse
Android.
Thx
Thnx for the information, all working ok on my samsung s4, get the last version v3.18.
thx again
backlight
first of all thanks for this thread :good:
the nite backlight on my tommy watch actually comes on after 5PM (17:00)
i am from Slovakia, phone language is English, time zone CET (GMT+1)
interesting to see that yours turns on after 23:00
chsustik said:
first of all thanks for this thread :good:
the nite backlight on my tommy watch actually comes on after 5PM (17:00)
i am from Slovakia, phone language is English, time zone CET (GMT+1)
interesting to see that yours turns on after 23:00
Click to expand...
Click to collapse
Thanks for the update. i decrypted some of the information from the official Weloop FAQ. and yes i can now confirm that you are right. it turns on from 17-8 thanks again. I have now updated the FAQ with the correct time for all Night settings. :good:
Hello! Can someone make last CHRONOS ECO apk link to download? I cant download it from google play.
k0ra said:
Hello! Can someone make last CHRONOS ECO apk link to download? I cant download it from google play.
Click to expand...
Click to collapse
Hi , the chronos eco app is not compatible with the Weloop Tommy.
Brand new Tommy, it was paired with my phone but the connection was unstable, so I tried and forced an OTA update, watch is "Updating... 0 pct" but now the phone cannot detect the watch any more
Resetting the watch will restart it in ota update mode again!
Any help appreciated...
l.capriotti said:
Brand new Tommy, it was paired with my phone but the connection was unstable, so I tried and forced an OTA update, watch is "Updating... 0 pct" but now the phone cannot detect the watch any more
Resetting the watch will restart it in ota update mode again!
Any help appreciated...
Click to expand...
Click to collapse
Happened to me also, try to delete connection under bluetooth settings on device. now connect to to weloop and pair from Weloop app. keep trying and then go to update. again persistence is key. keep trying to update suddenly it will connect and update.
Whas the watch on latest firmware when you tried the force OTA?
are you on android or ios see if there is an updated App for you phone. see link on OP for beta APK.
let me know if it works.
watch was not on latest firmware, cant' remember which version it had.
I'm on android, also v1.24 does not help as check for updates does not go beyond "Checking version...".
k0ra said:
Hello! Can someone make last CHRONOS ECO apk link to download? I cant download it from google play.
Click to expand...
Click to collapse
l.capriotti said:
watch was not on latest firmware, cant' remember which version it had.
I'm on android, also v1.24 does not help as check for updates does not go beyond "Checking version...".
Click to expand...
Click to collapse
Try to update the Weloop app, latest is 1.27.
kill weloop app
delete bt connection from phone.
Open weloop app
conmect and update. Keep trying it can take a couple of times.
If all fails if possible try with other device and or ios device
update: I used an iphone and after a few retries I got it on v3.18.
back to android, but the pairing and the sync is problematic, to say the least, on my Huawei P7...
skiiermike said:
I'm no Dev so I'm not sure if this is of any help. While updating the watch I wanted to ensure my screen stayed on so I was tapping the screen.
If you tap the center of the percentage 6 times a pop up appears for you to select your update file. If you select browse it gives you access to a bunch of folders that appear to be inside the app or maybe the watch itself. I tried it several times and 6 is the magic number to make the option appear or disappear. It doesn't work if the watch isn't upgrading it's firmware.
Hope it can be of some use
Click to expand...
Click to collapse
If it's allowing you to select an update file, surely it is showing you the file system of the phone? Otherwise, you'd have no way to put a firmware update file there to select. My understanding would be this allows you to install a firmware update file stored on your phone, although I can't test this for sure as my Android phone is currently being repaired. There's some discussion about this here and that thread also contains a very small amount of analysis on the firmware file (VERY small amount, basically just analysing the name of the binary file), and another app that is apparently in some way related (link).
For what I can glean from the description of that app (seemingly made by the manufacturer of the SoC [System on a Chip] used in the WeLoop Tommy), it would appear that devices using the SoC (including the Tommy) have three firmwares: "bootloader", "soft device" and "application". The one embedded within the WeLoop app apk has the name "ble_app_ancs.bin"; ble stands for bluetooth low energy and ancs apparently stands for apple notification centre services. That leaves "app" - my guess would be this is the "application firmware". I'm not entirely sure the roles of the "bootloader" and "soft device" firmwares, but my guess is the one or other allows the device to get into "DFU mode" (or "OTA mode" as it seems to be referred to also), meaning in theory it should perhaps be possible to recover from any bricks arising from flashing dodgy application firmwares.
So potentially there is the option of reverse engineering the firmware (easily obtained from here: http://wtf.li/ - mirror of the APKs of the app [each of which contain a version of the firmware], and also one version of the firmware (the .bin file) separately), and creating a custom/modified one, while still being able to recover (because bootloader & soft device should be untouched). However, I have neither the expertise nor the time to look into that.
Without an Android phone with which to run either of the apps right now, I can't poke about too much (I only received my Tommy today), but once I get my phone back I'll maybe try and see if I can find anything else interesting. I'd like to see if I can figure out any way to get access to the watch faces, and see if they can be reverse engineered in any way, for example.
EDIT: Here is the output of strings run on the firmware binary from the latest version of the app on http://wtf.li : http://pastebin.com/X7TQXTb3 - nothing particularly interesting, a few filenames of the source files and a few other strings seen in the watch interface and stuff.
EDIT: A couple of URLs accessed by the app (seemingly related to updating):
http://au.umeng.com/api/check_app_update
http://www.yfsmart.com/weloopInterface/getFirmware.do
I can't see anything on these sites, my guess would be they need query strings parameters or something (not really sure what, some way of identifying that the app is accessing the site) to actually do anything.
EDIT: Hmm... http://www.yfsmart.com/weloopInterface/firmware_Upload.jsp - this site seems to allow you to upload a firmware. I wonder if it allows anyone to upload a firmware, which would then be downloaded by everyone when they check for updates? Certainly seems rather insecure...There's a bunch of other pages at http://www.yfsmart.com/weloopInterface/ haven't looked through them all yet.
EDIT: From what I can glean from this page ("SoftDevices" section under the "Development Tools and Software" tab), it seems like the "soft device" firmware is essentially a bit like a library, it's a precompiled binary supplied by Nordic (company that makes chip inside Tommy) which provides all the networking functions etc. which the "application" firmware uses. So:
Code:
application = front end UI (basically, the part WeLoop made)
soft device = "library" via which application can access hardware etc.
bootloader = initial part of firmware that loads SD + app firmwares
So the only really interesting part is probably the application firmware, the part that is in the WeLoop app. That's the code that actually "matters", the rest is just low level stuff. For actually changing the interface or whatever, modifying the app firmware would be all that's needed (for example, to increase the font size or the back light duration etc.).
SifJar said:
If it's allowing you to select an update file, surely it is showing you the file system of the phone? Otherwise, you'd have no way to put a firmware update file there to select. My understanding would be this allows you to install a firmware update file stored on your phone, although I can't test this for sure as my Android phone is currently being repaired. There's some discussion about this here and that thread also contains a very small amount of analysis on the firmware file (VERY small amount, basically just analysing the name of the binary file), and another app that is apparently in some way related (link).
For what I can glean from the description of that app (seemingly made by the manufacturer of the SoC [System on a Chip] used in the WeLoop Tommy), it would appear that devices using the SoC (including the Tommy) have three firmwares: "bootloader", "soft device" and "application". The one embedded within the WeLoop app apk has the name "ble_app_ancs.bin"; ble stands for bluetooth low energy and ancs apparently stands for apple notification centre services. That leaves "app" - my guess would be this is the "application firmware". I'm not entirely sure the roles of the "bootloader" and "soft device" firmwares, but my guess is the one or other allows the device to get into "DFU mode" (or "OTA mode" as it seems to be referred to also), meaning in theory it should perhaps be possible to recover from any bricks arising from flashing dodgy application firmwares.
So potentially there is the option of reverse engineering the firmware (easily obtained from here: http://wtf.li/ - mirror of the APKs of the app [each of which contain a version of the firmware], and also one version of the firmware (the .bin file) separately), and creating a custom/modified one, while still being able to recover (because bootloader & soft device should be untouched). However, I have neither the expertise nor the time to look into that.
Without an Android phone with which to run either of the apps right now, I can't poke about too much (I only received my Tommy today), but once I get my phone back I'll maybe try and see if I can find anything else interesting. I'd like to see if I can figure out any way to get access to the watch faces, and see if they can be reverse engineered in any way, for example.
EDIT: Here is the output of strings run on the firmware binary from the latest version of the app on http://wtf.li : http://pastebin.com/X7TQXTb3 - nothing particularly interesting, a few filenames of the source files and a few other strings seen in the watch interface and stuff.
EDIT: A couple of URLs accessed by the app (seemingly related to updating):
http://au.umeng.com/api/check_app_update
http://www.yfsmart.com/weloopInterface/getFirmware.do
I can't see anything on these sites, my guess would be they need query strings parameters or something (not really sure what, some way of identifying that the app is accessing the site) to actually do anything.
EDIT: Hmm... http://www.yfsmart.com/weloopInterface/firmware_Upload.jsp - this site seems to allow you to upload a firmware. I wonder if it allows anyone to upload a firmware, which would then be downloaded by everyone when they check for updates? Certainly seems rather insecure...There's a bunch of other pages at http://www.yfsmart.com/weloopInterface/ haven't looked through them all yet.
EDIT: From what I can glean from this page ("SoftDevices" section under the "Development Tools and Software" tab), it seems like the "soft device" firmware is essentially a bit like a library, it's a precompiled binary supplied by Nordic (company that makes chip inside Tommy) which provides all the networking functions etc. which the "application" firmware uses. So:
Code:
application = front end UI (basically, the part WeLoop made)
soft device = "library" via which application can access hardware etc.
bootloader = initial part of firmware that loads SD + app firmwares
So the only really interesting part is probably the application firmware, the part that is in the WeLoop app. That's the code that actually "matters", the rest is just low level stuff. For actually changing the interface or whatever, modifying the app firmware would be all that's needed (for example, to increase the font size or the back light duration etc.).
Click to expand...
Click to collapse
Thank you for the insights and findings its all very promising. :good:
On a sidenote:
I talked to one of my colleagues who is an engineer (i'm not a dev but a Designer), it seems like we in the office are playing around with the exact same SOC from NordicSemiconducter. we tried one of the apps from the google play store and it connects to the weloop(see attached pic). The app was called "nRF Master Control Panel", tried the other apps from NordicSC but no luck.
Hopefully there will be some sort of SDK with the v3.0 release on the 30th...
I got my Android phone back today, and haven't tinkered too much with Tommy just yet, but I can confirm that the file system you are browsing when you tap the percentage 5 times during an update is just the phone file system. It browses from root (i.e. /), rather than /sdcard or whatever, which is the standard, user accessible partition, hence there are some folders etc. you may not recognise, but amongst them will be "sdcard" which will take you to your regular storage (note: this is the case on phones without a micro SD card as well), where you could easily place an update file.
SifJar said:
I got my Android phone back today, and haven't tinkered too much with Tommy just yet, but I can confirm that the file system you are browsing when you tap the percentage 5 times during an update is just the phone file system. It browses from root (i.e. /), rather than /sdcard or whatever, which is the standard, user accessible partition, hence there are some folders etc. you may not recognise, but amongst them will be "sdcard" which will take you to your regular storage (note: this is the case on phones without a micro SD card as well), where you could easily place an update file.
Click to expand...
Click to collapse
Thanks for the confirmation. :good:
taleboblen said:
Troubleshooting
Force OTA update:
Connect your watch to the charger.
Press all 3 buttons on the side simultaneously
Release the 2 side buttons, and keep the middle button pressed until you get the upgrade connecting display. (this might take some seconds)
Delete connection from phone
Connect and pair from app and upgrade
If you are on an Android device try an ios device, and vice versa
Click to expand...
Click to collapse
I tried to use the OTA update to go from 3.17 to 3.18 (on Android) but Tommy stuck on screen "WeLoop ... Udating 0%", my smartphone (HTC M8) with its APP (latest version) dont find the Tommy and it remains bricked, how do I restart it? I tried all combinations, but remains on the screen, help me!
Hey everyone, this morning my phone (N910T) notified me that it has an update to download. The update is huge, coming in at 1506.66 MB. I am downloading it now but it will take about 40 minutes. I know the current software update site still says manufacturer development but this is a good sign!
Edit: Confirmed. It is 6.0.1!
Edit 2: Change Log posted below.
Size: 1506.66 MB
Version: N910TUVU3EPE3/N910TTMB2EPE3/N910TUVU2EPE3
- OS upgrade - Android 6.0.1 Marshmallow
- The following functions have been deleted : Instagram, WhatsApp
- The new TouchWiz provides enhanced usability and an updated Visual design.
- Quick connect helps you easily find and connect to nearby devices by showing the currently connected devices and previous connections.
- Fingerprints are securely protected. An alternative unlock method (pattern, pin, or password) is required to add fingerprints.
- Advanced power saving mode restricts background data and extends battery life.
- A new vibration pattern concept has been applied.
- Settings for the following have been reset: Theme, Email, Icon/Widget
* Before OS 6.0 upgrade, please be sure to update the Samsung gear to the latest version.
* Android 6.0 Marshmallow does not support the Decrypt device function. If your mobile device is encrypted, encryption cannot be disabled after upgrading. If you want encryption to be disabled after upgrading, it must be disabled before you upgrade your device. To disable encryption go to Settings - Lock screen and security - Other security settings, then select Decrypt device.
* Some apps that were installed via the Lollipop OS may need to be updated after upgrading to the Marshmallow OS. Go to Galaxy Apps or Play store to update Apps.
* If present, the Email shortcut on you home screen will be removed during the upgrade. It can be added to the home screen again after upgrading.
* Some changes may vary depending on the country or network operator.
* The functionality of some features may differ after the upgrade. Some apps may not function normally.
* Errors during the upgrade may cause data loss. Back up any important data before upgrading.
If its that big, it's MM.
Sent from my SM-N910T using XDA-Developers mobile app
Update via Samsung Smart Switch
Download smartswitch from the samsung site.
Install on your PC. Connect your note 4 via USB. It'll download the update, and update your phone to MM.
Confirmed it is 6.0.1 being pushed OTA! I am starting the update now.
I got this instead, but yes I think it's MM
Smart Switch confirms it's MM
Oops. I missed the daily download limit. My phone has a bad USB port, and as such can't be connected to a PC to use Smart Switch.
Anyone having issues downloading it from smart switch? It keeps freezing after it says it is preparing the update
Sent from my SM-N910T3 using XDA Premium HD app
Mr. Clown said:
I got this instead, but yes I think it's MM
Click to expand...
Click to collapse
I'll try at midnight tonight (11pm here in Jamaica) before everyone else does.
Mr. Clown said:
Smart Switch confirms it's MM
Click to expand...
Click to collapse
Can you post the full change log when you get a chance? Thank you! :good:
Any word on root for this update?
Here is the full change log that was provided:
Size: 1506.66 MB
Version: N910TUVU3EPE3/N910TTMB2EPE3/N910TUVU2EPE3
- OS upgrade - Android 6.0.1 Marshmallow
- The following functions have been deleted : Instagram, WhatsApp
- The new TouchWiz provides enhanced usability and an updated Visual design.
- Quick connect helps you easily find and connect to nearby devices by showing the currently connected devices and previous connections.
- Fingerprints are securely protected. An alternative unlock method (pattern, pin, or password) is required to add fingerprints.
- Advanced power saving mode restricts background data and extends battery life.
- A new vibration pattern concept has been applied.
- Settings for the following have been reset: Theme, Email, Icon/Widget
* Before OS 6.0 upgrade, please be sure to update the Samsung gear to the latest version.
* Android 6.0 Marshmallow does not support the Decrypt device function. If your mobile device is encrypted, encryption cannot be disabled after upgrading. If you want encryption to be disabled after upgrading, it must be disabled before you upgrade your device. To disable encryption go to Settings - Lock screen and security - Other security settings, then select Decrypt device.
* Some apps that were installed via the Lollipop OS may need to be updated after upgrading to the Marshmallow OS. Go to Galaxy Apps or Play store to update Apps.
* If present, the Email shortcut on you home screen will be removed during the upgrade. It can be added to the home screen again after upgrading.
* Some changes may vary depending on the country or network operator.
* The functionality of some features may differ after the upgrade. Some apps may not function normally.
* Errors during the upgrade may cause data loss. Back up any important data before upgrading.
As a note, it was able to install successfully for me.
I would have thought there would be MUCH MORE people commenting on MM by now. Maybe everyone gave up?
-For those that have updated, what are your first impressions?
-I'm updating via Kies 3 as I type this [didn't think Kies worked]
-Optimizing app 93 of 292.
-And I have MM 6.01. Now I need ROOT to get everything back to proper order...
Has root been established for MM yet?
http://www.androidcentral.com/t-mobile-galaxy-note-4-now-receiving-marshmallow
If I were to flash the dok2 tar will it remove root and recovery? Then I could take the ota right?
Can someone post a link to where I can download the firmware? Other than sammobile. Or maybe be so kind as to upload it? ?
Personally, I'm hoping and wishing that someone puts up a root-friendly version on the Development section soon. I need MM to hold me over until the arrival of the Note 7 (actual 6)
Supersanborn said:
Personally, I'm hoping and wishing that someone puts up a root-friendly version on the Development section soon. I need MM to hold me over until the arrival of the Note 7 (actual 6)
Click to expand...
Click to collapse
Give it a couple of days [or maybe hours?] I updated without root to see what the big fuss is all about.
Downloads from SamFirm seems to be down. I am getting error 404. Does anyone else have the same?
dkb218 said:
Give it a couple of days [or maybe hours?] I updated without root to see what the big fuss is all about.
Click to expand...
Click to collapse
I'm not quite ready to go without Root, but given that the S7/S7 Edge are still sadly rootless, i may have to be prepared for that soon.
Supersanborn said:
I'm not quite ready to go without Root, but given that the S7/S7 Edge are still sadly rootless, i may have to be prepared for that soon.
Click to expand...
Click to collapse
That... I didn't know. I only need root for Viper4Android. I'd hate to have to do without it.