Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - poyo

#1
Looks like things are moving forward with the XCADEY ALPHA 800 and its software development! 👍

They've now opened a Discord server where users can report bugs, share feedback, and suggest new features. Great to see more direct communication between the developers and the community. Hopefully this will help improve the software even faster! 🚴�♂️

https://discord.gg/5v9AaA7nk
#2
I managed to get Karoo 3 Software running on the XCADEY ALPHA 800 – without root access!
The biggest challenge was porting Karoo 3 from Android 12 to the ALPHA's Android 8.1.
I developed a custom compatibility bridge to handle missing system services and an independent ANT+ host to overcome the sensor integration problems.
Heart rate, radar, Shimano Di2 via Ki2, and Power and other sensors are working through Karoo's native sensor management and extensions.   

Some issues remain, including UI compatibility, unsupported system functions, and the inability to use ANT+ radar and light control simultaneously.

If XCADEY provided an open SDK and opened up its sensor interface to third-party developers, we could add these features directly to the original ALPHA software without needing such a complex port.

One important thing: I'm not a programmer or software developer. I used AI to help with the coding and technical adaptations needed to get the software from my own Karoo 3 running on the XCADEY ALPHA 800. I guided the project, provided the hardware, and tested the results.

This is a personal experimental project intended to demonstrate what the ALPHA 800 hardware is capable of. I'm not distributing any Karoo software, modified APKs, or the port itself. I'm only sharing my results and a demonstration video.

https://uploadnow.io/f/x2DGMcb

#3
Quote from: yappy on September 23, 2026, 04:19:17 AM
The standout feature of the alpha800 is its Android-based operating system, which offers a way of using the device that differs from conventional cycle computers. If root access is unlocked, it should be possible to install custom-made apps and plugins.

Yeah, the Android side is probably one of the coolest things about the Alpha 800.
If root access can be unlocked, being able to run custom apps/plugins could make this thing pretty interesting.

I came across this hands-on report:
https://jedrysik.com/bike-computer-xcadey-alpha-800/

Also, one thing that isn't mentioned in the review: the Alpha 800 uses a **Blanview display**. The guy says he was riding in direct sunlight with only 25% brightness.
That's pretty impressive.

**Update:** Adam, who wrote the test I linked above, replied to my comment. He says GPS accuracy and lock are good so far, with no dropouts or issues during his test. Battery life is also looking very promising at around **5% per hour or less**. The current map view is north-up only, and he is still waiting for a follow-direction option.

#4
I've ordered the XCADEY ALPHA 800 and I'm curious to see how it performs in real-world use.

At the moment, I still see the device as being somewhat in a beta stage, but I also think it has a lot of potential, especially because of the Android-based platform and the possibility of extensions.

I've contacted XCADEY to ask whether they provide, or plan to provide, an SDK / Developer API. I'd be especially interested in things like custom data fields, additional sensor support, Di2 features, Komoot integration, navigation tweaks, and ride-screen notifications.

Once the device arrives, I'll take a closer look at what is actually possible and will share my impressions.

The ALPHA 800 is currently available at a reduced price on XCADEY's website:
https://xcadey.com/bike-computers/

#5
Quote from: Lotnik on September 17, 2026, 01:35:09 AM
It looks empty

Yeah, looks like they're still setting it up.
#6
They even have a website now.

https://www.anrancee-cycling.com
#7
Quote from: kbernstein on September 13, 2026, 12:51:20 PM
Does anyone know of a 12 speed 11-40 cassette ? I swear i've seen one before and AI also says so but I can't find it anymore. 38 and 42 are fine too if these somehow exist but I hate the gap in the cassette market for 12 speed

https://de.aliexpress.com/item/1005009369286201.html

#8
Quote from: bichler.bua on September 08, 2026, 12:50:53 AM
I am based in Germany and my AliExpress order on the Ryet Official Store was cancelled after it was initially accepted (reason: "issues with shipping") and refunded

I'm also based in Germany and ordered from the Ryet Official Store. My order has already been shipped.
#9
Quote from: DrRoB on July 27, 2026, 03:23:59 AM
No, unfortunately not; it mainly creaks when riding out of the saddle, and only when I stand on the pedals or move them with light pressure.
I suspect that neither the included bottom bracket nor the one from Kactus is compatible with a spacer. However, a spacer is necessary to adjust the crank preload.
I've already adjusted the preload several times with different cranks (P515, 105, Ultegra). Unfortunately, after 2-5 minutes it always starts creaking again.

For me, it turned out to be the rear thru-axle.
I had to tighten it really firmly to make the creaking go away.
I also had a direct mount hanger installed at the time, but I have since switched back to the original UDH derailleur hanger, and now it's fine.
Additionally, I swapped the included bottom bracket for a Praxis bottom bracket. It might be worth checking the rear axle torque before going crazy with the bottom bracket spacers!
#10
Quote from: Lotnik on June 21, 2026, 02:15:44 PM
I had it on 160 up and the caliper seats too high over the disc brake. I think this frame is 160/160 from the design.

In this specific case, flipping it to the "140" position is actually the correct workaround to keep the spacing at 160 mm!
#11
Quote from: Lotnik on June 20, 2026, 11:53:58 PM
Assembly in progress. But I run some hiccups. I installed XG 4 pistons caliper with 160 mm discs front and rear. Looks like they need to be on 140 adapter front and no adapter at rear. But still I can't say up then straight without rubbing. Usually my toopre tool was enough but not here. This is my first 4 pistons caliper so maybe I'm doing something wrong. Any ideas?

Hi,
The issue is with your front brake setup: your flatmount adapter is installed upside down!
These front fork adapters are asymmetrical because they act as reversible plates to switch between 140 mm and 160 mm rotors. Since you are running 160 mm discs, you need to rotate the adapter by 180 degrees. Usually, there is a marking like "160 UP" with an arrow on the plate—that arrow must point upwards.
In its current position, the caliper sits at the completely wrong angle and distance from the rotor. That is exactly why you can't get it aligned without rubbing, even with your alignment tool.
#12
Quote from: hubba on June 10, 2026, 12:46:59 PM
Sometimes even if the stem measures 1cm too long it might be the right size if the length is accounted in the reach. For example the Tavelo rise bar that is listed as 100mm stem and 75mm reach is actually 110mm stem and 65mm reach. The end result in length is exactly the same.

Some bars of course can be longer than stated. Always best to ask if someone has actually measured the bars and not just the stem.

You make a really interesting point with the Tavelo / Avro Rise example!
I was having a hard time imagining how a stated 75mm reach could physically become 65mm, but looking closely at their geometry chart, it actually makes perfect mathematical sense.

Here is what is happening:
The manufacturer measures horizontally: If you look at the Avro Rise sketch, their lines for "Length" (e.g., 100mm) and "Reach" (75mm) are perfectly horizontal (parallel to the ground).
This means the Total Horizontal Reach is 175mm.
You are measuring the physical carbon: Because the stem drops at a -10° angle, measuring along the top of the carbon stem gives you a physically longer measurement of about 110mm.
The Math: Since the total horizontal distance of the cockpit (175mm) doesn't change, shifting the imaginary center point further forward by using your 110mm stem measurement leaves exactly 65mm for the remaining handlebar reach (175 - 110 = 65).
So you are absolutely right, the end result in total length is exactly the same!
However, there is one more crucial variable: The stated reach of the bare carbon is only half the story anyway. At the end of the day, we can easily add or subtract 10–15mm of effective reach just by how high or low we position the shifter hoods on the drops.
Thanks again for pointing this out – it really shows why we can't blindly trust the spec sheets without understanding exactly how the brand measures!
#13
Quote from: eXtenZ on June 10, 2026, 08:48:58 AM
It is very strange, that T4 or ONE ultra handlebars are longer (measured) from bottom. Because I saw their description and it seems that they are measuring from centre to centre. So i am a bit confusing. Dont want to spend money for cockpit, what is exactly as I have now. So that's why I'm asking around on the forums and finding out as much information as possible.

I think there might be a slight misunderstanding about what I meant!
To clarify: When I say it is "measured from the bottom," I mean that the manufacturer specifies the size (for example, 100 mm) based on the length of the bottom edge.
Because of the downward angle and the thick shape of these aero carbon stems, the top edge is physically longer than the bottom edge. Here is how it plays out in reality:
If the official spec (measured at the bottom) is 90 mm.
The measurement at the top edge will actually be around 95-100 mm.
This means if you order a "90 mm" T4 Ultra or The One Ultra, you are practically getting a 95-100 mm stem (if you measure it from the top, the way we are used to with standard stems).
That is exactly why the sizing is so confusing and why many people end up with a cockpit that stretches them out much further than expected!

To show you exactly what I mean, I am attaching two photos of a 90mm T4 Ultra here. As you can see in the pictures, the bottom measures around 90 mm, while the top is around 95–100 mm.

#14
Quote from: eXtenZ on June 09, 2026, 01:14:20 PM
So my question is, what is 80mm real stem length ? If you guys have some of these handlebars, could you please measure that and tell me ?
Thanks !

The pitfall in practice:
When a manufacturer measures the geometry from the bottom, an aero stem specified as "100 mm" might actually be 110 mm long along the top edge. So, if you are switching from a standard stem (measured center-to-center) to an integrated aero cockpit, you should carefully check the manufacturer's geometry charts. Otherwise, you might end up stretched out 10 mm further on the bike than you originally intended. For instance, the specifications for the T4 Ultra handlebar and The One Ultra are indeed measured from the bottom. However, there are exceptions to this rule: my LightCarbon HBR17 measures exactly 100 mm from the top, which perfectly matches the manufacturer's specifications.
#15
Quote from: MF_one on May 28, 2026, 05:09:28 AM
That is new to me, I thought both come for 140 ready, if bigger, an adapter is needed. It is also reflected in their specs like this

This frame natively supports a 160 mm rear disc without an adapter.