Database Info

[APP] Open Mobile Suite [PC Suite for your Android phone]

Open Mobile Suite
Technical preview now available!​After exactly one year I can present you the first technical preview of this application!
I'm sorry it took so long, but there were some major changes in the application (e.g. splitting it in several parts and using DBus as IPC framework)
{
"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"
}
You connect to your Android phone using bluetooth (Wifi and USB will be supported soon, it will also be possible to initiate a connection using Android Cloud to Device)
You can write messages to multiple contacts using the very innovative contact browser (with support for auto-completion).
Here are all informations of your contacts.
It's possible to edit your contacts (although this is currently not supported by the Android server application on your mobile phone)
File browser
Informations about your mobile phone
A chat window, like it's known by popular instant messengers
You get notifications about incoming messages
Management of your devices
Chat theme selection
Messaging statistics
You can find more informations on the Facebook page!
DOWNLOADS
If you're running Ubuntu there is a PPA available:
Open Mobile Suite - Technical Preview 3, Ubuntu PPA
You can get the source code and the Windows binars from here:
Open Mobile Suite - Technical Preview 3, Source
I'll be happy about any feedback!
-------------------------------------------------
Original post from 27th December 2010:
Hello,
I'm the maintainer of Series60-Remote, an open source Software Suite for Symbian / S60 smart phones. This application connects to a Bluetooth service on your phone and allows you to manage your contacts, calendar entries, messages and files from your PC.
A few days ago I got my first Android-based phone, a HTC Desire HD, and now I want to port the application also to this platform.
The server application on the phone is rather simple (you can have a look at the Python source file for the S60 platform[1]). It just responds to some commands from your PC (e.g. request the hash of the contacts).
So this would be a great chance to have a FOSS suite that runs on Linux, Mac OS X and Windows and supports Symbian and Android!
What do you think of such a project?
I've never used Java before so it would be great if anybody could help me with the port.
If you need further informations you can go to the project page: series60-remote.sf.net (when the port is ready I will rename the software to 'Open Mobile Suite')
Thanks for your comments,
Lukas
* Sorry, I'm not allowed to post links to external sites
[1] series60-remote.svn.sourceforge.net/viewvc/series60-remote/trunk/mobile/mobile.py?view=markup

Guess this post should be bumped.
FOSS Rulez
I have no idea about development but maybe someone can help.

Open Mobile Suite Technical Preview 1 now available! (see first post)

This looks great! I run OSX, so I'll have to try it out when the project gets that far. If you want a beta tester, just PM me =)
Sent from my Nexus 6 through tears in rain.

Great application, I've used it on my Lubuntu VM and it is running perfectly.
However, I installed the application from the Ubuntu repository you have created and it seems that it doesn't list python-qt4-dbus as a dependency as such errors are shown whenever you attempt to start it. After installing python-qt4-dbus it works perfectly although I would recommend updating the dependencies.

Anxiously waiting for a windows installer
Sent from my GT-I9100 using XDA App

AllSeeyinEye said:
Anxiously waiting for a windows installer
Click to expand...
Click to collapse
As far as I can tell it's fully Python powered, so it should be fairly easy to port although I haven't looked in great detail into it.

Holy cow! Exactly the software I was looking for plus more!
Will try it on my Lubuntu desktop. Not only that, now I have a use for my bluetooth-USB for my desktop.

When I try launch openmobilesuite-connectionmanager I get an error:
Code:
ImportError: No module named base.element.device
Similar with openmobilesuite-gui:
Code:
ImportError: No module named base.element.connection
Which packages are dependencies? I'm on openSUSE 12.1, Python v2.7.2.

LuHe said:
It'd be happy about any feedback!
Click to expand...
Click to collapse
Hi Lukas,
First of all many thanks for your work, I used every day Series60-Remote on my old Nokia, it was very helpfull!
I'm facing an issue to test OpenMobileSuite on my droid (Alcatel OT-990). I assume I've installed it correctly (from ppa on my Ubuntu 11.10) and openmobilesuite-gui is running well (see attached log).
The bluetooth device scanning can't detect my droid ("No devices found", see attached log), although it detects my old Nokia (N95 8GB, but I can't save its paramaters, see attached log) and my droid is well detected by a "hcitool scan" (see attached log).
Thanks for your help to solve it!

Hello,
at first I'd like to apology for my late reply, i didn't get mail notifications for this post.
nfcfx said:
When I try launch openmobilesuite-connectionmanager I get an error:
Code:
ImportError: No module named base.element.device
Similar with openmobilesuite-gui:
Code:
ImportError: No module named base.element.connection
Which packages are dependencies? I'm on openSUSE 12.1, Python v2.7.2.
Click to expand...
Click to collapse
You need to install all of this packages:
openmobilesuite-base-0.9.90.tar.gz
openmobilesuite-connectionmanager-0.9.90.tar.gz
openmobilesuite-connection-oms-0.9.90.tar.gz
openmobilesuite-connection-obex-0.9.90.tar.gz
openmobilesuite-gui-0.9.90.tar.gz
openmobilesuite-mobile-android-0.9.90.tar.gz
(the order is not important)
You also need to have PyQt4 (with sqlite database support), PyOBEX, python-dbus (with Qt mainloop integration) and pypluez installed, python-matplotlib is optional (sorry, i don't know the openSuse package names)
Shæl said:
Holy cow! Exactly the software I was looking for plus more!
Will try it on my Lubuntu desktop. Not only that, now I have a use for my bluetooth-USB for my desktop.
Click to expand...
Click to collapse
Hope you'll like it.
BTW: Wifi, USB and Android Cloud-to-Device connections will be added soon
Concrete Donkey said:
As far as I can tell it's fully Python powered, so it should be fairly easy to port although I haven't looked in great detail into it.
Click to expand...
Click to collapse
AllSeeyinEye said:
Anxiously waiting for a windows installer
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
The predecessor of this application, Series60-Remote, had binary packages for Windows. The only difficulty to port Open Mobile Suite to Windows is that D-Bus is now a hard dependency. Some time ago python-dbus didn't work for Windows, but I talked to the maintainer of PyQt4, Phil Thompson, and he said that it should work with its latest release. So expect the windows binary installer soon.
Concrete Donkey said:
Great application, I've used it on my Lubuntu VM and it is running perfectly.
However, I installed the application from the Ubuntu repository you have created and it seems that it doesn't list python-qt4-dbus as a dependency as such errors are shown whenever you attempt to start it. After installing python-qt4-dbus it works perfectly although I would recommend updating the dependencies.
Click to expand...
Click to collapse
Thanks, I really forgot this dependency (thought PyQt4 contains this package, like it's the case with Fedora). I'll update them for the next release.
jontornblom said:
This looks great! I run OSX, so I'll have to try it out when the project gets that far. If you want a beta tester, just PM me =)
Sent from my Nexus 6 through tears in rain.
Click to expand...
Click to collapse
Actually it should already work under OS X. You could try it if you're brave enough to install all dependencies using macports.
I'll try to make an application bundle soon.
eiric said:
Hi Lukas,
First of all many thanks for your work, I used every day Series60-Remote on my old Nokia, it was very helpfull!
I'm facing an issue to test OpenMobileSuite on my droid (Alcatel OT-990). I assume I've installed it correctly (from ppa on my Ubuntu 11.10) and openmobilesuite-gui is running well (see attached log).
The bluetooth device scanning can't detect my droid ("No devices found", see attached log), although it detects my old Nokia (N95 8GB, but I can't save its paramaters, see attached log) and my droid is well detected by a "hcitool scan" (see attached log).
Thanks for your help to solve it!
Click to expand...
Click to collapse
Support for S60 will be added again in the next release.
The bug for the undetected droid is actually in pybluez.
I could fix it some time ago (see this mailing list thread: https://groups.google.com/group/pybluez/browse_thread/thread/3606131e5e108cd0 ) and the bugfix is already in the SVN repository of pybluez and will be in its next release.
Thanks for testing!

Thanks for your answer Lukas, I've installed the svn version of pybluez and my droid is now indeed detected!
But I'm still facing the other issue I described: although it detects my phone I can't save its paramaters:
Code:
Traceback (most recent call last):
File "/usr/lib/pymodules/python2.7/openmobilesuite/gui/window/settings.py", line 475, in accept
if self.saveSettings():
File "/usr/lib/pymodules/python2.7/openmobilesuite/gui/window/settings.py", line 483, in saveSettings
self.database.deviceHideAll()
AttributeError: 'Settings' object has no attribute 'database'
How to fix it?

The settings window is not yet ported to the new framework.. the only way to add a new device is to delete the .config/OpenMobileSuite folder and re-run the wizard

Thanks, now I can add my droid to OpenMobileSuite.
Another issue: I launch the application on my droid, "Service is running", "1 active connection", I see the name of my computer and its bluetooth adress.
In my computer, OpenMobileSuite is updating contact list and stuck to 60%.
And now, force close of the mobile application: Sudden closure of the Open Mobile Application Suite (com.hetzenecker.openmobilesuite process). Thank you for trying again.
I've attached OMS'log on my computer, but not sure it'll help you, tell me if you need something else

Lukas ?

bluetooth device not found
i have installed OpenMobileSuite on my ubuntu 11.10...all the installation process went fine..and in Technical Information dialogue box it shows that all the plug-ins are installed perfectly..but i still having problem connecting my Samsung Galaxy Mini ( emanoN v4 2.3.6 ) to openmobilesuite...its continuously showing "no bluetooth devices found"..will somebody pls sort it out what should i do?

eiric said:
Thanks, now I can add my droid to OpenMobileSuite.
Another issue: I launch the application on my droid, "Service is running", "1 active connection", I see the name of my computer and its bluetooth adress.
In my computer, OpenMobileSuite is updating contact list and stuck to 60%.
And now, force close of the mobile application: Sudden closure of the Open Mobile Application Suite (com.hetzenecker.openmobilesuite process). Thank you for trying again.
I've attached OMS'log on my computer, but not sure it'll help you, tell me if you need something else
Click to expand...
Click to collapse
The contact sync will be rewritten in the next release, if there are still errors it would be great if you could get a log from the device (using adb logcat)

bijoy.panda said:
i have installed OpenMobileSuite on my ubuntu 11.10...all the installation process went fine..and in Technical Information dialogue box it shows that all the plug-ins are installed perfectly..but i still having problem connecting my Samsung Galaxy Mini ( emanoN v4 2.3.6 ) to openmobilesuite...its continuously showing "no bluetooth devices found"..will somebody pls sort it out what should i do?
Click to expand...
Click to collapse
This is a bug in pybluez, which i could fix in their SVN version. I'll include this in my PPA too

Windows Port finished!
(this means that i managed to build dbus under windows, including the Qt mainloop integration and the python bindings; more information about that is here: http://web.archiveorange.com/archive/v/2mxmYng5gCA0MCJamGh9 )

LuHe said:
The contact sync will be rewritten in the next release, if there are still errors it would be great if you could get a log from the device (using adb logcat)
Click to expand...
Click to collapse
Cool, tell me when it's ready I cannot wait to test!

[REQUEST] bt-info for android

Oh man, i had fun with this little piece of software in school with my old sony erricsson c510. my friend and me used to link our phones, hide it behind the board and activate the music with the other one xD. the teacher didnt knew what was goin on ^^
anyways, bt-info was a fun program and i searched the web for an android version of this. i alao tried to convert the jar file into an apk file. it worked but the software was incompatible. can anyone make it work on my samsung galaxy s2?
Would be awesome....

lol i remember that app back in the times... but it worked only with a few target phones, I remember always failing against Symbians, working on some LG and SE ( AT standard commands huh?).
Anyway, in my free time I'm playing with some Android scripting and I could sort something like this... you got any request for features ?
As of now I got a "talk server"... just run on the phone, connect to its IP from anywhere else (another phone, iphone, ipad, pc...) type something and the phone will say it you could prank as well with that, but there could be added other cool functions...
Think that could be done via bluetooth too, though haven't tried much the bt libs..
Let me know if that could interest you

ell3 said:
lol i remember that app back in the times... but it worked only with a few target phones, I remember always failing against Symbians, working on some LG and SE ( AT standard commands huh?).
Anyway, in my free time I'm playing with some Android scripting and I could sort something like this... you got any request for features ?
As of now I got a "talk server"... just run on the phone, connect to its IP from anywhere else (another phone, iphone, ipad, pc...) type something and the phone will say it you could prank as well with that, but there could be added other cool functions...
Think that could be done via bluetooth too, though haven't tried much the bt libs..
Let me know if that could interest you
Click to expand...
Click to collapse
It would be awesome if you could it even get to work! it crashes on my phone when i try to connect! i used a jar to apk converter ..... maybe not the best idea
the app is/was great just the way it worked! maybe wifi support... and dissable the code request-thingy when i try to connect to a phone - but i think that would be iligal...
but yeah ... if you can get it to work, you could sell it on the market! or publish it anywere else! im not the only one whos searching for that app working on android!

See, targeting new generation phones with that old bluetooth app wont be of any effect.... will just work on old ones.
Removing the "code thing" you say it's the pairing procedure of bluetooth, the standard authentication feature of bt, actually you can't get around it, and though it would be illegal, it would get you big money if you ever find how to
That app used pseudo-standard AT commands through the bluetooth modem interface of the phone, and that supposedly to issue an action on the phone (like push/pull contacts,sms,calendars, raise volume, set alarm....) but that was not implemented in all phones so most commands failed, but virtually could work with any target as long as it was bt enabled and paired.
TL;DR
Not worth porting bt-info. So, as it must be build from scratch, you can suggest some feature request

ell3 said:
See, targeting new generation phones with that old bluetooth app wont be of any effect.... will just work on old ones.
Removing the "code thing" you say it's the pairing procedure of bluetooth, the standard authentication feature of bt, actually you can't get around it, and though it would be illegal, it would get you big money if you ever find how to
That app used pseudo-standard AT commands through the bluetooth modem interface of the phone, and that supposedly to issue an action on the phone (like push/pull contacts,sms,calendars, raise volume, set alarm....) but that was not implemented in all phones so most commands failed, but virtually could work with any target as long as it was bt enabled and paired.
TL;DR
Not worth porting bt-info. So, as it must be build from scratch, you can suggest some feature request
Click to expand...
Click to collapse
would be nice if someone could 'rebuild' that app on android bases... hacking the bluetooth 'password-thingy'™© isnt a big deal! the app worked great without it!
My question: is it POSSIBLE to make that app for android with all the functions that it has? and make it work with android-> symbian and android -> android?

Man I've been looking and wanting this for my phone forever.
Evo 3D in full Affect with WTSB HYDRO SENSE 3.5

Q: is it POSSIBLE to make that app for android with all the functions that it has and make it work with android-> symbian and android -> android?
A: Symbians hardly support AT commands, you can try yourself using old bt.info or any other AT enabled shell to issue a command to a Symbian, I had no luck in the past. Android to android I dont know if it could be done natively (client on one phone, no server in the other) but it surely might be done with an app. To get a 100% compatibility there should be a client or a server installer in BOTH phones, UNLESS you find some AT command that would run on all (hard, as most vendors implement them differently).
I found this lil app that can give you an example, it's called "AT COMMAND TOOL" (google -> "sd.at.c8600"). It says it has presets for Huaweii phones, but that's the only supported. Anyway, looks like you can issue any command, but you have to find out WHICH one works with other phones !!
Google "at command list" and get the idea...
I haven't tested it, but looks similar to what you're looking for.
I remember using
Code:
AT+CNUM
to get the phone number via BT... that could come handy in certain situations

CWM recovery | Custom Clean ROM | Tweaks for Android watch phone Z1 (MT6516)

Z1 (brand unknown) is wrist watch phone with Android OS. It was first released in 4/2012 and it is Android 2.2.1. It has WiFi, AGPS, GSM/EDGE, 2 MP camera, mic, speaker, loudspeaker, capacitive touchscreen, display of 320x240, SDHC & SIM card slots etc.
As most Chinese phones it has SoC from MediaTek, MT6516 (armv5).
See my Czech review for photos: http://hodinky.blog.mobilmania.cz/2012/06/z1-hodinko-telefon-s-androidem/
Tweaks/tips for stock ROM (2.2.1)
Market/Google Play is missing in stock rom but it cam be added if you follow instructions on the page: http://www.ibuygou.com/p-z1_smart_android_2_2_watch_phone_gps_wifi_bluetooth_html-3638-usd.html (included in Clean ROM)
Default DPI is 120 however most controls are too small. Change it to 160 which will make all icons sharp. (included in Clean ROM)
Typing on tiny QWERTY soft keyboard is a pain, Flit Keyboard makes entering text much easier. (included in Clean ROM)
To enter engineering mode, dial *#*#8787#*#*
ADWLauncher EX works even better if you (see):
Disable all animations including scrolling homescreen
Disable dockbar and use swipe up instead (included in Clean ROM)
4x3 icon layout for home screen and 5x2 for drawer (included in Clean ROM)
Use something like Extended controls for toggles
Use No Lock if you don't need swipe to unlock feature.
Remove alternative Chinese markets and Chinese network account/sync providers from /system/app (included in Clean ROM)
Creating flashable dump
Use MT6516 BackUpTool for dumping your stock rom.
Use MTK_Rom_Studio_1.0.0a for converting dump into flashable format.
Flashing
Basically you need the driver: "MT6516_YuSu_USB_VCOM.inf" and flashing tool: "SP Flash Tool v1.1110". All tools can be found on the internet when searching for "MT6516 flash tools". The only necessary tools reuploaded can be found also here. (I'm not sure about the legality of these tools though.)
You have to use 32 bit Windows (I only tried XP in both VirtualBox and VMware but it could work with 32 bit Vista or 7).
Power off the watch, connect it directly to PC (no USB hub or extention cable) - new device will connect for few seconds - use it to install the driver. Unplug watch. (You may retry that few times because the watch disconnect within few seconds) Open flashing tool and select files to flash (I would recommend not to flash anything other than boot/recovery/system/data/logo), hit start and quickly connect the watch - flashing will start automatically.
Recovery
First build of ClockworkMod 5.0.2.8 seems to be working however all its features were not tested yet!
Recovery can be flashed with "SP Flash Tool" (use provided scatter file).
Rebooting to recovery from launched Android using "reboot recovery" works but I wasn't able to find working button shortcut to launch recovery directly from cold start. Please help me if you find a way!
Custom Clean ROM based on stock 2.2.1
Features
Removed alternative Chinese markets and Chinese (social) network accounts
Integration of Google apps (sync, Google Play, setup wizard etc)
DPI changed to 160 which makes the watch easier to control and the icons sharper
Preconfigured ADW Launcher, Flit keyboard
Includes root with Superuser, Busybox binaries
Minor clean-ups
So far this ROM doesn't include anything power user from XDA wouldn't be able to customize but this ROM is afford to save other users time with experiments.
Important notes:
Backing up your current ROM + data is highly recommended (use the above listed MT6516 BackUpTool)
The seller says you shouldn't do factory reset because of IMEI lost - I can't confirmed that - IMEI is kept even during factory resets so it doesn't seem to be stored in user data partition. BUT backup your current ROM anyway cause I might be wrong.
Clean ROM notes:
The first boot is slow. After the first boot, I recommend not touching the watch for 5-10 minutes because dalvik cache is rebuilding in the background and the setup wizard may lag a lot.
The default ADW launcher is configured to not have app drawer button - swipe up to open drawer
Known issue (to be fixed later): Because of DPI change - Bottom row of button in Dialer is smaller, however all buttons can be pressed
Known issue (to be fixed later): Because of DPI change - Superuser (root) confirmation dialog buttons aren't readable however the buttons are partly visible and can be pressed (press bottom left button to allow root acces)
Known issue (to be fixed later): Because of DPI change - There is small graphical glitch on the lock screen which however doesn't break anything
Flashing recovery is not needed at all. Just make sure you flash both partitions (it will erase all your data on the watch but not on SD). Follow instructions above on how to flash.
ROM download: http://www.multiupload.nl/3LHJ33CW95
or http://www.multiupload.nl/JK6NOATJ57
{
"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"
}
CM ROM
WIP, first build of CyanogenMod 7 (2.3.7) booted so I continue testing/evaluating. So far I only used stock kernel but I have source for MT6516 kernel.
Notes: WiFi chip - MediaTek MT5921 - no open source driver
Currently on hold.
Proofs

Flit Keyboard
moneytoo said:
Typing on tiny QWERTY soft keyboard is a pain, Flit Keyboard makes entering text much easier.
Click to expand...
Click to collapse
I actually have bought 3 Z1's and virtual keyboard is REALLY a pain..
Flit Keyboard makes entering text much easier ! !
Just Eight ( 8 ) >> Huge << Buttons Keyboard..
..that By Easily Sliding You Can Type:
>> All << Alphanumeric Characters And Symbols ! !
No More Accidentally Typing Wrong Characters ! !
Perfect 5..
(this Should Have Been THE Number One Android Keyboard..)
Thanks moneytoo ! !
ff
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
Z1 Android Watch-Phone
From Wikipedia, the free encyclopedia:
http://en.wikipedia.org/wiki/Z1_Android_Watch-Phone
ff

Ive been thinking about buying the watch to use as a mp3 player, would you recomend it?
Sent from my NWZ-Z1000Series using xda app-developers app

Yes, I'm plugging my website, but hey, it's relevant.
I've just reviewed this device at:
http://linuxslate.com/Review_Z1_Android-2.2-Watch.html

Everything in this thread has been helpful, I just wanted to add my 2 cents.
DPI at 160 looks great. Unfortunately many apps will not fit, including keyboard, phone, and superuser prompt. Either find alternate keyboard and set superuser to auto-grant, or switch back and forth between 120 and 160 as necessary.
I like No Lock, but I find the phone wake-locking all the time until I turned No Lock off. I also like the fact that the time is there in big letters on the lock screen. It's very suitable for its watch functionality.

I did a manual backup without rooting (No need for Z4 Root)
Download and unrar MT6516 BackUpTool, but do not install anything.
On the Linux/Mac box, open the gscript folder, and open back22.sh in editor, or viewer.
Connect the watch via USB, and connect via adb shell
Cut, paste and execute each line from the back22.sh file
up to and including the last dd command in the first section - in other words
Code:
.
.
.
.
dd if=/dev/mtd/mtd11 of=/sdcard/backup_/expdb.img
Obviously, you don't do the comment lines.
exit the shell
Code:
exit
do:
Code:
adb remount
Install yaffs2image:
Code:
adb push <your_path_on_PC_to>/Install/BackUp/yaffs_back_2.2/gen/mkyaffs2image /system/bin/mkyaffs2image
Code:
adb shell chmod 4777 /system/bin/mkyaffs2image
(Again, the above is a cut and paste from the script)
Code:
adb remount
(for safety)
Code:
adb shell
Then cut and paste the remaining 3 mkyaffs2img commands.
Then:
Code:
exit
Copy the backup_ folder on the SD car to someplace safe.
If you want, you can remove mkyaffsimg:
Code:
adb remount
Code:
adb shell rm /system/bin/mkyaffs2image
Code:
adb remount
It's definitely more steps, but it leaves the system technically un-touched, un-rooted, and even returnable if you should have to.

Some more useful apps.
https://play.google.com/store/apps/details?id=com.coinsoft.android.orientcontrol
Orientation control to lock the screen in landscape mode; not free but worth it.
https://play.google.com/store/apps/details?id=itosisato.setsunasato.kokoroduyosato
Home button for soft home button in notification tray. Free.
https://play.google.com/store/apps/details?id=com.katecca.screenofflock
Off button in notification tray. Free.
https://play.google.com/store/apps/details?id=com.opera.mini.android
Opera mini has server side compression so makes best use of the slow 3g speed, but no multitouch so zooming is difficult.

m34n1ng said:
Ive been thinking about buying the watch to use as a mp3 player, would you recomend it?
Sent from my NWZ-Z1000Series using xda app-developers app
Click to expand...
Click to collapse
It can be done, but the MotoActv might be better, because the motoactv has a headphone jack so you can use any headphones you want. On the Z1, you have to use bluetooth headphones or a bluetooth headphone adapter.

I just ordered one of these last week, should have arrived today ... glad to see this exists!
Other than configuration/display-size issues, does everything work, i.e. all hardware? I noticed you had a note about the Wifi driver not being open source, but I assume that more effects if you try the MT6516 kernel. Even if it's a closed binary, I assume you could still load it and use it though. I'm not expecting any leaps and bounds in the kernel department.
As for CWM, is any part of it executed at cold boot? If so, I imagine you'd need to implement some kind of timeout menu that could optionally enter recovery before booting the watch. This is similar to what was implemented on the Kindle Fire which also doesn't have a normal stock recovery mode.
I assume you're still evaluating CM7 so you're not ready to distribute it ... but I do hope to see more from you soon, especially a HOWTO and download links!

I spent many nights trying to make GSM or WiFi working. Except few tweaks I only got the modem to start but nothing more. I have no experience with porting of binary drivers and this device has so many of them. Radio/modem and kernel modules - there are no problems with them but there are just too many dependencies on proprietary libs even from standard android native binaries.
So I'm giving up. At least for now cause I just don't have enough knowledge.
I consider making custom rom based on stock Android but I don't know if there would be any demand. Proper integration of Google apps, Chinese apps/account providers removed, tweaked launcher/drawer settings, tweaked global dpi/dpi of apps that not fit...
To have at least something, I give you very simple app "Z1 Backlight Toggle" apk (attached in 1st post) which can turn off completely display backlight. (Needs root) I use it on my bike when I have navigation running all the time cause it indeed saves battery and backlight isn't needed at all under direct sunlight, the display is readable the same.

moneytoo said:
I spent many nights trying to make GSM or WiFi working. Except few tweaks I only got the modem to start but nothing more. I have no experience with porting of binary drivers and this device has so many of them. Radio/modem and kernel modules - there are no problems with them but there are just too many dependencies on proprietary libs even from standard android native binaries.
So I'm giving up. At least for now cause I just don't have enough knowledge.
Click to expand...
Click to collapse
That's fine, I understand how frustrating these things can be. But still, can you post information about how to backup / restore the firmware and how to flash a custom ROM? I might try playing with it myself sometime and at least having the knowledge would enable further experimentation.

WTF!!!! a wrist phone with Android OS.... This is so freaking cool!!! :thumbup:
Awesome......
Sent from my GT-S7500 using xda premium

moneytoo said:
I spent many nights trying to make GSM or WiFi working. Except few tweaks I only got the modem to start but nothing more. I have no experience with porting of binary drivers and this device has so many of them. Radio/modem and kernel modules - there are no problems with them but there are just too many dependencies on proprietary libs even from standard android native binaries.
So I'm giving up. At least for now cause I just don't have enough knowledge.
Click to expand...
Click to collapse
I have an idea ... if we can get the MTK6516 kernel to build and boot, that's one step. If we can then get Android 2.2 stock to build, and then compare it against an image of the Z1's file system, we should, in theory, be able to identify all the unique areas of the watch's Android setup. If we at least know how to build an identical watch Android from source we should be able to extend that into making Cyanogen Mod work ... or something else. I think it's worth a shot anyway!
Also for an identical kernel, there shouldn't be any need to "port" binary drivers ... ideally they're built-in or load as modules, same as any other drivers.
I consider making custom rom based on stock Android but I don't know if there would be any demand.
Click to expand...
Click to collapse
You're probably right there will be very limited demand. So I ask again, if you can at least post steps about reflashing the watch, I'll give it my best shot. I just want to be sure I can restore the watch after messing around with it. Which I'm guessing you were able to since you didn't claim any permanent damage. It seems it should be able to go into a factory restore mode which I hope will override any messed up systems.
lokeshsaini94 said:
WTF!!!! a wrist phone with Android OS.... This is so freaking cool!!! :thumbup:
Awesome......
Click to expand...
Click to collapse
It really is neat. Kind of limited, but really neat. I think if we can get any amount of control over the kernel and Android version, we can really extend the abilities of the watch. It just needs a chance...

southbird said:
I have an idea ... if we can get the MTK6516 kernel to build and boot, that's one step. If we can then get Android 2.2 stock to build, and then compare it against an image of the Z1's file system, we should, in theory, be able to identify all the unique areas of the watch's Android setup. If we at least know how to build an identical watch Android from source we should be able to extend that into making Cyanogen Mod work ... or something else. I think it's worth a shot anyway!
Also for an identical kernel, there shouldn't be any need to "port" binary drivers ... ideally they're built-in or load as modules, same as any other drivers.
Click to expand...
Click to collapse
In my opinion there's no problem with kernel, modules or libraries, we can just reuse them. The real issue I think is native android binaries such as wpa_supplicant or rild. We can either use (original) already built binaries or build new ones - but this is the problem... Original binaries depend on proprietary libraries so they "do something" important with devices. Newly build binaries just don't have that unknown functionality. Yes, reusing stock binaries might work for 2.2 but my only target so far was 2.3 since that would be real benefit for us.
southbird said:
So I ask again, if you can at least post steps about reflashing the watch, I'll give it my best shot.
Click to expand...
Click to collapse
Have a look here: http://bm-smartphone-reviews.blogspot.cz/2011/02/mtk-hd2-hd9-flashing-tutorial.html
Basically you need the driver: "MT6516_YuSu_USB_VCOM.inf" and flashing tool: "SP Flash Tool v1.1110". You have to use 32 bit Windows (I only tried XP in both VirtualBox and VMware but it could work with 32 bit Vista or 7 as well).
Power off the watch, connect it directly to PC (no USB hub or extention cable) - new device will connect for few seconds - use it to install the driver. Unplug watch. Open flashing tool and select files to flash (I would recommend not to flash anything other than boot/recovery/system/data/logo), hit start and quickly connect the watch - flashing will start automatically.

moneytoo said:
To have at least something, I give you very simple app "Z1 Backlight Toggle" apk (attached in 1st post) which can turn off completely display backlight. (Needs root) I use it on my bike when I have navigation running all the time cause it indeed saves battery and backlight isn't needed at all under direct sunlight, the display is readable the same.
Click to expand...
Click to collapse
Which navigation software are you using?

adthor said:
Which navigation software are you using?
Click to expand...
Click to collapse
No idea what he's using, but I'll say that Sygic worked when NOT navigating (doing a route caused it to force close, I'm guessing possibly out of memory??) Using OsmAnd works pretty well ... of course, it's Open Street Map with all the usual limitations.

adthor said:
Which navigation software are you using?
Click to expand...
Click to collapse
I use RMaps (https://play.google.com/store/apps/details?id=com.robert.maps&hl=en) with collection of offline maps and prepared tracks for navigation.

southbird said:
No idea what he's using,
but I'll say that Sygic worked when NOT navigating
(doing a route caused it to force close, I'm guessing possibly out of memory??)
Using OsmAnd works pretty well ... of course, it's Open Street Map
with all the usual limitations.
Click to expand...
Click to collapse
Sygic 10 works nice with Z1 using 3D maps.
Sygic 12 works nice with Z1 using 2D maps.
When attempting to navigate Sygic 12 with 3D maps enabled,
the Sygic 12 crashes and Z1 returns to Home screen.
Correction..
Sygic 12 works nice with Z1 using 3D maps
only when Autozoom is turned off:
Settings > Map > Autozoom [untick]
ff

I consider making custom rom based on stock Android but I don't know if there would be any demand. Proper integration of Google apps, Chinese apps/account providers removed, tweaked launcher/drawer settings, tweaked global dpi/dpi of apps that not fit...
Click to expand...
Click to collapse
That is exactly what needs to be done! If porting the binaries is not possible at the moment, why not go ahead with building with stock android, with proper google account and apps, and removing the chinese accounts.
Once you have tweaked launcher/drawer, tweaked dpi of apps that not fit etc done, it would be almost as good as running CM7. Any improvement would be a big improvement
I sincerely hope that you continue development, the demand for a stock ROM is sure to come as the device becomes more popular, as of now, there is nobody developing for Z1, that i know of.

apurvasrishti said:
That is exactly what needs to be done! If porting the binaries is not possible at the moment, why not go ahead with building with stock android, with proper google account and apps, and removing the chinese accounts.
Once you have tweaked launcher/drawer, tweaked dpi of apps that not fit etc done, it would be almost as good as running CM7. Any improvement would be a big improvement
I sincerely hope that you continue development, the demand for a stock ROM is sure to come as the device becomes more popular, as of now, there is nobody developing for Z1, that i know of.
Click to expand...
Click to collapse
I started cooking custom ROM based on the stock two days ago and I'm very happy with it. Proper integration of setup wizard, google apps, keyboard, dpi, orientation, better preconfigured launcher, working voice search etc.

Using Gear Manager on Emulated device (Bluestacks, Genemotion, Andy and AVD)

Using Gear Manager on Emulated device (Bluestacks, Genemotion, Andy and AVD)
Hello all,
I have recently been without a Android phone for a while but i am trying to use the "Gear Manager" from a Emualtor/Virtual device like the ones mentioned in the subject of the post
So far it has been the easiest to get Samsung Apps and all its addons and the Gear manager software to run and work flawlessly on Andy Emulator
Andy cannot use Bluetooth though and from what i managed to understand neither does Genemotion.
Since the Gear 2 uses Bluetooth 4 LE im not sure that even if it did use BT that it would be compatible with any of my computer set ups
since my gear is rooted and i have a feeling this can be possible somehow i decided to ask the forum
Is there a way to tunnel when connecting the Gear 2 to the PC via USB to the Emulator so that the gear manager would pick it up to sync it.
or is there any thought to an alternative that can yield the same end result
in the Case of Andy (emulator) would i need to set up both sides through Terminal to find each other ? or bridge them through Windows... just throwing out thought here
Anyway would love for the forums thoughts on the subject or tips/help...

Mods, Customization - Snapdragon 835

Hi all, I would like to inquire if it is possible to be able to root the Quest and introduce mods, launchers, optimizations and customization especially that it runs snapdragon 835 ?

Hi!
I found the security patch level of Quest is a bit old.
2017-10-05
Maybe we can use existing vulnerabilty to get root.

Hehe, i like whre this is heading.
rurie said:
Hi!
I found the security patch level of Quest is a bit old.
2017-10-05
Maybe we can use existing vulnerabilty to get root.
Click to expand...
Click to collapse

rurie said:
Hi!
I found the security patch level of Quest is a bit old.
2017-10-05
Maybe we can use existing vulnerabilty to get root.
Click to expand...
Click to collapse
With Android 7.1.1, would any of the methods here work? Has anyone tried yet?

I tried waterdrop (CVE-2019-2025), but no luck.
info:
http://blogs.360.cn/post/Binder_Kernel_Vul_EN.html
https://www.exploit-db.com/exploits/46503
$ /data/local/tmp/poc
/data/local/tmp/poc: binder_become_context_manager: Device or resource busy
We need kernel hacker. Can anyone help?
---------- Post added at 08:26 ---------- Previous post was at 08:19 ----------
In addition, I found Quest have Qualcomm's EDL mode. By pressing vul-up,down and power will boot in EDL mode.
And Quest supports fastboot on USB Update Mode. but "fastboot oem unlock" needs unlock code.

I tried the dirtycow methods but I think that was patched out before this build, no success.
I also tried just running the usual commands to bring up USB Tethering, but that seems to need root as well. All I want is better ALVR streaming

fyi Oculus is unwilling to provide bootloader unlock codes citing section 4.1 of their Terms of Service, as being in conflict with the request.

I found this to be interesting.
I've began a support request to get the boot loader unlock codes and explicitly began requesting the GPL code (parts of Android and their Linux kernel source). This should give me a few options.
They may or may not decline giving me the boot loader codes. Not the end of the world.
They are legally obligated to give me certain source code for what's running on this device. Such as the linux kernel with the modifications they've made. If they don't provide this source in it's entirety, then there's some legal implications involved there. The first response from their support was pretty ignorant. They linked me to some download section of their website that only had developer SDKs, not the sources I was requiring of them.
Anyway, once I have the kernel source, if no bootloader codes are provided, I can begin scouring it for ways to elevate to root at least.

sync.demon said:
Anyway, once I have the kernel source.
Click to expand...
Click to collapse
I believe the kernel for the oculus go is here:
https://github.com/facebookincubator/oculus-go-kernel
I can't see any published quest kernel, perhaps it's the same?

reclaimyoursenses said:
perhaps it's the same?
Click to expand...
Click to collapse
It's quite possible for the kernel to be the same. I'm going to await confirmation directly from Oculus. If it goes well, I get to unlock my bootloader on top of having the correct source. If it goes poorly, who knows. I might get to see what the legal side of the GNU GPL looks like.
I really want to audit the support for this device and software I own.

Not the same. The posted kernel for Go is Linux 3 while Quest is using Linux 4.4.21. They've built on Android, which means they're starting with a stock Linux kernel, I don't think getting their sources is going to clue us into anything that can't be known already; they'll just upload that same vanilla Linux 4 kernel source. The drivers they will use for practically everything are almost certainly closed-source. They don't have to provide their kernel configuration either.
Best of luck on getting the bootloader, though, that's the holy grail at the moment

Well, the dudes that I'm talking with finally provided kernel source:
https://github.com/facebookincubator/oculus-linux-kernel
It's the Quest Branch of the Oculus Linux Kernel. So we have something to search through for vulnerabilities.
I'm still talking with them about flashing the hardware. I'm not convinced that it's locked, because they seemed a bit confused what I was talking about. Having not touched phone boot loaders in years, I'm still doing my research into the bootloading stuff, since I'm only guessing that it involves a signature check at the moment.

Waiting for mine to be delivered, where does it store the downloaded game files?

deconfrost said:
Waiting for mine to be delivered, where does it store the downloaded game files?
Click to expand...
Click to collapse
The game files, if you mean the apk-files are generally stored on the internal sdcard and are available as movable USB storage. I don't think you even need to set it in developer mode to access the apk files. Anyway, if you set the device in the supplied developer mode it works fine. So there is no problem to load your own applications or backup downloaded games. SideQuest is a great application that simplifies this for semi-advanced users.
You can also use adb quite extensively and for example use scrcpy to dump the full screen output to a computer. Over all the Quest allows you to do most things you need.
But... The "problem" is that the Quest Android OS is locked and some things, mainly Ethernet over USB, have been disabled. You can stream video to the Quest via Wifi and play Oculus or SteamVR games that run on your computer fairly decent as it is now (using AVLR), but if Ethernet over USB was activated it could more or less replace a Oculus Rift or other wired unit completely. Oculus would likely not be happy with this since it would threaten their business/ market strategies, their segmentation of devices and the Oculus Store. But, that is why rooting the device would be interesting.

I've been finding holes to install the USB ethernet driver, but with no luck. Hope somebody will root the device so i can use either USB Tethering or a USB Ethernet device. Will even pay the person that can crack the device haha.
If I enter this CMD:
adb shell am start -a android.intent.action.VIEW -d com.oculus.tv -e uri com.android.settings/.DevelopmentSettings com.oculus.vrshell/.MainActivity
I can't even enable RNDIS manually, but that is logic since they just only added the WLAN drivers to the device.

Yesl

I just want to check that you've definitely tried plugging in a USB-C ethernet adapter? If you haven't I'm going to order one, plug in to the Quest and do lsusb.
cicada said:
I tried the dirtycow methods but I think that was patched out before this build, no success.
I also tried just running the usual commands to bring up USB Tethering, but that seems to need root as well. All I want is better ALVR streaming
Click to expand...
Click to collapse
JohanTEA said:
The game files, if you mean the apk-files are generally stored on the internal sdcard and are available as movable USB storage. I don't think you even need to set it in developer mode to access the apk files. Anyway, if you set the device in the supplied developer mode it works fine. So there is no problem to load your own applications or backup downloaded games. SideQuest is a great application that simplifies this for semi-advanced users.
You can also use adb quite extensively and for example use scrcpy to dump the full screen output to a computer. Over all the Quest allows you to do most things you need.
But... The "problem" is that the Quest Android OS is locked and some things, mainly Ethernet over USB, have been disabled. You can stream video to the Quest via Wifi and play Oculus or SteamVR games that run on your computer fairly decent as it is now (using AVLR), but if Ethernet over USB was activated it could more or less replace a Oculus Rift or other wired unit completely. Oculus would likely not be happy with this since it would threaten their business/ market strategies, their segmentation of devices and the Oculus Store. But, that is why rooting the device would be interesting.
Click to expand...
Click to collapse
Pfreaker said:
I've been finding holes to install the USB ethernet driver, but with no luck. Hope somebody will root the device so i can use either USB Tethering or a USB Ethernet device. Will even pay the person that can crack the device haha.
If I enter this CMD:
adb shell am start -a android.intent.action.VIEW -d com.oculus.tv -e uri com.android.settings/.DevelopmentSettings com.oculus.vrshell/.MainActivity
I can't even enable RNDIS manually, but that is logic since they just only added the WLAN drivers to the device.
Click to expand...
Click to collapse

guys if you use 5ghz wifi you get speeds way faster than you need anyway - I dont know why you so need to enable ethernet?
the quest has a better screen res than the rift as well. Games come up mint using ALVR
I use moonlight to stream normal non-vr games as well - also works flawlessly
however - one thing that doesnt work too well - if i am using ALVR to stream a VR game that uses a gamepad and not the controlers, i pair my XBOX gamepad via bluetooth and ALVR crashes every time.
When i use moonlight and the bluetooth gamepad it does not crash.
This means i can only play VR games which require a gamepad if i am in proximity to the PC itself and not anywhere in the house which is what i would like.
Has anyone found a solution to this "ALVR crashes with Bluetooth Gamepad connected" issue yet?

Quest Root - 90Hz possibility
With the quest link coming up and the fact that the Quest's OLED displays apparently can support up to 90Hz (Though they won't change it due to needing to verify it with the FCC), I'm hoping that that could be a reason for people to start trying to go for root! Especially with PCVR, a Rooted Quest running at 90Hz would possibly be better than the Oculus Rift S!
{
"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"
}

one click root???
has anyone tried (one click root) to get root access
https://www.xda-developers.com/best-one-click-root-2018/
maybe the root master works or something else because android 7 was annouced in August 22, 2016 and rootmaster got last update 2017.
sry bad english.