Develop Bugs

7" Glanzix Tab (4.0.4)

I can not find any info on google at all for this other than places to buy.
It like it does not have a bootloader/recovery, i tried fastboot and button presses.
Its running Rk29sdk 4.0.4
tried to adb remount, no success, so i could not manually install su or superuser.apk
so im at loss now, it does have access thru adb, i run ubuntu , and have installed apks thru adb, i get a generic serial 0123456789ABCDEF for the device, any ideas?
it is a nice tablet, i like it better than the Craig 7" i rooted last week by simply copying the su and super file over. guess it was already unlocked.
Wondering if there is perhaps a custom loader.

i run adb reboot bootloader and the device shuts off.
I run adb rboot recovery and it will reboot into what looks like a default recovery. i can not see any text tho, just android laying down with ! in triangle. no fastboot access.

I am curious as to this as I'm getting one of these as well and can find nothing on it.

ya, i do find it odd that there is so little info about it, i thought compared to those craigs and polaroids people were getting, i think this one looks better for one. All glass with very tiny bezel like the xoom i got, def has a look that dont say $90 which is the total i paid shipping and all from amazon.
As far as rooting, i still didnt figure it out. i tried the psnueter, but im guessing that hole is fixed. also i started seeing people say 4.0.4 is unrootable, but i dont believe that. i think i have to trick it into temp root tho somehow so i can write to /system, that is all i need. I dont expect to find a custom flash for it anytime soon either. but i was thinking that all cheap 7" tablet were probably close to being the same. after messing with it as much as i did, im not so afraid of bricking devices now.
Im going to attempt some more on it right now, will post results

Well I'm starting to learn about ROM development so if I can get root the stock ROM can be pulled from it and tweaked from there. Not sure about getting to crazy with anything since I'm a huge n00b but at least tweak a few of the props and what not on it could be nice. Not much can be done without gaining root though. I'll know more once I get my hands on it later. I'm excited...I'm getting it thanks to a guy who meant to get Nex7 but this is what he got. Apparently the 7 was pictured...he can't send it back and he's sent feedback but wanted something to do with it and he gracefully donated it to me being a beginning developer. I've been playing with the stock GB ROM for my old phone (Galaxy S Mesmerize) and I'm going to start looking through AOKP's ICS ROM just to try and familiarize myself with ICS and eventually JB. Baby steps though...but let me know if you figure a hack for the tablet and I'll try some things tonight after work once I get the tablet.

I tried booting into a loader/recovery and haven't found a way or it just doesn't have it. ADB isn't even finding the device. Kind of lost now...looking into some alternative methods but not really sure with ICS. And I can't find anything on this tablet anywhere. Even at the glanzix.com site which apparently just sells it and other stuff.
Info from mine...just wanted to make sure we're working on the same thing.
Glanzix Tab
Model GL-7TA
System Rk29SDK
Android 4.0.4
Kernel 3.0.8+ [email protected] #67
Build rockchip IMM76D

McDaddyTree said:
I tried booting into a loader/recovery and haven't found a way or it just doesn't have it. ADB isn't even finding the device. Kind of lost now...looking into some alternative methods but not really sure with ICS. And I can't find anything on this tablet anywhere. Even at the glanzix.com site which apparently just sells it and other stuff.
Info from mine...just wanted to make sure we're working on the same thing.
Glanzix Tab
Model GL-7TA
System Rk29SDK
Android 4.0.4
Kernel 3.0.8+ [email protected] #67
Build rockchip IMM76D
Click to expand...
Click to collapse
yes it is the same one. still did not figure it out. it is weird there is no info on this thing. and like you said, its like it has no kind of recovery.

Yeah...still no luck yet here. I'm at a loss especially being a n00b.

Upgrading from JSS15Q to LMY48I

Hello all, I haven't been here for about 2 years, got busy with some things. I'm currently running a home compiled JSS15Q that has a touchscreen hack to load in the firmware that works best with my tablet. I'd like to build 5.1.1 LMY48I from source and give it a try. Do I need to upgrade any bootloaders or other stuff before attempting to push the new OS on there?
It's been 2 years since I did any of this stuff so I'm a bit foggy about it all. I had a good handle on it back then, but I've slept a lot since then. I might go with sfhub's locked in firmware this time since I was accomplishing pretty much the same thing just a different way. That's, of course, assuming that the old firmware is compatible with the newer releases of Android OS.
I built the older release in a VirtualBox VM running Ubuntu 12.04. I think I need to upgrade some things to be sure that the compile of 5.1.1 works as it should. I was about out of space on the 12.04 VM and I was going to grow the partition, but I'm thinking it might be smarter to just follow the build-from-source instructions from scratch in a new VM install. It takes a huge amount of space to do a build. AOSP took 20GB and JSS15Q took about 40GB of drive space. I "only" set up a 100GB VM which means I likely don't have enough room to download the newer release source.
If anyone that's done this has any advice, I'd sure appreciate hearing it. Thanks for reading.

Sounds like you already have it figured out.
There is a new bootloader so don't forget that. Sfhubs firmwares work fine.
I forget how big it was when I synced 5.1.1 but if you delete the jellybean code you should be fine.

LOL You're giving me wayyyy too much credit. I'm pretty much stumbling around in the dark here. I went with the new VM using Ubuntu 14.04. I struggled through all the apt-get commands especially the one with libgl1-mesa-glx:i386. It just didn't want to install because of some dependency quirk of some sort with something called cheese. I finally found a solution by doing this:
sudo apt-get install libglew-dev libcheese7 libcheese-gtk23 libclutter-gst-2.0-0 libcogl15 libclutter-gtk-1.0-0 libclutter-1.0-0 xserver-xorg-input-all
God only knows why I had to do all that to get the libgl-mesa-glx installed, but it finally let me do the get for libgl-mesa-glx:i386. Then I could finally create the symlink for the mesa library. After that, I successfully repo synced the source tree; it took up 35GB of disk space. I did the lunch command, picked flo user (11) and started my make command to build. That's running right now.
I was concerned about the proprietary binaries for the broadcomm stuff, but I found a directory under ./device/asus/flo called self-extractors. I'm guessing that stuff takes care of itself now and you don't have to do the steps of finding, downloading and extracting it into the tree. That's my guess anyway. I'm following this "howto":
http://source.android.com/source/requirements.html
I had been looking at an older one on blogspot, but it was for a different device and I figured it would be better to follow the one I'm using instead since it seems more current. I hope this build works okay and doesn't drag badly from bloat. I like my tablet's responsiveness on jellybean. I'm wondering now if I shouldn't have just gone to kitkat instead of all the way to lollipop. Oh well, live and learn. Thanks again for you input and for reading this. Let me know if I'm messing up.

I got it compiled. It took about 2.5 hours. I tried to find the program that I modified before, but I can't find it anywhere in the source tree. They've apparently moved everything around real good. If anyone knows where the touchscreen firmware update takes place, I'd appreciate knowing. It used to be in a program named ektf3k.c That program no longer exists in the build. I can use sfhub's utility to lock in the firmware I need, but I'd still like to know how where they moved the firmware update stuff.

afremont said:
I got it compiled. It took about 2.5 hours. I tried to find the program that I modified before, but I can't find it anywhere in the source tree. They've apparently moved everything around real good. If anyone knows where the touchscreen firmware update takes place, I'd appreciate knowing. It used to be in a program named ektf3k.c That program no longer exists in the build. I can use sfhub's utility to lock in the firmware I need, but I'd still like to know how where they moved the firmware update stuff.
Click to expand...
Click to collapse
I built the whole thing without the proprietary binaries installed. I'm guessing that my build is basically useless. I'm kinda disappointed that they don't bring up the binaries until after they walk you through the lengthy compile process. I guess I have to do a make clobber, unpack the binaries and then do the whole build over again. The build went fine as far as I can tell.
Can anyone verify if I have to do it all over with the binaries unpacked? I'm afraid to try flashing the stuff I built just to see what happens. Would there be any harm in that?

[test][rom]Anyone willing to do some ROM testing for this device?

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

No development progress :(

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

Question Reverting from GrapheneOS

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.