Database Users

Senior Android Developer Wanted for TeamSpeak Voice Chat Project!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
COMPANY: TeamSpeak Systems GmbH, Germany
JOB TITLE: Exceptional, Senior Android Developer Wanted
NOTE: European residency required as you will be working with our Germany-based dev team. English fluency required. German fluency is ideal but not required.
HOURS: Full time preferred, part time will also be considered.
JOB DESCRIPTION:
We are looking for an experienced Android developer to create a mobile version of our popular, cross-platform client which is primarily used for voice chat (VoIP). You will have the opportunity to look at sample code for an already existing version of this mobile app (former developer code) which utilizes a client lib for most of its operational, non-GUI features. Our intent, however, is for you to recreate this app with a more polished GUI look and feel, in addition to adding numerous missing features which will bring the app up to par with its iOS counterpart.
RESPONSIBILITIES:
- Review and understand our existing Windows/Mac/Linux client-server voice chat product, how it operates, and what sorts of features and functionality our existing users will expect for its Android version.
- Work with our development team to determine initial set of requirements, and contribute ideas for improving the Android app's usability and overall user experience.
- Write clean, modular code to implement the desired requirements with little supervision, and submit periodically to dev team for review via subversion.
- Engage in primary, core testing of the app although our development team will also conduct some testing and report bugs/issues back to you as well.
- Work with our support team to document and fix bugs with reasonable turnaround. You will need to setup, manage, and maintain your own bug-tracking software (eg - Mantis or similar). Our support team will require access to this system and assist in reporting bugs and issues for you to work on.
REQUIREMENTS:
- You must reside in Europe since you will be working with our Germany-based dev team.
- At least 4 years in mobile development experience, with 2 years in-depth experience in Android development.
- Demonstrated track record for developing and releasing Android applications. You will be asked for sample work and code.
- Strong understanding of Android OS, developing in ADS, interactive application development paradigms, memory management, network programming, audio playback and microphone hardware integration, concurrency and multi-threading.
DESIRED QUALITIES:
- Strong interpersonal and communication skills.
- Ability to work within a small collaborative team and have a great passion in producing quality products.
- Demonstrated experience in working with others to solve challenging technical problems related to performance and usability.
- Self-starter with the ability to assess and resolve complex technical problems.
COMPENSATION:
You will be compensated as follows:
- A fixed, one-time fee to be paid in 3 parts.
Part 1 to be paid once the developer agreement is signed.
Part 2 to be paid once the initial, documented and agreed upon set of requirements has been completed.
Part 3 to be paid upon release of the Android app to the public.
- Ongoing percentage-based rev share based on actual (net) income received from app sales.
- Details to be negotiated and determined prior to hire.
Applicants should apply by submitting their resume or inquiry to the Business Development department via TeamSpeak’s ticket system at
http://support.teamspeakusa.com
Thank you for your time and consideration.

[Q] Kiwix (Offline Wiki Reader)?

It's in the Play Store now: https://play.google.com/store/apps/details?id=org.kiwix.kiwixmobile
but not compatible with the NST (requires Android 3.0 and up)
Is it worth uploading the apk here for folks to test with? Or is this simply a matter of hurry up and wait?
This is what I just sent to [email protected] :
I was ecstatic to see Kiwix in the Google Play store today. However, it showed as not compatible with my rooted Nook Simple Touch (NST). I was able to borrow a friend's Asus Transformer to install Kiwix to, then pulled the .apk from it and transfered it to the NST via a microSD card. Unfortunately, I got a "Parse Error: There is a problem installing the package" immediately upon attempting to install.
The NST runs Android 2.1, with an 800 x 600 display.
I am willing to beta-test any fixes for the NST. You will also find a vibrant user & development forum @ http://forum.xda-developers.com/forumdisplay.php?f=1198
Thank you so much for making Kiwix available on Android. I believe this could be THE killer-app for the NST hardware!
Click to expand...
Click to collapse

ChimeraPhone said:
It's in the Play Store now: https://play.google.com/store/apps/details?id=org.kiwix.kiwixmobile
but not compatible with the NST (requires Android 3.0 and up)
Is it worth uploading the apk here for folks to test with? Or is this simply a matter of hurry up and wait?
This is what I just sent to [email protected] :
Click to expand...
Click to collapse
I too got "Parse Error" while trying to install on a Gingerbread mobile (so that I can convert my old mobile into a offline wikireader).
Have you find any solution for this, if so please let me know. Thanks.

The dev replied, politely informed me not to expect a solution. However, in the meantime I found Aard Dictionary. It works wonderfully on the NST, and has much more recently updated Wikipedia libraries than Kiwix. Be prepared for a long wait to download the libraries, though, even on broadband.

ChimeraPhone said:
The dev replied, politely informed me not to expect a solution. However, in the meantime I found Aard Dictionary. It works wonderfully on the NST, and has much more recently updated Wikipedia libraries than Kiwix. Be prepared for a long wait to download the libraries, though, even on broadband.
Click to expand...
Click to collapse
Thanks a lot for your suggestion. I also found Aard interesting and have been using it as a dictionary on my Nook first edition e-book reader. But I missed its ability to work as an offline wikireader.
Currently I had downloaded the zim files of Kiwix (18GB), currently I will stick to it as I am near to my download quota for this month. Later (may be next month) I will download the aard dictionary files.
Btw I had successfullly installed jellybean on my old mobile (though some features like camera are not working) and installed Kiwix and using it.

For what it's worth, an aarddict dev stated a few months ago that he was considering a move to the .zim format (see this ) . I could only suggest contacting the dev for a status update. Perhaps he might have a beta you could test?
By the way, I am curious to know what .zim language/dataset is 18GB?

ChimeraPhone said:
For what it's worth, an aarddict dev stated a few months ago that he was considering a move to the .zim format (see this ) . I could only suggest contacting the dev for a status update. Perhaps he might have a beta you could test?
By the way, I am curious to know what .zim language/dataset is 18GB?
Click to expand...
Click to collapse
Thanks for the info, I will contact the aard developer.
Regarding the size of .zim in Kiwix, there are two types of wikipedia datasets
1. Non Indexed zim (10-11 GB)
2. Indexed zim (18-19GB)
In terms of content wise both are same (updated in 2012), but the advantage with Indexed zim is that it allows to search even in the content where as with Non indexed zim, it only allows you to search in the titles of articles (so size is less).
One advantage with Kiwix is it allows you to create indexing for non Indexed zim on your local machine, so you can save a lot of bandwidth.
What I found with the simple wiki (around 130 MB) file in Aard is that it also works similar to Non indexed zim (only searching in the titles). Please correct me if I am wrong ?

Aard allows to search inside each article in the newer versions. There is a dedicated search button when an article is opened.
I am trying kiwix right now and it seems to work pefectly. I will post if i encounter any problems.

shorty66 said:
Aard allows to search inside each article in the newer versions. There is a dedicated search button when an article is opened.
Click to expand...
Click to collapse
I love Aard, and today downloaded v 1.6.6.1 to my NST. I do not see a dedicated search button or any way of searching inside each article, nor is there a Settings or Options button.
Searching would be wonderful in Wikipedia and Wiktionary. Have I missed something?

Joydeck said:
I love Aard, and today downloaded v 1.6.6.1 to my NST. I do not see a dedicated search button or any way of searching inside each article, nor is there a Settings or Options button.
Searching would be wonderful in Wikipedia and Wiktionary. Have I missed something?
Click to expand...
Click to collapse
Might be, that this option is only avaible in android 4 and higher. The search button is accessed through the menu icon introduced with android 4.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Microsoft Talks Windows 8.1

Microsoft news
Winsupersite
Engadget
The Verge
In Blue: Business Features in Windows 8.1
In Blue: Bing Integration is the Marquee New Feature
Windows 8.1 to include native Miracast wireless display support and internet sharing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

As I've been developing for the Windows 8 Store, I am wondering what this update will mean for current apps, whether they will need to be recompiled or changed to work on 8.1. My app focuses on tiles, and it seems they have introduced new types of tile so it looks like I will definitely have to make some changes to it, plus they've added new snap sizes so that will probably require some more changes! I will be a bit annoyed if my app starts crashing because Windows keeps calling new routines which didn't exist when I created it, especially since not everyone updates their app or asks for support, they just 1 star review it instead.
I also wonder if this means they'll force apps like Metro commander out of the store because they do the same job their own new file explorer will do..

They will, undoubtedly, maintain backward compatibility with the existing apps (for an example of this, see WP7 apps pre- and post-Mango or WP7.8). However, you may need to update your app to get access to the new features.

8.1 is mostly a known quantity at this point, and whatever needs to be said about its merits has already been said. Public preview will hit Build on June 26. RTM should be out late Aug, in time for OEMs to validate it for Oct launch. Basically, same as last time.
More interesting of the "official" announcement is the reaction from the online crowd. Recent 8.1 pieces have had hundreds if not thousands of responses. While some of that can be attributed to the usual vociferous minority, it's safe to say that the "your Metro in my desktop" controversy that started with 8 won't end with 8.1, the Start Button half-step notwithstanding. If anything the half-measure likely adds to deepening fray. Even sedate and staid NYT/WaPo pieces generated considerable volume of comments.
In short, whatever one thinks of 8, 8.1 probably won't change his mind. It's more of the same. I personally welcome the boot-to-desktop, since Classic Shell in 8 still flashes the Start Screen for a split second before loading the desktop--an irritant. But other than that, and the patches roll-up, there's nothing in 8.1 that warrants interest for desktop users.
The missing Start Menu, being easily replaced, doesn't matter as much as the noise would warrant. But it is a rallying point for dissent, a showpiece of MS' perceived heavy-handedness and cluelessness. I empathize with MS' intent to "stick to the plan" to push Metro, but I think whatever benefits gained from getting users acquainted with Metro is at this point outweighed by the growing user resentment. It's a PR thing.
Controversy aside, 8.1 should do better than 8 because the environment will be better. Touch PCs will be cheaper. The hardware will be faster (Bay Trail), and with longer batt life (Haswell). I don't think 8.1 will do better by much, as tablets are coming on stronger than ever, and Win 8.1 still has no real answer to the tablet. Windows still needs a physical keyboard. Windows tabs will still be $300 and up--better than $500+, but still not price competitive with Android which has dropped way below $200 to $100-and-under. Walmart is selling $69 NextBook tabs, which have gotten 4/5 stars from buyers.
Ignoring both the hardware and price points for the nonce, it's a truism that an OS' role isn't to look pretty or to have this or that feature, but to run software. For MS to convert its desktop userbase to Metro, there need to be Metro equivalents to not just Android/iOS apps, but replacements to regular desktop applications, utilities, and games. Users need to be pulled with a carrot, not prodded with a stick. The problem is, there is no carrot.
Looking forward to Win9.

In Blue: Business Features in Windows 8.1
In Blue: Bing Integration is the Marquee New Feature
Windows 8.1 to include native Miracast wireless display support and internet sharing

OK, here is the best news yet for Win8.1: It will get a reduced footprint. No more recovery partition yay! Hopefully SxS will die as well. I'm sceptical that 4GB cited is total space, although XP's size-optimized install was less than 2GB before MS went pig-wild with Vista.
Niehaus also told session attendees that Microsoft expects to have a reduced footprint size for Windows 8.1 as compared to Windows 8. He said the team has been working on removing old components, temporary files and improving NTFS compression to free up more space on users' machines. He noted that 4 GB of free space will be needed to install the Windows 8.1 preview builds. And he said that installation of Windows 8.1 will not result in the replacement of the recovery partition in Windows 8.
"If you deleted it, [8.1] won't replace it," Niehaus said.

Windows 8.1 Boot To Destop Option And Other Start Screen Settings

[XAP APP] Process Viewer

This program is found in the depths of the internet, and would like to share with you, because it deserves attention.
I hope the author will not be offended.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
View attachment Process.Viewer.WP8.xap

spavlin said:
View attachment 2635723
Click to expand...
Click to collapse
So nice . well done .
no Interop Unlock Needed and works very smooth and very fine .
Tested on Lumia 920 RM-821 .

Whoa, very cool! Mind sharing the source, or at least the technique used? I tried this months ago and concluded that apps could only see processes running in their own chamber. Even adding ID_CAP_FOREGROUND_TASK_MANAGER only helped a little (let me see the debugger when it was running, not much else). You managed to get a *ton* of info using only completely ordinary capabilities, and I'd really like to know how!
Thanks for sharing the app, though.

Oh, and however you're managing to open handles to system processes, how much access do those handles have? In particular, can you use debug APIs? I really doubt it, but it's totally worth trying... because if it is, we've got arbitrary root.

GoodDayToDie said:
Oh, and however you're managing to open handles to system processes, how much access do those handles have? In particular, can you use debug APIs? I really doubt it, but it's totally worth trying... because if it is, we've got arbitrary root.
Click to expand...
Click to collapse
reker written this programm)

...:laugh:

Working with my Lumia 925 :good:

Long time i've not been around, and suddenly found this really interesting thread (i'm playing with a lumia 920) i've been able to rebuild the application (generate source from xap) and found some interesting things, there are 2 dll that contain the process tools, one wrapper for them and one dll that is used to "protect" the application:
Win32ProcessWrapper_RT.winmd: wrapper for: WP8ProcessUtils.dll and WP8NativeShellHelper.dll
Win32ProcessWrapper_RT.dll : checks for the publisher id and application id (without that, it disables the dll call's
But the really really interesting part is that there are some functions not added in the wrapper but available on the WP8ProcessUtils.dll, not sure if it's due to elevation required or maybe for another reason (as far as i can see it is able to gain access out of the sandbox so elevation should not be an issue, but who knows, i'm not an expert on that)
here are the functions inside the WP8ProcessUtils.dll
and as you can see, they are not present in the wrapper:
I've attached the VS solution reconstructed from the xap (code is not something to say "ohhh" but it works ), maybe someone can take a look and see if the wrapper could be rebuilt to use the missing functions.
Salu2!

Interesting! I'd looked at the exports, but I hadn't caught the same things you had. The WP8_* functions are odd; Win32 doesn't use the "FindFirst/FindNext" paradigm for processes, so far as I can tell. However this app enumerates processes, it's doing something funky. It doesn't even call EnumProcesses, not that this surprises me terribly (since that API won't return any processes outside your AppContainer). The presence of multiple Open* (as in, WP8_OpenThread, WP8_OpenThread2) functions is intriguing. One can safely presume that one of them is the standard Win32 APIs (OpenProcess, OpenProcessToken, and OpenThread are all imported from kernelbase.dll). The question is, what are the other ones? Even "guessing" process IDs doesn't let you use OpenProcess on them...
All the interesting stuff seems to be in the native code (no big shock there, really). Gotta get that source...

Apologies for failing to notice the bit about finding (rather than writing) this app. I've emailed the dev.

GoodDayToDie said:
Interesting! I'd looked at the exports, but I hadn't caught the same things you had. The WP8_* functions are odd; Win32 doesn't use the "FindFirst/FindNext" paradigm for processes, so far as I can tell. However this app enumerates processes, it's doing something funky. It doesn't even call EnumProcesses, not that this surprises me terribly (since that API won't return any processes outside your AppContainer). The presence of multiple Open* (as in, WP8_OpenThread, WP8_OpenThread2) functions is intriguing. One can safely presume that one of them is the standard Win32 APIs (OpenProcess, OpenProcessToken, and OpenThread are all imported from kernelbase.dll). The question is, what are the other ones? Even "guessing" process IDs doesn't let you use OpenProcess on them...
All the interesting stuff seems to be in the native code (no big shock there, really). Gotta get that source...
Click to expand...
Click to collapse
You are right, there is some sort of "voodoo" hidden in that dll, but based on the level of "protection" the application has (for a lack of other term) i'm not pretty sure the dev would be willing to release that portion of the code (he wrote one wrapper to interface a dll that checks developer id in order to allow the app to use the exports, too much work for something that you are willing to release, and also a very good strategy to prevent MS/Nokia to patch it)
Maybe our best shoot is with someone with better ida - hex ray experience (for sure any experience is better than mine )
Cheers
---------- Post added at 03:47 AM ---------- Previous post was at 03:34 AM ----------
GoodDayToDie said:
Whoa, very cool! Mind sharing the source, or at least the technique used? I tried this months ago and concluded that apps could only see processes running in their own chamber. Even adding ID_CAP_FOREGROUND_TASK_MANAGER only helped a little (let me see the debugger when it was running, not much else). You managed to get a *ton* of info using only completely ordinary capabilities, and I'd really like to know how!
Thanks for sharing the app, though.
Click to expand...
Click to collapse
Btw, as i said, i'm not an expert on wp applications (just got the wp8 a couple of weeks ago) i've tried to add that capability on the application but says "invalid" is there other way to add it besides WMAppManifest? (additional files, etc.)
Thanks!

No. You can use it on capability-unlocked phones, but not on standard dev-unlock.
I'm not great with IDA but I can use it. It'll just take longer :/
Pretty sure most of the code isn't that exciting anyhow - I've written apps that get all that info once given a process handle - but getting those handles (to anything but your own process) is the hard part. We Shall See.

GoodDayToDie said:
No. You can use it on capability-unlocked phones, but not on standard dev-unlock.
Click to expand...
Click to collapse
I only have development unlock and the app worked on my WP8.1 Nokia.
GoodDayToDie said:
I'm not great with IDA but I can use it.
Click to expand...
Click to collapse
I'm good at IDA but don't know ARM assembly at all
GoodDayToDie said:
getting those handles (to anything but your own process) is the hard part.
Click to expand...
Click to collapse
Looks like to enum processes, this app just tries sequential process IDs, tries to open it, checks for status code.

Why snapdragon s4 has only 1.2 GHz clock??

What does that have to do with this thread, and why'd you post in a six-months-dead thread anyhow?

because i have joined, this forum 6 day ago

Experience with DUK-L09 Bootloader Unlock via Remote Services from Taobao

So recently, I was experimenting of having Linux network tools on to my old DUK-L09 and for sure those testing require me to get it rooted. After searching around on the XDA Forum, watching multiple YouTube videos, and those doesn't work at all. After some googling and thinking, I got to know that Huawei (honor was a sub-brand of Huawei during the release of this model) had no longer issuing bootloader unlock codes.
There are few options left for me:
1. Get to the local phone repair shop, and ask if they have the tools and knowledge to perform something like that ->
2. Try all available free methods (i.e boot-loader code brute-force)
3. Try some so called "paid" tools that look like a scam to me.
After failing on the 1st and 2nd options, it came to my mind that, if this phone is from Huawei, it might be available in the Chinese Market (it did, it is known as Honor v9). So after searching around, it came to me that this guy from Taobao that actually has the tools and technique to help to get it unlocked -> https://item.taobao.com/item.htm?scm=1007.13982.82927.0&id=617190382061&last_time=1631366110
After consideration, I've decided to reach him out and paid like around USD 7-8 ish to unlock my phone and it works. He have done it remotely through remote desktop access (was using some Chinese application known as Todesk) and we spend about 30mins on that.
Prerequisite:
- Install Todesk: https://www.todesk.com/
- For security reason, it works best for you to have a separated account for his usage (for some reason, it wont work if you are using VM) with cmd and grant admin rights on needed basis:
"net user username password /add"
- Active internet access
- A working USB cable
- A Taobao account -> https://world.taobao.com/
- That guy's url -> https://item.taobao.com/item.htm?scm=1007.13982.82927.0&id=617190382061&last_time=1631366110
- Google Translate
I am sharing my experience for those who need it, especially those who struggles after Huawei ended the Bootloader code release support. If anyone interested on this option, feel free to try it out on your own risk. If you are a mandarin speaker, it work best for you. If you are not one, well then you might need to struggle little to get the communication part done.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

hi
did this guy provide you with the unlock code ?
or did he just unlock it with out give u the actual code ?
thanks

For people who have troubles reading in chinese, here'a an alternative service but trusted I have tested previously +50432723033 worked me twice before, no issue so far

Mafworld said:
For people who have troubles reading in chinese, here'a an alternative service but trusted I have tested previously **Link removed** worked me twice before, no issue so far
Click to expand...
Click to collapse
I have removed the link from your post.
Once again, you are warned that linking to paid services is NOT permitted:
11. Don’t post with the intention of selling something.
Don’t use XDA to advertise your product or service. Proprietors of for-pay products or services, may use XDA to get feedback, provide beta access, or a free version of their product for XDA users and to offer support, but not to post with the intention of selling. This includes promoting sites similar / substantially similar to XDA-Developers.com.
Do not post press releases, announcements, links to trial software or commercial services, unless you’re posting an exclusive release for XDA-Developers.com.
Encouraging members to participate in forum activities on other phone related sites is prohibited.
Click to expand...
Click to collapse