yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] DecryptoApp:
Hello everyone! I am a Belgian developper and I want to share with you the first app that I developped: Decrypto.

ABOUT

Decrypto is an application that provides a range of encryption and decryption tools.

Over 15 traditional ciphers are implemented and I hope to be able to add others to the application in the future.

An explanation and a short history are provided with each type of encryption to better understand them.

CIPHERS

- Cesar code

- Binary code

- ASCII code

- Numeral code

- Roman code

- Reverse code

- Morse code

- Vigenère code

- Latin alphabet

- Atbash code

- Affine code

- Rotation code

- Playfair code

- Polybius square

- Base64 code

- Scytale code

- Rail Fence code

- AES code

- Charset encoding

- Pigpen code

FEATURES

- Automatic decryption: If you have an encrypted message, but you do not know the type of cipher used, the application can try to decipher the message for you! Indeed, a tool allows to test all the different types of ciphers and display the possible results based on a dictionary.

- Frequency analysis: A frequency analysis tool for an encrypted text is also available. You can know exactly the number of occurrences of each letter in the encrypted text in a few clicks. Even better, the application can perform a frequency analysis and replace each letter of the encrypted message by the most likely letter!

- Share messages: You can also save your encrypted messages to view them later or share them with your friends!

LINK

https://play.google.com/store/apps/details?id=info.valky.decryptor

Every feedback and bug report is welcome ans I will try to answer as soon as possible :)

If you want also to find some other ciphers in the app that are not currently implemented, don't hesitate to ask and I will try to implement them!
[Android Apps and Games] Salman Al-Badgail:
User finding problem in opening url plz select below url for apk-Play store

https://play.google.com/store/apps/details?id=info.valky.decryptor
[Android Apps and Games] DecryptoApp:
Thanks for posting the link! :)

[Edit]

Now the link is correctly displayed in the app description.
[Android Apps and Games] Idoo05:
Really a great job ! :D

I often need to decrypt small messages that are encrypted thanks to some of the ciphers that you propose.

However I don't see the ROT13 cipher. Is it possible to add it to the app? :)

And what about the new types of encryption that are used today?

Because the ciphers that you propose are very old for most of them.
[Android Apps and Games] DecryptoApp:
Thank you for the feedback! ;) :good:

Indeed there is no direct button to the ROT13 cipher. However the Rot13 is nothing but the rotation cipher with an offset of 13. :)

So in fact you can use the ROT13 cipher in the current version of Decrypto. But you're right I will add a direct link to the ROT13 cipher as this code is often used.

The type of ciphers used in cryptography today are not implemented because I developped the application to help people that encounter small crypted messages in some games or enigma.

It is thus often the old and more simple ciphers that are used :)

But if I receive multiple feedbacks that ask to add these types of ciphers I will try to add it shortly :)
[Android Apps and Games] Idoo05:
I didn't browse all the ciphers in details so i missed that we can simulate the ROT13 using the rotation cipher!

But again good job! :)

I will follow the future updates of your application :good:
[Android Apps and Games] DecryptoApp:
I am currently working on the addition of the ROT13 shortcut.

I also added the Rail Fence cipher in a recent update.

Again do not hesitate if you want to see other ciphers in the app ! :)
[Android Apps and Games] DecryptoApp:
New release

A new version of decrypto was released today! :good:

This update adds some recent ciphers such as AES or charset encoding.

You can also now decrypt messages encoded with the Pigpen cipher.

Every feedback about this update is welcome :)
[Samsung Galaxy Star] psych.half:
After maybe a month of working in the kernel.

I guess it's about time to release the kernel for testing.

Downloads in the second post are only there for easy follow ups.

Please read all the sections below before trying out this kernel first.

This kernel comes with absolutely no warranties whatsoever, period.

XDA:DevDB Information

This field is required., Kernel for the Samsung Galaxy Star

Contributors

psych.half

Kernel Special Features:

Version Information

Status: Testing

Created 2016-02-15

Last Updated 2017-10-12
[Samsung Galaxy Star] psych.half:
Downloads

Latest : kernel-mint2g-trilogy-stable-r10.zip

The latest version is tested to be booting on :

Stock JB4.1 with CWM 6.0.5.3 by [MENTION=7277635]dabakale[/MENTION]

CM-10.1 with Philiz recovery by [MENTION=6971798]medved197938[/MENTION]

CM-11 with TWRP 3.0 by me

If you are getting status 7 errors, while flashing.

Try with a different recovery, and if that doesnt help upload the /sdcard/liverepack.log along with recovery.log from your recovery.

Changelog:

==================================
r10 : Apr 7, 2016
- Added and fixed custom voltage control, It could be errornessly set lesser than 650mV.
- Added underclocking. Needs to be enabled manually, see post #
- Removed 1400Mhz and 1500Mhz frequencies, as it causes crashes on many devices.
- MTP should now work on both Stock/CM rom (needs testing )
- Fixed battery level getting stuck issue.
- Fixed brightness/constrast bug in stock ROM.
- Initial stable* release of trilogy version.
[Samsung Galaxy Star] psych.half:
Extra downloads

camctl : script to enable/disable camera for RAM
[Samsung Galaxy Star] psych.half:
How this thread is organized.

The OP has been broken down into sections. The first 20 posts reserved for info/wiki sort of.

So when things get updated/added it'll all be in the first few pages for everyone to see.

Each section will be short and to the point so you're having problem with one section.

And you're the type who just has to quote posts you might do so without getting on other people nerves.

And normally I just just ignore the forum's usual craptalks, but at this early stage of development, try to keep the noise minimal
[Samsung Galaxy Star] psych.half:
Let's make some things clear first.

This kernel is not for you if you want a stable kernel.

CM11 should already include the stable version of this kernel, so you should just stick to that.

This kernel is only for CM11. No other roms will be supported or even considered.

This kernel is higly experimental. Freshly made, straight from the lab.

So expect some breakage of functionality, random reboots, bootloops and explosions (unlikely, but I gotta cover myself).
[Samsung Galaxy Star] psych.half:
Flashing

The zip makes no backup of your current kernel as of now.

So if you wanna go back to shipped CM11 kernel you have two options.

i) Manually move the original modules to system and restore just the boot image from TWRP.

ii) Restore/flash the entire ROM.

As for flashing the zip, you should burn it on a CD, and choose boot from CD in your PC by keep pressing F10/F12 at BIOS screen.

Well no but, you should at least be familiar with flashing and backups.
[Samsung Galaxy Star] psych.half:
Breakages

Camera:

Well, it's due to updated ION drivers, which are not compatible.

In the meant time I have disabled memory allocation for camera.

Which should give some extra free memory.

If there's any other stuff broken here but not while using CM11 kernel.

Post it here instead of there. But not the stuff broken in shipped CM11 too.
[Samsung Galaxy Star] psych.half:
What are not bugs.

24mb of less RAM:

Linux ate the RAM, no really.. linux eats RAM http://www.linuxatemyram.com

Well it's due to enabling memory cgroups.

Android says keep it enabled for low ram devices.

As per https://source.android.com/devices/tech/config/low-ram.html

Also, see the below sections for frequency scaling
[Samsung Galaxy Star] psych.half:
Bug reporting

You know you won't get help the next time from a kernel dev if you give them a logcat.

So get the dmesg or no help for you.

And /proc/last_kmsg is not working due to ram console issues.

So if you're gonna be reporting random reboot issues, make it reproduceable.

And make it precise. If the issue is caused because you have installed, some 10 or 20 other mods.

Good luck solving it.
[Samsung Galaxy Star] psych.half:
What are in the kernel.

You get your usual stack of IO schedulers, governors, dynamics and mods. They won't be included in the change log below.

I don't even know what half of those are.

So don't ask me what/which one to use. See them for yourself.

You also get some usual tweaks, which can be changed with any kernel control app you like.

Same don't ask what/how to tweak.

If you want something to be added that you don't find. Let me know, and I'll see what I can do.
[Samsung Galaxy Star] psych.half:
Frequency scaling

Frequency scaling is already included from r3 onwards. So the previous instructions no longer applies.

The default min and max frequency is 1Ghz and default governor performance. ie. same as stock.

Any change to that is your own choice.

And your own loss if something goes wrong.

There are some limits to it.

i) It can be only changed 10 times a second, so it might cause lag sometimes.

So choose your governor and scaling wisely. Battery or performance. You decide.

Underclocking has been removed.

Going below 1000Mhz makes no sense, as the core voltage is the same.

There is no point in reducing frequency, if the power consumption is constant.

Overclocking has it's own section. See below
[Samsung Galaxy Star] psych.half:
Overclocking

First if you were using the older broken cpufreq driver and were in the impression that you were at 1.6Ghz you're gonna damage your device.

The driver written by me, really overclocks the cpu and the whole system, yeah mines fractured too. Nothing I can do about it.

So use at your own risk. And don't discuss about the safe overclocking frequency. There isn't any.

Issues caused by overclocking are not issues. or bugs.

I won't give you any overclocking advice. But here's one anyway.

Overclock only when necessary and do not keep the values persistent at boot, "Set at boot" in apps.
[Samsung Galaxy Star] psych.half:
Changes from stock:

A lot of thing has been updated, changed, modified. I will have to go through source again.

A short list of changes I can think right now will be posted soon.

- The you know, built with some GCC-5 Linaro toolchain and O2.

- Cherry picked upgrades from various kernel sources.

- Disabled a whole lot of Samsung debugging.

But there's more... see the Github repo.
[Samsung Galaxy Star] psych.half:
reserved
[Samsung Galaxy Star] psych.half:
#Reserved
[Samsung Galaxy Star] psych.half:
Source

kernel:

https://github.com/halfpsych/kernel_mint2g

cpufreq-driver: https://github.com/mint2g/kernel_module_cpufreq-driver
[Samsung Galaxy Star] psych.half:
Contributing.

Any contributions to both source and wiki are always welcome.

You can help fix typos or better clarify some sections or even help to write new ones.
[Samsung Galaxy Star] psych.half:
Credits

For bringing CM11 to this device

- corphish

- Dreamstar

- TeamButter

- All others involved in CM11 mint2g project

Initial testers and bug reports:

- Dark Knight Begins
[Samsung Galaxy Star] RJinxed:
Okay then :good:
[Samsung Galaxy Star] dabakale:
[MENTION=5925208]psych.half[/MENTION]

Sorry for wrong post

Please mention that it should be flashef with cwm

And i got a clue about the contrast bug

When phone gets booted the contrast will be normal and when i lock the screen, cpu will go to deepsleep aftergoing deepsleep if i unlock the screen it will be highly contrasted.

Thousands of thanks for ur kernel
[Samsung Galaxy Star] psych.half:
Alright, which version of cwm did you use?

Can you change the brightness from settings after that?

Or can you only change it by the terminal emulator method ..

I still think this is a ROM related issue, rather than the kernels
[Samsung Galaxy Star] RJinxed:
I remembered this issue on zapdos 2.0 before, but it was fixed in zapdos 4.0 and up.
[Samsung Galaxy Star] dabakale:
[MENTION=5925208]psych.half[/MENTION]

CWM6.0.3.7

And i can change the brightess from the settings still the screen looks colorless

Another bug in r9 is when i try to change the frequency or governer sometimes the phone is getting stuck and autometically rebooting.

---------- Post added at 06:02 AM ---------- Previous post was at 05:59 AM ----------

[/COLOR [MENTION=5925208]psych.half[/MENTION]

When i revert to stock kernel then there is no contrast bug .i m wondering how it could be possible
[Samsung Galaxy Star] RJinxed:
the rebooting only happens when you put the frequency to 1400 and 1500mhz but below that, you should be fine.
[Samsung Galaxy Star] psych.half:
[MENTION=7277635]dabakale[/MENTION]

I'm using the stock ramdisk from old boot,img . maybe the issue is there.. Can you upload your stock boot.img, I will use that and let's see if it makes any difference,,

And [MENTION=6749735]RJinxed[/MENTION] that happens when the clock is unstable, the system will halt.

I will increase the voltages for 1400Mhz and 1500Mhz, and you can see if it helps for you guys.
[Samsung Galaxy Star] dabakale:
[MENTION=5925208]psych.half[/MENTION]

It is basic kernel by corphish

When i use this there is no contrast bug
[Samsung Galaxy Star] BatDroid:
done
[Samsung Galaxy Star] dabakale:
Use philz recovery
[Samsung Galaxy Star] BatDroid:
+ BLK_SYSTEM=/dev/block/mmcblk0p21

+ BLK_KERNEL=/dev/block/mmcblk0p5

+ XTRCT_DIR=/tmp/xtracted

+ WORK_DIR=/tmp/liverepack

+ trap copylog_on_pre_exit EXIT

+ /tmp/busybox grep -o -E /tmp/updater .*

+ /tmp/busybox grep -v grep

+ /tmp/busybox cut -d -f 3

+ /tmp/busybox ps

+ OUTFD=24

+ /tmp/busybox test -e /tmp/update_binary

+ system_mount_check_rom

+ [ ! -e /system/build.prop ]

+ [ ! -e /system/build.prop ]

+ setup_workspace

+ /tmp/busybox rm -rf /tmp/liverepack

+ /tmp/busybox mkdir /tmp/liverepack

+ [ ! -d /tmp/xtracted ]

+ /tmp/busybox cp /tmp/xtracted/kernel /tmp/liverepack/kernel

+ getAndroidSDKVersion

+ /tmp/busybox awk -F = {print $2}

+ /tmp/busybox grep ro.build.version.sdk /system/build.prop

+ api=17

+ rdisk=/tmp/xtracted/ramdisks/ramdisk-17.cpio.gz

+ [ ! -e /tmp/xtracted/ramdisks/ramdisk-17.cpio.gz ]

+ /tmp/busybox cp /tmp/xtracted/ramdisks/ramdisk-17.cpio.gz /tmp/liverepack/ramdisk.cpio.gz

+ repack_bootimg

+ /tmp/mkbootimg --base 0 --pagesize 2048 --kernel_offset 0x00008000 --ramdisk_offset 0x01000000 --second_offset 0x00f00000 --tags_offset 0x00000100 --cmdline crappy samsung bootloader --kernel /tmp/liverepack/kernel --ramdisk /tmp/liverepack/ramdisk.cpio.gz -o /tmp/liverepack/boot.img

Segmentation fault

+ [ ! -e /tmp/liverepack/boot.img ]

+ ui_print FATAL: couldnt pack boot.img

+ [ 24 != ]

+ echo ui_print FATAL: couldnt pack boot.img

+ echo ui_print

+ exit 5

+ copylog_on_pre_exit

+ SD_PATH=/data/media/0

+ ui_print copying log to /data/media/0/liverepack.log

+ [ 24 != ]

+ echo ui_print copying log to /data/media/0/liverepack.log

+ echo ui_print

+ rm /data/media/0/liverepack.log

+ cp /tmp/liverepack.log /data/media/0/liverepack.log
[Samsung Galaxy Star] medved197938:
"The latest version ( r9 ) is tested to be booting on :

Stock JB4.1 with CWM 6.0.5.3 by [MENTION=7277635]dabakale[/MENTION]

CM-10.1 with Philiz recovery by [MENTION=6971798]medved197938[/MENTION]

CM-11 with TWRP 3.0 by me

If you are getting status 7 errors, while flashing.

Try with a different recovery, and if that doesnt help upload the /sdcard/liverepack.log along with recovery.log from your recovery"
[Samsung Galaxy Star] BatDroid:
twrp was failing to pack boot(as log shows).

philz did it
[Samsung Galaxy Star] psych.half:
Okay so here's an test build with the ramdisk from stock basic kernel.

[MENTION=7277635]dabakale[/MENTION]

If this doesnt fix the contrast issuse. then I dont know what will

[MENTION=6971798]medved197938[/MENTION]

Smartass and lulzactive should be selectable again..

[MENTION=7017727]Dark Knight Begins[/MENTION]

I guess maybe TWRP 3.0 is incompatible with older ROM's, I get no such errors on CM-11.
[Samsung Galaxy Star] dabakale:
Downloading will test

If it is not fixed give it up
[Samsung Galaxy Star] devilsam5:
somebody please check i think mtp usb media file transfer is broken again please help
[Samsung Galaxy Star] dabakale:
[MENTION=5925208]psych.half[/MENTION]

Tested the kernel and finally

Contrast bug fixed in this build

Thanks alot
[Samsung Galaxy Star] dabakale:
[MENTION=5925208]psych.half[/MENTION]

Please add underclock also if possible so battery will be saved.
[Samsung Galaxy Star] psych.half:
[MENTION=7277635]dabakale[/MENTION]

So no more constrast issue? Like I thought the issue is from other stuff and not the kernel..

Also I forgot to mention the test build

d has increased voltages for 1400Mhz and 1500Mhz, if anyone wants to test that.

And, about the MTP, it's either works on stock or CM.

I took a look at it, and looks like it can be built as a module..

If it builds I can probably write a script to detect ROM and load the correct one.

But I have no way to test it, also I might need to change some other parts of kernel.

So I will need logs for both stock and cm.

Or someone flip a coin and decide: stock or cm.
[Samsung Galaxy Star] dabakale:
[MENTION=5925208]psych.half[/MENTION]

I increased the frequency to 1.4 &1.5ghz for about 15 to 20 sec

The phone started lagging, kernel control app force closed and system ui crashed but did not reboot i revertback to 1.3ghz
[Samsung Galaxy Star] psych.half:
[MENTION=7277635]dabakale[/MENTION]

I had removed, underclocking because therotically it didnt make sense to lower the clock freqeunices.

In any case,

If someone wants to experiment with underclocking anyway.. the below zip should give upto 100Mhz.

Going below 600Mhz lowers down the RAM speed so much that everythings in slow motion,

And no that is not a warning, I'm..
[Samsung Galaxy Star] BatDroid:
will underclocking increase battery??

what about mv?
[Samsung Galaxy Star] RJinxed:
I don't know much about kernel stuffs but I realized that the game freezes only appears in the kernels that has freq scaling and CAMERA FIXED.

I never experienced those freezes in the kernels that has freq scaling and BROKEN CAMERA.

I don't want to pressure you to do a build, you've done so much for us. I just wanted to share what I noticed. My only question is... is it connected or something, or my observation doesn't make any sense? (I won't get offended since I don't have any clue about kernels)
[Samsung Galaxy Star] psych.half:
[MENTION=6749735]RJinxed[/MENTION]

Well, maybe because the Camera Broken has more RAM? Anyways you can disable camera from version r9 onwards,

You can try see if it makes any difference.. If it doesnt I look into some commits before r8, since from r8/r9 it's s just a stock upgraded kernel..

So I made some changes camera/enable disable script..

The name changed to "camctl" . And the controls are "kill" and "revive" to well, kill and revive the camera.

Yeah, it's still a script not an app, but I added some witchcraft to it if thats any consolation.

If you dont know what it does yet, it allows you to disable camera to get more RAM at the cost of losing your camera.

But you can change this with a reboot, so you can get the camera back again. Hence the new control names "kill" and "revive".

Download's in the 3rd post and it's available as a flashable zip now.

Ofcourse you will need an terminal emulator, and need to type su before. Then typing,.

camctl

should print an how to
[Samsung Galaxy Star] RJinxed:
it keeps telling me to unlock root powers even though I already entered su

---------- Post added at 06:48 AM ---------- Previous post was at 06:45 AM ----------

nevermind. manually did it by editing the control file in sys/kernel/nocam/
[Samsung Galaxy Star] psych.half:
Uhh., whats the output of the two commands

sh -x /system/xbin/camctl
which id

I'm guessing busybox is not installed..
[Samsung Galaxy Star] RJinxed:
[MENTION=5925208]psych.half[/MENTION] hey dude. apparently, my "theory" was right. im not sure how or why but the camera IS the one causing the touch freeze

---------- Post added at 08:00 AM ---------- Previous post was at 07:57 AM ----------

Usually, at about 5 mins of gameplay, I should be scratching my head and stare at my non responding phone. But now I disabled the camera, I've played for about an hour now and still no freezes.
[Samsung Galaxy Star] psych.half:
[MENTION=6749735]RJinxed[/MENTION]

Well, disabling camera also disables hw overlays actually, which is used by hwcomposer.

You could try "Disable HW overlays" in Developer Options while camera enabled and see if you still get freezes.

But I think the bug is in the hwcomposer from cm-11, as it's from other device.

If anyone on stock and cm10.1 can confirm, that hwcomposer dont break while camera is disabled. I will remove the hw overlay which should also give 10MiB more memory with camera enabled.

[MENTION=7017727]Dark Knight Begins[/MENTION]

A quote from this non-techinal friendly article, The truth about kernels and battery life

"I remember working on msm8960 devices that used the same voltage for every CPU frequency. In a case like that, undervolting could make quite a difference. "

Since, our processor can also run different frequenices at the same voltage, underclocking wouldnt make much difference in power consumption cause it scales linerally with frequency and exponentially with voltage.

As of undervolting, we're already at 650mV min limit, which is a hardware constraint.

So anyways, if people wanna save maybe 16-20mins of battery, they can underclock.

I'm adding upto 400Mhz, underclock in the next release, but don't do it unless you really like things in slow motion.

And oh, speaking of battery I have added an hack for the battery glitch.

Which means percent getting dropped/stuck issuse should now be fixed.

I still havent looked at the charger not detecting issue sometimes, cause the code for it is overwhelming. But at least now, the percent should bump up, so you know it's charging,.

I have also built MTP as a module for both stock and cm rom's so hopefully, it should be fixed.

I cannot test them so this needs to be confirmed. [MENTION=7092738]devilsam5[/MENTION] I guess you are on CM rom, so you can see if it works there.

[MENTION=6971798]medved197938[/MENTION]

I can reboot to recovery on CM-11, I had already fixed this bug,. Can you reboot to recovery by:

su
reboot recovery

So far, I belive this will be a stable release for both stock and cm roms.

It will be coming in a few hours or days or.... months whichever comes first.
[Samsung Galaxy Star] BatDroid:
underclock is awesome though..

going down 400mhz causes some freezing problem. ..
[MENTION=5925208]psych.half[/MENTION]
[Samsung Galaxy Star] RJinxed:
Nope. Disabling HW Overlays isn't effective.
[Samsung Galaxy Star] psych.half:
Heres an test build with only hwoverlay removed but not camera.

If it doesn't freeze on this one, then issue is with hwoverlay.

And this also, got 400Mhz underclock when I built it, so check CPU settings before gaming..
[Samsung Galaxy Star] medved197938:
10.1 cm on all runs smoothly, thank you very much, you can not only increase the frequency up to 1400/1500 MHz, Bro You are the best)))
[Samsung Galaxy Star] RJinxed:
This one is both better and worse.

It's good cause... the freezes now only last for 1 - 3 seconds

It's bad cause... now the freezes occurs every 5 seconds.
[Samsung Galaxy Star] psych.half:
What happens on this one when you disable camera..

If it doesnt freze with that, then the issue might be a low RAM issue, then anything else,
[Samsung Galaxy Star] RJinxed:
doesnt freeze when camera is disabled.

Im sure it wasnt ram's fault cause in beta 3 and stock, it's fine.

I guess I'll just stick to disabling the camera.
[Samsung Galaxy Star] BatDroid:
test build seems pretty cool.

game performance increased upto 2x with overclock.

just tried vegas,fifa 15 and blic psp.