kbalage

@Razer7 the Powered Up app uses virtual control elements on the screen and it does not support any external devices like gamepads. Your best chance to use the gamepad with that phone is the BrickController 2 app.

@fred67 I did not notice the bad battery life and I was running several different hubs in different vehicles. I am using rechargeable batteries from IKEA and they work very well. The last test I did was with 42109 and the Technic hub - it was running 8 hours straight on a test platform and even after that it was able to run on a carpet.

@lego3057 if you watch the video you can see what block is used to address the the different hubs. Each connected hub gets a number and there's a dedicated block that you can use to select the hub's number and the output port.

The full LEGO numbers are 6285646 & 6285647

The capability is in the motor and not in the hub, although you need an app that supports it for control. Currently only the Control+ app has proper return to center steering (but that only supports the Technic hub) and the BrickController 2 app, luckily that supports even your microwave oven so problem solved :)

A little comparison what the 4 port Technic hub has to offer compared to the 2 port "City" Powered Up hub in the Rally Car:

@efferman it is not possible, the other side is different and you cannot connect the clips:

I took the new differential from the 42109 App-Controlled Top Gear Rally Car and compared it to the previous generations, also tried to see if there are any changes/improvements/benefits:

Here's my take on the Rally Car:

@Juxtapoisson I don't think there's anything else apart from this thread. I use an ipega PG-9025 controller with my Android device and a SteelSeries Nimbus with an iPad, both work well.

I just tested the latest iOS version with the L motor acting as a servo and it really has some issues, at some points it seems to be working normally but then there's a significant lag and sometimes it gets stuck at the endpoint. The calibration process runs fine though. Did not experience anything similar in the Android version.

@rm8 just tested the latest iOS app with the servo, yes it seems to have a problem with the steering. The Android app works fine.

LEGO released the 3.0 update of the Powered Up app yesterday. As we were informed previously this is an important update with long awaited features like the multi-hub support or the support for the Technic hub and the L and XL motors. Check out my review about the update here: What I liked: new cleaner main interface looks good, easy to navigate multi hub support really works, 4 hubs can be connected simultaneously and they can be all different kind (Boost, AAA hub, Technic hub) sensor data from Technic hub can be accessed and used multiple sensors can be used the same time, external and internal as well phone/tablet orientation can be used as a controller although the zero position is still a question What I did not like: Biggest frustration – total lack of documentation. The app is getting super complicated, if I were a kid I would not bother trying to figure it out. This should be the number one priority to sort out. L & XL motors have proper speed control but steering is still laggy, absolute positioning does not work for steering Controller interfaces are still limited, the 2 slider one works only for tracked vehicles or the Batmobile, the joystick interface is not scaled properly on a tablet and cannot be used with the L/XL motors for steering The app still needs to be killed to disconnect all hubs or they have to be disconnected manually one by one The whole app looks like a tech demo for programmers beyond the set-specific controls. It does a lot but without any documentation and you don’t know what supposed to work and what not. It has a great potential for advanced users but totally misses the point for the ones who’d like to go one step further from the stock builds and want to add a light or a motor to a creation, it’s way too complicated.

There's no need for a feel-sorry-for-me campaign, you got the sets early and you're not bound by an embargo so go for it, share what you found :) 42107 is still a mystery, but 42105 is well known it's the Catamaran

The PU L motor for steering should work the same way as in 42099 with proper return to center steering (when used with the appropriate application)

@Valkyx reviews will come on the 26th

It's there since the announcement but the shipping date is still the 26th, when the reviews will go online.

BC2 can perfectly control the car.

It also depends in which mode you want to run it, BuWizz won't handle 8 XL motors in high/ludicrous mode for sure. If you want to use the full capabilities (meaning ludicrous mode) under heavy load then based on my experience the limit is 2-3 L or XL motors (depending on the stress and configuration) and only 1 buggy motor per unit.

You can check the size and comparison with some other wheels here

@Lipko I also see the comments so it's not location-dependent for sure

You don't really know if kids watch your content. YouTube statistics show the age of the accounts' owner, not who's actually watching the video. That was the main problem of the whole $170 million fine story... I recently made a video comparing the 1989 Batmobile and the Tumbler. Both sets are 16+, yet I'm sure kids love them. So shall this video marked as "for kids" or not? There are thousands of examples like this with many subjects and you can't be sure who's right or wrong. As @efferman said, potentially anything can be interesting for a 12 year old. What I'm saying is that the whole approach is wrong. The original source of the issue - Google collecting data about kids without parental consent. The way I see it there are several more simple solutions: - Don't sell ads targeting kids, that eliminates the source of the problem. Would surely hurt the revenue of many YouTubers but would still keep all the functionality. - Only show ads if you are logged in on that device. You need to be at least 13 to have a Google account so the responsibility is on the parents' side in this case. - Keep the "for kids" switch on the videos but that would trigger a popup asking for parental consent on whatever is needed. If it is accepted, everything goes normally. If it is declined, no data is collected.

That's not that simple. If you make a Horror/sex scene with Lego figures that should not be marked for kids under any circumstances, doesn't matter what Google says. Adult cartoons are not for kids either just because they are cartoons. Live streaming a 18+ video game should not be automatically considered kids' content just because it's a video game. I can even imagine a sex toy promotion being marked as "for kids" by their bots because it has the word "toy". Google tried to make the situation black or white but it's impossible to treat the subject this way. We'll see how it unfolds but if the restrictions will be applied as they are defined today then the "for kids" videos will have minimal reach, YouTube will become a video hosting platform nothing more. Actually the law (COPPA) and Google are saying different things, and we aren't safe at all until Google retains the rights to mark anything "for kids" and based on their on decision ban anyone or delete their channel. Honestly in this situation the FTC is the good cop, at least they ask people about their opinion and they show some effort to understand what are the potential issues. Google simply choose the worst solution for everyone and tries to push all responsibility on the content creators.

You need space inside for 6 AA batteries and the 4 connectors, can't really be smaller than the current one.

From a functionality standpoint yes, but as @AVCampos said it'll most likely have a similar form factor to the AA smart hub.