Related
Could anybody please show us how to install Microsoft Office Mobile on the Note PRO 12.2 LTE? I keep getting an error saying that the app cannot be installed since the device is not a phone.
petercohen said:
Could anybody please show us how to install Microsoft Office Mobile on the Note PRO 12.2 LTE? I keep getting an error saying that the app cannot be installed since the device is not a phone.
Click to expand...
Click to collapse
From what I've seen on the G+ community, you can install it but it will only function as a viewer on devices over 10". Because of that I have not bothered with it, but I will look and see what I can find out for you.
EDIT: It installed fine for me, but it does function only as a viewer with an Office 365 subscription. To install, I just opened the Google + app. Went to the Microsoft Office for Android Tablets group. You will need to join it if you haven't already. Once you have accessed the group, click the drop down on the header and follow the links in the instructions to become a tester and install the apps.
petercohen said:
Could anybody please show us how to install Microsoft Office Mobile on the Note PRO 12.2 LTE? I keep getting an error saying that the app cannot be installed since the device is not a phone.
Click to expand...
Click to collapse
I have read it somewhere that it is only for the tablet with a size of 7 inch to 10 inch. So you have to wait till ms comes up a new version for all kinda devices.
I just downloaded Word, Excel, and Powerpoint from the Play Store and it runs great on the Note Pro. I have a valid Office365 Subscription and I must say it's actually much better than the Hancom suite that's on the tablet.
tdetroit, can you save a file to the SD card with those programs? I'm having a heck of a time trying to save a file using hancon or office suite 8. Both of those can not save to the SD card because of kitKat. Office Suite doesn't even save back to Dropbox and once you open a file that was on a SD card it seems impossible to save it anywhere. Until this problem is fixed, we can never use this tablet for real work stuff.
treetopsranch said:
tdetroit, can you save a file to the SD card with those programs? I'm having a heck of a time trying to save a file using hancon or office suite 8. Both of those can not save to the SD card because of kitKat. Office Suite doesn't even save back to Dropbox and once you open a file that was on a SD card it seems impossible to save it anywhere. Until this problem is fixed, we can never use this tablet for real work stuff.
Click to expand...
Click to collapse
Sure you can. If you are rooted install xsposed and there is a module you can download and enable to allow full access to the ext sd. . The is also a guide here that can show you how to go into the build.prop and edit some stuff to fix. However i didnt have luck with that like others but the module works like a charm and i can save to external with all my apps on kit kat
I m xsposed download just search kit kat external and you should find it. .or kitkat sdcard
Thank you but I'm not rooted yet. Scared.
treetopsranch said:
Thank you but I'm not rooted yet. Scared.
Click to expand...
Click to collapse
Nah nothing to be scared of and only going to make it so much better
Zugshad said:
Nah nothing to be scared of and only going to make it so much better
Click to expand...
Click to collapse
Why not being scared of it?hehe sorry but have read some cases where it has bricked devices
Valholy said:
Why not being scared of it?hehe sorry but have read some cases where it has bricked devices
Click to expand...
Click to collapse
Important distinction... "some"....
Cautious is a better description.
Sent from my SM-P900 using Tapatalk
muzzy996 said:
Important distinction... "some"....
Cautious is a better description.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Would you mind giving some advice as I have the same model as you p900,have read some tutorials, some say you have to select files for the exact same compile version you have, others that its enough by selecting the model type, and have read that once you root you can start having blue screens.
You can be cautious and still brick this device. Still scared here.
Valholy said:
Would you mind giving some advice as I have the same model as you p900,have read some tutorials, some say you have to select files for the exact same compile version you have, others that its enough by selecting the model type, and have read that once you root you can start having blue screens.
Click to expand...
Click to collapse
It's been a year since I rooted and when I did so I just followed the CF-Autoroot thread to do it. I'd have to completely wipe my tablet and start from scratch to give a better guide than that. Whichever way you go, as long as you're following a root method that someone specifically wrote for your variant you should be fine.
Often where I've seen people get into trouble is flashing entire images of systems onto their devices that were meant for another variation of the device. In those cases if the system files are different it can cause instabilities and whats worse is if the partitions are different causing the device to soft brick.
When Lollipop comes out for the SM-P900 I'm guessing guides will get updated to reflect root methods more clearly for it. I'll likely full wipe my tablet at that point and try to document the process.
As for the blue screen issues, I can't say what's going on with that . . I've never seen it on my device. I've had random crashes when I didn't completely disable Knox but once I did that I was golden . .
muzzy996 said:
It's been a year since I rooted and when I did so I just followed the CF-Autoroot thread to do it. I'd have to completely wipe my tablet and start from scratch to give a better guide than that. Whichever way you go, as long as you're following a root method that someone specifically wrote for your variant you should be fine.
Often where I've seen people get into trouble is flashing entire images of systems onto their devices that were meant for another variation of the device. In those cases if the system files are different it can cause instabilities and whats worse is if the partitions are different causing the device to soft brick.
When Lollipop comes out for the SM-P900 I'm guessing guides will get updated to reflect root methods more clearly for it. I'll likely full wipe my tablet at that point and try to document the process.
As for the blue screen issues, I can't say what's going on with that . . I've never seen it on my device. I've had random crashes when I didn't completely disable Knox but once I did that I was golden . .
Click to expand...
Click to collapse
Got so much to research then about disabling knox and rooting,looking forward for your guide when lollipop comes out.
Hi folks. I'll start off with some disclaimers.
I'm not part of the Jide team or in any way affiliated with RemixOS other than that I was given permission to post an "easy install" package here.
I cannot fix bugs. If you want to tell me about bugs you are welcome to, but there's nothing I can do about them. This thread *may* be monitored by Jide team members, but I cannot guarantee timeliness nor thoroughness.
I am only here to support this thread in regard to "How To Install It". That said, I will try to assist anyone with any issues that I can. I can't fix bugs, but I can answer question and may be able to resolve some issues.
This process WILL WIPE your device, so be sure to back up any important files beforehand.
Now that all that's out of the way, let's get to it.
If you haven't heard about RemixOS, here's a little intro: http://www.jide.com/remixos
Remix is a different kind of Android experience.
The only way to install RemixOS at this moment is through fastboot. I took their firmware files and simplified "flash-all" batch script and packaged it alongside ADB and fastboot. If you already have ADB and fastboot, you can download the firmware directly from Jide and install just like always: http://www.jide.com/remixos/devices/nexus9
If you don't have ADB or fastboot, or just want to speed up your install process, keep reading.
You will need an UNLOCKED BOOTLOADER to do this. Unlocking your bootloader will wipe your device, but so will installing this ROM normally, so again be sure to back up important files. Click the spoiler button in the instructions below to see the additional steps for unlocking your bootloader.
Pre-install: Enable "OEM Unlocking" in Developer Settings. To do this: go to "About Tablet" in Settings. Tap "Build Number" seven times. You'll see a notification that you are now a developer, and now you'll have a "Developer Options section in Settings. Go into Developer Options and enable "OEM Unlocking" by flipping the toggle.
1. DOWNLOAD EASY INSTALL PACKAGE:
https://www.androidfilehost.com/?w=files&flid=92087
2. Unzip the package. Just the .zip file you downloaded, no need to unzip anything within the original .zip file.
3. Boot your Nexus 9 into bootloader mode. (power off tablet, hold "Volume Down" and "Power" buttons simultaneously for 4-5 seconds. You'll see a white screen with multicolor text if successful)
4. Connect tablet to PC via microUSB cable.
To unlock bootloader, if necessary:
A. Hold Shift and right-click within the unzipped folder containing ADB and fastboot tools, then click "Open a command window here". A command prompt will pop up.
B. Type
Code:
fastboot oem unlock
C. This will wipe your device and takes a few minutes. If it reboots afterwards, get back into bootloader mode to continue.
5. Double-click "flash-all.bat", the batch file within the folder you unzipped from the package.
6. Wait for a while. It takes a few minutes. Do not unplug the tablet or turn off your computer during this process. It will reboot automatically when complete.
Congratulations, you are now running RemixOS 3.0!
A few notes for modders:
I was able to root using CF Auto Root.
TWRP works fine for flashing some .zips, but remember this is a heavily modified AOSP so not all mods will work.
I have not tested Xposed.
Layers do NOT work.
If you install a custom recovery or modify /system you will not be able to install OTA updates, you will have to flash the entire package manually.
Awesome! Can't wait to try it. I just left remix because I couldn't stand to run a 5.1 base. But it was always fast and smooth!
Sent from my HTC 10 using XDA-Developers mobile app
Rather than this, a TWRP flashable version would be awesome.
dictionary said:
Rather than this, a TWRP flashable version would be awesome.
Click to expand...
Click to collapse
Make me one and I'll post it up.
Or use the method provided.
Your choice.
Sent from my XT1575 using Tapatalk
Runs beautifully and was a breeze to install! Thanks
Sent from my SM-N930T using XDA-Developers mobile app
how to get lte working?i really need this
mangomonkey00 said:
how to get lte working?i really need this
Click to expand...
Click to collapse
I am not sure it supports LTE. I only have a WiFi Nexus 9, and have no way to test it.
I'll ask @RemixOS_Jason to check on it for you.
I have been using it from when I got N9 from swappa. Tried other custom and stock ROMs. I keep coming back. Been the best so far. The last stock was dp5 haven't tried 7.0
We have the LTE one ready. I'll share in this thread the download link within 24-48 hours. Thanks!
borxnx said:
I am not sure it supports LTE. I only have a WiFi Nexus 9, and have no way to test it.
I'll ask @RemixOS_Jason to check on it for you.
Click to expand...
Click to collapse
RemixOS_Jason said:
We have the LTE one ready. I'll share in this thread the download link within 24-48 hours. Thanks!
Click to expand...
Click to collapse
its nice but i was able to get lte working on this after the whole installation had to manually flash vendor.img from latest google image
mangomonkey00 said:
its nice but i was able to get lte working on this after the whole installation had to manually flash vendor.img from latest google image
Click to expand...
Click to collapse
From latest Google image, as in from Nougat? Wouldn't any 6.0.1 vendor image work, so long as it was more recent than the ROM build?
RemixOS_Jason said:
We have the LTE one ready. I'll share in this thread the download link within 24-48 hours. Thanks!
Click to expand...
Click to collapse
Would love another update for WiFi version as well, but I have two questions.
1. Is there any way we can be given the choice of using our own launcher? It's really frustrating.
2. If we can't, can the option be added back to not have all apps on the home screen? It was present I believe in the previous build, but it's gone again. I could have two apps on the screen, and everything else in the app drawer. Prefer that.
Hey dictionary,
I talked to migration team and, as of my writing, there is no schedule for another update for the the Wi-Fi version.
1) Currently, Remix OS doesn't support other launchers.
2) Putting this feature back into Remix OS for N9's can be done if we gather enough feedback from the community for it. Personally, I totally get the reason you'd rather have clean desktop option, but we have limited resources here and I need for the feature to be asked by many users first.
Thanks and I do hope you understand. Btw, have you tried any of our other products (ie. Remix OS for PC or Remix OS Player?) They both have the clean desktop feature.
Thanks!
dictionary said:
Would love another update for WiFi version as well, but I have two questions.
1. Is there any way we can be given the choice of using our own launcher? It's really frustrating.
2. If we can't, can the option be added back to not have all apps on the home screen? It was present I believe in the previous build, but it's gone again. I could have two apps on the screen, and everything else in the app drawer. Prefer that.
Click to expand...
Click to collapse
RemixOS_Jason said:
Hey dictionary,
I talked to migration team and, as of my writing, there is no schedule for another update for the the Wi-Fi version.
1) Currently, Remix OS doesn't support other launchers.
2) Putting this feature back into Remix OS for N9's can be done if we gather enough feedback from the community for it. Personally, I totally get the reason you'd rather have clean desktop option, but we have limited resources here and I need for the feature to be asked by many users first.
Thanks and I do hope you understand. Btw, have you tried any of our other products (ie. Remix OS for PC or Remix OS Player?) They both have the clean desktop feature.
Thanks!
Click to expand...
Click to collapse
1) yeah, was just hoping they'd allow it.
2) I don't know why it'd be an issue, as it was there before. Shouldn't it be the same as remix for PC? I tried remix player, but it didn't run that great on my PC. I currently also run Remix for PC dual booting on my laptop. Runs great
You may want to try Remix OS Player again if you're still interested as we made some optimizations and now allow you to use all your CPU cores rather than leave at least one core for your host OS and PC.
http://www.jide.com/remixos-player#download
For tablets like N9, our product managers made a call that for touchscreen devices, there is minimal need for the Desktop mode since it's more intuitive for PC environments and keyboard and mouse input.
QUOTE=dictionary;68895033]1) yeah, was just hoping they'd allow it.
2) I don't know why it'd be an issue, as it was there before. Shouldn't it be the same as remix for PC? I tried remix player, but it didn't run that great on my PC. I currently also run Remix for PC dual booting on my laptop. Runs great[/QUOTE]
RemixOS_Jason said:
For tablets like N9, our product managers made a call that for touchscreen devices, there is minimal need for the Desktop mode since it's more intuitive for PC environments and keyboard and mouse input.
Click to expand...
Click to collapse
I would also like to have the option of using a clean desktop on my N9
Thank you for the great work, btw!
I used latest 6.0.1 vendor IMG as nougat factory image is not available for lte
RemixOS_Jason said:
You may want to try Remix OS Player again if you're still interested as we made some optimizations and now allow you to use all your CPU cores rather than leave at least one core for your host OS and PC.
http://www.jide.com/remixos-player#download
For tablets like N9, our product managers made a call that for touchscreen devices, there is minimal need for the Desktop mode since it's more intuitive for PC environments and keyboard and mouse input.
QUOTE=dictionary;68895033]1) yeah, was just hoping they'd allow it.
2) I don't know why it'd be an issue, as it was there before. Shouldn't it be the same as remix for PC? I tried remix player, but it didn't run that great on my PC. I currently also run Remix for PC dual booting on my laptop. Runs great
Click to expand...
Click to collapse
[/QUOTE]
I'll give player another shot later today.
No disrespect to the PM's, but I vehemently disagree. There is no easy way to sort them, and putting all things in folders isn't very aesthetically pleasing. I have well over 60 apps installed, and it's just a jumbled mess. I always run a clean desktop on my devices. I find it much more intuitive having all apps right by my thumb.
If they refuse to, that's fine. I'll try to find a way to just move the launcher and file manager from my Remix OS for PC over to the n9
@dictionary Your opinion is duly noted. I've definitely passed on your opinion to them as well as @KSS2016 's comment.
Let me know how Remix OS Player works out for you. Thanks.
Any word on the LTE easy install package?
Sent from my Nexus 9 using Tapatalk
I have this device, but right now I am unable to root and twrp it because of warranty but I really want to build a ROM for it and we have the sources so I really want to do it. Any beta testers would be frickin amazing.
So, building asteroids and syncing with latest sources and also trying to fix bluetooth is my main goal here.
First test build is complete! Link: [urlhttp://www.mediafire.com/?0c0xusva0z5e0[/url]
That is the link to a folder containing 2 files, an ext4 file and a fastboot file.
To flash it, make sure your bootloader is unlocked
This will only dual boot the software, because it is just a test and in case it'd mess anything up, it won't affect the watch.
Once you've downloaded the files and put them into your adb and fastboot folder, enable adb debugging (obviously huehuehue).
Once that is all done, don't switch off your watch, leave it in android wear and make sure that adb detects it (adb devices and it should say authorized next to it).
Run adb push -p /location/to/file/asteroid-image-tetra.ext4 /sdcard/linux/rootfs.ext4 (pushes the file to the virtual sdcard)
Once that is done, reboot to bootloader by running adb reboot bootloader.
Then, once you've sure made that fastboot recognizes it (fastboot devices), do fastboot boot /location/to/zImage-dtb-tetra.fastboot
If you want to try and overwrite your current android wear installation, do fastboot flash, however I don't recommend this.
Good luck! Oh, and as a sidenote, since this isn't android wear, the android wear app won't work and I am surprised that bluetooth even works (if it does, report it here!).
RAZERZDAHACKER said:
I have this device, but right now I am unable to root and twrp it because of warranty but I really want to build a ROM for it and we have the sources so I really want to do it. Any beta testers would be frickin amazing.
Please, either send me a pm or write here on this thread and I'll try to release a flashable zip asap
Click to expand...
Click to collapse
Hi
I'm always open for some beta testing. In what direction of development where you thinking? A themed stock, or something radical?
amunarjoh said:
Hi
I'm always open for some beta testing. In what direction of development where you thinking? A themed stock, or something radical?
Click to expand...
Click to collapse
Not themed stock, sure they're great for some people but I am not a huge fan of them so I will obviously not make one. Right now I am compiling resurrection remix for my phone but I might try later on and get a compiled version
RAZERZDAHACKER said:
I have this device, but right now I am unable to root and twrp it because of warranty but I really want to build a ROM for it and we have the sources so I really want to do it. Any beta testers would be frickin amazing.
Please, either send me a pm or write here on this thread and I'll try to release a flashable zip asap
Click to expand...
Click to collapse
I am willing to be a beta tester
Alright, stay tuned. Building rom right now, also getting instructions for how to flash it (I don't think it is a simple twrp flash, not sure, we need some tester to confirm that).
RAZERZDAHACKER said:
Not themed stock, sure they're great for some people but I am not a huge fan of them so I will obviously not make one. Right now I am compiling resurrection remix for my phone but I might try later on and get a compiled version
Click to expand...
Click to collapse
That sounds interesting. Looking forward to further development
Build finished after a couple of hours. Since I am new to this whole android wear thing, I am a bit confused as to which files to flash, but I assume it is the one that is the largest and has the correct file format, right? So here is where the beta tester thingy comes into place. I am still experimenting on flashing the rom (the flashing method can be a bit confusing for new people) so I am planning on coding a toolkit that does all of that for ya, but the main thing is that I use linux and I don't really have a windows machine available to test this and quickly be able to change some things in the code (or either the rom files and then pack em up) so if someone is willing to perhaps skype or something similar where they can test such things that would be amazing, since I don't believe that a lot of people are running linux and want to flash this particular rom for this particular device etc.
Enough ranting! Here comes the rom link! http://www.mediafire.com/?0c0xusva0z5e0
That is the link to a folder containing 2 files, an ext4 file and a fastboot file.
To flash it, make sure your bootloader is unlocked
This will only dual boot the software, because it is just a test and in case it'd mess anything up, it won't affect the watch.
Once you've downloaded the files and put them into your adb and fastboot folder, enable adb debugging (obviously huehuehue).
Once that is all done, don't switch off your watch, leave it in android wear and make sure that adb detects it (adb devices and it should say authorized next to it).
Run adb push -p /location/to/file/rootfs.ext4 /sdcard/linux/rootfs.ext4
Once that is done, reboot to bootloader by running adb reboot bootloader.
Then, once you've sure made that fastboot recognizes it (fastboot devices), do fastboot boot /location/to/file.fastboot.
If you want to try and overwrite your current android wear installation, do fastboot flash, however I don't recommend this.
Good luck! Oh, and as a sidenote, since this isn't android wear, the android wear app won't work and I am surprised that bluetooth even works (if it does, report it here!).
Doesn't boot for me get stuck at the Smartwatch 3 screen then reboots in to wear.
niai_mack said:
Doesn't boot for me get stuck at the Smartwatch 3 screen then reboots in to wear.
Click to expand...
Click to collapse
Thanks for trying, and you followed the instructions here I assume. I'll try to compile a new one today (I got some interesting warnings when compiling)
Aye I followed to the tea, put it in /sdcard/linux/ with the name rootfs.ext4 then booted with the supplied fastboot file.
You do know there's the official release from the dev of Asteroid OS that works without any issues (meaning it boots and functions as expected, minus the bugs), right? In case you didn't, here it is: https://asteroidos.org/install/
I get that you're trying to do something new, and I'm all for it. I'm just posting this here, in case anyone else was curious. It's been out for quite a while now, almost a year by my reckoning.
Bluetooth does not work though, blame Broadcom.
Some extra info. When you fastboot boot the kernel from Asteroid OS, it loads the system that you earlier pushed to your internal memory using adb. You can run the (barebones) OS till your next reboot. Once you reboot, you'll be taken back to Android Wear itself, and you have to reflash the kernel to go back to Asteroid.
niai_mack said:
Aye I followed to the tea, put it in /sdcard/linux/ with the name rootfs.ext4 then booted with the supplied fastboot file.
Click to expand...
Click to collapse
Can you perhaps try "adb push -p /location/to/file/rootfs.ext4 /sdcard/linux/rootfs.ext2" ? Thanks.
I can test as well
d_crossfader said:
I can test as well
Click to expand...
Click to collapse
Sweet, I assume you pretty much know what to do. Can you also test the above mentioned flashing method? So you're replacing the vritual sdcard with ext2 instead of 4.
drakonizer said:
You do know there's the official release from the dev of Asteroid OS that works without any issues (meaning it boots and functions as expected, minus the bugs), right? In case you didn't, here it is: https://asteroidos.org/install/
I get that you're trying to do something new, and I'm all for it. I'm just posting this here, in case anyone else was curious. It's been out for quite a while now, almost a year by my reckoning.
Bluetooth does not work though, blame Broadcom.
Some extra info. When you fastboot boot the kernel from Asteroid OS, it loads the system that you earlier pushed to your internal memory using adb. You can run the (barebones) OS till your next reboot. Once you reboot, you'll be taken back to Android Wear itself, and you have to reflash the kernel to go back to Asteroid.
Click to expand...
Click to collapse
Missed your reply. Correct, and I am aware of that. Just that I want to get into android wear development so I decided to build this from source and perhaps eliminate the bluetooth thing and maybe even have it as a permanent rom instead of android wear, just saying. It'd be pretty cool, though not the most practical thing ever.
RAZERZDAHACKER said:
Missed your reply. Correct, and I am aware of that. Just that I want to get into android wear development so I decided to build this from source and perhaps eliminate the bluetooth thing and maybe even have it as a permanent rom instead of android wear, just saying. It'd be pretty cool, though not the most practical thing ever.
Click to expand...
Click to collapse
Having it permanent is easy. All you'd have to do is fastboot flash the kernel as opposed to fastboot boot.
The Bluetooth thing is almost impossible to fix, it's due to the blobs from bcm. Unless you're proficient at reverse engineering complex code, it's pretty hard.
drakonizer said:
Having it permanent is easy. All you'd have to do is fastboot flash the kernel as opposed to fastboot boot.
The Bluetooth thing is almost impossible to fix, it's due to the blobs from bcm. Unless you're proficient at reverse engineering complex code, it's pretty hard.
Click to expand...
Click to collapse
I can always try :/
RAZERZDAHACKER said:
Sweet, I assume you pretty much know what to do. Can you also test the above mentioned flashing method? So you're replacing the vritual sdcard with ext2 instead of 4.
Click to expand...
Click to collapse
I can do the steps on the first page, not sure about replacing the virtual sd though
d_crossfader said:
I can do the steps on the first page, not sure about replacing the virtual sd though
Click to expand...
Click to collapse
What you're doing on the first page is basically moving the files and flashing them from the virtual sd card so all I ask is if it doesn't work to change the last number in the adb command from a 4 to a 2
RAZERZDAHACKER said:
What you're doing on the first page is basically moving the files and flashing them from the virtual sd card so all I ask is if it doesn't work to change the last number in the adb command from a 4 to a 2
Click to expand...
Click to collapse
cool, will try in a few
It's kinda sad to see the forum for the Duo not really progressing even with a device with an unlocked bootloader.
This device is amazing , it sucks to see it not getting much love from the dev community
I was thinking the same. I'm sure making the dual screens function as they should might be offsetting.
josh_zombie said:
I was thinking the same. I'm sure making the dual screens function as they should might be offsetting.
Click to expand...
Click to collapse
Android 11 supports multi screens out the gate from what ive heard.
Im also hoping someone just makes an optimized deodex stock rom. the ram management isnt great :\
you can try GSI in the meantime
GSI?
also i noticed this was a dead forum. ppl are on the reddit. but im wondering if ppl just waiting on the Android 11 release then hustling on that. ALSO a lot of BS bad press from APPLE funded mainstream reviewers....so i mean..... i really get annoyed with my device SOMETIMES but MOST of the time....im loving it....and its a HUGE head turner and convo starter....its a great device
Same and same. Was really looking forward to that speaker mod.
After having to use an iPhone as a work issued device for the last 10 years, and being an Android person since the first Droid arrived way back when, 2 weeks ago I bought this device. I LOVE IT!!! I am now loving reading my ebooks, could never find a device I liked to read them on. I have literally 10 years of books to catch up on. The form and function of this device is far more advanced than the iPhone XR I was using. Yeah the camera leaves something to be desired, but it makes up for it in form and function. I don't need a great camera, what I need is a flexible device that allows me to integrate my work and home life balance. The 2 screens and being able to do more things at once is awesome. I am really hoping development takes off for this device.
darkherman said:
you can try GSI in the meantime
Click to expand...
Click to collapse
Have you tried any of the gsi roms yet? I've been thinking if it too.
This device was released first in the USA. I believe now that other countries are starting to get this device. I believe we will see a lot of development for this device. Remember android 11 and 12 were designed for dual and non dual screens. More to come guys. Im actually interested in learning linux. I heard it just commands.
none24 said:
It's kinda sad to see the forum for the Duo not really progressing even with a device with an unlocked bootloader.
This device is amazing , it sucks to see it not getting much love from the dev community
Click to expand...
Click to collapse
They are baking the multi-screen features into Android 11. Any custom development now requires incorporating all that stuff into a ROM (which means ripping it from an existing ROM, figuring out how it all works and then porting it to AOSP, maybe a piece of cake, maybe a nightmare) whereas in theory the AOSP 11 source will allow us to just build as-is and get at least minimal dual-screen support without having to do a bunch of extra work.
Microsoft has some decent documentation up for the Duo already but it's Microsoft's first Android device, there is a lot of work to be done.
renegadeone8 said:
They are baking the multi-screen features into Android 11. Any custom development now requires incorporating all that stuff into a ROM (which means ripping it from an existing ROM, figuring out how it all works and then porting it to AOSP, maybe a piece of cake, maybe a nightmare) whereas in theory the AOSP 11 source will allow us to just build as-is and get at least minimal dual-screen support without having to do a bunch of extra work.
Microsoft has some decent documentation up for the Duo already but it's Microsoft's first Android device, there is a lot of work to be done.
Click to expand...
Click to collapse
Yeah, I agree. It's a lot of work and you have to find the software changes that they made inside the system image. I managed to get the system images separate from the OTA files, but I'm stuck on extracting the data from the system image. Microsoft used a different file type than other developers, but once we can access the data from system images, we'll be one step closer to ROM development!
JengaMasterG said:
Yeah, I agree. It's a lot of work and you have to find the software changes that they made inside the system image. I managed to get the system images separate from the OTA files, but I'm stuck on extracting the data from the system image. Microsoft used a different file type than other developers, but once we can access the data from system images, we'll be one step closer to ROM development!
Click to expand...
Click to collapse
I'm looking forward to it!
This is one device with tons of potential screaming for development. I would buy it just for the things a rooted Duo could do!
We already have gCam.
What I need as a rich DeX like desktop mode where I can plug in my dock and connect to multiple monitors and work like I do with my regular Surface.
Then minute that happens I'm grabbing one ASAP.
System and Vendor Files Extracted for Build 2021.817.35 (and for future builds):
[Resource] System and Vendor Files for Surface Duo & How-To Guide
Extracted System and Vendor Files Please use these files for your correct system version only! I am not liable for any system crashes or errors. This is only a resource for development purposes. Access Extracted Files (GitHub): Access System...
forum.xda-developers.com
This is awesome!
Also Microsoft recently announced Android 12L support next year.
Google's Android 12L update coming soon to support Surface Duo 2 and other large screen devices - OnMSFT.com
Google is planning a feature for its latest Android 12 operating system large enough to warrant a name change dubbed Android 12L that will give tablets,
www.onmsft.com
Hopefully it'll be both Duos getting the update to 12L
Would someone be willing to test my TWRP boot image? My Duo is bricked and I can't flash any files to the system anymore :/
This is the software you need to be on: 2021.913.25. If you can, you can dm me or reply here!
I'm on 2021.913.27 unfortunately, and I have another duo thats been off for a few months if that will help at all.
Im already 2400 in the hole and moved on to the iPhone 13mini so I'm happy to help test if it can get this device a few steps closer to functional.
kmccall said:
I'm on 2021.913.27 unfortunately, and I have another duo thats been off for a few months if that will help at all.
Im already 2400 in the hole and moved on to the iPhone 13mini so I'm happy to help test if it can get this device a few steps closer to functional.
Click to expand...
Click to collapse
The phone doesn't power on anymore? If you can send me the 2021.913.27 zip file that's used to restore your phone, I can make a TWRP image you can test.
JengaMasterG said:
The phone doesn't power on anymore? If you can send me the 2021.913.27 zip file that's used to restore your phone, I can make a TWRP image you can test.
Click to expand...
Click to collapse
you misunderstand so heres the full story you can skip if you want
I purchased 2 Duos with my partner. He stopped using his after a short while and some mild water damage and I stopped using mine after cracking it. The insurance process with Asurion was such a pain in the ass that I never got either repaired but both still boot and operate completely fine. I just hate them.
I would like to hate the phones I spent so much money on a lot less and am willing to even accidently brick them in the process but haven't done more than rooting and TWRPing samsung and OnePlus phones. but I work in robotics so it can't be too outside my depth to assist with.
Click to expand...
Click to collapse
TLDR: I have two beatup Duo phones that boot and run perfectly. I am happy to help flash and mess around with them.
[[ If you can send me the 2021.913.27 zip file that's used to restore your phone ]]
Where would I find this file? Or is there a way to get non rooted phones to spit out their updater files?
kmccall said:
you misunderstand so heres the full story you can skip if you want
TLDR: I have two beatup Duo phones that boot and run perfectly. I am happy to help flash and mess around with them.
[[ If you can send me the 2021.913.27 zip file that's used to restore your phone ]]
Where would I find this file? Or is there a way to get non rooted phones to spit out their updater files?
Click to expand...
Click to collapse
Oh gotcha. You can find how to get it here:
Surface Recovery Image Download - Microsoft Support
support.microsoft.com
You can send me the zip file. I'll get the resources from it and send you a boot image to boot from fastboot. If the phone successfully boots, we have TWRP. If not, it's back to the drawing board.
JengaMasterG said:
Oh gotcha. You can find how to get it here:
Surface Recovery Image Download - Microsoft Support
support.microsoft.com
You can send me the zip file. I'll get the resources from it and send you a boot image to boot from fastboot. If the phone successfully boots, we have TWRP. If not, it's back to the drawing board.
Click to expand...
Click to collapse
And if it bricks, I'll somehow still be satisfied. I'll get back to you this evening.
Just started my shift
I tried GrapheneOS and it's ok but too many compromises I have to make with several apps I'm using not working and small issues here and there.
Has anybody ever used Android Flash Tool to revert back from GrapheneOS to stock? If so, any issues?
Yeah plenty of times, no issues. Download firmware, extract it then flash-all in CMD
Thanks. No need to download FW or for CMD there, flashing is web based: https://flash.android.com/
Worked flawless.
sabai27 said:
Thanks. No need to download FW or for CMD there, flashing is web based: https://flash.android.com/
Worked flawless.
Click to expand...
Click to collapse
Can't wait to see more devs implement this system. My laptop is borked so it's really cool seeing such a simple alternative emerge
I've been thinking of using GrapheneOS for a bit. What was some stuff that didn't work for you?
Opensystem said:
Can't wait to see more devs implement this system. My laptop is borked so it's really cool seeing such a simple alternative emerge
Click to expand...
Click to collapse
I would definitely love to see this with other manufacturers. I got a Windows ARM laptop that has become unresponsive in BIOS, meaning I can't tell the system to install a new Windows version via the Boot menu. Such a tool would save that device. It should be mandatory to offer decent web flashing tools.
asj0422 said:
I've been thinking of using GrapheneOS for a bit. What was some stuff that didn't work for you?
Click to expand...
Click to collapse
Most things work with Sandboxed Google Play. But a few things don't like Android Auto, Google Pay and Chromecast. But other than that, I haven't had anything not work. They are close to getting Android Auto to work if I remember correctly - and Google Games ( I don't use either but looks like release is imminent). Check the other GrapheneOS threads on here or you can message me if you have any specific questions.
One thing I recommend though, is to leave "oem unlocking" enabled on the device after locking your bootloader. that way if something goes wrong, you can flash factory image. You don't want to brick your new phone. (I always leave my bootloader completely unlocked but that's a personal preference and I know the risks).
In other words, only a bunch of proprietary closed source gooble spyware crap doesn't work. The best thing about going to graphene or other security minded distributions of AOSP, is specifically *to* eradicate all of that.
It can be difficult initially, to clear yourself of all the gooble spyware, but its worth it and you don't even notice it after you get used to it. You're just much more safe and secure.