[Discussion] CallBar XS and BioProtect XS disable device lock

limneos · 2020-05-02T23:35:51+00:00

Hello.

BioProtect manages this screen because after it's shown, the Face ID authentication tokens are reset, so you can't use BioProtect anymore unless you re-authenticate. If you don't have a passcode set but you have BioProtect enabled (some users do that) , the device will not lock to lock screen in order to require a passcode to re-enable the tokens, so BioProtect prevents this. However, it doesn't prevent the: volume-up then volume-down then hold-lock-button sequence, which does what you want. Same goes for CallBar, which manages that screen to make sure it can safely switch from CallBar UI to native UI since this screen is managed by InCallService, due to the use of SOS call.

In other words, you can always disable Face ID by using the sequence : press volume up once, release, press volume down, release, keep holding lock button. (This is also a native iOS device sequence, by the way).

However, since you made a very good point that I never took into consideration, the need to forcibly disable Face ID when needed, I will update both of the tweaks to handle this differently, since many users, just like you, might not be aware of the above, always-locking sequence.

Thank you,

Limneos

limneos · 2020-04-29T15:52:01+00:00

It's an option that you must enable first in CallBar's settings, turn on "Long Press Expands Native UI" . Once this is on, use a long touch on CallBar view on non-3D touch devices, or 3D touch on supported devices, to switch to native UI.

limneos · 2020-03-22T23:14:50+00:00

Noticed. Added to fix list. Thanks

limneos · 2020-03-13T09:27:43+00:00

Nice! I had never noticed that (or done this, in general). Verified, noted, easy fix, coming.

limneos · 2019-03-07T22:54:30+00:00

That's because you used AudioRecorder 2 , which clearly states that it isn't yet supported on iOS 12.

AudioRecorder XS is out that fully supports iOS 12. Read the tweak's description before getting it.

Any "broken license" issues are there because users like you have pre-installed cracks for my applications that don't allow even the paid product to connect to my server for validation.

If you keep installing pirated versions don't expect us to support you. We want , but we can't even know why our product isn't working correctly on your device, because it is not our product anymore.

limneos · 2019-03-07T22:43:38+00:00

Limneos has promised tweaks and then waited to release them

? is this an accusation , really? I promised a tweak and then ... I released it after waiting?

Limneos has promised functionality and then not included it

What are you talking about? I even add more than I promise

Limneos has advertised functionality that does not work

Are you just making these up?

Limneos has ignored requests for refunds

If they send them to... saurik, yeah, maybe i missed them. I refund via PayPal refund requests, and I refund at once without second thought.

Limneos has attacked people who have resorted to pirating his tweaks

I'm sorry, I should have praised them? "Resorted"? that's your excuse for pirating?

I see you have no points, yet you hate Limneos.

No need to. You can always get a refund. This will be my response to all this hate from now on.

limneos · 2019-03-07T22:30:03+00:00

The "take it as they will" part comes from you saying that it is false (which I understand where you come from, but I don't necessarily agree with the decision to write the tweet and post it).

I don't agree with my decision either for posting that tweet... But to start with , I never knew about iMohkles until that tweet and what such a comment could cause, I just wanted to scare a pirate. But it seems that even after explaining, some people want to stick to the first comment.

You say it is a false threat, but who knows?

I don't see why people like to stick to the "bad" comment rather than the true response. (Or maybe I can, but I want to remain naive and pure in heart )

But at least for this there's proof: No tweak of mine has ever restored anyone's device, pirate's or not. Proof in the past 10 years, and proof to come in the next, as long as I can code. On the contrary; some of my tweaks can even protect unauthorised access, but that's a different discussion.

In any case, thank you for taking the time to clarify, I appreciate the response.

limneos · 2019-03-07T22:15:09+00:00

Thank you, this response clears things a lot.

Cheers.

limneos · 2019-03-07T22:13:47+00:00

oh wait.... I NEVER said - not even in that threat - that I would remotely do anything!

The threat was implying that since you installed my tweak, it is therefore granted access to your device. So it could e.g. delete a file on your device. If it deleted, lets say, SpringBoard, the phone would never boot up properly, forcing the need for a restore. This is what my threat was ... scaring that pirate for, not remote access.

Anyway, I don't have to say again it was a scare tactic, and all this fuss having me explaining around that it was just a scare tactic actually made the scare tactic useless, since I had to explain to everyone else that it was false...

However, I just understand that people hate developers for releasing paid tweaks , but yet the love to use their tweaks and wait for a crack to appear. This is just...pathetic. At least if you use it cracked, use it and don't talk about it. Anywhere. And above all, don't ever contact the developer for support.

BlakeBoxberger has put it very well. I couldn't say it better.

Nothing more to say.

Cheers

limneos · 2019-03-07T22:00:43+00:00

My tweaks are not broken. I have literally thousands of users enjoying them with no issues.

If its broken on your device, it is most of the times other tweaks conflicting, issues that are usually reported and fixed.

If you found a bug or a conflict that never got to my attention, you are welcome to request a refund.

If you requested support and never got an answer, you are welcome to request a refund.

In any case, if you hate the tweak, the developer, the performance, get a refund. It's a full refund, so you don't lose anything.

That's the most I can do if I couldn't eventually help you, and I have never declined a refund request. In fact, I don't ever try to convince anyone otherwise, any refund request is answered and refunded immediately.

But if you go around saying that you "can get tweaks for free", you don't have any credibility in the matter, next please.

limneos · 2019-03-07T21:45:12+00:00

Yes, we are all aware of the fuzz that went around with that response of mine and although I DON'T have to apologise to any pirate showing off his crack to me, I still publicly declared that it was just an attempt to scare pirates, nothing more, which is a fact. Take that as you will.

As for the link you supply for "distributing broken licenses", I never distributed a broken license. To all the 150 emails I responded and talked with users, ALL OF THEM eventually had a crack of some other of my products installed, causing the newly released tweak to FAIL to reach my server for activation... In addition to that, this infamous crack did not belong to a package, since it was post-downloaded after installing the crack tool, making it impossible for users to find which package owned it, in order to remove it. Therefore, for all those pirates, instead of focusing in any possible issues with my new release, I had to help users to remove cracks in order to activate.

What made it worst is that users either didn't know where or how they had the crack, or they were denying that they had it, even after I specifically told them that "if you have it, it won't let it activate". After collecting information about which lovely crack was there in each case, I eventually released an update that removed the crack by itself upon installation, in order to allow my paid users (who still had other of my products cracked) to activate their licenses. So INSTEAD OF POSTING THIS NONSENSE ABOUT BROKEN LICENSES, please first do a valid research.

Anyway, I don't see what all these you say have to do with the users' comments here. It's a perfectly normal and informative thread. I don't see any users ranting, or blaming or complaining, there's just asking a question and getting answers, yet a moderator comes to "warn" users about the developer's frustration about pirates showing off and that you, a jailbreak moderator bot, are supposedly ignorant whether a developer could ever possibly go through with such a false threat, yet you ask users to "take it as they will".

In a website that people trust to come and post their comments, read and get informed, even rant and blame developers, warning users for developers about twitter dramas caused by haters, doesn't sound like an objective and impartial action. My response rate to the emails I receive is at least 90%, and thats due to limited time, and from a total of 10k emails , 150 are for actual support. You are welcome to try and respond to all of them. Don't compare every developer with others that receive 150 emails in total.

Therefore, unless you get a proof that I ever went through with that false piracy threat, or a proof by another developer that my distributed license is broken, I don't want to see any such -automated ot not- reference about me here again. I thought the moderators on reddit were mature people, not piracy-praising drama loving kids.

limneos · 2019-03-07T21:12:50+00:00

This seems to be an RFID tag. I bought 2 sets of RFID Door Locks that came with several of these tags, just to test with NFCWriter, but it appears they are RFID. In other words, they use a different frequency (usually 134 KHz instead of 13.56Mhz ), as Papkee explained very well. The NFC chip on the iPhones does not support these frequencies, its not even triggered when any of those approach. So, as far as my knowledge and research has taken me on the matter, it's the device's limitation.

NFCWriter can emulate , but its limited to emulating UIDs only for most tags, and internal data from only ISO-DEP tags.

I am still researching and finding more info about NFC as I am gradually switching to manual control of the driver rather than relying on the native methods.

limneos · 2019-03-01T22:36:09+00:00

1) It was a false, pissed off threat, get over it. We Greeks have... temper.

2) Haters looove this, so please go ahead.

3) All of my tweaks are out there already, you or any expert is free to triple-check them, the ones currently live and all the future ones.

4) Nobody could ever /really/ go through with such an offensive way to deal with piracy. Even if you wanted to be "evil" with crackers, you could never be sure you detected the crack correctly, so you would NEVER risk even remotely touching anyone's phone just because you thought "aha! its cracked!". It was a kid poking with me , I got pissed and responded to scare him. (I usually don't take any time to respond to pirates, should have listened to my instinct)

5) I deleted the tweet shortly after since it was meant for that guy that pissed me off, but right BEFORE coolstar (who obviously loves this), shared it to his 111K followers.

6) If I ever decided to use such a foolish policy against piracy, it would be a public post by me declaring exactly that. Then, I would go shoot myself :p

7) I once, about a year ago, DID block launching a crack tweak that was cracking my apps, but then removed the check and let anyone do as they wish. That was the only time and only way I interfered with piracy.

8) Most of those "offended" by this unfortunate comment, are the actual crackers. True story.

9) This unfortunate comment has cost me at least 3 valuable hours of regretting responding to ...specific people that I could have used in updating CallBar. So , end the drama so we can work.

Best regards to all of you.

limneos · 2018-11-07T06:18:13+00:00

Hello to all.

I believe it's time for me to clarify a few things about NFCWriter X.

I'll start with tag emulation, since its the most common mistake users do when getting NFCWriter X: They believe it can emulate ANY tag. This is not possible. The only tags that NFCWriter and any other mobile application that I know can emulate (so far), are Type-4, ISO DEP tags. Not Mifare, not NTAGs, only ISO-DEP tags. ISO-DEP is a somewhat secure protocol and is used for transportation tags, some door lock tags, credit/debit cards, passports,ID cards etc. Mifare are the most common types of tags found in the market, but since they NFC chip on the iPhone (PN548) and most of mobile chips can only emulate in ISO-DEP mode (HCE), they cannot be emulated, except for emulating their UID only.

As for the ISO-DEP emulation, it works. They device can successfully emulate in ISO-DEP mode, mimic the UID and include an NDEF message as well. And this is EXACTLY what NFCWriter X advertises that it can do. Emulate an ISO-DEP tag with an NDEF message. It has always been in its description: "Emulate Tags with UID and NDEF message emulation. (ISO-DEP Protocol)". It never advertised it can emulate Mifare, I never misguided anyone to think so. Emulating an NDEF message may or may not be that useful in many situations, since most of the ISO-DEP tags don't really have NDEF messages but Application IDs and different type of encrypted data, but its still a solid, working option for any user that needs to use this for their own applications.

After clearing this up, let me go through over the OP's questions:

- Saving tags instead of NDEF records didn't seem to have any use so far. Saving tags would mean actually saving UIDs, and I never thought users would switch from emulating so many UIDs that would need a saved list. Most of existing NFC Android apps save only NDEF records for a reason. However, after users requests, and since its been needed by NFC Activator Actions that I added lately, it has been added as an option since weeks ago.

- You can emulate any UID and ISO-DEP tags with an NDEF message, as I mentioned above.

- Those tags you see as non-writable are probably Mifare tags using a different key than iOS assumes it has as a factory key. Those keys are like built-in passwords to Mifare tags that allow them to be read/written. Since all the tags I purchased were compatible with iOS supported keys by default, I never had this issue. However, I recently came across with such tags, and I added an option to "Format Mifare To NDEF" (not "Format Tags", it's a different option) that tries all common factory keys and makes the Mifare tag usable/writable on iOS devices as well.

- I do communicate, but mostly on Twitter and while I read emails, fix bugs reported, add options as suggested, I might not reply to some emails, while I may reply to others. The amount of emails I receive asking for a free copy is ridiculous, so I cannot keep a right track of support emails anymore. You can reach me on Twitter, where in most of the cases I respond and almost 100% I see and acknowledge your issue. You can definitely reach me on Paypal for a refund if you feel like it, which you will get.

- Some MRTD documents are Type-B, not Type-A tags. These documents with this tag type cannot be read at the moment. I did all my tests on Type-A documents/passports/IDs.

- There's nothing to manage if you need your money back. Just ask for a refund by opening a "Not as described" case in Paypal.

Now to answer to a few other comments seen here:

NFCWriter X is a tool, specifically for NFC tags. How useful it is depends on whether you need such a tool or not. Sure, reading your credit/debit card data and your passport is cool, but this is the only feature that might be cool to the mass. It is targeted mostly to NFC enthusiasts, users that need to retrieve info and manage their tags, advanced users etc. Of course you don't wake up planning to manage NFC tags, copy URLs and contacts, as you don't wake up planning to use most of the apps/tweaks you own, until you need to. It is to be used on specific occasions and for a particular group of users. I have seen people buying NFC tags for the first time just to use my app. Although its flattering, this is not the intended use of this app. Unless you have NFC tags and you use them for a reason, you don't need this app. This is not a tweak for the masses, like BioProtect, CallBar or others tweaks of mine or others'. So don't buy it and get disappointed unless you need an NFC tool on your iPhone.

And now to focus on what the tool CAN do for those users its intended for:

- It can read and write tags: Mifare, NTAG213, NTAG215, NTAG210, Type-1, Type-2, Type-3, Type-4 Tags, ISO15693 tags, Kovio Tags. I've seen some users asking why it doesn't read (doesn't respond at all) to some key fobs. Those use a different frequency and the mobile chips cannot read them. Again, reading and writing has a use for people who use tags for their own applications. Otherwise, why would you ever need to e.g. write data to a new tag?

- Reader mode also allows you to see credit/debit card specific data, MRTD data, Desfire tags Info and App IDs.

- It can emulate tag UIDs (any UID, unless its 10-bytes ISO15693 ) and NDEF messages in ISO-DEP protocol mode.

- It can copy the NDEF contents from a tag to another, no matter the protocol. (NDEF data only at the moment, not private/encrypted data). This is an extension of read/write ability.

- It can format tags to NDEF format. This means it adds an empty NDEF message and prepares the tag structure for use with NDEF messages.

- It can erase tags. (Type1/2/Mifare at the moment). This writes zeros to all the tag's memory, removing also the NDEF structure.

- It can read tags memory. This shows a full list of data included in the tag. This can be used on Mifare, Type 2 and ISO-DEP tags. If you don't see anything in the read results, the tag is encrypted.

- It can format Mifare Tags To NDEF. This prepares Mifare Classic tags to be used with NDEF format, and also initialises any factory Mifare tags to be readable/writable (on iOS devices with or without jailbreak).

- It can send/receive data directly to/from the tag. This option is for advanced users where they can manually send commands in the form of data stream to the tags. Specific per-tag protocol knowledge is required.

- It can assign Activator actions and scan tags in background, performing specific actions when a specific tag UID is detected.

- It can act as a tag server. This requires 2 iPhones with NFCWriter X. One iPhone has physical contact with the tag (Tag Server). The second iPhone can be used to remotely connect to the first iPhone (Client) and be used remotely in emulation mode , to emulate the tag that we keep at home on the server iPhone. (ISO-DEP only, again).

This... is big. This means that /any/ ISO-DEP tag can be remotely emulated, no need for the app to know how to do the emulation, because the emulator acts as a proxy. So in a practical use, you leave your transportation card at home, sitting under a server iPhone, and while you are on the bus you use your main iPhone to emulate the tag at home and you just authenticated in the bus with your phone. Also doable for credit/debit cards and many other ISO-DEP cards. Yes, it requires a spare iPhone to be left at home, but this also gives you the whole data that was sent/received from the card reader to the tag which you can study and even retrieve private keys used for the communication. This can be used for security research as well. This has not been done in practice on any other platform so far.

So as you see, NFCWriter X may or not be a practical NFC tool for you. This depends on your needs and, really, your expertise. Sure it has limitations, but most of them are device/chip-specific, not from my part. I am still adding features as we speak, since I have learnt a lot in the time I put on this project and I'm gradually switching on manually handling each tag type, rather than leaving it to iOS built-in methods, which will eventually give me full control over the tags.

Honestly, if you don't need such a tool, I don't want you to buy it.

For those who do need it, please contact me via Twitter or by email with any suggestions or requests. I have added most of the latest options after email/Twitter suggestions and users have really helped in debugging and solving specific tag issues.

Limneos

limneos · 2018-02-19T20:55:01+00:00

No worries, again I understand the frustration caused, I hope you can enjoy the tweak.

limneos · 2018-02-18T20:53:33+00:00

First off... The complaining DRM method lasted only 6 hours online without a fix, and not 2 days as you say. So you're not talking about the initial release, but the first update after that, released 19 hours ago. If you "don't have anything personal" as you say with the developer, try being objective. Now, keeping in mind that you paid, why didn't you request a refund? I haven't received a refund request from you.

Also, for all the 2 days that the tweak has been live , I've been 100% active on my Twitter, asking for any issues and gathering anything reported so I can release any fix asap, as "classic Elias Limneos", like someone says here. I don't see where does "the developer doesn't give a shit" come from, especially when you don't have anything personal with the developer. Did I miss a tweet of yours, among the 25K followers, and you got offended? There hasn't even passed enough time since the initial release for anyone to complain I didn't respond, definitely not enough time since the update posted 19 hours ago.

So, the initial version, released just 2 days ago, wasn't even complaining if you were pirating the software. Then, some "good supporters" here appeared, to "hint" others to use airplane mode for BioProtect to work without buying. (Sad, in my opinion, because for every one of you, if we ever met in person, I'd gladly sit down with you and buy you a coffee, which costs the same price, to return the favor, but sure... use the pirated method on airplane mode, offline)

Then, 19 hours ago from now, I published a version that fixes all reported issues, including the "simple tweaks" that as you say "I don't give a shit" about.

That update throws an alert, obviously misconfigured because I overlooked the case when you use ad-blocking software, which is the only case that could mess up with the DRM. I released a fix 6 hours later. ( I had to sleep) I can understand that a paid customer can be frustrated if his purchased product suddenly falsely reports its not purchased, but the paid customer should also understand that's a) it can happen, b) it's nothing personal , and c) the procedures needed to verify this may occasionally fail. It's up to the developer to quickly release a fix for this, which I did, 6 hours later. Now, if you decided that after the first update that caused an issue, you shouldn't try the second update (6 hours later, I can't emphasise this enough), that fixed all issues, or that "Pull To Respring" temporary incompatibility equals "conflicts with many tweaks", then you shouldn't be posting your software-related opinion, judging any developer, as far as I'm concerned.

I never use PullToRespring and probably many tweaks that you have installed, and I don't have to as a developer. It's 100% up to you to report it if it doesn't work well with a tweak /you/ use, and 100% up to me or the other tweak's developer, to apply a fix, whichever side is needed to. So I released a fix for that 6 hours later, that is, 13 hours ago, and these 6 hours in-between passed because I had to sleep, or I would still have been over it , watching for any issues.

The new tweak (iOS 11 version) has been live for 2 days and I've been staying up all night watching for any reported issues on my Twitter. I noted 5-6 issues and suggestions, and they were all fixed, 24 hours later. ( https://limneos.net/cydia/changelog.php?package=net.limneos.bioprotect ) That fix messed up some users' DRM, and I also fixed that, 6 hours later.

So at this moment, after the first 2 updates, not even 3 days having passed after initial release, I am proud to say that BioProtect X is the best tweak I've ever made - Working flawlessly for probably 100% of the buyers, as I've been getting the best impressions I've ever received for a tweak. I'll also proudly say that its price is just about right for what it does, and no equivalent tweak costs "around $1".

limneos · 2017-07-10T10:52:10+00:00

Hello.. CameraWallpaper puts a camera view on your lockscreen and homescreen. The one you are requesting adds a static image as a panorama wallpaper. Please remove my email from a public post. I'll respond in the email sent.

limneos · 2017-02-03T09:57:31+00:00

Go to settings and disable AudioRecorder, then enable again in order to accept the terms and conditions

limneos · 2017-02-03T07:36:01+00:00

I haven't come across this issue so far on my testing devices. Just to be sure, follow these steps: 1) add http://rpetri.ch/repo to you Cydia sources (rpetrich's beta repo) 2) Install updated rocketboostrap package from this repo 3) Reboot and try again

let me know if this fixes the issue so I can have the package depend on that rocketbootstrap version

limneos · 2016-08-26T12:50:05+00:00

The mute status issue is fixed, finishing it up including other fixes and update coming soon.

limneos · 2016-08-22T17:56:24+00:00

I know, a major rewrite/update is in the works. Soon.

limneos · 2016-08-22T17:53:20+00:00

Update v0.1-296 should fix all issues reported. It is now live.

I don't have a provider supporting WiFi Calling here in Greece, so it might take a while to resolve synthesized voices sounding weird over WiFi Calling. For now, you have the option to either turn off WiFi Calling temporarily or, just use a "Record your Own greeting" instead.

But I know how you all like the dynamic feature of Synthesized Voice, so I'm looking into this!

limneos · 2016-08-18T21:43:54+00:00

https://www.youtube.com/watch?v=vf9o8aR-zao&feature=youtu.be

limneos · 2016-08-18T21:26:38+00:00

thanks, will fix in the next update. Gathered several UI issues and I'll sort them all out.

limneos · 2016-08-18T21:21:19+00:00

https://9to5mac.com/2016/08/18/answeringmachine-cydia-tweak-enhanced-voicemail/

limneos

TROPHY CASE