OK, This is a question for the devs: Is it possible to legitimately disable mobile view?
Apparently I installed/upgraded a few packages and broke it. I get the error "Could not acquire name on session bus" when i start webtop. I was thinking this is actually a blessing in disguise because that damn thing uses precious resources, and having the option to disable/enable it would make webtop all the more useful.
i can see why webtop dev isn't a high priority given the fact that it's a jaunty distro and you really can't do much with it.
you could try a dirty hack by looking in the /osh partition and deleting stuff
not sure which package broke the thing i wish i knew tho. seems like it broke after i installed libgdk-pixbuf while trying to install an aurora gtk engine deb
I'm pretty sure it gets called in the start-oshwt-1.sh script in /osh/usr/local/bin. I forget the name of the binary, but if you comment it out there it shouldn't open the mobile view.
I don't know what it would save you in resources though, my guess is not much since it seems like just a VNC viewer.
Caveat Emptor: edit those scripts at your own risk.
https://www.box.net/shared/tuj7vkxmeizv6j9ak4b4
Push to /osh/usr/local/bin
Warning this is not tested and may break web top. (Pull the original or rename)
sent from my AL60R!THM Atrix
Related
I'm developing a touch screen based system for controlling electronic music. As part of the development, we'll be building our own touch screen, but that's not going to be ready for some time. In the mean time, I need to start writing the software (which will be done in java), and I'm going to need a touch screen to use for testing.
So, I am NOT trying to write an application for the Galaxy Tab. I am writing a application that runs on the my desktop, and I'd like it to be able to get touch information from the Galaxy, in any way practical. I've looked into using an iPad for this, but it looks to be too much of a pain to be worth it. All I need is a way of my java application receiving the list of co-ordinates of touches from the tab, in real time. I don't need any higher level gesture interpretation (as I'll have to do that on my end for the final system anyway), just all the touch co-ordinates. Does anyone have a suggestion on the best way to go about this? Is there something in existence already to accomplish this easily, or is there any kind of java library I can use to make calls to a connected tab from my application? I've been googling around, but haven't found any particularly useful information on the subject, as the tab is chiefly meant to be a stand-alone item, not a pc peripheral. Any tips on where I might start looking would be a huge help. Thanks!
-cullam
cullambl said:
I'm developing a touch screen based system for controlling electronic music. As part of the development, we'll be building our own touch screen, but that's not going to be ready for some time. In the mean time, I need to start writing the software (which will be done in java), and I'm going to need a touch screen to use for testing.
So, I am NOT trying to write an application for the Galaxy Tab. I am writing a application that runs on the my desktop, and I'd like it to be able to get touch information from the Galaxy, in any way practical. I've looked into using an iPad for this, but it looks to be too much of a pain to be worth it. All I need is a way of my java application receiving the list of co-ordinates of touches from the tab, in real time. I don't need any higher level gesture interpretation (as I'll have to do that on my end for the final system anyway), just all the touch co-ordinates. Does anyone have a suggestion on the best way to go about this? Is there something in existence already to accomplish this easily, or is there any kind of java library I can use to make calls to a connected tab from my application? I've been googling around, but haven't found any particularly useful information on the subject, as the tab is chiefly meant to be a stand-alone item, not a pc peripheral. Any tips on where I might start looking would be a huge help. Thanks!
-cullam
Click to expand...
Click to collapse
Ok, well I'm going to try and be brief and not turn this into an Android programming essay so here goes.
You have a couple of different routes you can take.
1. If you use eclipse for development and you hook up your tablet, you can watch the log and see that it prints useful information constantly, basically debug output that tells you whats going on in the background. If you just want to look at it, you can probably see it there.
2. This would be my choice, but I'm a programmer so I love a new adventure. I would recommend you just write a quick app for your tablet that pumps out the location of a touch whenever you touch the screen. If you are familiar with sockets and such, you can just write a simple server Java app that collects packets of data from your tablet, and just have the tablet send out a multicast packet containing the coordinates you touch every time you touch the screen.
There are probably some other ways, but if you are already going to be doing the bulk of the project in Java, you aren't looking at a difficult learning curve to write a basic little android app.
Thanks! I'll definitely try the eclipse trick. And yeah, writing an app on the tab is probably going to be necessary, but MUCH easier than having to learn a new language, and get an official license to do one on the iPad. The thing I'm really unsure about is the available communication methods for getting data back and forth between them. I was hoping there might be some sort of java api to get calls going through the usb connection. So I'll guess I'll see what the Eclipse hook up shows me.
cullambl said:
Thanks! I'll definitely try the eclipse trick. And yeah, writing an app on the tab is probably going to be necessary, but MUCH easier than having to learn a new language, and get an official license to do one on the iPad. The thing I'm really unsure about is the available communication methods for getting data back and forth between them. I was hoping there might be some sort of java api to get calls going through the usb connection. So I'll guess I'll see what the Eclipse hook up shows me.
Click to expand...
Click to collapse
apple stuff is crap anyways, leave them to their pretentious commercials and closed minded development.
as far as the android sdk, I think it will take you a lot less time to just use network communications. google socket client/server java tutorials and you should be set to go in about 2 hours. I have implemented it, its all straight forward, and imho probably an easier app to write that something that pumps out of the usb port
Awesome, thanks
So I am basically trying to figure out the pro/con of either method. I have no background in linux but am trying to get my new lapdock ready as a lightweight netbook. Basic browsing, email, watch movies, use openoffice, etc etc.
What is the "best" method? Do they accomplish different end goals? Is one easier/harder to implement and maintain?
Like I said, no background in linux (yet) so I am just getting into the game here and trying to feel my way around.
Thanks
the best is Webtop2SD with Webtop scripts and XFCE4 (or Gnome) cause it's real Ubuntu.
Honestly, if you have no experience in Linux, you will probably have nothing but headaches. Linux itself isn't too bad to learn on a PC, but throw in broken dependencies and other oddities of running it on a mobile platform...it's like trial by fire.
Your best bet is like ovitz says...go with webtop2SD, follow instructions. Personally I've given up on all the other fancy window managers...I simply installed gnome-panel (disabling awn, of course) and go with a mini-gnome setup that way.
Play around after you get it set up and want to learn, but I would suggest you familiarize yourself with Linux on a PC first...or not because it may be a let down to see how poorly it performs on the phone compared to a PC.
Having said that, I've been able to use the modified webtop as a decent laptop replacement for the work I do, since most of my work is on remote servers. Putty has been very nice to me.
thanks for the input, luckily I'm about 80% of the way to function webtop2sd I think.
I don't mind the technical difficulties, the journey of getting it setup and learning that is half the fun usually.
And like said, I only really want it for basic stuff, nothing too heavy. I have the big work laptop for that.
Webtop2sd takes the existing Moto product, "unlocks it" [fixes all the .deb junk and gives it some disk space].
"Full Debian" lets you chroot out of the Moto prison into a standard Linux.
The first choice is better if you just want to add some apps to what Moto provides. The second is best if you want to play God with your system.
If you are not a serious Linux user, the 2SD approach is best.
If you like to build your own Linux system, then the latter is the way to go.
exwannabe said:
Webtop2sd takes the existing Moto product, "unlocks it" [fixes all the .deb junk and gives it some disk space].
"Full Debian" lets you chroot out of the Moto prison into a standard Linux.
The first choice is better if you just want to add some apps to what Moto provides. The second is best if you want to play God with your system.
If you are not a serious Linux user, the 2SD approach is best.
If you like to build your own Linux system, then the latter is the way to go.
Click to expand...
Click to collapse
Thanks for the explanation, that was basically what I was looking for.
Is it possible to run the "full debian" method within/alongside the webtop2sd variant? To try out both worlds?
Having not ever used chroot, as I understand it, I would basically be running a "full" version of linux within the moto environment, like opening a citrix window and getting into a complete windows setup (roughly speaking)?
Hey guys when the latest RUU was released I pulled all the WiFi calling stuff out (well.. lots of bits and pieces) to update my fourth bar install... Figured I'd share it here. This will fix the increasing lag/delay with WiFi calling on all ICS sense based roms..
It shouldn't work on cm10 but i haven't tried it.I am pretty sure the movial implementation of WiFi calling requires many sense hooks though... But the interesting thing to me is that I have modified fourth bar quite a lot from the original to the point where there is practically no sensE stuff left whatsoever.. so it's either a modified telephony provider or it doesn't require sense at all... I haven't tested it much. Feel free to play around if you want.
Made this on the fly from my phone (and also is why I using DB) so let me know if it works if not I'll make one proper. Feel free to try on viper but if you do I'd suggest also.copying over htc frameworks.as well as telephony provider from a sense rom, just a suggestion!
You can tell.the update worked.because the WiFi calling active icon will be different. Oh and those using fourth.bar or speedrom..WiFi calling doesn't have to be permanent.. simply make a shortcut to the WiFi calling activity "wificall preferences" using apex or nova activity shortcuts.. you can also make shortcuts to the full IMS config including SIP reg server, auth info, protocol type, etc. I wouldn't mess with these.settings but could be useful to those porting. FLASH.THE ZIP.IN RECOVERY
LINK: http://db.tt/4B6tcCE1
(uHH... got a PM asking if it was odexed... these files are obviously deodexed..lol.. considering there's no .odex file... but yeah I mounted the system.img from the latest RUU, extracted it, deodexed the entire thing.. and pulled these out to make this zip. I've actually been combed through it with diff to the last RUU and there's really not a lot changed at all. Couple libs here and there, maybe a few other APKs... Not much at all!.. if you need it odexed, it's easy enough to reodex.. I actually prefer my phone to be odexed as well. Good tool to do this is called Dexo, The Universal Odexer.. you can find it on google. It's basically a couple of binaries and a script.. works like a DREAM and the basic script odexes your system apps as well as framework.. and it's easy enough to modify to odex data.. only thing with odexed data is you must delete the .odex file manually after you uninstall any apps because you'll get out of space etc errors if you do not... I find things are much MUCH faster on an odexed system, by far... matter of fact I'll go ahead and create another post with the Tool and a quick batch file I wrote for windows that makes the process very quick and easy.)
Good work :dance:
Just wondering, would there be anyway to get it to work with Miui
build.prop
might need to add this to the build prop if it isn't there
ro.ril.enable.ganlite=1
ro.ril.def.agps.feature=1
chevycowboyusa said:
might need to add this to the build prop if it isn't there
ro.ril.enable.ganlite=1
ro.ril.def.agps.feature=1
Click to expand...
Click to collapse
actually I think that's for the Kineto Gan implementation of Wifi calling, which uses a Userspace application (The one we tried to port over for Viper)
This is actually the Movial IMS implementation. Have you tried this implementation on viper perhaps? You would need some framework files, I think... but it's worth a shot honestly. I don't think it's as tightly hooked into Sense as a lot of us originally thought. I decompiled all of the APKs and I combed through it and I didn't really see any hooks into Sense.. I think that it more than likely depends on a modified telephony provider..
The Kineto Gan implementation used a bit of trickery with what's called a RIL switch, where it would (as the name implies) basically switch the RIL out on the fly between Kineto's RIL (for wifi calling) and the normal one. This implementation is a lot cleaner, and the configurations are included within the files themselves... It actually uses SIP. All the configuration info is actually easily found within the XMLs once the APKs are installed as system apps. The trickery is with the authentication. I've been running wireshark and capturing packets... between that and decompiling the APKs it appears that a basic SIP registration address is used for everyone, it's not unique. There's some kind of SIP address->mobile number translation that happens... the IMS project is open source, and the full source code is actually available on Google Code.. and it has even been updated for Jelly Bean. The interesting part is, I was able to compile the IMS Test App for ICS, take the configuration information I found.. entered it into the test App, and was able to establish half-way working service with the Test application. The thing is, even though it uses SIP, it's not your everyday run of the mill SIP. There's some wrapping and translation going on that uses info contained in the packets to determine where it's going (mobile number).. and don't even get me started on Text Messaging.... that looks like one giant hack-job...basically hijacking the SIP/RTP protocol for a proprietary implementation that just uses the base outline.
I tried to register with a regular SIP client using the configuration information I found (The password was TMO-VOIP-TRIAL) and i couldn't establish registration... and looking at the source I could definitely see why. There's a lot of stuff going on behind the scenes.
The good news is there's VERY LITTLE that appears to have been changed when it was updated for jellybean... what this means is... theoretically if someone was skilled enough they could take the DIFF's (which are freely available on google code) and update the IMS implementation for jellybean. It would take a good amount of time and effort, but I honestly think it's much more possible than a lot of people originally believed. It's the authentication part that's tricky..
But yeah, you might want to give it a shot on Viper! For a start I would probably move over ip-provider.apk, ims-service.apk, IPService.apk, WifiCall.apk (This is basically the on/off switch that Settings calls.. you can just use an activity shortcut to reach it though), and gba-service.apk
Push those all to /system/app
Then on the framework side I would move over javax.obex.jar, gba-service-lib.jar, and the other important one is going to be jsr-api.jar... I didn't know that it was related but it's clearly defined in the IMS source code (https://code.google.com/p/the-ims-open-source-project-for-android/source/browse/#git/jsr-api)
I would also copy over TelephonyProvider.apk and Phone.apk, for good measure. .. and see what happens.
You would need a way to trigger it ON, which can easily be done with Nova/Apex by making an activity shortcut to WIfiCall.apk, you can also make activity shortcuts to all the configuration options within the IMS-server itself but it comes preconfigured.
it's worth a shot... currently WiFi calling is working flawlessly for me on Fourth Bar and I have pretty much EVERYTHING htc related disabled. Including com.htc etc...
Could be in the HTC frameworks though.. or somewhere else... but it's def. worth a shot!
I think this is a awaresome job,although I don't know what's this...
Please do that!
Great work. I tried your file to no avail. Good catch on the other files. I read somewhere that phonesky is also required.
Biggest issue I had with the semi working one that I used is that it wouldn't read the SIM. I moved some files around and then it hung on connecting to the Wi-Fi due to a lack of server address
I'll follow your instructions tonight and see where I can get... I still am working on GPS and now vpn too. Last night I attempted a sense 3.6 venom build.
Wasn't pretty. Something kept failing in the updater script and I got too tired to pay with it..
**tried all the files and made the short cut..
No love.. It didn't work..
Still trying a few things
Any other ideas?
chevycowboyusa said:
Great work. I tried your file to no avail. Good catch on the other files. I read somewhere that phonesky is also required.
Biggest issue I had with the semi working one that I used is that it wouldn't read the SIM. I moved some files around and then it hung on connecting to the Wi-Fi due to a lack of server address
I'll follow your instructions tonight and see where I can get... I still am working on GPS and now vpn too. Last night I attempted a sense 3.6 venom build.
Wasn't pretty. Something kept failing in the updater script and I got too tired to pay with it..
**tried all the files and made the short cut..
No love.. It didn't work..
Still trying a few things
Any other ideas?
Click to expand...
Click to collapse
Hmm... there IS a build.prop entry that I actually just noticed
ro.ril.ims=1
I would try to add that.
Phonesky is just the updated google play market, I believe.
I would try that build.prop entry, then get a logcat if you can and post it. I'd try but currently can't really mess around with my phone as I need wifi calling for work stuff.
See what is going on in the logcat, or post it and I'll comb through it. See if there's API calls that are failing under something like Function does not exist or something or another.. that would seem to indicate some missing framework stuff that provides those functions. Then it might just be including said frameworks as well as altering the bootclasspath in the kernel (Pretty easy thing to do, just break the boot.img into parts with unpackbootimg, un-gzip the ramdisk with gzip and CPIO, edit the init.rc, recompress the ram disk with GZIP, then recompile the boot.img with mkbootimg) and I believe you'd also have to deodex the ROM itself, then if you wanted it odexed you'd have to odex it back with the correct BOOTCLASSPATH or else it will not boot. I'm not sure but I THINK deodexed APKs need to be built with the right bootclasspath.
There HAS to be a way to get it working on Viper. After all it's the same underlying android OS version.. The sensation guys got it worknig on CM9...
ok..
ericdjobs said:
Hmm... there IS a build.prop entry that I actually just noticed
ro.ril.ims=1
I would try to add that.
Phonesky is just the updated google play market, I believe.
I would try that build.prop entry, then get a logcat if you can and post it. I'd try but currently can't really mess around with my phone as I need wifi calling for work stuff.
See what is going on in the logcat, or post it and I'll comb through it. See if there's API calls that are failing under something like Function does not exist or something or another.. that would seem to indicate some missing framework stuff that provides those functions. Then it might just be including said frameworks as well as altering the bootclasspath in the kernel (Pretty easy thing to do, just break the boot.img into parts with unpackbootimg, un-gzip the ramdisk with gzip and CPIO, edit the init.rc, recompress the ram disk with GZIP, then recompile the boot.img with mkbootimg) and I believe you'd also have to deodex the ROM itself, then if you wanted it odexed you'd have to odex it back with the correct BOOTCLASSPATH or else it will not boot. I'm not sure but I THINK deodexed APKs need to be built with the right bootclasspath.
There HAS to be a way to get it working on Viper. After all it's the same underlying android OS version.. The sensation guys got it worknig on CM9...
Click to expand...
Click to collapse
I fixed VPN and I'm uploading it in a few. I think I noticed something as well. I went back to stock ota to see what was going on and noticed wifi calling isn't showing up in settings/more should be there with vpn/ wifi hotspot/ nfc etc....
ericdjobs said:
The trickery is with the authentication. I've been running wireshark and capturing packets... between that and decompiling the APKs it appears that a basic SIP registration address is used for everyone, it's not unique. There's some kind of SIP address->mobile number translation that happens... the IMS project is open source, and the full source code is actually available on Google Code.. and it has even been updated for Jelly Bean. The interesting part is, I was able to compile the IMS Test App for ICS, take the configuration information I found.. entered it into the test App, and was able to establish half-way working service with the Test application. The thing is, even though it uses SIP, it's not your everyday run of the mill SIP. There's some wrapping and translation going on that uses info contained in the packets to determine where it's going (mobile number).. and don't even get me started on Text Messaging.... that looks like one giant hack-job...basically hijacking the SIP/RTP protocol for a proprietary implementation that just uses the base outline.
I tried to register with a regular SIP client using the configuration information I found (The password was TMO-VOIP-TRIAL) and i couldn't establish registration... and looking at the source I could definitely see why. There's a lot of stuff going on behind the scenes.
Click to expand...
Click to collapse
How was the Test App half-way working for you? I didn't compile it, but I tried an apk I found a while back and it CLAIMED it was registered, but I couldn't make it call out. I tried random presence and subscribe options but I don't think they were taking and nothing happened when I called my mobile number from somewhere else. My guess is that I have to subscribe or set presence to something magic for my phone number. After not really finding what I should actually be doing from skimming the 4th or 5th spec, and noticing that the nexus 4 guys have a $1400 bounty and don't really have progress, I gave up.
Yeah there's a pile of authentication (on both sides) that IMS has over SIP. If I understand right, the first part of registration is similar, but then TMO's side says you're unauthorized along with a challenge that's supposed to be sent to the ISIM and part of a key for establishing an IPSec tunnel that everything else goes through. Can't tunnel, then use SIP because you need the key (and part of that probably comes from the ISIM too), and a regular SIP client will just think it failed.
Greetings,
At my office, we rotate after-hours email monitoring but some of the older guys are apprehensive about getting cell phones, so keeping up on-the-go can be difficult. I am wondering about buying a ZTE Open off of ebay and getting a pay/mb data plan and we can pass that around as a dedicated email reader.
Up to that point, there is nothing to worry about, but what I am thinking of playing around with is cutting the OS down to only the email app and settings. I'd like to have it boot directly to email with settings available from the pull-down menu, if possible. I mainly want to keep it simple enough for cellular-phobic people and also take away the ability to browse the web and run up my cellphone bill.
I'm not super fluent in the in's and out's of FXOS beyond the app level, but I'm interested poking around, I'm just looking to gauge the difficulty. There are cheaper android devices that I could try with as well, but I'd much rather hack around in HTML/JS than Java. That being said, I have the option of just customizing the Andriod UI to remove everything except the mail app, so if tearing down the Firefox UI would be a lot of work, I'll just do that.
I have a Flame that I can run tests on before spending any money, but I appreciate your opinions before a throw away a bunch of time that could be used on something useful.
John
That's super doable and not very difficult I think! Only with one (obvious?) condition: you must have full root access to your device. ZTE gives a rooting tool, so if you stick with the Open C (or the flame) you should be good to go. Don't choose a Kliff for example, as they are not rootable yet.
First of all, stripping all of gaia (the top layer of firefox OS, containing all the UI) has already been done by JanOS (for IoT device), so you can get inspiration from them. They reduced it to only one js file and a folder, where you can put your own js that gets executed at startup. Your use case is a bit more complex though: you still want to access settings, and be able to go back to email when needed. Basically, you need the email app to replace the homescreen right?
Creating alternate homescreen is a possibility that firefox os gives you, see https://developer.mozilla.org/en-US/Apps/Build/Manifest#role
You can try adding the role "homescreen" to the email app, flash your device, change the homescreen in the settings and see what happens!
NB: when you change the manifest of an internal apps, you might need to rehash it by downloading https://github.com/julienw/config-files/blob/master/addpref and execute
Code:
./addpref rehash-manifest
while your device is connected (and usb debugging is on).
You might need to add handler in the email for the home button to work correctly, in a similar fashion as in verticalhome (which is the name of the folder containing the homescreen app, not "homescreen").
Good luck! Don't hesitate to ping me if you need any help.
---------- Post added at 11:00 AM ---------- Previous post was at 10:46 AM ----------
Dude I just tried this and it's working like a charm. The thing that took me the most time was the configuration of the email account
I have a multi-boot touch screen enabled machine running Android as one of the partitions. I like the idea of transitioning from Android to ChromeOS, but I have to have use of Android apps. The Brunch project has given me a way to install ChromeOS and seems to work extremely well for what I need. But there are a few ChromeOS quirks that keep me from making the swap. Search seems to indicate they are not solvable at present, but maybe this community can help.
1. The biggest issue with ChromeOS is its insistence that I login using my full Google password every time. The Android (or ChromeOS) partition would not be my main driver, so simply sleeping is not a feasible option for me.
a. Is there a way to mod chromebook to login from cold boot using a PIN? And if so, would such a mod survive updates? Sorry, I'm pretty sure that's a hard no, but it's worth asking.
b. Alternatively, I think I could get this to work if I could hibernate (suspend to disk) to work. I know suspend to disk is not part of the nominal use case of chromebooks, so maybe it's not even supported? Either way, I'm struggling to fine resources for it. If that worked, then I think that I could simply login with a PIN most of the time.
2. Brunch includes a great mod to allow tablet mode to be turned on/off by way of terminal. What would be better is to have a link to a script that could toggle with a tap (or maybe two). But I don't see a way to run a script for android terminal without going into terminal. Is there a way to run scripts without having to switch to the terminal? Bonus points if I can give that way an icon and stick it in the dock.