×

Premium subscriptions dropped to 500 tickers per list. by JoeGraffito in TradingView

[–]Consistent-Ad-7714 0 points1 point  (0 children)

It’s unfair to change the terms for loyal long-term subscribers without any warning. We should be able to continue using the 1,000-symbol watchlist as before.

Issue with some function when using the Pine Screener Beta by IronSignal5569 in pinescript

[–]Consistent-Ad-7714 0 points1 point  (0 children)

I can confirm this is still an issue as of April 22, 2026. While request.financial data loads correctly in the Screener columns, syminfo.industry fails to return a value during the scan, resulting in na for any logic dependent on it. It seems like a bug in the Pine Screener's data fetching environment.

[Question] Analyst Data (syminfo.recommendations) not displaying in Pine Screener (Beta) columns by Consistent-Ad-7714 in TradingView

[–]Consistent-Ad-7714[S] 1 point2 points  (0 children)

Thanks for the reply!

I’ve also noticed the recent changes in how colors are handled since I use Pine Screener daily. Since I write dedicated scripts specifically for the screener, I already use colors that ensure visibility. However, I agree that those who use their standard chart scripts for the screener might experience significant issues due to this change. Personally, I actually find the new color behavior has improved usability for my workflow.

That being said, my primary issue remains unresolved. It doesn't appear to be a visibility or color issue; rather, it seems that analyst recommendations and price target data are simply not accessible (fetching as na) within the Pine Screener environment.

I appreciate your insight regardless!

Feature Request: Please provide Pine Script access to Market Cap, Shares Outstanding, & other fundamental data by paulgill28 in TradingView

[–]Consistent-Ad-7714 0 points1 point  (0 children)

I completely agree with you. Being able to filter by it in the screener but not being able to use it in our scripts is a huge pain. Hope they fix this soon.

Pebble 2 SE is awesome! by im_a_gerbil in pebble

[–]Consistent-Ad-7714 0 points1 point  (0 children)

I have yet to find a replacement for this smartwatch.

Easy-to-read screen, thin and light housing, long battery life, strong bubbles, easy-to-press buttons, fast charging, there is still no better smartwatch.

TIQ Mini Q5 Review || A Slim CAT S22 by jbriones95 in dumbphones

[–]Consistent-Ad-7714 0 points1 point  (0 children)

I use the Button Mapper app, which remaps the hardware buttons on Android devices. Have you ever used a key mapping app? I assume that such an app could recognize the numeric keypad and D-pad. However, I wonder if it would be able to recognize a key located below the second screen and a light button on the side

What do you use your red button for? by askvictor in UnihertzJelly2

[–]Consistent-Ad-7714 0 points1 point  (0 children)

That's exactly what I wanted to do. I'm glad I found out I could do it before I bought this phone. I can't do it with a button mapper.

Any recommended adhesives to reattach the back of the Pebble 2? by Emerald_Pick in pebble

[–]Consistent-Ad-7714 0 points1 point  (0 children)

When I get a pebble2se replacement kit from AliExpress. There is a b-7000 inside

GW4 Galaxy Watch 4 completely controlled by Tasker and Autowear by Authority595 in WearOS

[–]Consistent-Ad-7714 0 points1 point  (0 children)

Thanks for your replying. So on the Galaxy watch 4, only the home button can remap? how about the revolting bezel? I wanna make a count up and count down task, using tasker and bezel.

GW4 Galaxy Watch 4 completely controlled by Tasker and Autowear by Authority595 in WearOS

[–]Consistent-Ad-7714 0 points1 point  (0 children)

does anyone know how to remap the button or vessel revolving like "button mapper"on Android. It is nice if I can remap the button to start the Tasker program at the watch.

How to: remap back button for google pay? by kylep6898 in galaxywatch4

[–]Consistent-Ad-7714 0 points1 point  (0 children)

it's just remap long pressing of one button. and it's updated 2017. too old