[ROM] [13.0] [Dragon] ArrowOS 13.0 [UNOFFICIAL]

Search This thread

tabormeister

Senior Member
Recently got myself the keyboard (hard to resist at 20$!) and I'm also having pairing issues. Initial setup isn't a problem and it connects right away afterwards, but it stops working after the device is turns off for a while. Now, in all honesty, I'm fine removing/repairing it every time, but it would obviously be even better if it would just work as intented! 🙂
Mine did that at first and now works every time. *Shrug*
 

thebaz67

New member
Nov 19, 2010
3
0
I have run into what is a minor issue but I wanted to check and see if I am the only one having this issue. When I try to enable Smart Lock to use a Trusted device it is not listed as an option, I only show on body detection and Trusted places. This is not vital but I figured if I don't ask I certainly will not find out.
 
Last edited:

michie

Senior Member
Apr 15, 2007
1,549
2,549
Hasselt
Guys, Followmsi asked me to take over the lineage builds. Unfortunatly I don't have enough space on my disk to maintain more than 1 rom. Each one is about 400Gb.

Arrow is faster to release a major Android version so it's possible that it will be the first Android 14 build before stable LineageOS 21.

For now I have to drop ArrowOS, sorry for any inconvenience :)
 

tabormeister

Senior Member
Guys, Followmsi asked me to take over the lineage builds. Unfortunatly I don't have enough space on my disk to maintain more than 1 rom. Each one is about 400Gb.

Arrow is faster to release a major Android version so it's possible that it will be the first Android 14 build before stable LineageOS 21.

For now I have to drop ArrowOS, sorry for any inconvenience :)
Do you need more storage? I have oodles of disks laying around I could ship you if you're in the US, or I'm sure we can scrape some dough together if you need an upgrade :) 2TB SSDs are even pretty cheap lately. (Obviously whatever is best for you)
 

pat_wild

Member
Jul 29, 2022
31
13
Guys, Followmsi asked me to take over the lineage builds. Unfortunatly I don't have enough space on my disk to maintain more than 1 rom. Each one is about 400Gb.

Arrow is faster to release a major Android version so it's possible that it will be the first Android 14 build before stable LineageOS 21.

For now I have to drop ArrowOS, sorry for any inconvenience :)

That is very unfortunate (for us, on Arrow) but I fully understand that you also probably have limited time to dedicate to these projects! After all, we all have to pay the bills! 😉

So, since I'm not necessarily pro one ROM versus another, I have to ask: do you foresee Lineage's will (or already is) perform well as Arrow does? The main reason I moved to Arrow was because of it's speed compared to other offerings. Knowing at Lineage will now get your full attention (and magic touch), just wondering if I should jump ship as well! 🙂
 
  • Like
Reactions: tabormeister

michie

Senior Member
Apr 15, 2007
1,549
2,549
Hasselt
Thank you for your offer but It's ok. The public for Arrow or PE is relatively small compared to Lineage so I guess this is the way to go?

Let's see what the future brings.
 

michie

Senior Member
Apr 15, 2007
1,549
2,549
Hasselt
That is very unfortunate (for us, on Arrow) but I fully understand that you also probably have limited time to dedicate to these projects! After all, we all have to pay the bills! 😉

So, since I'm not necessarily pro one ROM versus another, I have to ask: do you foresee Lineage's will (or already is) perform well as Arrow does? The main reason I moved to Arrow was because of it's speed compared to other offerings. Knowing at Lineage will now get your full attention (and magic touch), just wondering if I should jump ship as well! 🙂

I'm using all my optimizations on Lineage as well so the system runs just as smooth and you will have alot more customization options.

The only difference right now is boot time. After the first boot and signing in to your google account, every reboot seems tot take some time at the end of the boot animation.

Not really a big issue but it annoys me lol. Could be some lineage bug. From a user perspective this shouldnt really matter.

Please do let me know if you feel any difference in performance because if there is, I will certainly keep providing Arrow builds one way or another.
 

TheNicholasNick

New member
Dec 27, 2022
4
4
Check your 5g wireless channels! Might be using an EU pixel C and need to change the wifi country code to US, EU pixel C is set to eu wifi so won't work with some 5g channels out of the box
Yeah it was was this.
I have a US Dragon, was fine on the Military/DFS WiFi 5G channels with LineageOS. Have changed my router setup and now back on 5G WiFi.

I wasn’t able to figure out how to change ArrowOS to US WiFi…
 
  • Like
Reactions: tabormeister

michie

Senior Member
Apr 15, 2007
1,549
2,549
Hasselt
Yeah it was was this.
I have a US Dragon, was fine on the Military/DFS WiFi 5G channels with LineageOS. Have changed my router setup and now back on 5G WiFi.

I wasn’t able to figure out how to change ArrowOS to US WiFi…
Actually I threw the setting out because it was giving trouble building Android 13. Is it an important feature? I can work on it to bring it back?
 

locuturus

Senior Member
There is/was a build.prop option to manually enable WiFi bands -- "ro.wifi.channels" but the last time I needed to use that was back when the Pixel C was still officially supported and I was traveling. Google offered no way to officially change WiFi bands for a WiFi only tablet back then (maybe still?).
 

tabormeister

Senior Member
Actually I threw the setting out because it was giving trouble building Android 13. Is it an important feature? I can work on it to bring it back?
It seems to have stuck through factory resets? You had it in pixel experience and it worked. I have an EU pixel C in US so it's nice to have for me. If there's something that can be edited in build.prop then maybe we can just enable all of them? Idk if that's possible
 

locuturus

Senior Member
It seems to have stuck through factory resets? You had it in pixel experience and it worked. I have an EU pixel C in US so it's nice to have for me. If there's something that can be edited in build.prop then maybe we can just enable all of them? Idk if that's possible
You shouldn't enable all of them because the FCC takes that pretty seriously. I recommend you only enable the channels allowed for use in the country you are in.
 
  • Like
Reactions: tabormeister

locuturus

Senior Member
Very good point. Although wouldn't that only matter for broadcasting, like in the case of a router? Client device wouldn't be broadcasting additional frequencies
Without doing more research I'm not super confident about power levels and actual risk of discovery but any WiFi device obviously does broadcast as part of an active connection... but yes as long as the router is in compliance the client shouldn't cause any problems. What might get you though is whenever your tablet is looking for available connections it might broadcast network requests on the forbidden frequencies.
 

scottrix

Senior Member
Jul 19, 2012
53
23
Guys, Followmsi asked me to take over the lineage builds. Unfortunatly I don't have enough space on my disk to maintain more than 1 rom. Each one is about 400Gb.

Arrow is faster to release a major Android version so it's possible that it will be the first Android 14 build before stable LineageOS 21.

For now I have to drop ArrowOS, sorry for any inconvenience :)
I was thinking of trying to build the ArrowOS Rom myself and maybe I could publish them if others might like them. However, I am having issues building the rom. I have added the dragon roomservice.xml to local_manifests and changed the revisions to ones that actually exist in the repos. But now when building I'm getting:
[Output: error: device/google/dragon/light/Android.bp:15:1: dependency "libc++fs" of "[email protected]" missing variant: os:android,image:vendor.33,arch:arm64_armv8-a_cortex-a53,sdk:,link:static available variants: os:linux_glibc,arch:x86_64 (alias to os:linux_glibc,arch:x86_64,link:static) os:linux_glibc,arch:x86_64,link:static os:linux_glibc,arch:x86 (alias to os:linux_glibc,arch:x86,link:static) os:linux_glibc,arch:x86,link:static os:windows,arch:x86 (alias to os:windows,arch:x86,link:static) os:windows,arch:x86,link:static os:windows,arch:x86_64 (alias to os:windows,arch:x86_64,link:static) os:windows,arch:x86_64,link:static os:android,image:,arch:arm64_armv8-a_cortex-a53 (alias to os:android,image:,arch:arm64_armv8-a_cortex-a53,sdk:,link:static) os:android,image:,arch:arm64_armv8-a_cortex-a53,sdk: (alias to os:android,image:,arch:arm64_armv8-a_cortex-a53,sdk:,link:static) os:android,image:,arch:arm64_armv8-a_cortex-a53,sdk:,link:static os:android,image:,arch:arm_armv8-a_cortex-a53.a57 (alias to os:android,image:,arch:arm_armv8-a_cortex-a53.a57,sdk:,link:static) os:android,image:,arch:arm_armv8-a_cortex-a53.a57,sdk: (alias to os:android,image:,arch:arm_armv8-a_cortex-a53.a57,sdk:,link:static) os:android,image:,arch:arm_armv8-a_cortex-a53.a57,sdk:,link:static os:android,image:ramdisk,arch:arm64_armv8-a_cortex-a53 (alias to os:android,image:ramdisk,arch:arm64_armv8-a_cortex-a53,sdk:,link:static) os:android,image:ramdisk,arch:arm64_armv8-a_cortex-a53,sdk: (alias to os:android,image:ramdisk,arch:arm64_armv8-a_cortex-a53,sdk:,link:static) os:android,image:ramdisk,arch:arm64_armv8-a_cortex-a53,sdk:,link:static os:android,image:recovery,arch:arm64_armv8-a_cortex-a53 (alias to os:android,image:recovery,arch:arm64_armv8-a_cortex-a53,sdk:,link:static) os:android,image:recovery,arch:arm64_armv8-a_cortex-a53,sdk: (alias to os:android,image:recovery,arch:arm64_armv8-a_cortex-a53,sdk:,link:static) os:android,image:recovery,arch:arm64_armv8-a_cortex-a53,sdk:,link:static /ICODE] Any ideas ?
 

michie

Senior Member
Apr 15, 2007
1,549
2,549
Hasselt
I was thinking of trying to build the ArrowOS Rom myself and maybe I could publish them if others might like them. However, I am having issues building the rom. I have added the dragon roomservice.xml to local_manifests and changed the revisions to ones that actually exist in the repos. But now when building I'm getting:
[Output: error: device/google/dragon/light/Android.bp:15:1: dependency "libc++fs" of "[email protected]" missing variant: os:android,image:vendor.33,arch:arm64_armv8-a_cortex-a53,sdk:,link:static available variants: os:linux_glibc,arch:x86_64 (alias to os:linux_glibc,arch:x86_64,link:static) os:linux_glibc,arch:x86_64,link:static os:linux_glibc,arch:x86 (alias to os:linux_glibc,arch:x86,link:static) os:linux_glibc,arch:x86,link:static os:windows,arch:x86 (alias to os:windows,arch:x86,link:static) os:windows,arch:x86,link:static os:windows,arch:x86_64 (alias to os:windows,arch:x86_64,link:static) os:windows,arch:x86_64,link:static os:android,image:,arch:arm64_armv8-a_cortex-a53 (alias to os:android,image:,arch:arm64_armv8-a_cortex-a53,sdk:,link:static) os:android,image:,arch:arm64_armv8-a_cortex-a53,sdk: (alias to os:android,image:,arch:arm64_armv8-a_cortex-a53,sdk:,link:static) os:android,image:,arch:arm64_armv8-a_cortex-a53,sdk:,link:static os:android,image:,arch:arm_armv8-a_cortex-a53.a57 (alias to os:android,image:,arch:arm_armv8-a_cortex-a53.a57,sdk:,link:static) os:android,image:,arch:arm_armv8-a_cortex-a53.a57,sdk: (alias to os:android,image:,arch:arm_armv8-a_cortex-a53.a57,sdk:,link:static) os:android,image:,arch:arm_armv8-a_cortex-a53.a57,sdk:,link:static os:android,image:ramdisk,arch:arm64_armv8-a_cortex-a53 (alias to os:android,image:ramdisk,arch:arm64_armv8-a_cortex-a53,sdk:,link:static) os:android,image:ramdisk,arch:arm64_armv8-a_cortex-a53,sdk: (alias to os:android,image:ramdisk,arch:arm64_armv8-a_cortex-a53,sdk:,link:static) os:android,image:ramdisk,arch:arm64_armv8-a_cortex-a53,sdk:,link:static os:android,image:recovery,arch:arm64_armv8-a_cortex-a53 (alias to os:android,image:recovery,arch:arm64_armv8-a_cortex-a53,sdk:,link:static) os:android,image:recovery,arch:arm64_armv8-a_cortex-a53,sdk: (alias to os:android,image:recovery,arch:arm64_armv8-a_cortex-a53,sdk:,link:static) os:android,image:recovery,arch:arm64_armv8-a_cortex-a53,sdk:,link:static /ICODE] Any ideas ?
Check if Arrow source has something like this: https://review.lineageos.org/c/LineageOS/android_external_libcxx/+/335628

Then you should be able to build libc++fs as a shared lib.
 

scottrix

Senior Member
Jul 19, 2012
53
23
Check if Arrow source has something like this: https://review.lineageos.org/c/LineageOS/android_external_libcxx/+/335628

Then you should be able to build libc++fs as a shared lib.
Thanks, that with a couple of other fixes got me a build, however, it doesn't boot, and no logcat.. Don't know information to provide, but I did notice the images are significantly different sizes:

Code:
Archive:  Downloads/Dragon/Arrow-v13.0-dragon-UNOFFICIAL-20221203-VANILLA.zip
signed by SignApk
Length      Date    Time    Name
---------  ---------- -----   ----
334  2009-01-01 00:00   META-INF/com/android/metadata
215  2009-01-01 00:00   META-INF/com/android/metadata.pb
564011301  2009-01-01 00:00   system.new.dat.br
0  2009-01-01 00:00   system.patch.dat
62144257  2009-01-01 00:00   vendor.new.dat.br
0  2009-01-01 00:00   vendor.patch.dat
2229888  2009-01-01 00:00   META-INF/com/google/android/update-binary
2886  2009-01-01 00:00   META-INF/com/google/android/updater-script
7270400  2009-01-01 00:00   boot.img
1190  2009-01-01 00:00   install/bin/backuptool.functions
4324  2009-01-01 00:00   install/bin/backuptool.sh
7493  2009-01-01 00:00   system.transfer.list
812  2009-01-01 00:00   vendor.transfer.list
1675  2009-01-01 00:00   META-INF/com/android/otacert
---------                     -------
635674775                     14 files

Archive:  Downloads/Dragon/Arrow-v13.0-dragon-UNOFFICIAL-20230202-VANILLA.zip
signed by SignApk
Length      Date    Time    Name
---------  ---------- -----   ----
333  2009-01-01 00:00   META-INF/com/android/metadata
214  2009-01-01 00:00   META-INF/com/android/metadata.pb
680094394  2009-01-01 00:00   system.new.dat.br
0  2009-01-01 00:00   system.patch.dat
73464372  2009-01-01 00:00   vendor.new.dat.br
0  2009-01-01 00:00   vendor.patch.dat
2470448  2009-01-01 00:00   META-INF/com/google/android/update-binary
2889  2009-01-01 00:00   META-INF/com/google/android/updater-script
7352320  2009-01-01 00:00   boot.img
1190  2009-01-01 00:00   install/bin/backuptool.functions
4324  2009-01-01 00:00   install/bin/backuptool.sh
8581  2009-01-01 00:00   system.transfer.list
992  2009-01-01 00:00   vendor.transfer.list
1675  2009-01-01 00:00   META-INF/com/android/otacert
---------                     -------
763401732                     14 files
 

michie

Senior Member
Apr 15, 2007
1,549
2,549
Hasselt
Thanks, that with a couple of other fixes got me a build, however, it doesn't boot, and no logcat.. Don't know information to provide, but I did notice the images are significantly different sizes:

Code:
Archive:  Downloads/Dragon/Arrow-v13.0-dragon-UNOFFICIAL-20221203-VANILLA.zip
signed by SignApk
Length      Date    Time    Name
---------  ---------- -----   ----
334  2009-01-01 00:00   META-INF/com/android/metadata
215  2009-01-01 00:00   META-INF/com/android/metadata.pb
564011301  2009-01-01 00:00   system.new.dat.br
0  2009-01-01 00:00   system.patch.dat
62144257  2009-01-01 00:00   vendor.new.dat.br
0  2009-01-01 00:00   vendor.patch.dat
2229888  2009-01-01 00:00   META-INF/com/google/android/update-binary
2886  2009-01-01 00:00   META-INF/com/google/android/updater-script
7270400  2009-01-01 00:00   boot.img
1190  2009-01-01 00:00   install/bin/backuptool.functions
4324  2009-01-01 00:00   install/bin/backuptool.sh
7493  2009-01-01 00:00   system.transfer.list
812  2009-01-01 00:00   vendor.transfer.list
1675  2009-01-01 00:00   META-INF/com/android/otacert
---------                     -------
635674775                     14 files

Archive:  Downloads/Dragon/Arrow-v13.0-dragon-UNOFFICIAL-20230202-VANILLA.zip
signed by SignApk
Length      Date    Time    Name
---------  ---------- -----   ----
333  2009-01-01 00:00   META-INF/com/android/metadata
214  2009-01-01 00:00   META-INF/com/android/metadata.pb
680094394  2009-01-01 00:00   system.new.dat.br
0  2009-01-01 00:00   system.patch.dat
73464372  2009-01-01 00:00   vendor.new.dat.br
0  2009-01-01 00:00   vendor.patch.dat
2470448  2009-01-01 00:00   META-INF/com/google/android/update-binary
2889  2009-01-01 00:00   META-INF/com/google/android/updater-script
7352320  2009-01-01 00:00   boot.img
1190  2009-01-01 00:00   install/bin/backuptool.functions
4324  2009-01-01 00:00   install/bin/backuptool.sh
8581  2009-01-01 00:00   system.transfer.list
992  2009-01-01 00:00   vendor.transfer.list
1675  2009-01-01 00:00   META-INF/com/android/otacert
---------                     -------
763401732                     14 files[/COD
[/QUOTE]

What fixes do you mean? You shouldn't need more than the patch I gave you and the patches on my github ;)

Sync my Lineage device repo and revert
https://github.com/ThaMichie/androi...mmit/e88a8852c4cc74fb2b6f62c11c48f1a9568543a6

Make sure you have the patch mentioned earlier, apply these patches

This should be all for a working build.
 
Last edited:

a8smith

New member
Feb 5, 2023
3
0
Hi,

I was given a pixel c from a neighbour who was moving away and I loved how premium it looked and felt and so I thought it would be interesting to see how up to date I could bring it. Took a bit of googling to figure out what to do and how to do it (unlock bootloader, custom recovery, flash custom rom, magisk to certify device etc) but I'm really impressed with what has been done by ArrowOS. I also bought an official keyboard for £5.

But I do have one issue...

Battery life seems terrible when it's not being used. Unplugged with the keyboard on it as a cover it loses probably 8-10% an hour. Overnight it can go from fully charged to 25%. Could there be something always running, or is it likely the battery is just toast?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    New build up, fixes on par with Lineage and PE
    1
    Dirty flash just fine over the build I installed back in November. The other one was causing some battery drain much faster the LOS in battery saver mode. Recently the tablet was dying in a few days vs. a few weeks. I am hoping this update solves that one. Thanks again for keeping this one alive. Let me know if you need me send you a beer!
  • 23

    logo.png



    ArrowOS



    /* * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at us for messing up your device, We will laugh at you. * It is your fault because you chose to do all the modifications on your device. * Remember projects like these and the work done on them is a hobby to the * contributors and the team members, no one is working for you nor is getting paid for it * have some respect for the work done by them since it is done purely on interest or a hobby */


    ABOUT
    ArrowOS
    is an Android Open Source Project based Android mobile operating system started with the aim of keeping things simple, clean and neat.

    Website: https://arrowos.net
    Telegram: Channel | TG Portal/Links
    Github: https://github.com/ArrowOS
    Code Review: review.arrowos.net
    E-mail: arrowos.contact
    PayPal: Donate to us
    Blog: blog.arrowos.net

    Checkout more documentation at (maintainership/contributing): Check this out

    WHAT WORKS?
    • Almost everything

    WHAT DOESN'T WORK?
    • Camera
    • Webview based browsers won't play videos
      • Use a browser like firefox as a workaround (SW Codecs)
    • SELinux is permissive
    Be sure to include a log: check how to

    DOWNLOADS
    Click here to Download

    Recommended Gapps Package: MindTheGapps

    Read our blog article/post about:
    * HOW-TO report a bug
    * GAPPS and VANILLA variants
    * Checking build integrity

    GPL compliance:
    ROM Source
    - https://github.com/ArrowOS
    Kernel Source - https://github.com/ThaMichie

    ROM OS Version: Android 13
    Security patch level: January 2023
    ROM Kernel: Linux 3.18
    Based On: AOSP
    14
    New build is up:

    * Fixed Bluetooth connection
    * Fixed Bluetooth audio
    * Replaced our old bluetooth hal with Shield Bluetooth configs
    * Ported Wifi Shield configs
    * Performance optimizations (GPU boost)
    * November security patch

    I forgot to include the H264 patch, will do next build.
    12
    New build up!

    - Improved UI performance (Smoother Animations)
    - Improved multitask performance
    - Updated device & vendor props
    - Upreved audio HAL to V7
    - Enabled H264 Codec
    - Ported Shield Health HAL
    12
    thank you very much for all the work and bringing life back to our pixels c.
    What next changes are you planning to bring? Do you think it will be possible to bring back 2k youtube or fullhd netflix?
    What are the pros of that shield 9.0.0 firmware?
    Thank you again
    I've put alot of work and time in our device tree to clean and upgrade everything I can which makes it easier to port future android versions. Will check if I can make it treble compatible too.

    The firmware itself wont make much difference without decent kernel drivers supporting it but let's see what I can do with our old kernel.

    With spoofing we might be able to bring back widevine but let's do one step at a time 😁

    My dad bought a 2022 mid range tablet. Feels way more sluggish compared to the pixel now 😎
    11
    New build up!

    - Updated CPU firmware to Shield 9.0.0
    - Updated GPU firmware to Shield 9.0.0
    - Updated xusb firmware to Shield 9.0.0
    - Fixed Led bar behaviour: Made my own variation to have a dimmed lightbar when screen is on so it does not disturb in dark rooms and turns off at screen off.

    Also cleaned our device tree.