I need the latest DockServices.apk & PortalApp.apk files that have not been modified for the Webtop hack. I need them so I can startup the Webtop when i connect my Electrify to my modded Atrix Lapdock. Any help with these two files would be greatly appreciated! TIA!
Sent from my Motorola Electrify using xda premium
Yays 1024 zip
Sent from my MB855 using XDA App
Open to Suggestions!
Thanks for your help joker but I still cannot get the WEbtop interface without the modded WEbtop Hack DockSErvices and PortalApp apk files. That's no good because the keyboard and trackpad won't work.
Can anyone modify the WEbtop hack files to utilize the keyboard and trackpad on the lapdock? SEe below for what I have tried and results so far.
I am using a refurbished Lapdock and am starting to think that maybe it's the lapdock!
I was able to get the Webtop interface to come on twice after I opened the box the first time. Both times, it was while the cables were loose and the phone was sitting flat behind the lapdock on a table. However, the Webtop would not come on right away, it would take a few minutes and then the phone screen would go dark (no backlight but you could still see the clock on the screen) and the webtop UI would come on...on the lapdock.
After dremeling it all down flat (at Mean flat) I was unable to get webtop to come on again. So, I downloaded the WEbtop hack with modified Dockservices and PortalApp files for the photon. INstalled them and viola I had instant recognition of the phone and it offered me the WEbtop option at the top of the HDMI options screen on the phone. Offered Webtop, Gallery, Music, and Mirror. The Webtop option works but the trackpad and keyboard do not work on the Lapdock. Not acceptable for me.
I figure it must have something to do with the drivers. So, I asked for help for the Photon's unmodified DockServices and PortalApp apks. I installed them and they worked but don't offer me the WEbtop option period. So, no joy!
I took the tray apart again and hooked it up with the cables loose and cannot get the WEbtop experience again at all. (This based upon original Electrify files) I am going to reinstall the Photon unmodded files and see if it will work with the cables loose. I am hooking up the USB first but get no reaction from the phone or lapdock until I hook up the HDMI cable.
Anyone got any ideas. I am thinking I got a cheap HDMI monitor right now....worse case scenario! LOL I paid $75 for it so it was worth the risk.
I have something that may be similar that happens to me. Did you by chance do any mods to change the resolution of your webtop over HDMI cable? Meaning did you edit the file in the osh folder to support higher resolutions? I did this based off one of the guides in this forum, and I have noticed something strange. If you have done this, then you know that the phone becomes a track pad mouse with a virtual keyboard option. When I have the resolution set to the preinstalled Motorola resolutions (1280x720, etc), the phone works as a mouse pad with no problems, and responds correctly. But, if I raise the resolution, in my case to 1680x1050, the touchpad stops responding. A bluetooth mouse and keyboard still work perfectly, but the phone won't interface.
Have you tried plugging in a USB mouse? Just to see if it's something related to the dock? If a USB mouse works, try a USB keyboard. That might help you get to the bottom of the mystery.
Next time post this in the Q&A Area, this is NOT an Accessories post, other than the mention of your Atrix dock.
So I've watched the ICS Motorola Webtop Beta 3.0 video and it may be me but it looks very similar to the Evo Desktop PC in concept and function. Considering that ICS wasn't even available this time last year this would have been the logical progression of the project. I'm not asking for Moto to send me a check but I'm waiting to see how the credits roll out. If the Sun here on Mars has baked my brain then feel free to say so.
Lokifish Marz said:
I'm not asking for Moto to send me a check but I'm waiting to see how the credits roll out.
Click to expand...
Click to collapse
Wow
The check is in the mail.
CCallahan said:
The check is in the mail.
Click to expand...
Click to collapse
So are you going to send it on their behalf?
Actually I've been in contact with Moto since the videos surfaced and am getting the "hot potato" treatment. All I'm looking for is to have a civil dialog with them about it. All I'm getting is being told I need to contact Department A by Department B after just being directly referred to Department B by Department A. I have even gone so far as to include the direct referral and names in my communications. You probably have a good idea as to how well that's working.
The odd thing is that with 200+ views nobody has said I should have my head checked. Is everybody on XDA being nice?
Interesting question, locki. Definitely a fair one. If I understand correctly, from watching the video (I had the volume down - A cold and a headache coming down so I'm trying to minimize the noises). In any case, your version looks to me like phone mirroring with a keyboard and a mouse. Not sure how it's set up (you probably said it in the video). But I don't think the ICS demo is a complete demo. This looks like he just reviewed the phone mirroring version, but didn't do a complete webtop review. Also, webtop on the current system is also pretty limited. From that video, I don't see much difference between the ICS and what we have on our phone, except that this is a proof of concept. In any case, you could say the same thing about a comparable presentation from the webtop experience on the mopho if you only show the the phone window usage. could also say the same thing about your ubuntop if you only show a limited version of the capabilities. I guess my point is I don't think you have a fair comparison at this point. But my head is stuffy and I am on my way to an early bedtime, so maybe I'm missing something...
I replaced the video of webtop 3.0 with one that shows webtop3.0 in use. I also have a copy of the ICS RAZR leak and osh (or anything related to that partition) is nowhere to be found. Neflix is obviously Netflix for tablets. The desktop look of Chrome appears to be a ui switch for the mobile chrome browser. If the ICS leak is anywhere near what the official release is, then the tech/android reports are correct that the new webtop is nothing more than modified tablet mode mirroring.
I'm not saying it's not good work. Had HCL Launcher, Chrome mobile browser and Netflix for tablets been out when I released Evo Desktop you would be hard pressed to tell the difference.
My other concern is if the leak I have and the videos are correct this does not bode well for Webtop becoming a true desktop with ICS like many had hoped.
So If I am understanding things correctly, the new webtop is just tweaked phone mirroring, as opposed to now where there are 2 operating systems running side by side. I guess ubuntop won't work on that system then. very disappointing.
As nice as Evo Desktop was there were tons of drawbacks. So I can tell you from experience that this is going to be a serious step backwards for "Webtop". Open up a mobile browser and visit a page that has flash based chat embedded. You cannot leave that page (view another page in another tab) because as soon as you leave the chat page tab everything gets suspended. When you go back to the chat page tab you have to log back in and start over.
Document editing will also be an issue as you have to use cloud based editors like Google Docs because to my knowledge none of the current office apps have that tablet switch needed change how the ui is rendered. When you combine this with the browser tabs issue and that Google Docs puts a fairly heavy load on the browser, you can say goodbye to any real doc editing.
What it comes down to is that many app devs are going to have to add the needed ui switch and changes to keep the new webtop from being trash. This will not be easy. I fought for months to just get a browser with a "desktop ui" look with no success. Even with thousands of users on the Evo project nobody would touch it. I ended up having to modify an existing browser to give my users a desktop look. Multiply that by how many commonly used apps that would need a ui switch and Moto is just asking for failure.
My other concern is what happens to the, now wasted, 1.3GB osh partition? The leak has no mention of it in the install script. It looks like it will still present but only accessible via vnc which has it's own issues and drawbacks.
It doesn't make much sense to scale phone GUI to larger screens like monitors (24"+) or even Plasmas (42"+), so logical question is whether is already possible to enable tablet GUI when Video out is enabled (only then and without reboots)?
Does Google or CM team plan to integrate that feature in the OS?
I believe that with some custom mods it's possible to switch to tablet GUI and have it extended normally via video out to larger 1080p screen, but why not have it out of the box and rule the HTPC scene?
Galaid said:
It doesn't make much sense to scale phone GUI to larger screens like monitors (24"+) or even Plasmas (42"+), so logical question is whether is already possible to enable tablet GUI when Video out is enabled (only then and without reboots)?
Does Google or CM team plan to integrate that feature in the OS?
I believe that with some custom mods it's possible to switch to tablet GUI and have it extended normally via video out to larger 1080p screen, but why not have it out of the box and rule the HTPC scene?
Click to expand...
Click to collapse
This isnt the proper forums to place this question since its solely about Google or CM. Please use this link: http://forum.xda-developers.com/forumdisplay.php?f=1236
LeviathanPT said:
This isnt the proper forums to place this question since its solely about Google or CM. Please use this link: http://forum.xda-developers.com/forumdisplay.php?f=1236
Click to expand...
Click to collapse
As I plan to use this feature on SGSIII, I thought this might be a good enough forum, because it may actually work on GSIII.
I don't believe this should be in the hacking territory but should come out of the box, shouldn't it?
Not really, this question isnt new in the XDA forums and has been asked before in the Galaxy Note section, you can consult it here: http://forum.xda-developers.com/showthread.php?t=1523880&highlight=tablet+gui and from you can see no one seems to care, this should either go the thread i mentioned above or directly to the CM9 forums.
So, basically, I got the smart dock and, it's pretty damn awesome. But OMFGTHATFREAKINGMOUSECURSORTHATWON'TGOAWAY.
Anyway, I did some searching and found that there's no way to get it to disappear under stock. Grr. But some custom ROMs allow it. Unfortuantely, none of them seem to say whether they do or not, so I need your advice! BUT! There's other things I need too, which are even more important than being able to make the cursor disappear. So... I need:
1) NTFS support, read AND write. If the ROM isn't Android 4.2+, Paragon NTFS & exFAT can take care of that. So; I need a ROM that's either 4.1 based or has built-in NTFS support. (I don't need exFAT.)
2) Works with the smart dock. The one that has the audio out, HDMI, and 3 USB ports, and isn't officially compatible with the S3 but works anyway.
3) Can make the freaking mouse cursor disappear. Even better if this can be set on an app-by-app basis or toggled with a key shortcut on an external keyboard.
4) Decent battery life. Doesn't need to be better than stock, just not one of those ROMs that runs the thing flat in half an hour.
5) Being based on Samsung's rather than AOSP would be a bonus, but I'm not *overly* fussed on this.
(I heard some custom ROMs result in the FM Radio not working. I really couldn't care less about this, I never use it, so it's fine if that doesn't work.)
I don't need to be walked through how to install it etc, I've done all that several times before. Just need a reccomendation on which one to use, to save me trying every one of the millions out there. Even if you can only confirm some of those features and aren't sure about others, that'll at least narrow down the selection to try. Thanks in advance guys. =)
Recommend a ROM threads aren't allowed. You have to read the features in the rom thread.
That said:
1) This is KERNEL related
2) Only Touchwiz support video out
3) The mouse cursor you turn on in developer options? Or you mean when you're using the mouse? Can't imagine using a mouse without a cursor
4) Again, mainly kernel related. But since you narrowed it down to only touchwiz roms in point 2, it's not really relevant anymore.
5) Not really got a choice.
^^^^This^^^^
Thread Closed
Similar to my TWRP / Multirom thread, this is temporary until xda decides to add this device to the dev db list. A few comments and a known issues list will be all in this post. Please report any and all problems you find. This is still very early in the development process.
NOTES:
This will only install using my TWRP build here because I'm have to do some hacky things to support a unified build. I may eventually find a cleaner method.
This doesn't yet contain my attempt at controller pairing. The framework patches are there, but not the apk. It will be tested and included in later builds. Wifi doesn't work, so pairing wouldn't work anyways.
I had to use aosp libs to make this boot, which is different from my Portable and Tablet releases. The hdcp libs seems to be very different, so I have no idea if 4k works at all and I seriously doubt youtube and netflix drm will verify correctly.
You will have to wipe data to install this, make a backup first. Do note this is just /data, not the entire internal sd.
KNOWN ISSUES:
Wireless controller pairing not implemented
No audio over hdmi (so, no audio at all)
SOURCE:
device
kernel
vendor
CURRENT RELEASE:
cm-13.0-20160224-UNOFFICIAL-foster.zip
OLD RELEASES:
cm-12.1-20150819-UNOFFICIAL-foster.zip
cm-12.1-20150720-UNOFFICIAL-foster.zip
cm-12.1-20150709-UNOFFICIAL-foster.zip
missing default android keyboard?
installs fine boots into CM - displaying in 1080p on my monitor just fine.
missing android keyboard.
works fine with usb keyboard (logitech k400r)
amazon app store installs fine, recognizes all apps - minecraft PE crashes on start
touch pad / mouse freezes intermittently
netflix installs but does not play
great start, looking good.
I'm finding all kinds of interesting things working on this... Well, I got the stock libs 'working'. HDCP (or something in the graphics stack) locks up the system on boot when using a custom built kernel. From within CM or even from Nvidia's aosp tree. It will only boot with the kernel pulled out of an official boot image. I compared the ikconfig out of the official kernel with what I'm building in CM and they match. So, I'm kinda lost as to what black magic is at work here... Is something doing a crc check? Is there black box GPL violations in the stock kernel? I don't know. And I had a custom kernel booting stock when I was first trying multirom stuff. So that makes me *really* confused. For the moment, I've disabled kernel compiles in my device tree and I'm shipping a blob kernel. And I hate doing that.
Haven't looked at the missing keyboard yet.
Wifi is closer, but still not there. The wlan0 interface seems to init, but the p2p interface fails and brings it immediately back down. I'll do some more research into that over the weekend.
The screen flickers at times. Don't know why, but I think I saw some system props that affects the screen drawing on stock, once I find those again I should be able to fix that.
The OMX libs work now. Which means game streaming works. I tested a grid game already. Don't have Windows, so I can't test local streaming. And theoretically the aforementioned Netflix problem should be fixed by this as well.
I'm kicking off a build to run overnight (takes 4+ hours for a clean release build [on a AMD FX 9370, no less]), so I should have this stuff up first thing tomorrow morning (pending life (r)).
Edit: And... build failed. Starting over... So, looking at this afternoon now.
Edit 2: Well... I can make it boot when I tinker with it manually, but I'm not having much luck making a reproducible build from source. So... I'll have a release eventually, but with 4 hour rebuilds, I can't say when at this rate.
Steel01 said:
Similar to my TWRP / Multirom thread, this is temporary until xda decides to add this device to the dev db list. A few comments and a known issues list will be all in this post. Please report any and all problems you find. This is still very early in the development process.
NOTES:
This will only install using my TWRP build here because I'm have to do some hacky things to support a unified build. I may eventually find a cleaner method.
This doesn't yet contain my attempt at controller pairing. The framework patches are there, but not the apk. It will be tested and included in later builds. Wifi doesn't work, so pairing wouldn't work anyways.
I had to use aosp libs to make this boot, which is different from my Portable and Tablet releases. The hdcp libs seems to be very different, so I have no idea if 4k works at all and I seriously doubt youtube and netflix drm will verify correctly.
You will have to wipe data to install this, make a backup first. Do note this is just /data, not the entire internal sd.
KNOWN ISSUES:
Wifi doesn't enable. (ethernet works fine, though)
Keyboard not installed
SOURCE:
device
kernel
vendor
CURRENT RELEASE:
cm-12.1-20150709-UNOFFICIAL-foster.zip
Click to expand...
Click to collapse
screenshots ?
Glad to see ATV gettin some action ... ooooo hel I'm excited. I've been fastbooting your twrp img. for a few things and its working quite nicely on my pro model. BIG BIG thanks for that @Steel01 Does it look like there will be any issues reguarding which version console its running?
@aniel300: Screenshots? It's Cyanogenmod. The same Cyanogenmod as on any other device...
@ElwOOd_CbGp: Like mentioned in the OP, I do a hacky thing or two to support unified builds. It have the pro version myself, so that's what I test on. I'm pretty sure it will work with no extra problems on the 16 GB model, however.
Alright, I *think* I finally ironed my build problems (all related to using a prebuilt kernel... got to figure out a way to not have to do that), so theoretically I'll have a build out tomorrow. Probably won't be able to test much until the afternoon, so I doubt it'll be out bright and early.
yey! please keep going! AOSP + Kodi + Support for official remotes would be awesome!
Steel01 said:
@aniel300: Screenshots? It's Cyanogenmod. The same Cyanogenmod as on any other device...
@ElwOOd_CbGp: Like mentioned in the OP, I do a hacky thing or two to support unified builds. It have the pro version myself, so that's what I test on. I'm pretty sure it will work with no extra problems on the 16 GB model, however.
Alright, I *think* I finally ironed my build problems (all related to using a prebuilt kernel... got to figure out a way to not have to do that), so theoretically I'll have a build out tomorrow. Probably won't be able to test much until the afternoon, so I doubt it'll be out bright and early.
Click to expand...
Click to collapse
is it a hybrid rom ?
@[email protected]: Kodi is of great interest to me as well, so I'll work to make sure works well.
@aniel300: No, it's pure CM. I plan to make the TV stuff accessible, but it won't be there by default.
I finally got a bootable build, but it does show more problems. The launcher and some programs lag terribly. Not locking up, but slow enough to trigger ANRs. Netflix does still crash when loading a video, hopefully that won't be hard to fix once I can read the logs. The interface still flickers, but only the interface, not videos or games or such. I'll do some more testing this afternoon and unless an even worse problem shows up, I'll release.
New build is up. It appears the netflix bug affects others things too, like youtube. Appears to be audio related, but I don't have time right away to try and track down the root cause. So, consider this another bug hunting build and not truly usable.
I've fixed an audio problem, so sound and YouTube and all that works again. Netflix is still confusing me a bit, though. It appears to be a problem with the OMX libs, but not one seen on any other Shield device. Haven't spent too much time looking the last few days.
I'm in the process of restructuring the build setup on my dev machine. Like moving the build trees to a faster spinny disk and ccache to a ssd. That should get builds going a lot faster. 4 hours per build gets old real fast. And 45 minutes for a one package change. I plan to release a new build once I get that all sorted out.
what about you try to port android m tv developer preview instead or at least cm but with all the good stuff from android tv.
It seems Forge has unlockable bootloader they posted instructions also for home images so it's a start it should be easy to flash recovery if there was one. Sorry for going little off topic but this seems more active here
New build up. Seems the OMX libs are only partially working. Youtube works, but mxplayer and kodi fall back to their software decoders. Wireless appears to finally work, but logcat messages lead me to believe it's still not completely there. Oh, and the UI flickering is still there.
So, I loaded this build up and promptly installed HALauncher and Kodi. With the controller wired in, this seems to be a pretty usable setup. As things begin to stabalize, I'll probably start to recommend that launcher as a replacement for leanback. Now if only I can find a replacement for the leanback keyboard, I won't have to include any Google blobs... Suggestions are welcome for a free and preferably open source dpad enabled keyboard.
Really good progress tonight. Barring something patentably bad happening, I should be releasing a new build tomorrow. List of progress:
1. Interface flickering is way down. Don't know if it was something I did or if upstream CM tweaked stuff. Either way, it's bearable now. I only notice it on some transitions, whereas before it was all the time on builtin android interface stuff.
2. OMX libs work. Hardware accelerated video and movies, plus game streaming and grid works now.
3. Leanback IME (controller enabled keyboard) is part of the build. It's smaller than on stock, but still usable.
Some things still need work, though:
1. Netflix still fails to play a video. At least it doesn't crash to desktop anymore...
2. Wireless controller pairing fails. The app runs and it tries to set stuff up, but seems to hit the same problem the Portable does most times. I have got the Portable to pair once or twice, though, so some people might be more lucky than me and it'll actually work.
All in all, this looks like a very usable test build, if not a daily driver for some use cases.
Hi steel01
I am planning to buy this device, pro version, but its true that the SSD storage drive has some problems about performance and response, speed, looking all around for a good review about this and nothing found yet,unbelievable, I want to be sure the 16 GB or pro version.
Counting on you,like you doing on the shield tablet,interesting approach with CM,look forward, when I get it I will install the Zulu99 full android ROM first and them....cm
Good luck on this, thank for you hard work
I haven't had any lag problem with the Pro edition, but I also haven't done anything IO intensive. So, I'm not really a good yardstick for that. However, the pro edition does have the 16GB hardware, just needs some tweaking to be able to access it. Probably could do some boot image trickery to get /system on that device. Haven't looked at that yet since CM and multirom are higher priority in that order.
Other stuff came up today, so I didn't get to test the new build. As soon as I drag it back across the house to reflash it, I'll verify the build and upload. Maybe tomorrow afternoon.
I am just a thinker, its possible to use all the best feature of CM and put it in android tv or viceversa.
I dont own yet a android tv device, but is like no to manny peoples like it, may restrictions from google, its entirely new or old UI, developers needs to port their apps to android tv platform, maybe we like the custom launcher or just the regular launcher, well its until everybodys decision.
Multirom sound good, but i like the basic and fast, what about if we can have two launcher in the GUI or UI, can be possible, there is a really need an apps to be ported to android tv platform, why google put restriction, we can sideload to get what we want, i think this is confusing android OS is android.
I think the best thing to do its going back to the basic.
Well, I didn't get to testing today either. I think I'll run another build tonight and try to get to a test tomorrow night.
@duanim: That is my end goal for my device. The Shield TV running CM with a 10 foot launcher (that isn't leanback) and everything accessible from the controller. The current build isn't too bad for that, but not all the way there. CM and HALauncher works pretty well. But the controller still needs help wirelessly.
There's one major problem with running android and android tv simultaneously. It seems the play stores are different. You either get the TV apps or the normal apps, not both. If someone knows different or a way to work around this, I'd love to hear it.
Still can't get the dumb wireless controller libs to package the way I want. So the latest build is missing some, causing the app to continuously force close, making the build unusable. I'll split it like I didn't want to and should have a releasable build tomorrow.