Related
The following is a direct copy paste from somewhere else Enjoy! The wait is over for Alpha!
___________________________________
CyanogenMod for TouchPad
ALPHA 1
"LOWER YOUR EXPECTATIONS" EDITION
* READ THIS COMPLETELY *
Sweet, sweet Internet,
You waited more-or-less patiently for over a month, so at long last, here it is-- an alpha version of CyanogenMod 7.1.0 (an enhanced version of Google's Android 2.3) for the TouchPad.
Understand, this version is definitely an alpha, with all that implies. Those expecting perfection will be sorely disappointed. Many things won't work as well as they will eventually. But you wanted it ASAP, and hopefully, this version should be somewhat useable and gives a sense of progress.
With that said, let's answer some questions, FAQ style.
WHAT KIND OF WARRANTY DOES THIS SOFTWARE COME WITH, IF ANY?
THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Got it? Good.
WHAT IS CYANOGENMOD FOR TOUCHPAD?
CyanogenMod is a community-developed and supported Android distribution for over 60 tablets and phones. This ported version is for the recently discontinued HP TouchPad tablet.
In truth, this "alpha" version is not intended for the general public. Rather, those technically competent hobbyists and developers who are interested in testing an early development version and fully understand the risks of doing so may find interest in it. But there are many bugs and problems in this alpha version. There will be MANY app compatibility issues as well.
WHAT IS THE "ALPHA 1" VERSION AND HOW DO I INSTALL IT?
*** This early version represents the start of a process, not the end, and as such will not be sufficiently awesome, so take any expectations you have and lower them. Now lower them about five feet below that. ***
To be clear, you are encouraged NOT to install this software, as the alpha is only a test version and as stated above, there is no claim that it is fit for any purpose. You may experience issues ranging from the benign to the very serious, including potential data leakage, and/or permanent loss of data, and even the possible "bricking" or permanent disabling of your device. Or worse. It can't be emphasized enough how risky its use may be. Try it entirely at your own risk and with full understanding of the potential for problems and acceptance of any consequences that may result.
That said, if you do understand, acknowlege, and accept these risks and still want to continue, there are installation instructions (and additional exciting caveats and warnings) bundled with ACME Installer.
DOES INSTALLING CYANOGENMOD VOID MY WARRANTY WITH HP?
While HP has expressed moral support for the project ("For those of you in the development community actively working to port Android to the Touchpad, we applaud your efforts"), other HP representatives have also stated that "anyone who loads Android on their Touchpad voids their warranty."
Therefore, it may be prudent to assume that installing (or attempting to install) Android or any other OS besides the stock WebOS would result in the voiding of your manufacturer's warranty. Generally speaking, you must assume any and all risk when experimenting with this software.
SO WHAT WORKS AND WHAT DOESN'T WORK?
Most hardware features of the Tablet should now be supported, although not 100%. There may be issues with sound, camera, wifi, etc. As stated previously, it is definitely an alpha build.
Here is a helpful list of features that are near-completion. Thanks to DarkRedFlame for compiling this.
* Booting into Android
* ADB commands via ADB
* Power, back/home and volume button layout
* Touchscreen support (Multi-touch, 10 fingers)
* GPU Acceleration (2D Acceleration doesn't work, but not a release blocker)
* Dual core processing
* Bluetooth
* Sound
* Accelerometer
* Power Management
* Battery Reporting
* Camera(only video chat, no recording or snapshots)
* Vibration
* Backlight
* LED
* Multiboot (via moboot)
* ClockworkMod Recovery
* Fast Switch Boot
* Fake SD card Mount
* Light Sensor(need to check "Enable Light Decrease" in cyanogenmod settings->display->automatic backlight
* Accessing webOS files from Android and vice versa
* Touchstone Support
* Softkeys
* Wifi
* And much, much more!
As far as what *doesn't* work, that list is probably too long for a FAQ.
* Many apps will have compatibility issues. Many. Including possibly your favorite app.
* Phone-related items (such as the dialer and text messenger) are left in the build. These apps consume minimal energy and can largely be ignored.
* Speaking of energy-- power management has not been the focus of the port thus far. Battery life is not as good as it might be, and you can probably expect improvement in this area over time.
DOES ROM MANAGER WORK?
Not completely. It can't be used to install or update ClockworkMod Recovery for example. Developer Koush will first need to add TouchPad compatibility to Rom Manager.
ONCE THE ALPHA IS INSTALLED, HOW DO I UPDATE FROM THERE?
Once CM is installed, you can use the original ACME installer to install most (but not all) subsequent "update...zip" files you come across.
Or, if you have installed and are familiar with ClockworkMod Recovery, you can also use it to install "update...zip" files as you would for other CyanogenMod devices.
WHAT IS THIS "CLOCKWORKMOD RECOVERY" EXACTLY?
ClockworkMod Recovery, which you can start into from the boot menu, is a special "Recovery" mode-- often used in emergencies when your regular system doesn't load for some reason. Once you have started ClockWorkMod, you are presented with a series of menus and can chose to reset your installation of CyanogenMod to factory settings or load or format individual areas (called "partitions") of your installation.
Additionally, ClockworkMod can be used to back up or restore your entire Cyanogenmod installation to your SD Card. It can also install updates from special "update files" (which are usually named update-some-name.zip).
Since ClockworkMod Recovery is part of CyanogenMod, it is only "aware" of your Cyanogenmod installation. It can not back up or install updates to WebOS or any other operating system.
THE TOUCHPAD DOESN'T HAVE AN SD CARD SLOT. YET CLOCKWORKMOD RECOVERY AND OTHER APPS IN CYANOGENMOD MAY REQUIRE ME TO USE AN SD CARD. WHAT NOW?
If you've used WebOS, you may be familiar with the user-accessible "media" partition that can be mounted to your computer via USB. Well, that "media" partition is now also shared with ClockworkMod Recovery and CyanogenMod, both of whom now identify it as the SD Card (or /sdcard or /mnt/sdcard). So think of this area as a "fake" SD Card, which can be accessed from WebOS, ClockworkMod Recovery, AND CyanogenMod. You can therefore use it as a common area to share files between different operating systems as well as mount it to your PC (again, from different boots). Neat, huh?
I KEEP SEEING REFERENCES TO "MOBOOT". WHAT'S THAT?
MoBoot is a project separate from CyanogenMod, lead by jcsullins and tmzt and based on the "lk" project, which allows the TouchPad to boot into multiple operating systems or recovery images. Technically speaking, it loads just after the "bootie" bootloader that comes with the TouchPad, and displays a menu for the user to select whether they'd like to boot into the stock WebOS or Cyanogenmod, or something else.
You can install the latest version of moboot using ACME Installer. It can NOT yet be installed from ClockworkMod Recovery.
More information about using moboot can be found on IRC (freenode server) in the #moboot channel.
Or, you can learn more about the project at:
http://code.google.com/p/moboot
SO WHERE DO I REPORT BUGS?
The issue list is currently at http://code.google.com/p/cmtouchpad/issues/list
To avoid duplication, do not submit a new issue until you have thoroughly read the existing issues.
OH NOES! I SCREWED EVERYTHING UP! WHAT DO I DO IF I "BRICK" OR SOMEHOW MY TABLET STOPS WORKING?
After you freak out and regret having tried this, you can attempt to hold down the "home" button and the power button together for about 30 seconds.
DIDN'T WORK
Still nothing? Or maybe you have a dreaded triangle-with-an-exclamation-mark on the screen?
Another "emergency" idea (for advanced folks only) is to boot ClockWorkMod Recovery *directly* from your computer via USB cable rather than from the TouchPad's internal storage. To try this, find an "update...zip" file that contains ClockWorkMod. Inside this zip file is a file called something like "uImage.ClockWorkMod". Extract/unzip that file to your computer, then use novacom (which you used with ACME installer) to "inject" ClockworkMod into your TouchPad.
This process should be familiar to you-- very similar in fact to using ACME Installer. It's done by starting the tablet with the up-volume key held down. When you see the USB icon, connect your computer to the TouchPad via USB, then, in a Terminal, navigate on your computer to where the uImage.ClockWorkmod file is, and type:
novacom boot mem:// < uImage.ClockworkMod
Assuming everything went well and ClockworkMod did start up, you may now use CWM to re-install "update...zip" files, restore from backups, format partitions, or reset everything to factory settings. Or use ADB (search online for "ADB" if you're not familiar with this fantastic Android tool) to figure out what's wrong.
I DON'T UNDERSTAND ANY OF WHAT YOU JUST SAID. CAN'T I JUST START OVER?
Sounds like you should give the "WebOS Doctor" a shot. The WebOS Doctor is a program from HP that is used, effectively, to wipe your TouchPad and reinstall the WebOS software so you can begin anew. Get more info here:
http://ws.hpwebos.com/webosdoctor/sorry.htm
The very helpful homebrew site WebOS-Internals.org also has a page that talks about how to use it:
http://www.webos-internals.org/wiki/How_To_Recover
DO I HAVE ANY OTHER OPTIONS FOR HELP?
If none of the above ideas helped, you'll have to go online for assistance.
Browse to http://webchat.freenode.net/ and fill out the web form. Under "Channels", put #cyanogenmod-touchpad and hopefully someone there will have some helpful advice. It is usually not necessary to preface your question with "Can I ask a question?"-- just go ahead and ask.
You may also try one of the many support forums at www.rootzwiki.com or www.xda-developers.com or another Android site.
To a large extent, the Android community will have to help each other as this is an unofficial, buggy release with no corporate, official, or really *any* support. Now you know the reason for all the caveats and warnings.
WHERE IS THE SOURCE CODE FOR THIS RELEASE?
Some of the Android code licensed under the Apache and other Open Source licenses for this alpha test version is not yet available to the general public. However, all GNU Public Licensed software that comprises CyanogenMod, including the kernel, is available at http://www.github.com/cyanogenmod. The kernel for TouchPad used by this project is available at https://github.com/CyanogenMod/hp-kernel-tenderloin .
When appropriate (hopefully sooner rather than later), CyanogenMod will open the code, and patches/fixes can then be submitted by developers via Gerrit at:
http://review.cyanogenmod.com
IS THIS ALPHA OVERCLOCKED?
Overclocking is optional and can be done with an app like SetCPU. Keep in mind it can cause additional instability!
HOW CAN I DONATE TO THIS PROJECT?
To be clear, the key developers of CyanogenMod for TouchPad are not interested in monetary donations for this effort. This is a project motivated by the challenge and satisfaction of working on the port itself, not by financial reward. The developers have previously announced that any "bounty" won for completing this port to TouchPad will be donated to charity.
That said, there are some who have insisted on making some kind of donation to express their support and gratitude. It should therefore be noted that the official CyanogenMod Web site does have a "donation" area in the bottom right-hand corner of the front page.
http://www.cyanogenmod.com/
Also, the CM for TP developers recommend you learn about the Electronic Frontier Foundation ( http://www.eff.org ), which is an organization fighting to preserve and protect the legal rights of the common citizen in this rapidly changing digital age. As large companies and governments try to limit or narrow your rights, the EFF is on the front lines defending the public interest. A contribution to the EFF is also tax-deductible for United States citizens. As supporters, the developers invite you to visit the EFF web site and learn more about their activities and goals.
http://www.eff.org
I AM A "KANGER" WHO WANTS TO TAKE CYANOGENMOD, MODIFY SOME MINOR FEATURE SUCH AS FONTS OR THEMES, THEN OFFER IT UNDER A NEW NAME AND ASK FOR DONATIONS (OR SELL IT) AS IF THIS IS ALL MY WORK. CAN YOU HELP ME?
Absolutely not. One of the concerns about releasing an early alpha is the sad fact that unscrupulous parasites will creep from the shadows of the Internet, slap their name on this port, then try to sell it for an inflated and unwarranted profit. This has been the case for CM on other devices, and we expect, unfortunately, the same thing will likely happen here.
While the GPL and Apache licenses certainly allow CyanogenMod and Android to be sold, and while there may be legitimate occasions where installation or support expenses may warrant or justify charging money, the CM for Touchpad developers are unified in disgust for those who prey upon the uninformed by simply not telling them that a free version of the software is available or by claiming in their advertisements or to the media (who should know better) that they have created or designed the port themselves.
To be clear now-- mods, themes, remixes, and hacks are great- it's the life blood of open source. And there's nothing at all wrong with asking for donations or even charging for something of value you've contributed. But skimming off the free work of others is plain douchy. And not in a good way.
So the developers ask YOU, beloved Internet, to do your part in keeping an eye out for each other's welfare, and enlighten those, including in the media, who might otherwise be taken in by unscrupulous hucksters.
SO WHAT ABOUT YOU? WHO DO YOU WANT TO THANK?
Shout-outs, yeah! Let's start with Hewlett Packard/Palm -- for creating a wonderful tablet, then making it affordable. We are inspired and encouraged by their commitment to Open Source (and do hope this kernel source kerfuffle is resolved quickly). Generally speaking, we really like WebOS and especially the WebOS community, and wanted to made sure that WebOS would continue to be accessible along with CM7, so that users can have the best of all worlds. While thanking HP, it's appropriate to also thank their technical partner Qualcomm, whose Code Aurora project makes CM7 possible not only on the TouchPad, but many other devices as well.
Thanks to Rootzwiki for hosting a forum where people could have meta-conversations about what was appropriate for the forum, as well as meta-meta-conversations and meta-meta-meta conversations... to degrees extending into meta-oblivion. Similarly, thanks to the residents of the freenode IRC channel #cyanogenmod-touchpad for never, ever asking for an ETA. Again, big ups to the WebOS homebrew community for their participation and willingness to offer all kinds of technical insights into how things worked. Particularly we'd like to recognize http://www.webos-internals.org as a source of enlightenment for anyone who's interested in WebOS. If you haven't installed their excellent Preware by now, you have no excuse. Go do it.
A special moment of recognition goes to the members of Team TouchDroid. Wow, that was some drama, huh?
There are countless others who deserve buku credit-- Google, Github, Kernel.org, the wider CyanogenMod and Android community, the thread-that-never-ended on slickdeals.net, those who contributed TouchPads to developers, our teachers, parents, wives, husbands, children, pets, Newton, Tesla, Turing, etc. But this isn't the Grammys, so we'll stop here. The general point is to recognize that all developers stand on the shoulders of giants.
So thanks, everyone, for your help and support so far. And if anyone was missed, sorry.
WHAT HAPPENS WHEN ICE CREAM SANDWICH COMES OUT?
You mean the next version of Android expected from Google sometime in November '11? Well, if the transition from Froyo (2.2) to Gingerbread (2.3) is a model, it may take several months from the release of the Ice Cream Sandwich source code before a viable port to TouchPad is available.
Or not. Ya never know.
WHERE IS THE SOURCE CODE?
Source code can be found at http://www.github.com/cyanogenmod
As of alpha 1 the kernel source is open. The rest of the source will be opened
as soon as some code can be merged into mainline CM7. This expected to happen
very soon.
DOWNLOADS
Initial install will require multiple files to download. Download the installer README first
and be sure you understand the directions.
Note: Please do not link directly to files. Link only to this thread.
Alpha1:
Note: Alpha1 is an extremely rough build. Expect more crashes than you can count. Many many things do not work yet.
Mirror 1:
REAMDE: http://mirror.dal.tdrevolution.net/kmobs/ACMEInstaller README.txt
Installer: http://mirror.dal.tdrevolution.net/kmobs/ACMEInstaller
CM7: http://mirror.dal.tdrevolution.net/kmobs/update-cm-7.1.0-tenderloin-a1-fullofbugs.zip
Clockwork Recovery: http://goo-inside.me/roms/cmtouchpad/alpha1/update-cwm_tenderloin-1012.zip
Mirror 2:
README and Installer: http://goo-inside.me/roms/cmtouchpad...EInstaller.zip
CM7: http://goo-inside.me/roms/cmtouchpad...fullofbugs.zip
Clockwork Recovery http://goo-inside.me/roms/cmtouchpad...rloin-1012.zip
Please keep the conversations civil!
First video: http://www.youtube.com/watch?v=c20yOVKm5UM
Second video: http://youtu.be/fsZXe-_v9uQ
Third video: http://youtu.be/8IVkj_vdY6s
Fourth video: http://www.youtube.com/watch?v=ApfeSj4Ql6Q
Alpha video: http://tinyurl.com/43gwjlo
Show Your Support
To receive notifications regarding updates -> Click to Mark as Installed.
If you like this modification -> Click to Nominate for Modification of the Month.
If you like to thank the author -> Click Here
This modification may not be copied, reproduced or published elsewhere without author's permission.
CM7 Alpha Released 10/13
CM7 Alpha Released [10/13]
CyanogenMod - (A Project that goal is to be able to dual-boot android and webOS)
What currently works:
COMPLETE Wifi (Fixed 10/9)
COMPLETE Camera (Fixed 10/7)
COMPLETE Touchstone Support (Fixed 10/6)
COMPLETE Power Management (Fixed 10/4)
COMPLETE Clockwork Recovery (Fixed 9/30)
COMPLETE Battery Reporting (Fixed 9/29)
COMPLETE Fake SD card Mount (Fixed 9/26)
COMPLETE Vibration (Fixed 9/26)
COMPLETE Bluetooth (Fixed 9/24)
COMPLETE Dual CPU Processor (Fixed 9/23)
COMPLETE Fast Switch Boot (Appears fixed to me Video Update 9/23)
COMPLETE Booting into Android
COMPLETE ADB commands via ADB
COMPLETE Power, back/home and volume button layout
COMPLETE Touchscreen support (Multi-touch, 10 fingers)
COMPLETE GPU Acceleration (50/50 2D Accel support, just like any other gingerbread device out there)
COMPLETE Sound http://www.youtube.com/watch?v=ApfeSj4Ql6Q
COMPLETE Accelerometer http://www.youtube.com/watch?v=8IVkj_vdY6s
COMPLETE Backlight (Confirmed in IRC)
COMPLETE LED (Confirmed in IRC)
COMPLETE Multiboot (Confirmed in IRC)
COMPLETE Light Sensor (Confirmed in IRC)
COMPLETE Accessing webOS files from Android and vice versa
COMPLETE Softkeys
PARTIALLY Compass (Bugs need to be worked out)
What does not currently work:
See issues below
What's currently being worked on:
Gyroscope
Beating Metal Gear Solid 4 under 5 hours.
Bugs and Issues, see below.
What can possibly work:
HDMI through Micro USB (The System-on-a-Chip has the required hardware, have to find which pin #) (webOS 3.0.4 may have HDMI support, and if so we can reverse engineer the process, stay tuned)
GPS (Does not seem possible to implement because hardware seems to be lacking GPS functionality)
Issues:
High Priority Cannot record sound, unless sound is already playing [Accepted]
High Priority Battery Drains while sleeping and active [Accepted]
High Priority Plugging in headphones does not mute external speakers [Accepted]
Medium Priority Apps in market are being filtered [Accepted]
Medium Priority Battery does not shut down device at critical battery level [Reported]
Medium Priority Camera does not take pictures [Accepted]
Low Priority Reboot and Shutdown can take a long time [Accepted]
Low Priority LED light turns off while sleeping [Accepted]
Low Priority Light Sensor does not work automatically, needs to be turned on manually [Accepted]
Low Priority No audio support for BT headsets [Accepted]
Low Priority Add divx codecs for video support [Started]
Low Priority GPS apps crashes because apps assume for valid GPS [Accepted]
Fixed Reboot to Android from webOS app (Fixed 10/12)
Fixed msm_rotator does not work correctly. Screen may rotate for video, but becomes distorted. (Fixed 10/11)
Fixed Sleep Issues (Fixed 10/11)
Fixed Touchscreen has feedback issues (Fixed 10/11)
Fixed Camera fails to save to disk, does not rotate (Fixed 10/11)
Fixed Airplane mode stays on once turned on, happens because the touchpad doesn't have a real radio interface layer. (Fixed 10/10)
Fixed Screen stays blank for 10 second before boot animation appears (Fixed 10/9) (Confirmed in IRC)
Fixed Wifi Issues (Fixed 10/9)
Fixed Sh exceeds the open file limit (Fixed 10/9)
Fixed Sleep Issues for Wifi (Fixed 10/9)
Fixed CPU stays on max frequency (Fixed 10/8)
Fixed Touchscreen turns off when accelerometer is disabled (Fixed 10/7)
Fixed Touchstone works and charges, but no event is raised to show you it's charging (Fixed 10/6)
Fixed Touchscreen events (touches) are ignored after sleep (Fixed 10/5)
Fixed Protect certain partitions in the kernel (Fixed 10/5)
Fixed Root for bluetooth cmattach (Fixed 10/5)
Fixed Touchscreen stays on at all times, even when screen is turned off (Fixed 10/4)
Fixed Touchscreen has issues with pinch gestures (Fixed 10/3)
Fixed No root access (Fixed 9/30)
Way to double post there ace...man these forums are a joke now. Ill stick to rootz from now on.
Nice... installed perfectly anyone pushed Market.apk to theirs yet....?
Scratch that... Installed "gapps gb 20110815 signed.zip"
Been waiting for this.. Thanks to all the devs working on this project.
Any feedback from the early installers?
At work, so I won't be able to try this for a good 10-11 hours.
Missing G-Apps still trying to find an update that will install them, other than that the device is very snappy touchscreen it so much more responsive a few minor bugs (one of which it wont connect to my work's wireless) other than that i am very impressed.
Just Me said:
Any feedback from the early installers?
At work, so I won't be able to try this for a good 10-11 hours.
Click to expand...
Click to collapse
I watched the install vid. but i need to install from a windows computer. anyone with a walkthrough?
jdmtsx said:
I watched the install vid. but i need to install from a windows computer. anyone with a walkthrough?
Click to expand...
Click to collapse
I've written a "somewhat" easier tutorial here
Question at all: is it normal there is no marketplace?
(I'm not that android-guru ^^ )
so two questions to the early addopters: will it delete/modify the custom kernel in webos and will it **** up the partition layout on the touchpad?
mendel129 said:
I've written a "somewhat" easier tutorial here
Question at all: is it normal there is no marketplace?
(I'm not that android-guru ^^ )
Click to expand...
Click to collapse
Thanks for your tutorial!
However step 5 is vague.
could you please elaborate on:
grab the cmd, browse to the place where you’ve downloaded the acmeinstaller file, and type “C:\Program Files\Palm, Inc\novacom” boot mem:// < ACMEInstaller
How do I "browse to the place I've downloaded the acme installer?
Lets say for example it is in: C:\Users\Zak\Desktop\cm7touchpad\ACMEinstaller
How do I browse there in CMD.exe ?
Thanks!
zgroten said:
Thanks for your tutorial!
However step 5 is vague.
could you please elaborate on:
grab the cmd, browse to the place where you’ve downloaded the acmeinstaller file, and type “C:\Program Files\Palm, Inc\novacom” boot mem:// < ACMEInstaller
How do I "browse to the place I've downloaded the acme installer?
Lets say for example it is in: C:\Users\Zak\Desktop\cm7touchpad\ACMEinstaller
How do I browse there in CMD.exe ?
Thanks!
Click to expand...
Click to collapse
cd \Desktop
cd \cm7touchpad
or just cd C:\Users\Zak\Desktop\cm7touchpad\
(you can autocomplete with tab )
mendel129 said:
cd \Desktop
cd \cm7touchpad
or just cd C:\Users\Zak\Desktop\cm7touchpad\
(you can autocomplete with tab )
Click to expand...
Click to collapse
Thanks!!
Sorry for bugging you, one more question...
I am getting "Access is denied" after typing:
C:\Program Files\Palm, Inc\novacom” boot mem:// < ACMEInstaller
zgroten said:
Thanks!!
Sorry for bugging you, one more question...
I am getting "Access is denied" after typing:
C:\Program Files\Palm, Inc\novacom” boot mem:// < ACMEInstaller
Click to expand...
Click to collapse
1) are you running cmd in elevated permissions?
2) do you have novacom installed in the first place?
mendel129 said:
1) are you running cmd in elevated permissions?
2) do you have novacom installed in the first place?
Click to expand...
Click to collapse
Yes, and Yes.
It shows up in my programs list as "Novacomd"
Well mine installed ok but it seems to wipe your WebOS install (at least it did for me) so I had to restore my palm profile!
Not had much time to play with android yet but im impressed so far!
Loving this! xD
Sent from my HP Touchpad using Tapatalk
Can't imagine why it wasn't released here.
/sarcasm
My problem is actually that I cannot get it to mount.
mendel129 said:
Question at all: is it normal there is no marketplace?
(I'm not that android-guru ^^ )
Click to expand...
Click to collapse
download the google apps package from here: http://wiki.cyanogenmod.com/wiki/Latest_Version#Google_Apps
put in on your touchpad
boot clockwork recovery using novacom (same as for installing cm7, but instead of using "ACMEInstaller" use "uImage.ClockworkMod", go to install, install from zip on sd card, choose the google apps package
done =)
and you have a functional marketplace
Jelly Bean Android version 4.1 and announced a few months ago by Google, has already his successor. It would be called, according to the latest rumors, Key Lime Pie or tart limes in French and is labeled with the number 4.2.
It is the site Android and Me brings us the latest news, with an internal source who has provided accurate information in the past.
According to them, this new version bring a personalization center, Project Roadrunner, or updating applications Google Play Now Google and video player.
The personalization center:
According to the source, a personalization center will be available to change ringtones, language packs, wallpapers, launcher, and a few other customizable filters. Certain assumptions are talking about custom themes introduced by the manufacturers, but that would be only a supplement and not pre-installed interface directly fused to the system time. This center is primarily a convenient way to allow the average consumer to make some basic customizations. The range of options can obviously be extended via Google Play.
This new system will allow manufacturers to provide their own interfaces manufacturers through this new center. When updates to Android if the manufacturer fails to provide a version compatible with the theme, simply return the terminal to the classic user interface.
So it sounds like a dream come true. Google may have finally found a solution that will allow consumers to update the Android operating system base, without having to wait for the new version of the interface builder.
The Roadrunner Project:
Somewhat in the same spirit as the Butter Project on Android 4.1, which allows an increase in the number of FPS (note: the number of frames per second), the Roadrunner Project will improve battery life by optimizing and reduced power consumption, allowing improved overall autonomy.
Update Google Play Now Google and video player:
Play Google: it is enhanced with new features such as personalized search - Optional integration with promotions - Improved notifications and improved in-app purchase;
Now Google: Google voice assistant now offer a user guide that will, for example, ask such questions as: "How do I enable Bluetooth? "Or" How can I reduce the brightness? "Facilitating these operations for novice users;
The native video player: it would benefit from an update regarding APIs and codecs will probably accounting expanded video formats, allowing the development of a new application dedicated to this medium.
It should be borne in mind that all this must be considered as a rumor, even if that source is reliable. Ilandroid-4-2-visits seems that Google has also begun to distribute devices to its employees since some sites are beginning to see the emergence of Android 4.2 in their statistics.
The concept of a certification program for Google Nexus is not excluded given the number of phones provided by Google this year. This will allow the web giant to take a little more control over certain issues and improve the Android experience.
What do you think of these potential new? Are you impatient? As often, Wait & See.
You could have just contributed to this very similar and active thread instead of creating a whole new thread.
Duplicate thread.
Please search before starting a new thread.
Sent from my GT-I9300 using xda premium
Please search before posting.. Is it that difficult?
Thread closed
Below are the entries for the Tablet Z Development Contest (in random order). The subsequent posts in this thread have more details of each project including the developer's most recent information on the project. Before casting your vote, read through each of the projects in full - you can't change your vote after you've made it!
lilstevie - Open Source LK (LittleKernel) Bootloader + Recovery
Apache14 - Open Source Infrared Receiver & Transmitter Library
zacthespack - LinuxOnAndroid Project (Standard/ROM/Native)
sailnw - App for Sailors and Cruisers Using Waterproof Tablet (no link)
rayman - Tablet Multiboot Manager
anthonycr - Lightning Browser (Open Source Web browser)
bluefa1con - PAC All-In-One ROM
mamenyaka - Ubuntu Touch Porting
rydo88 - Tablet Z Smart House System
lilstevie - Open Source LK (LittleKernel) Bootloader + Recovery
What is LittleKernel?
LittleKernel is an opensource bootloader for qualcomm devices available from codeaurora.
Why LK?
TL;DR Version
LK allows running separate boot and recovery that are fully independant of eachother.
Sony use a special method of booting into recovery for their updates, this is not available when you are unlocked, and there is no button combination to enter this mode. As a result the common method to get recovery on Xperia devices has been to use an initrd that has a script to load either normal boot or recovery boot based on a button press. This is a far from ideal solution as when you update your kernel it also updates your recovery. If something goes wrong you are stuck needing a computer to reflash the kernel partition.
With the recent addition of TWRP support for the latest devices there have been advances made in this technique making recovery updatable it still requires the flashed boot image to support that method. This is less than ideal still as it reduces choice in what you want on your device, giving the decision to the dev of the rom you have flashed. This also leaves you in the position of needing your computer if a kernel update fails for any reason.
LK solves these problems by separating out boot and recovery to their own kernels with their own ramdisks like every other device, if you flash the boot kernel, recovery isn't touched and will be there for you as a failsafe in case anything goes wrong. This removes the need to have a computer near by in case of breakage occuring.
What progress has been made?
LK is operational, small bugs still need work and driver porting for lcd and notification led are underway.
Click here for the project thread
Apache14 - Open Source Infrared Receiver & Transmitter Library
I have been working on the open source library for allowing the use of the IR transmitter and receiver on the Tablet Z, At the beginning of this project I believe there was no other project looking into IR functionality in community driven roms (so this project was started from scratch).
As this project was started from almost no information about the IR device / protocol ect. there have been many stages of the development, this was split into 3 very distinct stages, please see below a lost of these stages and the progress made.
Stage 1 (Analysing communications)
This stage was mainly finding how the information was sent to the IR device and in what form. It was found that the IR device was connected to a tty serial port on the qcom main processor (ttyHSL2 in user space), from this I was able to "sniff" out the data sent and received by the application on the sony stock rom. This data was analysed and all possible commands where extracted (Get raw data, Send raw data, send specific key, get version).
Stage 2 (Create native library)
After the commands where known a library was created (in C) to enable the use of the IR blaster chip, this was a lot of trial and error as it was very timing specific (sleeps / poll ftw ). This part was surprisingly easy and i was able to get a working library that enabled learn and send command within a few days
Stage 3 (Create a application for everyone to use)
Once the library was completed to a point where it was usable, an application was created making use of the library as a JNI library. As I have little android java experience this is probably the weakest aspect of the project to date. This app went through a number of revisions and started off as 2/3 buttons for testing (this is illustrated below in the picture / video section. The xda member isimobile took one of the revisions and made improvements to the UI as well as using an SQL database to store the keys.
One aspect of the original plan that has not been explored is the robotics aspect, however this is mainly due to the amount of work required being much more than i first planned on.
Please find the links to source code (for library and app) as well as some videos and pictures to illustrate the projects timeline.
Library Src
APP Src
Early Application
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Current Application
Initial Test Video (day 1)
Initial App Test
I would like to finish by extending thanks to all at XDA and Sony who have made this competition happen and giving me this opportunity to develop a fun project.
Click here for the project thread
zacthespack - LinuxOnAndroid Project (Standard/ROM/Native)
As it stands below is the current placement with the three parts of the project:
Standard LoA - I have completed testing of all current images and everything works as it should, when running stock you must make the system partition r/w but this has all be added to my thread. In fact, this is the best device so far in terms of smoothness and actually usability over VNC.
However I have also made good progress with getting rid of VNC and using the Android frame buffer for graphics out put, so it takes more to switch between Android and Linux BUT you get a much better linux experience. I hope to release this in the coming few days once a few graphics glitch with Unity have been fixed.
LoA ROM - I have also started work on the ROM, getting my read around the ROM git structure has been the first port of call and actually getting my mods integrated into a repo so others could build is what I am working on at the moment. As it stands I have pretty much finished integrating the required code to launch and boot the images within the ROM so no need for a stand along app, just pull down the status bar and hit boot linux. Also added the settings for it all into the ROMs settings menu to make it all feel nice and one. I have plans then to integrate Linux and Android more, with the final result being a free version of everything Ubuntu edge can do but on hardware that you can actually buy
Native Linux - Only just started on this now as personal I prefer the other two parts of the project as I like to still have android at my finger tips when needed
So in all while I may have not completed as much as other projects I do think my project has a lot more to do and is certainly not something I will be stopping any time soon. Users already have access the standard LoA and I have started to see more Tablet Z popping up as installing the app, we also hope to push a 'alpha' of the ROM to the tablet Z very soon once the git is all sorted so people could integrate LoA into other base ROMs if they so please.
Click here for the project thread
sailnw - App for Sailors and Cruisers Using Waterproof Tablet
As I mentioned in the contest entry, the app I am working on is for active sailors and cruisers which would utilize Xperia Z's waterproof features and excellent form factor for use in salt water environments under way. At this stage I am collecting input from active sailors and cruisers regarding features and design of the app. Planning to have app flow and some screen designs in September. Also actively looking for project participants on the development side.
No forum thread is available for this entry.
rayman - Tablet Multiboot Manager
Goal: Create a multiboot solution for the Tablet Z.
The goal consists of two parts:
1) Ability to dynamically boot images without flashing them
2) A solution for picking the boot image to run.
Step 1 was completed within the first week after receiving the tablet,
and sources are available on my github.
Step 2 was much more complex. I first evaluated the solutions
currently available, primarily kexecboot(.org), MultiRom (TWRP-based
for N7) and petitboot. Common to all those solutions is that they are
overcomplicated. Some automatically scan for things that looks like
roms and some requires special made update.zip's. On top of that most
solutions are less than good looking.
With that in mind, I set out to create something extremely simplistic - the result is Hydra.
There are some minor features missing before it's ready for release, but the GUI and boot setup works.
Features:
* Auto-aligning grid of large, good looking icons for selecting image - currently a maximum of 10 images.
* Flashy buttons automatically created based on a target-specific image
* Optimized graphics display to ensure smooth rendering
* Automatically append required commandline arguments
* Read boot configuration from a simple boot.ini format - supports boot.img's and raw kernel + ramdisk + cmdline setup.
* Auto-boot a default image after a configurable timeout
Planned Features:
* Per-boot.img runtime settings - planned but that's for version 2.0
* Scrollable grid - allowing for more than 10 images.
* Automatically locate boot.ini's in a boot subdir on all storage units that are mountable. This means autodetecting available images on microsd or usb harddisk.
Some Images:
Click here for the project thread
anthonycr - Lightning Browser (Open Source Web browser)
I've kept the source code updated on github (https://github.com/anthonycr/Lightning-Browser). A direct download to the latest beta is here (https://github.com/anthonycr/Lightni...s.apk?raw=true), and a description can be found on the main project page.
What I've accomplished:
- added a History page
- added better bookmark layout (fixed bug in full-screen mode)
- better full screen URL handling
- added some more animations
- incognito mode (does not record URLs visited or searched, and runs without cookies for extra protection)
- notify user of SSL certificate errors
- popup tabs now work
- fixed bug where certain sites wouldn't display until touched
- better full-screen video (flash is still partially broken… it’s Adobe's problem)
- memory management
- HTTP authentication
- multiple search engines
- ability to change download location
- text re-flow
- ability to import bookmarks from either the stock browser or Chrome if you are signed in
- text size
Current Screenshots
I haven't had much feedback in the Tablet Z forum, so I've mostly been working off the feedback I've been receiving in my main thread in the application forum. It's a lot more lively there.
Thanks! I've had wonderful time developing with the Xperia Tablet Z.
Click here for the project thread
bluefa1con - PAC All-In-One ROM
Information about this project is available in this PDF document: https://dl.dropboxusercontent.com/u/20579840/PAC/PACmanTabletZ.pdf
Click here for the project thread
mamenyaka - Ubuntu Touch Porting
I am mamenyaka from XDA. My project is about porting Ubuntu Touch to the Tablet Z.
My thread is located here, and you can also check out the Ubuntu wiki page of the device.
Ubuntu Touch is running in a separated container on top of an Android kernel, so it is made out of two images: the device image and the ubuntu image.
The ubuntu image is provided by ubuntu in the form of a .zip file.
The device image is built by me, and it is based on CM.
To install Ubuntu Touch, you just need to flash the two .zips in recovery.
The journey
The first step was to build the device image and remove unnecessary Android components. Some hacks were needed, because some components relied on external parts of CM that were excluded from Ubuntu Touch and some proprietary blobs were missing too. And there were some modifications needed by Ubuntu Touch, documented in their porting guide.
After successfully building the image, it turned out that WiFi and the Camera didn't work.
The WiFi needed some extra binaries and the kernel module itself needed to be loaded manually at init (insmod). But the WiFi is now working, and that is the most important part. Without it no development can be done with the Ubuntu SDK, because it downloads and installs a lot of packages on the device that are necessary to deploy your QT/QML apps.
The camera was fixed partially by acquiring the right blobs, but the Camera app itself is buggy, I think. Maybe it will be fixed in future releases.
All my work can be found and reproduced by using my github repos (the ones for Sony) and by following the porting guide.
The future
As Ubuntu Touch is making the switch from being "just another Android shell":
Instead of booting into android and firing up the Ubuntu system after
android has booted, the new images now boot into Ubuntu and initialize
android inside an LXC container during boot.
the development will continue. Sadly, from 07-12 until now there has been no new porting guide, so the ports do not work with the new image (yet) and the development of the old format has stopped. Until then I am releasing updated images and experimenting with dual boot. In the xda thread I wrote a little tutorial on how to do dual booting with Ubuntu Touch and CM based Android ROMs, but it's not the real thing, but it works without the need of a PC (no need to flash boot.img via fastboot).
Click here for the project thread
Click here to make your vote in the contest - the password is 'xdasonycontest852'
rydo88 - Tablet Z Smart House System
No response received asking for project update. Information below taken from project thread:
As for the hint, I’m going to start with two of them, as I didn’t add one last week. This project originally began as part of this prescient home and then I decided I could adapt part of it to be more fun than practical.
1. A great place to set down one’s drink.
2. Tabletop gaming.
What I’m calling the proof of concept project was put together while moving. It starts with a secret… I’m a bathroom reader. Okay, so maybe that’s not a huge secret (books and magazines strewn around the bathroom is a bit of a giveaway), but it’s not exactly a polite conversation topic. It was conceived while describing the project to a friend who pointed out that he doesn’t cook, but there was an alternate use he found noteworthy (i.e. reading the royal reports on the porcelain throne). Henceforth this will just be described as the book preparation device (or BPD to save some typing). The materials needed are superglue, a sharp knife (preferably something like an Exacto), an NFC tag, and a magazine that you don’t want to read anymore. Use the superglue to laminate a block of pages together, either the whole magazine or just a section large enough to house the NFC tag. The one I did was about a 3 inch square through the whole magazine, excluding the cover. This also left the edges loose, providing a more authentic magazine look, rather than a big mess of superglue. Once this is set and dried, outline the NFC tag on the block for the pattern to cut. Cut and remove layers until you’ve made a cavity large enough for the tag to fit. Snugness is a personal preference, I left mine so that the tag was removable, but a tight fit and some glue could make this more permanent. Sony’s native Smarttag software works well for this application. Just customize the options so that the tag (blue in this case) triggers the tablet to open Play Books. A nice feature of Sony’s application is that there are ‘end’ actions, so a second contact with the tag causes a second set of actions to occur. I set this option to return to the home screen and read the time aloud (so that I know how late I am to wherever I’m headed). Once this is set up, leave the magazine near your reading chair. Place the tablet on the BPD as you sit down and presto! Your book is opened, as if by magic. When you’re done reading, set the tablet down again, stand, stretch, and poof! Your tablet has closed the book, told you how long you were lost in it, and is ready to travel to the next project.
I’ll add some pictures and a video here before too long. Maybe even a witty/catchy acronym to rename the project.
Concept:
To utilize NFC and other features of the Tablet Z in order to produce a system which causes the tablet to perform actions in a semi-predictive matter.
Methodology:
I intend to modify items to produce convenient and unobtrusive ways of integrating NFC tags. This will provide the infrastructure for the system. On the device, software will be used to carry out instructions specific to the tag and other variables.
To put my sciencey talk into a more tangible example, take for instance the kitchen. What function would be handy for a tablet to perform by itself? The most obvious answer to me, is for it to open up a recipe. In order to accomplish this, I intend to create a stand with an integrated NFC tag, which would trigger the tablet to open a recipe app. Depending on the software side (which I plan on mostly using existing apps, as I'm not much of a coder), I would ideally have the system cross reference a menu that's been planned out (i.e. that you had planned for meatloaf on Monday night, the tablet would open directly to a meatloaf recipe). As a starting point, it will likely open to a random recipe. For anyone following along at home, the action should be easily modified on the software side. Perhaps some people prefer to catch up with HBO or listen to some Sinatra while cooking. The idea is in the same vein as the whole home-of-the-future concept.
This concept will be extrapolated to several rooms.Other planned functionality would be to automatically turn on the TV in the living room, play music in the den, set alarms in the bedroom, and perhaps a few other tricks along the way.
Before I wrap this post up, I'd like to say thanks to XDA and Sony for holding this competition and giving me the opportunity to create this project. I'd also like to say thanks to everyone who takes the time to follow the projects in this contest and hope that everyone has a bit of fun.
Click here for the project thread
All features, full flexibility, no bloat -- one simple solution!
On the one hand, it is frequently being suggested to build into Lineage various apps and features. Most of these suggestions are required by some users only, would bloat the core ROM, or have other downsides. On the other hand, these apps and features are usually already implemented somewhere, most users want incremental updates and many would prefer a fully-featured ROM without GApps installed.
To satisfy those wishes and yet avoid the downsides, I suggest simply supporting F-Droid and microG instead:
Idea outline:
Provide API for and build in F-Droid Privileged Extension
Thus have a Store, with automatic updates, and all bells and whistles
Ship with (rebranded fork of) F-Droid pre-installed and a custom LineageOS repository pre-configured (like Guardian Project in F-Droid)
Add AOSP apps, Lineage apps and Lineage-specific versions / branches of apps to LineageOS repository
Use "unstable update" marker in F-Droid to beta test new versions, e.g. of launcher, locker, ...
For additional, bloating apps and features, have users install what's already there (for instance, Location Services: UnifiedNLP with LocalWifiNlpBackend)
Add to Lineage Wiki a curated list of well-tested app suggestions for basic tasks (for instance, WebDAV: DAVdroid, Tasker, Etar, ...).
Key Advantages:
Developer effort most efficiently used
Faster time to market, because much is already implemented
Higher quality, less bloat, more features by referring users to existing apps and joining efforts
Easier innovation, because versions of pre-installed / system apps are publishable like regular apps
Developers happy, because LineageOS is clean at its core
Enthusiasts happy, because they can built on a minimal ROM
End Users happy, because they can easily use ROM, using curated list of apps
Regular, normal app updates for all system apps and pre-installed apps through Lineage repository
Does not prevent using GApps, but improves life without
Major step towards fully featured ROM, and yet without any proprietary apps or services
For good reasons, it's what Google does, it's what GNU/Linux distributions do.
One framework will solve most problems, provide most features ever suggested.
This will make everybody happy.
tldr
Bump!!!!
1, 2, 3 - Fully agree. If I had a proper Play Store alternative I wouldn't need Gapps at all.
4 - Essential in what way? I'd say its best to have only AOSP apps and to let every user download the apps he uses.
There would be practically no bloatware available and the ROM would truly give users the best choices.
8 - Additional preinstalled apps? Rather not.
9 - Rather AOSP mail. Someone might not want to use K-9, but for those who do they can always download it.
10 - Same as 9, avoid preinstalling apps that are already provided by AOSP.
11 - Eleven is OK for me, but still I find it somehow way underpowered. I really miss Apollo from early CM days...
14, 15 - I agree on ROM type. Allow users to select nightly, weekly or stable update channel through settings. Regarding basic preloaded apps, it would be OK only by means of AROMA installer where you could choose which ones you actually want/need.
Cheers!
In this thread it is being suggested to build into Lineage various Launchers, Themes, Widgets, Apps, WebDAV support, et cetera. As a contrasting response to that, I suggest simply supporting F-Droid and microG instead. A Lineage repository for F-Droid could include all AOSP apps; F-Droids own repository would supplement this.
It appears to me, almost everything which has been popularly requested would thereby be solved.
dj_chapz said:
4 - Essential in what way? I'd say its best to have only AOSP apps and to let every user download the apps he uses.
There would be practically no bloatware available and the ROM would truly give users the best choices.
Click to expand...
Click to collapse
Here, "essential" refers to, more or less, what's needed to install other apps (launcher, browser, file manager),
but could be thought of as to include functions, which were typical for feature phones, too (basic messenger, dailer, calendar).
dj_chapz said:
8 - Additional preinstalled apps? Rather not.
9 - Rather AOSP mail. Someone might not want to use K-9, but for those who do they can always download it.
10 - Same as 9, avoid preinstalling apps that are already provided by AOSP.
11 - Eleven is OK for me, but still I find it somehow way underpowered. I really miss Apollo from early CM days...
Click to expand...
Click to collapse
These were just written-out to illustrate what would be possible.
I'll adjust the original post for clarity.
Anybody can fork it and add their ideas. Some people do not want to support fdroid. Keep it clean + gapps.
goorek said:
Anybody can fork it and add their ideas. Some people do not want to support fdroid. Keep it clean + gapps.
Click to expand...
Click to collapse
Even if F-droid wasn't preinstalled, could be a Lineage repo for it?
LineageOS IMHO should really seek to become the ROM for professional PIM, self-employed, small-business or even big-business device users which seek to avoid GApps and rely on a clean slim ROM. So I like many of grefnab's ideas but currently have no clear idea what the stakeholders of LineageOS have as main goals for the midterm.
Having everything App based in an "FOSS App Package" (as GApps and commercial/device App replacement) with advanced support by LineageOS and/or other main CustomROMs would be geat. See my post in What features would you like to see in Lineage that CM didn't have?
support 1-3
I really hope that this thread will get recognition. I really like the idea of having priviliged F-Droid build into the ROM.
That would make everything much easier.
I fully support the three first points
Provide API for and build in F-Droid Privileged Extensio
Thus have a Store, with automatic updates, and all bells and whistles
Ship with F-Droid pre-installed and a custom LineageOS repository (like Guardian Project) pre-configured
Click to expand...
Click to collapse
The rest is nice but I would put emphasis on the first three points. They seem like a real advantage to have.
Rephrased some sentences to clarify
This seems like a very good idea to me :good:
I mean it is basically the same procedure Google has in place to keep its apps up-to-date without people having to update their firmwares. Being able to update the apps independently from the rom would be a huge benefit in my opinion. While I don't use gapps on my phone at all, I understand, that some people find it essential. Therefore it would be a bad idea if this interfered with installing gapps in any way.
herrritschwumm said:
While I don't use gapps on my phone at all, I understand, that some people find it essential. Therefore it would be a bad idea if this interfered with installing gapps in any way.
Click to expand...
Click to collapse
This would not prevent installing GApps, it would simplify and improve usage without them, though.
+1 for having LOS F-droid repo and bundling F-droid and having fewer other preinstalled apps.
I think this thread is a very good idea!
Just a clarification on technicalities:
microG kinda requires signature spoofing. More specifically MicroG effectively has two principal frameworks inside -- location services and GCM. Location services would work regardless, but iirc for GCM to work properly the ROM itself would need a signature spoofing support. All other ways to enable spoofing employing needlepatch or whatever are ridiculously impractical and one cannot expect normal users to bother with them.
I have two phones (OP1 and OP3) and for both the choice is of exactly ONE custom rom only (based on LineageOS14.1) with a spoofing patch. Therefore applying spoofing patch into the main code base would be great. However the caveat here is that any app or framework like SafetyNET would most likely stop working. Since the developers decided to push for compatibility, I seriously doubt that they would implement signature spoofing.
They could try to implement the patch in a flashable zip like with root but I don't know if it is possible.
fully agree for spoofing support since we are out ot cm
Sent from my Nexus 5 CAF using Tapatalk
I would like to see signature spoofing built into lineageOS or an optional flashible zip, too. But right now a flashible zip could take a long time to flash. See: https://github.com/microg/android_packages_apps_GmsCore/issues/196
Sounds great.
dj_chapz said:
If I had a proper Play Store alternative I wouldn't need Gapps at all.
Click to expand...
Click to collapse
You could try Yalp Store, it's there in the F-Droid repository.
@grefnab: My flashable zip help those that want to automatically without any effort: remove GApps, install microG and F-Droid Privileged Extension.
1plus said:
Just a clarification on technicalities:
microG kinda requires signature spoofing. More specifically MicroG effectively has two principal frameworks inside -- location services and GCM. Location services would work regardless, but iirc for GCM to work properly the ROM itself would need a signature spoofing support. All other ways to enable spoofing employing needlepatch or whatever are ridiculously impractical and one cannot expect normal users to bother with them.
However the caveat here is that any app or framework like SafetyNET would most likely stop working. Since the developers decided to push for compatibility, I seriously doubt that they would implement signature spoofing.
Click to expand...
Click to collapse
Tingle is very easy to use, if you find something impratical just tell me.
SafetyNet do pass for me.
I'm wanting to modify my 6P to increase my usage of free and open source software, and increase my overall security and privacy protection.
Unfortunately, I still have some proprietary Google dependencies, so I need to maintain access to the Play Store and a minimal set of GApps, so CopperheadOS is off the table (for now). Also, I want to be able to stay up to date, so something like Replicant is also out of consideration. Usability is a priority.
Currently I'm using OmniROM, with Brave for the browser, Silence for SMS. ProtonMail for email, and DuckDuckGo for search. I've gone back and forth between OmniSwitch and Trebuchet for my launcher---I'm not crazy about either, but haven't settled yet.
I'm currently rooted with SuperSU, but I'm planning to switch to phh's SuperUser soon.
Is Omni the most open source and security conscious ROM that is up to date, and GApps compatible? Are there other app substitutions you guys could suggest?