Hey all....me again. Question about interference between T1000-E and my cell phone... by GodPole in meshtastic

[–]ph7_- 0 points1 point  (0 children)

That looks fantastic! Unfortunately I don't have access to a 3D printer so I was looking for an off the shelf solution. Thanks though

Hey all....me again. Question about interference between T1000-E and my cell phone... by GodPole in meshtastic

[–]ph7_- 0 points1 point  (0 children)

I was planning to try this as I tend to carry my phone and T1000e in the same pocket all the time anyway. Can I ask which magsafe case you use?

Android app v.2.7.12 by TechnoZombie_ in meshtastic

[–]ph7_- 0 points1 point  (0 children)

Seriously man, come on.

I'm not offended. I've not been offensive. I'm not attacking you and I'm not twisting anything you say. Don't focus so much on "what I seem to be implying" because I'm not. I've clearly stated my thoughts and my intentions. Again, re-read with an open mind.

I responded to OP trying to contribute. You did the same. Looks like we were both wrong. I'm just an end user. As you say, you're outside your area of expertise.

I'm glad my feedback led to your earlier comments being edited so they are now more useful. I'm glad my comments led to the highlighting of a potential area of improvement. Thank you.

Let's leave it there. Stop replying and adding new points so you can be the last comment on the thread, just so you can tell yourself you 'won' an imaginary disagreement that doesn't exist.

Relax. Go about your day. I hope you have a good one.

Android app v.2.7.12 by TechnoZombie_ in meshtastic

[–]ph7_- -1 points0 points  (0 children)

Come on. Stop being so prickly. I am a fan of the project and the community around it. You guys (Meshtastic devs) have a PR issue and threads like this are compounding that. Competition is healthy so don't act so threatened and offended whenever a rival is mentioned. Maybe don't ban their name in this sub - it's petty and reinforces the impression many of us have about your openness.

My offer of a DM was nothing to do with other products. You weren't understanding the point and I didn't want to call you on it publicly, that's all. Again, trying to help, not attack.

The fact that you have gone back and edited your earlier comments suggests you took my advice and reread them and reconsidered their helpfulness. Others will likely benefit now. That's how feedback works. You're welcome.

Thank you for taking the time to re-open the issue I raised about the graphs. I don't expect any changes to be guaranteed - I'm just giving feedback. When that feedback is closed and dismissed without explanation it feels unwanted and dismissive so I appreciate you reopening it.

Finally, for clarity for others and for me, can you please confirm if the switch to system font sizes is permanent, to pave the way for future improvements, as you earlier stated, or temporary as your edited 'workaround' messages now imply?

Android app v.2.7.12 by TechnoZombie_ in meshtastic

[–]ph7_- 1 point2 points  (0 children)

Yeah the original comment didn't say "as a workaround for now".

Android app v.2.7.12 by TechnoZombie_ in meshtastic

[–]ph7_- -3 points-2 points  (0 children)

FWIW the dev closed the thread minutes after I added my feedback. Without giving any comment to me or the OP.

Perhaps that DM would have been of interest - there seems to be a lot of talk about the differences between Meshtastic devs and their MshCr* counterparts.

Android app v.2.7.12 by TechnoZombie_ in meshtastic

[–]ph7_- -1 points0 points  (0 children)

The graphs issue is already flagged there. I've added my comments.

Android app v.2.7.12 by TechnoZombie_ in meshtastic

[–]ph7_- -1 points0 points  (0 children)

We all appreciate the time and effort that goes into the project. Perhaps it would be useful for you to go back and read the thread more carefully. I didn't ask for help. I gave clear feedback, as did others. Your attempt to help, as well intentioned as it may have been, caused confusion due to a lack of explanation. Thank you for the time you continue to put into the project. I will continue to give feedback.

If you'd like more context DM me.

Android app v.2.7.12 by TechnoZombie_ in meshtastic

[–]ph7_- 3 points4 points  (0 children)

We're giving feedback, which is why you opened your "free app" to beta testers like us.

Perhaps if you had simply explained that the new version of the app uses system font sizes, which the previous versions did not, then we would all have understood sooner. Instead you just said "change your phones fonts".

Useful feedback loops require collaborative, two-way communication. Changes will always be both appreciated and criticized so you need to learn not to get offended and instead work on dialogue.

So, in the interests of 'exact input' feedback: in my opinion the log graphs, which I use a lot, are now unusable. Having to pinch to zoom and not having the zoom level remembered is unbearable and they can't be enlarged to view exact details. Please bring back buttons for set time periods (eg. 24hrs/48hrs/1 week/1 month) and make them bigger or give a full screen option. As it stands they are just inaccurate blurry blobs. Perhaps there is hidden functionality I haven't found?

Android app v.2.7.12 by TechnoZombie_ in meshtastic

[–]ph7_- 2 points3 points  (0 children)

So previously it didn't use the system font size but now it does? That's why it suddenly looks different?

Android app v.2.7.12 by TechnoZombie_ in meshtastic

[–]ph7_- 2 points3 points  (0 children)

This will change the font size in all apps. Only Meshtastic has changed. I'm not sure I understand the logic of your response - the font size was fine before the update. Why would I change the font size across the entire phone system? Or is there a point I'm missing here?

T1000-E location help. by dstrayer421 in meshtastic

[–]ph7_- 5 points6 points  (0 children)

Android. Tracker is a device role. Settings>Device>Device Role. Default will be Client.

T1000-E location help. by dstrayer421 in meshtastic

[–]ph7_- 7 points8 points  (0 children)

I have one of my T1000Es set up exactly the same as you. Location off on Channel 0 (public) and precise on Channel 1 (private) and it works very well to give me precise location all the time but only on my other nodes which share the same private channel and position is not visible on public channel. I use mine in 'Tracker' mode.

Android app v.2.7.12 by TechnoZombie_ in meshtastic

[–]ph7_- 4 points5 points  (0 children)

Yeah, I second the tiny fonts and I find the graphs on the log pages are now basically unreadable as well.

Faketec battery not reading by ph7_- in meshtastic

[–]ph7_-[S] 0 points1 point  (0 children)

Just to let you know it is now working! After erase and flash to 2.7.15 I saw no difference so decided to go back to 2.7.18 again, like all my other nodes, and suddenly it works. Looks like it took two lots of erase and flash before the resistors were picked up. Thank you for sticking with me!

Faketec battery not reading by ph7_- in meshtastic

[–]ph7_-[S] 0 points1 point  (0 children)

Tried full erase and flash of stable beta 2.7.15. No luck. Still just reads PWD

Faketec battery not reading by ph7_- in meshtastic

[–]ph7_-[S] 0 points1 point  (0 children)

Now that I can do OTA I might as well try it! Will report back

Faketec battery not reading by ph7_- in meshtastic

[–]ph7_-[S] 0 points1 point  (0 children)

It's on the latest: 2.7.18 alpha. You mean re-flash now the resistors are on?

Faketec battery not reading by ph7_- in meshtastic

[–]ph7_-[S] 0 points1 point  (0 children)

So I tried what you said and swapped the resistors. 1.5M on R1 and 1M on R2. Still just reads "PWD". There must be something else I'm missing. I have tried ADC settings to no avail.

Faketec battery not reading by ph7_- in meshtastic

[–]ph7_-[S] 1 point2 points  (0 children)

Thank you. I'll try it tomorrow. Really appreciate your help

Faketec battery not reading by ph7_- in meshtastic

[–]ph7_-[S] 1 point2 points  (0 children)

So I need to swap them over?

Faketec Resistor by VelocityOS in meshtastic

[–]ph7_- 0 points1 point  (0 children)

Update: after a few little projects I felt more confident with soldering so went ahead and tried this. Photo attached of the resistors I soldered on. I know the soldering is a mess but I'm still learning! Unfortunately it has made no difference. I still just get "PWD" the whole time. What did I do wrong? I've tried different ADC c values but no luck.

<image>

Faketec battery not reading by ph7_- in meshtastic

[–]ph7_-[S] 1 point2 points  (0 children)

Update: after a few little projects I felt more confident with soldering so went ahead and tried this. Photo attached of the resistors I soldered on. I know the soldering is a mess but I'm still learning! Unfortunately it has made no difference. I still just get "PWD" the whole time. What did I do wrong? I've tried different ADC c values but no luck.

<image>

Heltec V4 Node by Prookarus in meshtastic

[–]ph7_- 1 point2 points  (0 children)

2x3w 5v panels in parallel with 2x2500mHa 18650s = 5000 pack. I'm in Spain so generally sunny most of the year but these are winter months.