SmartThings on LineageOS - LineageOS Questions & Answers

I need help getting SmartThings working with LineageOS.
Short Version:
I have LineageOS 17.1 installed on a Tab S (SM-T700)
When I launch the SmartThings app it crashes
I've tried changing the build.prop
I've tried installing some Samsung account APK files
Long version:
I have two of the original Samsung Tab S (SM-T700) tablets that I bought new to use as controllers for my smart home. I have lots of smart home stuff, but I mostly control it all with SmartThings. The tablets are perfect for my needs: Thin and light in the perfect size, however they are now so old that the new version of SmartThings no longer works with the newest available stock Android, nor does Sonos, rendering them basically useless.
In an effort to revive them for their original use, I flashed one over to LineageOS. It works fine, however SmartThings crashes as soon as you get to the login.
I have read that this is caused because SmartThings looks at the build.prop, sees that this is a Samsung tablet, and then looks for the stock Samsung account management APKs.
First I tried changing the build.prop file. I rooted the device with Magisk. I then navigated to the /system folder and found the build.prop file. I opened it with a text editor. This thread https://forum.xda-developers.com/t/smartthings-crash-on-lineageos-with-samsung-tablet.4109423/ said to change
ro.product.brand=samsung to ro.product.brand=google
and
ro.product.manufacturer=samsung to ro.product.manufacturer=google
However, those exact lines don't exist in my build.prop. The closest I could find were ro.product.system.brand and ro.product.system.manufacturer. I assumed they were basically the same and changed those. When I saved the file, and opened it again, it had reverted back from google to samsung. So I copied the file to another folder and tried again. Saved the changes and they stay. However, if I copy back to /system, they revert to samsung. The only way I could get it to stick was to delete the original build.prop and THEN copy it back, but when I do that, and I reboot, the tablet hangs at the startup animation.
Clearly I am doing something wrong with changing the build.prop file. Can someone please explain this to me with step by step instructions?
I also saw this thread:
Getting Smartthings to work when you have debloated or used another rom
Hi, Just wanted to let you guys know how I got the Smartthings app to work on my S20 FE (Also my older Samsung devices) Some of the debloat guides/scripts remove either 1 or 2 packages required for Smartthings to work on Samsung devices. The...
forum.xda-developers.com
This says I just need to get
com.samsung.android.easysetup
com.samsung.android.beaconmanager
Installed and everything should work. I hunted down a couple APKs of those packages, but even after I installed them SmartThings refuses to load. Maybe I didn't have the correct version? Does anybody have a link to the exact files I should install to get this to work?
It seems like there are a couple of work arounds that will get me up an running again, but I can't seem to get anything to work. Please help!

Related

UK 1.2.0 Glow ONLY TFU Software Upgrade

After much debate I have decided to make my work public as a lot of people seem to want these features!
THIS IS AN ALPHA SOFTWARE! EXPECT BUGS!
THEREFORE IF YOU INSTALL, ITS YOUR CHOICE. I TAKE NO RESPONSIBILITY IF THINGS GO DOWN THE PAN!
To get this working well, I need you guys! The testers - the community!
TFU ROM UPGRADE PACK ALPHA 3
What is it?
This software pack will supply your STOCK UK nook with software 1.2.0 with the following features:
ROOT
BUSYBOX
ADB
A clean nook friendly interface
A custom kernel (Thanks guevor http://forum.xda-developers.com/showthread.php?t=1906507)
Multitouch
Browser, Email, PDF, News Feed, Lots of tools
A custom built video mod to improve multitouch speed, refresh rates, delay and general display performance
MORE (but I cant remember)
Follow this guide to backup your nook and find out everything you need to know about the process. Please do this BEFORE any other tinkering! Make sure you know what you are doing!
http://forum.xda-developers.com/showthread.php?t=1961835
How to Install
Make a CWM SD card:
http://forum.xda-developers.com/showthread.php?t=1360994
Flash my zip:
http://dl.dropbox.com/u/13673492/TFU_ALPHA3.zip
Reboot:
You now have everything you need to get started!
BUGS:
Cant install apps unless you use ADB or drop them into /data/app and install.
If some of the preinstalled apps don't work follow this procedure:
-Open nook color tools and disable/enable allow non-market apps.
-Use file explorer to browse to /data/app and click on and install the broken app.
If you need help with ADB or want a different way to root check out my other post here!
http://forum.xda-developers.com/showthread.php?t=1961835
If you find a bug let me know please!
RESERVED
Hi Loney,
Installed just now and all seems well so far - well done!
John
I'd like to suggest an addition to the backup method that many folks are using - always test your restore, but dont test it (the first time) on your device.
Your backup file should be about 2 gig.
find a 2 gig or larger flash drive or sdcard and restore your backup image to that drive.
when you're done, there should be 8 partitions, as there were on your Nook to begin with.
If you can't get that working - you're not ready to root yet. Until you're sure you can restore, don't start making changes, please.
People turn up all the time having screwed themselves over by restoring a partial backup and not knowing it, or having restored only one partition from a complete backup and having blown out the partition table.
Out of curiosity is this listed as Glow only just because that was all you had to test it on?
I have the non-glow version so was going to test it, is there any reason why this may be a bad idea or has anyone else tried this yet? Thanks
stelph said:
Out of curiosity is this listed as Glow only just because that was all you had to test it on?
I have the non-glow version so was going to test it, is there any reason why this may be a bad idea or has anyone else tried this yet? Thanks
Click to expand...
Click to collapse
You are spot on. I didn't want to cause problems for people. Is your firmware 1.2.0? its firmware differences which are most likely to cause a problem. If you have a good backup, give it a go. If it works great. If not, you could try sending me your framework.jar file and I can try and find out what the differences are. Good luck!
roustabout said:
I'd like to suggest an addition to the backup method that many folks are using - always test your restore, but dont test it (the first time) on your device.
Your backup file should be about 2 gig.
find a 2 gig or larger flash drive or sdcard and restore your backup image to that drive.
when you're done, there should be 8 partitions, as there were on your Nook to begin with.
If you can't get that working - you're not ready to root yet. Until you're sure you can restore, don't start making changes, please.
People turn up all the time having screwed themselves over by restoring a partial backup and not knowing it, or having restored only one partition from a complete backup and having blown out the partition table.
Click to expand...
Click to collapse
Thanks for posting this. Very useful for people who aren't familiar with the nook. I will mention your name and this post when I update my guide with this information.
Also, the US nook touches - both the NST and NSTG - are now going to be running under OS 1.2.0 per BN.
The BN support announcement on this is here:
http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175
Hopefully, we'll wind up with net fewer folks quasi bricking their devices.
roustabout said:
Also, the US nook touches - both the NST and NSTG - are now going to be running under OS 1.2.0 per BN.
The BN support announcement on this is here:
http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175
Hopefully, we'll wind up with net fewer folks quasi bricking their devices.
Click to expand...
Click to collapse
This is great news. Everyone will benefit from some constancy across all devices.
Thanks, yes my nook is 1.2.0 so I've now installed the ROM on my non-glow light and it looks like it works fine! Seems stable and could start using it straight away, the only fault was opera wouldn't load/didint install properly but I followed the guide and re-installed it and it now works
I think the simple layout is really great, although one question, I plan to add the kindle app. Will I be able to add it to the "book" symbol (ie when I press the reading book it'd be nice to get an option of barnes&noble or kindle)? Im sure there is probably a legal reason why it hasnt but i think a kindle app would be good to include as standard, since kindle is one of the most popular ebook services and I bet most people have some books they'd want to access
Great work on the ROM!
stelph said:
Thanks, yes my nook is 1.2.0 so I've now installed the ROM on my non-glow light and it looks like it works fine! Seems stable and could start using it straight away, the only fault was opera wouldn't load/didint install properly but I followed the guide and re-installed it and it now works
I think the simple layout is really great, although one question, I plan to add the kindle app. Will I be able to add it to the "book" symbol (ie when I press the reading book it'd be nice to get an option of barnes&noble or kindle)? Im sure there is probably a legal reason why it hasnt but i think a kindle app would be good to include as standard, since kindle is one of the most popular ebook services and I bet most people have some books they'd want to access
Great work on the ROM!
Click to expand...
Click to collapse
In my next update you will be able to customise the launcher as you like. The fact that you cant is a bug that can be fixed by clearing the launcher data using the included titanium backup program.
Since i'm back from the hell of the "bricked nook", now i can come back to test your mod with more understanding.
It seems that if we change the language to all but english, the installation of the mod is doomed to a blank launcher. (that was the case for registering the nook i have to do it in english).
I reflash my nook after setting it in english and that correctly installs everything (not Opera but that's easy to recover it).
may be a note for foreigners who try to install this mod is to be aware of keeping the nook in shakespeare's mother tongue.
would you mind integrating in your future version the manga reader "perfect viewer"? fastmode.apk is also a request but now i understand that is not so easy.
thanks for your contribution. :highfive:
I'll report my experience using this technique. A few days ago, I purchased a US Nook Simple Touch (non-glow) which came with software v.1.0. I made a backup using the method referenced in the OP. I then upgraded to software v.1.2 via the manual (USB mode) method shown at http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175/ . I made another backup. I verified both backups using the SD card method as suggested by roustabout. Everything looked good.
I followed the OP instructions and was successful in installing TFU_ALPHA3.zip with CWM.
Upon reboot of the NST, I saw a dialog chooser asking me to select either the standard Nook software or Launcher7. I first tried Launcher7 and was greeted with a large gray "n" background. Nothing else. The only button that had functionality was the "n" button which brought up the "home" menu at the bottom of the screen. This got me back to the standard Nook software. So at least the reader still worked.
I rebooted and tried Launcher7 again, just to be sure. Still nothing but the large gray "n" background. No apps.
I restored my v.1.2 backup without any problems, and am now back to a "stock" NST. All good.
So while the TFU_ALPHA3.zip installation proceeded without incident, I didn't see any apps that I could run from Launcher7. I guess I'll have to try a different technique.
it seems like the same problem i said in my previous topic. did you set your language to anything but english?
i had the launcher7 without anything loaded. I had to set the language in english then reinstall the TFUAlpha3 to make it work correctly.
hope it helps.
jjinkou2 said:
it seems like the same problem i said in my previous topic. did you set your language to anything but english?
Click to expand...
Click to collapse
I have the US version of the NST. I couldn't find any way to change the language in the settings.
fastmode is working but we have to set it manually. i read this here http://forum.xda-developers.com/showthread.php?t=1241419, and i tested it.
Code:
adb shell
# cd /sys/class/graphics/fb0/
# echo -n 1 > fmode
# echo -n 0 > pgflip_refresh
since no-refresh and fastmode are autoexclusive i set pgflip_refresh to 0.
values are lost when the nook reboots.
New version coming soon. Lets start a list of requests guys. And if anyone has tested custom graphics settings, what works for you?
Loney,
Things that aren't working for me:
* Launcher 7 settings can't be altered (changes don't "save")
* apk installs are hitty-missy. Sometimes moving an apk into /data/apps and rebooting will work, other times I need to install it again by clicking on it in a file explorer.
* Fast mode app does nothing (but we knew that...)
Other than that, all is cool. I have also installed the patched .jars from the "mod manager" thread and they work alongside your changes.
Well done for your efforts on our behalf. Shout if you want anything specific testing - I'm confident that I can recover from "bricking"!
John
loney01843 said:
New version coming soon. Lets start a list of requests guys.
Click to expand...
Click to collapse
I haven't tried this yet, but when I do I would imagine access to google markets would be needed.
A follow-up on my experience which may (or may not) help getting this to work with the US NST (non-glow). Yesterday, I decided to give GlowNooter (http://forum.xda-developers.com/showthread.php?t=1675706) a try. Suspecting that it wouldn't work out-of-the-box, I deleted /system/framework/framework.jar from the glownooter.zip file. Installation of the .zip succeeded, and I was able to run ADW Launcher. I added my account to YouTube, attempted to sync in GMail, rebooted, and installed the PART-2-END.zip. Then I tried to open up Market, but kept getting connection errors. I also tried the Browser app, but was unable to enter text into Google's search page. So I guess there is stuff in glownooter's framework.jar file that is needed for everything to work. I didn't try too much more.
Anyway, I reverted to the stock NST 1.2 software for now. But I am happy to help with testing new firmware since I'm pretty confident about restoring to stock software.

Remove Phone Setup - During Phone boot

Hi All,
Can anyone help me figure out the APK files to be removed in order to bypass the phone setup when I boot the phone for First time.
I do not want to enter the First Name, Last Name or add WiFi during the first boot of the phone.
In few Samsung phones I found there is a APK file called 'GooglePartnerSetup.apk' but I am not sure what it does. (Not sure if it's relevant in Nexus)
Any help will be highly appreciated.
On the WELCOME screen, try clicking the screen corners in this order: left-up, right-up, right-down, left-down. This should skip the setup process.
Or, if you insist on removing that APK altogether, look for a file named "SetupWizard.apk".
Sent from Lenovo Erazer Z500 @ Android-x86 4.3

AirDroid on AFTV Stick?

Is anyone able to get sideload AirDroid onto there Amazon FireTV Stick (non-rooted)? I always get DEXOPT error or something like that during the actual install process. From what little reading I did it looks like its due to android SDK version apk was made with and version SDK that is installed on fire stick or something.
Thanks,
~SG
SomeGuy2008 said:
Is anyone able to get sideload AirDroid onto there Amazon FireTV Stick (non-rooted)? I always get DEXOPT error or something like that during the actual install process. From what little reading I did it looks like its due to android SDK version apk was made with and version SDK that is installed on fire stick or something.
Thanks,
~SG
Click to expand...
Click to collapse
Have you tried pushing it to the sdcard and just installing it manually?
Side note-what are you trying to do? Push notifications and texts to the AFTV?
I mainly use it to view and control the screen of many of my android based devices as well as the camera in most of my android devices over the internet. Yes i have tried manually installing via adb command but always get the same error.
SomeGuy2008 said:
I mainly use it to view and control the screen of many of my android based devices as well as the camera in most of my android devices over the internet. Yes i have tried manually installing via adb command but always get the same error.
Click to expand...
Click to collapse
I just got it working... by downloading and sideloading the latest version in rev 3 (3.2.6) from here: airdroid(DOT)en(DOT)uptodown(DOT)com/android/old.
Out of the box, it works fine for transferring files through wifi (which can also be done with ES File Explroer easily). It also works as a keyboard input and screen mirror when USB connected to PC.
HOWEVER, there are several options for AirDriod that can only be enabled through the Firestick interface, and, at least for me, cannot actually be accessed (like it wants touchscreen input typically found on phones).
Overall, I'm missing the benefit of having it running in it's current state. ES File Explorer does file transfer fine. I can't really see the application of screen mirror and keyboard control when it must be plugged in to my pc. It's pretty useless in t's current form, imho.
Update: Also, since it's an outdated version, it will not work over the web portal.

Gear manager vs LineageOS

Hello I recently broke my newer phone and went back to my old Galaxy S3 and got Lineage android 7.1.2- Works perfectly BTW.
But I have this problem with Gear manager app. I can install it, but when I open the app - there is an error:
The Operating system on your device been modified in unauthorized way, andis not compatible with the Samsung Gear app.
Check your operating system and try again.
I tried cash wipe, restart.. But this error is still there.
I have read about some modded Gear manager, but could not find any reliably source.
Thank you for any information.

problem installing Aurora Store direct from Auroraoss.com

Hello all,
I'm trying to install the Aurora Store directly from https://auroraoss.com to my Samsung Galaxy Tab 3 (SM-T311) but I'm having some trouble with it.
Once the apk is downloaded I am unable to install it - I get the error message "Can't open file" - please see screenshots 1 and 2.
That's using the Android stock browser, but I tried with Firefox too and it gave the same error.
However, I am able to download the same version of Aurora store from an apk site like Apk Mirror and this will install ok - please see screenshot 3.
I am able to install an alternative equivalent App store e.g. Apptoide directly from their website without problem - see screenshot 4.
Finally, as shown in screenshot 5, the file downloaded from Auroraoss.com shows in File Manager as an unknown file type, but the same apk from an alternative source is recognised as an installable apk for Android, as shown by the icons displayed.
It seems to me that the file downloaded from Auroraoss.com is not triggering the Packet Installer (or being recognised by it), on this device for some reason.
I have already enabled/allowed installation of apps from unknown sources. But maybe I am missing something else, another setting??
Also FYI, my tablet is running Android Nougat 7.1.2 (Lineage OSS 14.1).
I tried running some other custom roms but got the same result.
Just to be clear: of course I know can install Aurora Store from alternate sources as I explained above, but I would much prefer and feel safer to download it direct from original source at Auroraoss.com. Apart from that it's just annoying and a little bit worrying that it mysteriously does not work for some strange weird reason.
Any ideas why this might be happening or what I can do to fix it?
Would appreciate any advice!
Cheers
Dave
cc: @gre8nole, @cuberio1, @tigger2014

Categories

Resources