Database Develop

[ROM] 2.3.1 boot.img with ro.secure=0 and ext4 hack. adb remount with CM7 boot.img

this is the 2.3.1 kernel off my nexus s modded with ro.secure=0. adb remount works again! apparently people really like this option? lots of complaints it didnt work since upgrading to 2.3.1.
edit: added @supercurio's ext4 file system hack. all credits to him for providing the how-to.
edit2: added the boot.img from CM7 with @supercurio's ext4 file system hack.
test:
Code:
fastboot boot roext4.img
install:
Code:
fastboot flash boot roext4.img

Thank you sir, trying this now.
Yes I love my adb remount, makes things a ton easier for upgrading the market manually with adb push for example.

Michael.B. said:
Thank you sir, trying this now.
Yes I love my adb remount, makes things a ton easier for upgrading the market manually with adb push for example.
Click to expand...
Click to collapse
Worked great. Wifi and adb remount again on 2.3.1

Michael.B. said:
Worked great. Wifi and adb remount again on 2.3.1
Click to expand...
Click to collapse
glad someone got some use out of it.

Any chance you can make a version that works on CM7? I just tried this and wifi doesn't work w/ CM7.
Sent from my Nexus S using XDA App

added cm7 boot.img with ext4 hack.

My bluetooth stopped working after flashing roext4.img. it tries to activivate but fails......

Thanks for the CM7 version! Works great.
Sent from my Nexus S using XDA App

unremarked said:
Thanks for the CM7 version! Works great.
Click to expand...
Click to collapse
glad i could give something back. even if its minor.

teckhwee said:
My bluetooth stopped working after flashing roext4.img. it tries to activivate but fails......
Click to expand...
Click to collapse
I just test my bluetooth w/ the CM7 version. It doesn't work as well. I guess the ext4 hack breaks it in general. I went back to my original boot.img, and bluetooth works again.

Luxferro said:
I just test my bluetooth w/ the CM7 version. It doesn't work as well. I guess the ext4 hack breaks it in general. I went back to my original boot.img, and bluetooth works again.
Click to expand...
Click to collapse
yep. bluetooth seems to be an issue with it. i dont use bt at all so its not really an issue for me.

I confirm that there is a problem with Bluetooth

k0mpresd said:
yep. bluetooth seems to be an issue with it. i dont use bt at all so its not really an issue for me.
Click to expand...
Click to collapse
^
I'm okay with giving up Bluetooth for the performance enhance.
Sent from my Nexus S using XDA App

MMM, wifi is working but i can't complete quadrant benchmark!

MrNameless said:
MMM, wifi is working but i can't complete quadrant benchmark!
Click to expand...
Click to collapse
Quadrant doesn't work correctly on gingerbread. It happens on stock roms as well. it's just random, and sometimes it will complete.

this is voodoo kernel? do you need special recovery?

k0mpresd said:
Code:
fastboot flash boot cm7.img
Click to expand...
Click to collapse
It looks like the noauto_da_alloc flag has to be applied to the /data mount after bluetooth services are started. Where in the img did you have it specify that flag was it in the initial mount or did you remount with it at the end of init?

Zenoran said:
It looks like the noauto_da_alloc flag has to be applied to the /data mount after bluetooth services are started. Where in the img did you have it specify that flag was it in the initial mount or did you remount with it at the end of init?
Click to expand...
Click to collapse
here is the modded file. if you have a better solution, let me know and ill post an img.

[REQUEST] Can someone post a guide to how to get Froyo on eMMC?

I don't want to dual-boot, even, just have a nice "normal" Nookie Froyo install on eMMC. I've seen several allude to the fact that it worked for them but no reviews of how they did it. I've backed up my 2.1 install with Clockwork so I'm not really worried about that.
TIA.

It's quite simple actually. All you need is basic knowledge of adb.
All disclaimers apply, I'm not responsible for any damage. Just know that mine is running on internal partitions. And the SD does mount too!
Before doing anything, I would recommend applying a dd from your partitions to your pc.
With, for example on mmcblk0p1 (boot) adb: dd if=/dev/block/mmcblk0p1 of=boot.img
You should do that for each partition to be safe (0p1 to 0p8).
All the following commands can be execute one after one, the separations are only there to makes things a bit more clear.
Then,
Boot to a working Nookie (NF) with your uSD fresh from burning, without any google apps, and without any uSD damaged errors.
Empty your internal system and copy uSD system over, by doing:
- adb shell mount -o remount,rw /dev/block/mmcblk1 / (---there is a space after the 1---)
- adb shell
- mkdir tmpfolder
- mount /dev/block/mmcblk0p5 tmpfolder
- cd tmpfolder
- rm -r * (---note that there is space after the r---)
- cd ..
- cp -r system/* tmpfolder (---this will take a few minutes---)
- umount tmpfolder
Click to expand...
Click to collapse
Then, you need to boot push the attached files (bottom of post) except for the 2 vold files to your boot partition: mmcblk0p1. Unzip, copy content, not zip.
You could very well replace uImage with the new Quickie overclocked uImage for froyo (see dev thread).
To push attached files to boot, do:
- mount /dev/block/mmcblk0p1 tmpfolder
- exit
- adb push [folder-containing-4-attached-files-except-vold.fstab] tmpfolder
- adb shell
- umount tmpfolder
Click to expand...
Click to collapse
I would also recommend erasing all your data. But that's up to you, if you want to keep your data on it. In any case, you can revert back with the data.img you created above . So next part you could skip, haven't tried skipping personally:
Non mandatory, but you could do:
- mount /dev/block/mmcblk0p6 tmpfolder
- cd tmpfolder
- rm -r *
- cd ..
- umount tmpfolder
Click to expand...
Click to collapse
Then you need to push vold.fstab and vold.conf (unzip volds, copy content) to system/etc
Copy vold's to system/etc:
- mount /dev/block/mmcblk0p5 tmpfolder
- exit
- adb push [folder-with-vold's] tmpfolder/etc/
- adb shell
- umount tmpfolder
- rm -r tmpfolder
- exit
Click to expand...
Click to collapse
Then shut down, remove uSD, and boot.
Again, you can choose to push the Quickie uImage, I you prefer, but the accelerometer doesn't work with it at the moment. The 950 kernel does sometimes crash on boot, but once booted is quite stable.
I think that's all folks. I could have been a bit vague at some times, but this should work. And if you made your imgs as recommended, you're bullet proof.
To revert back to initial state with img files, you need to copy files to sdcard and then dd:
- adb shell mount -o remount,rw /dev/block/mmcblk1p1 sdcard
- adb push XXX.img sdcard (--could take a few minutes--)
- dd if=XXXX.img of=/dev/block/mmcblk0pX
Click to expand...
Click to collapse
Do that for each partition.
For those who don't feel up to the task, I could make a CWR flashable zip file of all this. The only thing is, CWR dosen't boot on Nookie just yet. So you couldn't restore with a zip after the change.

[Before doing anything, I would recommend applying a dd from your partitions to your pc.
With, for example on mmcblk0p1 (boot) adb: dd if=/dev/block/mmcblk0p1 of=boot.img
You should do that for each partition to be safe (0p1 to 0p8).
[/QUOTE]
I am a little confused here. What are the names of the 7 other partitions? Thanks, Great guide btw!

See here.

Do you see improved speed and touch response running nookie from emmc?

im getting a "No such file or directory" error after "adb push [folder-with-vold's] tmpfolder/etc"
I created the directory but now it looks like i am stuck at the landscape android splash screen on boot...
any ideas? I am attempting to redo the whole process again just incase i missed something.

Sorry, there's a slash after etc.
Make sure you've copied the systen files, with "ls" inside tmpfolder where you copied system. Should be a etc folder there.
Sam

to the op: I'm not knocking you here, but do you have a basic idea of generic linux file hierarchy or operations in general? Getting a basic grasp on working with files in a linux terminal will make all of these operations make a lot more sense, since most "adb shell" commands are basic linux commands.

FastCR said:
to the op: I'm not knocking you here, but do you have a basic idea of generic linux file hierarchy or operations in general? Getting a basic grasp on working with files in a linux terminal will make all of these operations make a lot more sense, since most "adb shell" commands are basic linux commands.
Click to expand...
Click to collapse
Thanks but I don't see how that comment adds anything here.
Looks like the issue is above commands copy the actual system folder (not the contents of the folder) To the root of the partition. ls shows the folder "system" not the contents including etc. They are inside the folder but if the partition is mounted as system then the folder is redundant. Will check copying the contents and see if that helps.
Once I get it working in will post back to let others know
**** in the first block of code replace
Code:
- cp -r system tmpfolder (---this will take a few minutes---)
with
Code:
- cp -r system[B]/*[/B] tmpfolder (---this will take a few minutes---)
many thanks!

FastCR said:
to the op: I'm not knocking you here, but do you have a basic idea of generic linux file hierarchy or operations in general? Getting a basic grasp on working with files in a linux terminal will make all of these operations make a lot more sense, since most "adb shell" commands are basic linux commands.
Click to expand...
Click to collapse
Why would you go out of your way to say that? It's not constructive. As a junior member with three posts and 0 thanks after a year and a half, sharpen your teeth here at XDA before you act like a big shot.

Right thanks. Changed it.
Has it worked for you?
Sent from my HTC Desire using XDA App

samuelhalff said:
You could very well replace uImage with the new Quickie overclocked uImage for froyo (see dev thread).
Click to expand...
Click to collapse
Are you certain on this part? Last I read in that thread, Froyo needs a different minimum kernel.
UPDATE: Nevermind, I missed this updated effort.
Homer

Well, last time I checked, my NC was running at 950 on froyo with setcpu.
Check the forum. There's a nookie version of quickie. Except accelerometer doesn't work..

First, huge thanks to the second poster - great guide! Can we sticky this?
Second, yes I know what dd does, etc, I've been working with Linux for about ten years . I just don't know the ins and outs of embedded devices yet.

samuelhalff said:
Right thanks. Changed it.
Has it worked for you?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
yeah i was up till 4am last night but got it working. first i tried to use my existing nf sd card... bad idea. would boot from emmc to the touch android screen to begin, but could not get past. i assume it was the issue on nookdevs because wifi was not enabled. so i removed the setupwizard.apk but somehow bricked and was unable to boot from emmc. so i took the following steps to get things working properly:
1. reimage boot and system from the stock 1.0.1 images and reset the nook to stock, didnt even touch. at the intro screen i just powered it off.
2. next i took a fresh nf sdcard and run steps from your post(with the correction to copy system contents)
3. from there i had a working nf from sdcard! i did my tweaks (google apps, market fix and button remapping from nookdevs froyo tips)
i might to put together a post with a more verbose set of instructions for a one stop froyo shop but if i do i will be sure to give you credit for your contribution.
thanks again!

Hi,
Second, yes I know what dd does, etc, I've been working with Linux for about ten years . I just don't know the ins and outs of embedded devices yet.
Click to expand...
Click to collapse
Well, that's a nice contrast. I've been working on Linux/Android for about 2 months now
I should have mentioned that the NF uSD Card must be a newly burnt image, without all the nookie tips added to it. Of course, your Google framework will crash if you port it without your data.
By the way, there's a nice trick to get past the numb android interface, simply touch every corner of the screen, starting with top left and going clockwise. You'll then be sent the your home screen, and from there you'll log on to google account again.
I think the best way of doing it would to create a flashable .zip, which I'll make tonight if I find the time and if people are really interested. But don't forget CWR dosen't work on nookie for the time being. The only way back would be through adb.
So, does anyone wish to have a flashable zip of this? Or will it be a waist of time?
Sam

samuelhalff said:
Hi,
Well, that's a nice contrast. I've been working on Linux/Android for about 2 months now
I should have mentioned that the NF uSD Card must be a newly burnt image, without all the nookie tips added to it. Of course, your Google framework will crash if you port it without your data.
By the way, there's a nice trick to get past the numb android interface, simply touch every corner of the screen, starting with top left and going clockwise. You'll then be sent the your home screen, and from there you'll log on to google account again.
I think the best way of doing it would to create a flashable .zip, which I'll make tonight if I find the time and if people are really interested. But don't forget CWR dosen't work on nookie for the time being. The only way back would be through adb.
So, does anyone wish to have a flashable zip of this? Or will it be a waist of time?
Sam
Click to expand...
Click to collapse
I would love a flashable .zip. I think many others would as well.

starkruzr said:
I would love a flashable .zip. I think many others would as well.
Click to expand...
Click to collapse
Can't wait for a flashable zip. Maybe even some cm7 release candidates would make me real happy.
Sent from Nooted NookColor using XDA App

[MOD] Webtop Via HDMI Without a Dock Added support for 4.4.80.MB860 (South Africa)

I Modified These APK files to enable the Webtop on any HDMI connection.
Removed the Device ID check from the Webtop Launcher in PortalApp.apk
And Made DockProvider/DockService Display the Webtop as an option whenever an HDMI cable is connected.
We got PROPS from Engadget: http://www.engadget.com/2011/03/05/motorola-atrix-docks-literally-and-figuratively-torn-apart-hack/
NOTE THESE FILES ARE FROM THE ATT BRANDED ATRIX v4.1.26
THEY WILL NOT WORK ON THE BELL ATRIX VARIANT
Added Support for:
Atrix 4.4.80.MB860 (South Africa) Users Go HERE: Updated Mod Files for Atrix 4.4.80.MB860 (South Africa)
Version 4.5.91 Users Go HERE: (This works now.) ATRIX 4.5.91 WEBTOP MOD FILES
ATT version 4.1.57 Users Go HERE: ATT ATRIX 4.1.57 WEBTOP MOD FILES
Bell Users Go HERE: BELL ATRIX WEBTOP MOD FILES
*new* CWM Install Method - CWM Required:
Get CWM here: http://forum.xda-developers.com/showthread.php?t=1019143
Then install the flashable zip here: CWM-ATT-4.1.26.zip
You no longer need to be rooted OR deodexed!!!!
Install Method 1 - No Root or Deodex Required:
Simpler install method:
Download The Mod Files here: HERE
Hook up your phone via usb with ADB enabled
run INSTALL.bat from the unzipped files
sit back, relax, wait until it reboots (can take upto 5min, be patient!!)
Read the disclaimer below
Enjoy!
RETURNING TO STOCK - Root Required:
This will restore the files that were backed up by the install script.
If you were Deodexed it will restore the modified files to the original Deodexed State, if you were not deodexed it will restore to stock and allow motorola updates to work again.
Note: If you were deodexed you can ignore the three lines about the odex files.
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /mnt/sdcard/WebtopModBackup/DockProvider.odex.bak /system/app/DockProvider.odex
cp /mnt/sdcard/WebtopModBackup/DockService.odex.bak /system/app/DockService.odex
cp /mnt/sdcard/WebtopModBackup/PortalApp.odex.bak /system/app/PortalApp.odex
cp /mnt/sdcard/WebtopModBackup/DockProvider.apk.bak /system/app/DockProvider.apk
cp /mnt/sdcard/WebtopModBackup/DockService.apk.bak /system/app/DockService.apk
cp /mnt/sdcard/WebtopModBackup/PortalApp.apk.bak /system/app/PortalApp.apk
chmod 644 /system/app/*
Install Method 2 - Root Required:
Other than that, install with ADB
Code:
adb push DockProvider.apk /mnt/sdcard/
adb push DockService.apk /mnt/sdcard/
adb push PortalApp.apk /mnt/sdcard/
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
mv /system/app/DockProvider.odex /system/app/DockProvider.odex.bak
mv /system/app/DockService.odex /system/app/DockService.odex.bak
mv /system/app/PortalApp.odex /system/app/PortalApp.odex.bak
cp /system/app/DockProvider.apk /system/app/DockProvider.apk.bak
cp /system/app/DockService.apk /system/app/DockService.apk.bak
cp /system/app/PortalApp.apk /system/app/PortalApp.apk.bak
cp /mnt/sdcard/DockProvider.apk /system/app
cp /mnt/sdcard/DockService.apk /system/app
cp /mnt/sdcard/PortalApp.apk /system/app
reboot
Or just use root explorer to copy the files to /system/app and rename the .odex files to .bak
Make sure you set the permissions on the files to rw-r--r-- or they will not work.
Then Enjoy your fully functional webtop.
Having problems? Read Below.
Try clearing your Dalvik Cache:
Code:
adb shell
su
rm /data/dalvik-cache/[email protected]*.dex
rm /data/dalvik-cache/[email protected]*.odex
rm /data/dalvik-cache/[email protected]*.dex
rm /data/dalvik-cache/[email protected]*.odex
acardinale said:
It was INDEED permission issues.
If using the root explorer method, you MUST fix permissions for all three files to rw-r--r--
Thanks Fenny!
Click to expand...
Click to collapse
Additionally, try unfreezing any frozen apps in Titanium Backup.
Thanks to DG for his ADEO installer script.
Appreciate my work? Buy Me a Beer:

Fenny said:
I Modified These APK files to enable the Webtop on any HDMI connection.
Removed the Device ID check from the Webtop Launcher in PortalApp.apk
And Made DockProvider/DockService Display the Webtop as an option whenever an HDMI cable is connected.
YOU WILL NEED TO BE ROOTED AND DEODEXED!!!!
@DesignGears, Mind if I modify your Installer script to load these? BTW You are in SLC? I am in Draper, We should totally meet up.
Other than that, install with ADB
Code:
adb push DockProvider.apk /mnt/sdcard/
adb push DockService.apk /mnt/sdcard/
adb push PortalApp.apk /mnt/sdcard/
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /mnt/sdcard/DockProvider.apk /system/app
cp /mnt/sdcard/DockService.apk /system/app
cp /mnt/sdcard/PortalApp.apk /system/app
reboot
Or just use root explorer.
Then Enjoy your fully functional webtop.
Click to expand...
Click to collapse
HAHA you beat me to it i was up all night last night doing this ... good work ill test yours out

Hehe told you the answer was in PortalApp.apk.

Can you do the mirroring HDMI too in the same or similar way?
Anyway you're great!

mercuryzzz said:
Can you do the mirroring HDMI too in the same or similar way?
Anyway you're great!
Click to expand...
Click to collapse
I have been looking into it, I don't think the DockPicker Activity HAS a mirroring option, but I think it should be possible with third party software.

Fenny said:
@DesignGears, Mind if I modify your Installer script to load these? BTW You are in SLC? I am in Draper, We should totally meet up.
Click to expand...
Click to collapse
We totally need a xda meetup I am in Kearns

Fenny said:
Hehe told you the answer was in PortalApp.apk.
Click to expand...
Click to collapse
Yep, i did waste alot of time in the others as well, than i spent morning posting themes etc , any how congrats and glad to see either way we on same page... now we got to get some drivers and functionality over to this webtop, as my magic track pad is lacking any multi touch but im confident in getting that done , i mean after all if is Ubuntu !!

AWESOME work.
Are you sure we need to be deodexed? we are just replacing the APKs here.

clubtech said:
AWESOME work.
Are you sure we need to be deodexed? we are just replacing the APKs here.
Click to expand...
Click to collapse
Yes if you dont understand why you need to re read up on it, as .odex files contain parts of the program that were moved out side to be optimized

So, when I copied the last one using Root Explorer it kept crashing the process PortalApp so I ended up removing the battery and yet to test it.

So we basically need to install "Adeo" to get a deodexed system...
Before i do this, when connected only with HDMI and the webtop, does the on-screen trackpad works?

ankitb4u said:
So, when I copied the last one using Root Explorer it kept crashing the process PortalApp so I ended up removing the battery and yet to test it.
Click to expand...
Click to collapse
Yeah, you need to reboot after replacing the files, can't hurt to clear the dalvik cache either. But the crashing is expected until you reboot.
clubtech said:
So we basically need to install "Adeo" to get a deodexed system...
Before i do this, when connected only with HDMI and the webtop, does the on-screen trackpad works?
Click to expand...
Click to collapse
Yeah, the on screen Trackpad, AND Keyboard work great.

clubtech said:
So we basically need to install "Adeo" to get a deodexed system...
Before i do this, when connected only with HDMI and the webtop, does the on-screen trackpad works?
Click to expand...
Click to collapse
you dont need Adeo per-say but that might be the easiest way for you to get a deodexed system unless you know what you are doing... i do not have adeo but am deodexed

Works PERFECTLY.
Did have a continuous FC after loading PortalApp.apk, but it went away with a reboot.
Tested all the WebTop functions and from what I can tell, they all work without issue.
Nicely done!

Props to the OP + contributors for getting this much-needed functionality going so quickly.

I am super excited about this. Props to all that was involved. I will be trying this later. I really need to get more familiar with ADB. Thanks again.
clipse94

Webtop via HDMI cable is working great! Now to find a working ARM-based JRE...

Awesome
correct me if im wrong, but now a bluetooth keyboard and mouse are a neccessity for 'desktop computing' right
since the dock allowed us to use a USB one
?

If I recall correctly, the phone itself has an trackpad and onscreen keyboard that can be used for desktop computing. Otherwise, a bt mouse a keyboard would be in order.......and are ordered.

clipse94 said:
If I recall correctly, the phone itself has an trackpad and onscreen keyboard that can be used for desktop computing. Otherwise, a bt mouse a keyboard would be in order.......and are ordered.
Click to expand...
Click to collapse
Correct.
BT keyboard and mouse not required.
Built in track-pad mouse and keyboard work fine.
Takes getting used too though.
This comment was made via the webtop.

[MOD] Webtop over HDMI Hack for Atrix GB 2.3.4 (HKTW, AT&T 4.5.91, ORFR 4.5.2A)

I am pleased to announce that I've patched the Atrix webtop files, allowing us to run webtop over HDMI on HKTW, AT&T 4.5.91 and ORFR 4.5.2A based system images (yes this will work on custom ROMs too), without the requirements of an official dock!
The goal is to enable the Webtop function over HDMI on any display, not just official Motorola Docks. There seem to be more HDMI display options that are disabled, for example: Clock Widget, Gallery, Music, Home. Sadly, none of these options actually do anything on the big screen, they just display the interface on the phone
However, Webtop works great! Just use the instructions below to replace the original DockService and PortalApp apk's.
Included are two versions of the DockService in the zip attached to this thread, one will enable only the additional Webtop mode for HDMI. The second one will be a "dev" version that enables every option, for those of you that are curious and/or want to try to get some of them to work over HDMI! Only one version of PortalApp is included, which is required for webtop to work, with both versions of the DockService.
One particularly interesting option that many of you are interested in is included in the dev build too: Mirror phone on display . Sadly, as stated above, it does not work (yet?). Will you get it to work?
Requirements:
Have one of the supported build and functional webtop flashed
Be rooted
Be able to work with adb
First, unpack the attached zip-file.
Go into the correct directory for your version.
Now run (in a terminal)
Code:
adb push DockService.apk /sdcard/
adb push PortalApp.apk /sdcard/
adb shell
# you are now in the phone shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
mv /system/app/DockService.apk /system/app/DockService.apk.bak
mv /system/app/PortalApp.apk /system/app/PortalApp.apk.bak
mv /system/app/DockService.odex /system/app/DockService.odex.bak
mv /system/app/PortalApp.odex /system/app/PortalApp.odex.bak
rm /data/dalvik-cache/*DockService* /data/dalvik-cache/*PortalApp*
cd /system/app
cp /sdcard/DockService.apk ./
cp /sdcard/PortalApp.apk ./
chown 0:0 ./DockService.apk
chown 0:0 ./PortalApp.apk
chmod 644 ./DockService.apk
chmod 644 ./PortalApp.apk
reboot
NOTE: if these instructions dazzle you, try Ronaldo's CWM package (for AT&T only!): http://forum.xda-developers.com/showpost.php?p=15871616&postcount=53
NOTE2: ignore errors concerning odex files if you are deodexed.
NOTE3: If you have issues with the Touchscreen Input not working, try a reboot first. If the problem doesn't go away: fastboot flash a (stock) webtop image for your base ROM. It is currently unclear what causes this problem, but my guess is a bad flash of the webtop partition, possibly CWM related. Reboot/reflash has solved the problem for a few people encountering this issue.
Thanks to Gizmo, eval & romracer!

More information on dev version
Some extra information on the different modes that are available (but currently non-functional):
Clock: Transform your phone screen into a big clock with perks. See the time from afar, set alarms, play music, view photos and get live weather information. This mode was designed for your bedside but is useful in the kitchen and as a desk clock too.
WidgetDock: Get access to the same Android widgets, apps and shortcuts as on your phone home screen. Arrange them and change the wallpaper to your liking. All of which will be saved and applied the next time your dock your phone.
Mirror: Access and display all of the phone applications on a larger display
Other: Displays non-smart mode dock apps
Gallery: View photos and videos
Music: Access, listen, and share music
There is also mention of an "easport" option, with the following description: "Entertainment detailed description goes here. To be added later."
Although not working currently, they give a good insight in what is to come

IMO, one of the best features of the Atrix right here. You're the man!

Great, I was looking forward to this. Thanks again.
Sent from rooted Atrix on 2.3.4 with unlocked bootloader using xda premium app.

_unknown said:
Today, I am pleased to announce to you a modified DockService.apk which allows us to run webtop over HDMI on HKTW, without the requirements of an official dock!
...
Major thanks go to a friend who prefers to stay anonymous, but was key in solving this problem! And as always thanks to the ever-helpful eval- for his assistance
Click to expand...
Click to collapse
Bull****, this was all you!! Awesome work, BTW =) Excited to go back to 2.3.4!

Touch pad controls dont work for me

Everything works fine

Holy **** ! That is all.

So, frist, thanx for this excelent work! Now my webtop works.
I just have one problem, my mousepad on lapdock doesnt work!

works great! thanks!

Awesome work! I only used my atrix for a few minutes before flashing 2.3.4 so I have no idea how well this worked before, but I'm pleased. All I know is when I plug in the HDMI, it restarts into the webtop mode and it works well from there. The entertainment center app crashes but that isn't as a result of this, it definitely did that when I tried to run it before.

mouse not working
loads fine but no mouse control for me either..

Same for me. The webtop loads up fine, but no mouse control on the touchpad.

_kansei_ said:
Awesome work! I only used my atrix for a few minutes before flashing 2.3.4 so I have no idea how well this worked before, but I'm pleased. All I know is when I plug in the HDMI, it restarts into the webtop mode and it works well from there. The entertainment center app crashes but that isn't as a result of this, it definitely did that when I tried to run it before.
Click to expand...
Click to collapse
Does your mouse work ? A majority, myself included, it does not ....
For the ones whose touchpad does not work.
Did you install the CG61.img or do the Update's for HKTW 2.3.4 - Roll-up of Fixes and Mods (Navalynt's Mod) that included the Webtop Fix?
I'm using Rollup tried version 1.4 and 1.5. Touchpad is broke ****.

dicksteele said:
Does your mouse work ? A majority, myself included, it does not ....
Click to expand...
Click to collapse
I was having the same problem with the mouse I fixed it by reflashing webtop from fastboot.
Sent from my MB860 using XDA App

NYG-SBXLII said:
I was having the same problem with the mouse I fixed it by reflashing webtop from fastboot.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Before I read your reply I said wtf and tried that before I gave up for the night and that was my fix also.
Now to start hacking it and get lxterminal going.
Thanks !!!

dicksteele said:
Does your mouse work ? A majority, myself included, it does not ....
For the ones whose touchpad does not work.
Did you install the CG61.img or do the Update's for HKTW 2.3.4 - Roll-up of Fixes and Mods (Navalynt's Mod) that included the Webtop Fix?
I'm using Rollup tried version 1.4 and 1.5. Touchpad is broke ****.
Click to expand...
Click to collapse
if by touchpad you mean using the screen of the phone as a touchpad, it's working fine. I don't have a lapdock to test, but I could walk over to the AT&T store in the AM to check it out.
Edit: if that is the case, and something is working on my Atrix but not on many others, I assure you it was just a lucky accident. I may be a systems engineer by date but by night I'm little more than an Android n00b. I'll gladly poke around on my device to collect info that might help others get their webtops sorted.

I successfully flashed the webtop and the touchpad is working fine. But I did notice at times, GUI became unresponsive to the touchpad (touchscreen). It it not perfect, but it works

See now this almost makes me wish I still had my Atrix...
I would love to tinker around with these APKs some more. Especially with the new options cropping up.
But, as it is I am doing it all blind... doing DEV for a phone you don't have is tricky business.

Awesome!! Worked perfect!
Installed using ADB via OP commands. Never flashed the CG61.img or the Update's for HKTW 2.3.4 - Roll-up of Fixes and Mods (Navalynt's Mod) that included the Webtop Fix and I am having absolutely NO problems using the screen as the mouse pad.
Make sure you followed all commands and set the permissions correctly with the chmod command.
No problems at all here, but I did flash the non-dev apk.... if you flashed the dev apk then that may be where the mouse pad issue is, I can not confirm.

HP Touchpad running Ubuntu Touch

THIS THREAD IS NOW OUTDATED. Page 17 and on contains information for Ubuntu Touch Saucy port.
NEW THREAD ON THE WAY.
http://forum.xda-developers.com/showthread.php?t=2426924
What works. Wifi+ADB+Touch.
What doesn't work: Sound+Bluetooth. Bluetooth doesn't work yet in Ubuntu Touch, and Sound doesn't work with the Evervolv source. Camera.
Download these files.
http://cdimage.ubuntu.com/ubuntu-to...c-demo/quantal-preinstalled-phablet-armhf.zip Ubuntu Touch RootFS
Recovery Image.
http://gdurl.com/A0mz/download
Put on your SDCARD and install in ClockWorkMod. You know.. when you first turn on the tablet, moboot loads.. you should see a menu for clockwork recovery mod.
EDIT: Oh yeah.. First do a factory reset in recovery mod, THEN install the zip files... The factory reset formats the cm-cache and cm-data partitions.. There are 3 partitions. cm-cache cm-data cm-system. Factory reset formats cache and data.. When you install the first zip, it formats the system partition. Then after that install the RootFS.zip that you downloaded from ubuntu... It extracts the RootFS to the cm-data partition, that you formatted. So it should be clean.
Reboot.
Enjoy!
Oh yeah.. Onscreen Keyboard is not sized right. Seems to be an Ubuntu bug... If your fonts are wrong. .reboot.. check out /system/etc/init.d/90userinit for the stuff I added.
thanks to the usual guys. JCSullins, Evervolv, Tigeris and litz and ompx in ubuntu-touch on irc. The wifi fix was an idea I got while stuck in traffic. Can't believe it worked.
Oh yeah.. THANK YOU DR. MARBLE.
PS. I read somewhere you need at least 600MB of free space, AFTER you copy the files to the sdcard, for the extraction to go well...

nice

Awesome, can't wait to try this out!

How to install that on tp?

Way too cool!! tnx for all the hard work

tux-world said:
How to install that on tp?
Click to expand...
Click to collapse
He says: POST IT SOON. In other words: you have to wait until he finishes the porting.

Crazy how the font turned out like that
Sent from my SAMSUNG-SGH-T989 using xda premium

Great news
SGA, thanks for your effort in bringing Ubuntu touch to Touchpad!
If you need help with testers, let me know

Vistaus said:
He says: POST IT SOON. In other words: you have to wait until he finishes the porting.
Click to expand...
Click to collapse
is this CM?

tux-world said:
is this CM?
Click to expand...
Click to collapse
No. It's Ubuntu Touch, but from what I have heard on XDA Developer T.V. (check 'em out on YouTube) it is based on CyanogenMod.
Sent from my Xperia S ~XZXperience~Unlocked BL~Rooted~6.1.A.2.55~

I'm assuming the install process will be similar to The Nexus line, flash the core system then the phablet zip.
Sent from my Nexus 7 using xda app-developers app

What source did you use to compile? I tried to compile it and kept getting some weird error got frustrated and gave up.

blmvxer said:
I'm assuming the install process will be similar to The Nexus line, flash the core system then the phablet zip.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I think that's how it will always be. The core zip is device specific and contains the CM base while the phablet zip is for all devices.

Off to 3.0.8
EDIT TO POST. UNMOUNT PROC OUTSIDE OF CHROOT VIA USERINIT, AND NETWORK MANAGER WORKS WITHOUT FANOTIFY
Going to try a newer kernel to get wifi working. We need Fanotify in the kernel for the network manager to see the wireless. Has to do with proc mounted inside of a chroot and daemons having permission. Sad because once you run ubuntu_chroot shell to get in, you can run iwlist wlan0 scan...
Status Update Complete.
How to compile. Grab evervolv's device folder, but not his vendor folder.. grab hardware/qcom hardware/atheros and the compat-wireless from.. some folder.. forgot the name... I got these from evervolv's ubuntuphone branch for tenderloin.. (the kernel) and his build of android.
Those are the current sources.. May change.. Be sure to change ev.mk file to cm.mk, and change /vender/ev (inside of ev.mk) to /vendor/cm, ev.dependencies file to cm.dependencies....
JCSullins announced he will start work on JB. So that is cool. But.. 3.0.8 Kernel doesn't have working sound or bluetooth. Until someone figures that out with 3.0.8, Ubuntu-Touch and the Touchpad WILL NOT HAVE SOUND. (cough cough nag jcsullins cough cough).. That guy is the man to go to for that.
Backporting Fanotify is not easy. You run into having to change the msm code. (I ran into msm-watchdog.c) So much you might as well just go to 3.0.8.. I have an odd feeling that is someone were to backport it, sound would stop working....
EDIT TO POST. UNMOUNT PROC OUTSIDE OF CHROOT VIA USERINIT, AND NETWORK MANAGER WORKS WITHOUT FANOTIFY
Backup you jellybean system folder to a tarball and then extract it somewhere.. Same with the Ubuntu Touch system folder.
(I was about to give up!)
cp -R -f /jellybean/lib/* /system/lib
cp -R -f /ubuntutouch/lib/* /system/lib
cp -R -f /jellybean/etc/firmware/* /system/etc/firmware (my adreno firmware was missing, so this will fix that)
reboot.. and it worked.. merged libraries.
Fonts are not bad all the time..... Going to try this with 3.0.8 tonight.. If someone is bored today, give it a shot. Let us know how it works.
To brunch tenderloin I have to manually create out/host/linux-x86/bin and stick mkimage in there.
go to vender/cm/vendersetup.sh and add add-lunch-combo cm-tenderloin-userdebug.. I think.
there is a mkimage in the ubuntu touch source.. I used that. /system/extras/mkimage.. it needs to be compiled gcc mkimage.c -o mkimage -lz
then copy it cp ./system/extras/mkimage/mkimage ./out/host/linux-x86/bin no idea if this is required.
there are 2 bzr branch commands that need to be run.. google that.. Should be in Ubuntu Porting guide, but it's not. ubuntuappmanager library and some other library.
edit: run this inside of the ubuntu touch source folder/ubuntu
"bzr branch lphablet-extras/libhybris hybris" stupid smiles. =)
"bzr branch lplatform-api platform-api"
http://forum.xda-developers.com/showthread.php?p=38745624
dont forget to run extract-files.sh and get-prebuild, etc.
source build/envsetup.sh
lunch (pick 14)
brunch tenderloin
I bring over ts_srv and that other ts program from jellybean to ubuntu and currently add commands to /system/etc/init.d/90userinit to get stuff running.. Lazy, I am.
Confused? That is my rough draft guide.
A dude by the name of tigeris, or something that started with tig.. he helped me a lot on ubuntu-phone on irc. So did another guy named.. omxy.. I think... I will find them. Gotta go,
EDIT TO POST. UNMOUNT PROC OUTSIDE OF CHROOT VIA USERINIT, AND NETWORK MANAGER WORKS WITHOUT FANOTIFY

My wife would really like someone to pick this work up.. She wants me to .. "come back to the family"....

Oh yeah.. Wifi does work.
To get wifi working..
do this.
ubuntu_chroot shell
mount -o proc proc /proc
network manager should now bomb.
this is for open security.
ifconfig wlan0 essid "your essid"
ifconfig wlan0 up
dhcpcd wlan0
dhcpcd taken from jellybean tar.gz from the bin folder.. So.. yeah.. but no network-manager without fanotify and some other daemons. be sure to take dhcpcd stuff from etc.
DONT RUN ubuntu_chroot all by itself.. It will crash.
ALSO you MUST unmount proc before shutting down or it will be stuck in mtab and you will have old stuff inside of the /proc folder, inside of chroot, or rather /data/ubuntu/proc..
Problems? Restore ubuntufs tarball in recovery.
I will release something sometime soon.. after testing 3.0.8.. but if you know how to do all this stuff, be my guest.

Why don't you create your own github and share with us?
I bet that there are a lot of devs who want to continue.
I am really interested but I kind of got lost when you said to get the files from Evervolv... Can you post links to be more specific please?
Thank you.

Its just githib.com/evervolv
Sent from my Touchpad using xda premium

Doing that tonight... By the end of tonight I will release something..
It will be 3 files.
The first will be the .zip file that has the actual /system folder
second is of course from ubuntu and is the rootfs.
Third will be a tarball you guys can extract once the tablet is booted that will just have touch and graphics working. You can use wifi if you run it from adb, and keep the tablet powered on.
I haven't even touched pixel ratio.
Oh.. a 4th file.. of the whole ubuntu touch folder.. cleaned and made proper.. Uploaded to google drive.. Or hell I guess I can look at github...
Gotta play mario with my little girl first.

jshafer817 said:
Gotta play mario with my little girl first.
Click to expand...
Click to collapse
LOL
Gotta always spend time with them :good: