[Android Q&A, Help & Troubleshooting] Twenty-Three:
hi

you have to be running kitkat or earlier for these effects to not occur because this version and below didnt have the technology available then.. from my understanding.... the arabic code confuses the text rendering engine due to its marginal settings.. basically they stick malicious binary script or code in certain areas of the binary of the original character code. they then convert to utf 8 from binary. doing this you have incomplete or unrecognizable characters which the engine renders as null and parse as invisible characters. you wont ever see it. until you select all in the textview field. these characters you do see cause the text engine to try and render it. when viewing and then cannot parse it but the kernel runs it regardless underneath the security of the android layers, where the interpreter/ interpreter engine runs. that arabic and characters you do see are basically bull**** to distract you and also causes the engine to run certain parts of the code.. the arabic codes you see also have marginal settings that our en-us language can not understand and it causes it to flip it to correct itself and then tries again to run it.. this is causing your reduced performance..

you can cause a massive app failure by writing code as follows...

inside of this parent script with the marginal errors , you write the same exact code but with the correct ltr marginal settings.. by doing so, you now have created a mass confusion in the text engine because it corrects itself by flipping the parent string which causes, the child string inside, which was written correctly, to now flip backwards like parent script was. it reruns from the beginning , the parent script now readable to interpreter and the engine makes its way on to that child script... it causes confusion from its new marginal settings applied by the engine, from the parent flip process.... it then flips the parent or containing script to try and correct the childs error. this causes the parent script to now return to its original state and reruns the code... we are now back at square one. this process will cycle fast and will causes any application this script comes in contact with to fail due to it not being able resolve this failure. you can send these codes via sms and render anyone's messaging app useless and to crash upon opening it..this will happen until the sender of the code sends you a rescue message. something simple as a hi will knock it off the preview list of the sms app and stops rendering it because now instead of the code on preview list from sender, now sits the rescue message. a factory reset is the only other way to rid this issue... your possibilities are endless here in this case.. if the right activator characters are present, you can get any modern android to do wtf you want...with-in its capabilities of course. ive witnessed a script with variable after variable stacked inside and only becomes malicious when fully assembled. like pieces of a puzzle... variables themselves are not malicious and neither are their definitions. the script itself assembles these innocent variables like a puzzle and then it becomes malicious... at that point its too late.. if anyone would like examples of this crazy sht or if you need to educate me because errors in above text.. hmu i love to learn as much as i do educate...