If user is using default system keyboard input method, the committext() is called,
otherwise, the sendKeyEvent() is called instead. So it needs to be handled different way.
Also I still find no other way to send the meta key combination without using KeyEvent(),
and only one meta key is allowed to be combined at a time for now.
Whenever the device is reboot, the app can not receive the broadcast intent sent by sendOrderedBroadcast() immediately,
that broadcast intent is pending way a lot behind other broadcast intent.
The solution can be founded here -> https://stackoverflow.com/questions/44516173/broadcasts-are-delayed
Found out when nethunter app sending activity intent to nhterm, if nhterm is first opened by that intent sent by nethunter,
then all the next activity intent with the same action and category will not be process, as it's a android mechenism.
see https://stackoverflow.com/questions/3781182/activity-not-started-its-current-task-has-been-brought-to-the-front
The way I found to solve this issue is to added 'android:launchMode="singleTask"' to the corresponding activity.
To avoid errors when "data" is encrypted.
"data" should always be unencrypted but this change will make NetHunter
mostly work when decrypting "data" has been omitted.
Signed-off-by: Re4son <3520622-re4son@users.noreply.gitlab.com>
Closing the application on Android Nougat and older causes a null
pointer exception so we check if the NotificatiionManager Service
exists and start it if it doesn't
Define common properties at project level:
compileSdkVersion=28
minSdkVersion=14
targetSdkVersion=28
versionName="2019.2-rc1"
Downgrade gradle version requirements to 3.2
We can remove system symlink if we just add nethunter app folder to path. Will save a lot of hassle hopefully.
Signed-off-by: binkybear <binkybear@nethunter.com>
We can force the terminal to run busybox resize. I think this will reduce errors such as:
```
root@bacon:/ # 1;148R
```
because the app is running vice the bootkali script, which is where most of the errors seem to be coming form.
This requires busybox to be in the path…however if the user doesn’t have busybox then they can’t chroot anyways.
Signed-off-by: binkybear <binkybear@nethunter.com>