u/LeadershipUsual8634

Opinions on the Polestar 3/4 leases that were just announced? As they are exiting the US Market, and will offer full warranty during the lease period, it seems like a reasonable deal?
Both are at 7,500 miles a year.

Monthly lease payment of $399 per month for 39 months is based on new 2026 Polestar 4 Long range Single motor with an adjusted capitalized cost of $38,795 (MSRP of $57,800 including destination and delivery fee of $1,400, plus acquisition fee of $995, less $1,000 capitalized cost reduction, and $19,000 Polestar Clean Vehicle.

Monthly lease payment of $579 per month for 27 months is based on Polestar 3 Long range Dual motor with an adjusted capitalized cost of $50,795 (MSRP of $74,800 including destination and delivery fee of $1,400, plus acquisition fee of $995, less $5,000 capitalized cost reduction, and $20,000 Polestar Clean Vehicle Non-cash Incentive)

Proposed Roundabout at Austin Pkwy/Commonwealth

UPDATE: Out of curiosity, I emailed City of Sugar Land Engineering Department and asked!

I got a very detailed response, which I am paraphrasing below:

Roundabouts were evaluated for the Austin Pkwy & Commonwealth intersection, but several site-specific constraints made them impractical here. The intersection sits on a major pipeline easement, and the pipeline owner does not permit a roundabout at this location. Relocating the pipeline would add roughly $2 million in cost.

A roundabout would also require a much larger footprint, likely involving acquisition of private property and shifting the roadway closer to adjacent residential backyards. Addressing both the pipeline issue and property impacts could delay construction by approximately two years.

Multiple alternatives were studied, considering cost, timeline, right-of-way impacts, and operational performance. Based on that analysis, a traffic signal was selected as the preferred option because it can address congestion more quickly, manage peak school and rush-hour traffic effectively, and minimize project cost and risk.

Original Post:

For those of us who live in Commonwealth and parts east (Riverstone/Lakefield/Lake Colony/Commonwealth), the Austin Parkway / Commonwealth 3 way stop seems to be getting worse over time with long lines backed up on all three roads. Especially during school/rush hour and weekends. It can take a good ten minutes or more to get through.

I was wondering what the consensus was to turn the intersection into a roundabout?

Or would just be a disaster due to Texans not knowing how to use a roundabout?

Hello

Not sure if the correct forum or not:

USA based, Samsung S21, had two phones for longest time (personal S21and business iphone). Now consolidated into S21 only.
SIM 1 - personal (major US carrier)

SIM 2 - business (cheap MVNO)

Everything works properly (phone calls, texting, RCS, etc)

EXCEPT, I cannot send a SMS from SIM 1 to SIM 2, or SIM 2 to SIM 1 (not a big deal, just testing stuff). The google messages app shows RCS delivered (2 check marks), but it does not show up as a received message at all in on the "left side) of the conversation.

Same thing happens if I text myself (SIM 1 to SIM 1 or SIM 2 to SIM 2). In the past, before I enabled Dual SIM, I could text myself on SIM 1.

Wondering if this is intentional?

I have a Samsung S21 that does not back up the photos every night despite the setting on the Ugreen app because of stuff previously documented. I have followed all the instructions for keeping the app alive, background, etc.

I did some research and followed some instructions from a another redditor and set up a Samsung “routine” to turn on the phone, connect to WiFi, and open up the Ugreen app at 3AM and then reverse the process at 3:30 AM.

Now, when I wake up in the morning, the Ugreen app is open but asking for my biometrics to login. I notice that nothing backs up unless I use my fingerprint to open the app and then it says “backing up”.

Is there way to do this without me actively logging in with my fingerprint every morning?

Thanks in advance!!

Samsung Messages is being discontinued, Google Messages can't handle dual SIMs for SMS very well. Is there an alternative app that works well with RCS? eSIM 1 = Personal, eSIM 2= business

Or should I do what AI agents suggest: Google Messages the primary app for Line 1/RCS and Textra the backup/secondary app for Line 2/SMS without RCS?

Before anyone comments, please note that Android Auto (AA) is NOT Android Automotive Operating System (AAOS). Apologies for the caps and bolding, but whenever I bring this up, people just don't understand.

Issue:

AA in one car, GM EV with AAOS in the other. Samsung Ecosystem. Logged in using the exact same login id.

USA 3rd generation South Asian family with South Asian names speaking English. Hindi names in an English context for which Android is crap at recognizing. Whenever I say, "call Deepika Padukone" Google has NO IDEA who I want to call. It comes up with the most random suggestions and starts to dial unless I totally slaughter the pronunciation and sound like I have never spoken Hindi: "Call DEEE PEE KAY PAD YOU CONE"

So for years, I just associated "Deepika Padukone" with "Wife" in my Android Contacts Settings under "Spouse". I did the same for my daughter and son. "Call my wife" "Call my daughter" "call my son" all worked in AA. I used their first names under "Nicknames"

Last year, I got a General Motors EV that runs AAOS, logged in with my account and though all was good.

However, whenever I say, "Call my wife" I get an error message. "Sorry who do you want to call?" Same for son and daughter. I occasionally get the message "This contact has not been set up yet" or something like that.

Google Assistant Settings under "Your People" are correct. This works in AA but never has in AAOS.

Research says that Gemini is doing this, but i have no idea how to access those settings in my car or on the phone as I purposely do not use Gemini.

Thoughts and advice appreciated!

Long story short, car dealer service center uses Lyft through Xtime for pickups and dropoffs.

My car was ready, so dealership sent the Lyft. It was rush hour, so I thought the Lyft was rerouting us via a quicker option, it wasn't until we passed the turn towards the dealership that I asked the driver where we were going. My Lyft app AND the Driver's Lyft app was sending us to a city park miles away from the dealership, DESPITE the correct address showing on the app. For some reason, the Lyft GPS thought a car dealership on a major hwy in Houston was in a park in the middle of the city!

I told the driver that this made no sense, but she insisted on following the Lyft GPS instructions until we ended up at a city park staring at some kids on the playground (no car dealership in sight!!)

I finally convinced her NOT to use the Lyft GPS and her car's built in google maps to get us to the right direction. All through this extra 30 minute diversion, the Lyft GPS is yelling at her to go back to the park. The only options for me are to call 911 or ADT, both of which are overkill for a GPS kidnapping.

Today, just for grins, I put in the name of the dealership again into the Lyft app, and the park comes up!

I have no idea how to tell Lyft that there GPS is messed up, and the dealership is just as baffled as I am!

I, and I think, many others, will pay for a decent audio book player (especially one that access audiobookshelf) for AAOS. To date, there is not one.

Apologies for the all caps & bold, as when I discuss this on different forums, people just don't get it.

Android Automotive Operating System (AAOS) is DIFFERENT from Android Auto (AA).

AAOS is the standard operating system EVs from GM, Polestar, Volvo, Acura, Honda. SOME of these allow dual use with AA, others do not.

I don't know a single thing about programming, though I was pretty good with BASIC back in the 80s.

Per Google:
Android Auto and AAOS should be thought of as different products, not the same app in two places. Android Auto is phone-projected, while AAOS runs natively inside the car, so the app has to be designed for vehicle hardware, system bars, fixed screen behavior, car-specific UX limits, and the automotive Play distribution requirements. In practice, that means rebuilding around Google’s car app templates and quality rules, keeping driving tasks simple and safe, handling parked-only features where needed, testing in the AAOS environment, and meeting car-app standards like no blocked screens, no dead ends, fast response times, and category-specific restrictions before release.

Thanks in Advance!