Related
Hey,
After reading the threads, I presume I'm not the only unlucky one to have a phone without Android Market, combined with the "dreaded" 1.33.0010 SPL, therefore unable to root.
So what's the best way to get new apps for my brand new HTC Sapphire? SlideMe and Leaf Open Market just don't cut it for me.
Alternatively, can I download the Android Market apps via the web?
Ciao,
CUGWMUI
PS: Someone, please root this phone!
you mean like these?
http://www.androidtapp.com
http://www.android.com/market
but i presume you're aware of a google search phenomena so i guess that is not what you were looking for
Not sure if slideme is locked to the mobile emai number or anything else but you can try to open your browser on the mobile and go to http://m.slideme.org/SAM/ and install there application store manager.
Thanks...
I guess the best thing is to acquire as much from as many sources as possible...
Can't wait for my Magic to get rooted..
Ciao,
CUG
Found a methode where i can get applications/games from the market into my non-google magic.
look at my post here: http://forum.xda-developers.com/showthread.php?t=529170
You might want to have a look at this website...it lists all alternatives for appstores per platform: http://www.wipwiki.com/appstores
Bazaar and Aptoide as alternative to Android Market
Hi guys!
Try bazaar.aptoide.org as alternative to Android Market,
As developer let me share with you the following features:
- Bazaar's site allows you to create your own market;
- Under the motto "Own your market!" you can now have your own Aptoide repository with your applications.
- Upload and manage your applications and share them with the world or just your friends.
- Easily browse the available Android Apps and choose which to install from your Android device.
- Discovering more in bazaar.aptoide.org
The Aptoide app allows users to easily install applications from distributed repositories, without having to rely on the Google Market.
The Aptoide enables you the following extra features:
- Add repositories via QR-code.
- Support for private repositories with login credentials (through the standard httpaccess file).
- Faster reloading of the list of applications from the repository
- Many other features and bug fixes.
Best regards,
Fábio
Fabio Te said:
Hi guys!
Try bazaar.aptoide.org as alternative to Android Market,
As developer let me share with you the following features:
- Bazaar's site allows you to create your own market;
- Under the motto "Own your market!" you can now have your own Aptoide repository with your applications.
- Upload and manage your applications and share them with the world or just your friends.
- Easily browse the available Android Apps and choose which to install from your Android device.
- Discovering more in bazaar.aptoide.org
The Aptoide app allows users to easily install applications from distributed repositories, without having to rely on the Google Market.
The Aptoide enables you the following extra features:
- Add repositories via QR-code.
- Support for private repositories with login credentials (through the standard httpaccess file).
- Faster reloading of the list of applications from the repository
- Many other features and bug fixes.
Best regards,
Fábio
Click to expand...
Click to collapse
Gonna install that myself right now
BLAHBLAH as an alternative to market
You could give google a try I know it cannot replace the android market but there is one advantage download paid apps for free.Sorry cannot give the url.
MOD EDITED BECAUSE THIS MEMBER CANNOT READ AND/OR UNDERSTAND FORUM RULES.
swapnilraj said:
You could give applanet a try I know it cannot replace the android market but there is one advantage download paid apps for free.Sorry cannot give the url.
Click to expand...
Click to collapse
open browser >>> go to google.com then download the market.apk install it.
don't forget to check the unknown source in setting application.
MOD EDITED BECAUSE THIS MEMBER CANNOT READ AND/OR UNDERSTAND FORUM RULES.
isnt this kinda warez helping?
swapnilraj said:
You could give google a try I know it cannot replace the android market but there is one advantage download paid apps for free.Sorry cannot give the url.
Click to expand...
Click to collapse
dnhrmnsyh said:
open browser >>> go to google.com then download the market.apk install it.
don't forget to check the unknown source in setting application.
Click to expand...
Click to collapse
If you guys want to get banned then post that crap again!
I have ZERO tolerance for even hinting warez distribution!
In fact... I've had it! Consider this thread closed.
Yes, this is a discussion thread, but you are not allowed to make "meaningless" posts in here.
If you have made some discoveries post it, but no one in here is interested in "thank you" posts or similiar.
Okay, let's try to get the Android 4.2 gapps working as good as possible on our phone.
As you know Google dropped support of non-neon phones and tablets with Android 4.2.
Our Tegra2 SoC doesn't support these neon instructions, which results in a couple problems with the default gapps package.
We need to replace a couple files with older ones to get everything back working.
Update 27.04: I finally found some time to work on gapps and provide a (hopefully) fully working non-neon gapps package in the second post now!
One example: the biggest annoyance is probably the dying keyboard.
This happens because the gapps package replaces the libjni_latinime.so file included in the ROMs with a proprietary one by Google to enable Gesture input.
Unfortunately it does need neon, so you should remove the file inside the gapps package (/system/lib/) before flashing it.
In the logcat you'll usually see a SIGILL error, like this one:
Code:
A/libc(3910): Fatal signal 4 (SIGILL) at 0x4f6233a6 (code=1), thread 3910 (putmethod.latin)
I/DEBUG(92): signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 4f6233a6
I'm starting this thread to colloborate together on a gapps package with as much stuff working as possible, so if you do have any insights please share them
You can download the CM10 gapps package and get the nonneon files (they're in /optional/nonneon) - but not all of them are still working with Android 4.2.
P.S.: For the love of God, don't call them fapps - fapps is a foss (free and open source) package which uses OpenStreetMaps instead of GMaps and so on.
We still want gapps, just without neon libs.
Okay, here's my non-neon fixed gapps package.
Important: If you already flashed another gapps package do format /system, reflash your ROM then reflash these gapps.
If you don't do that you'll have leftovers from the former package, which results e.g. in a dying keyboard.
Changes compared to the official package:
Fixed the aosp keyboard crashes
Fixed Google Talk videochat crashing
Fixed Faceunlock
Fixed Google TTS
Fixed Google Now & Voice Search crashes on non neon devices & restored hot-word detection
Fixed Talkback
Removed unuseful stuff
Notes:
Swipe keyboard won't work - nothing I can do about that.
Complain to Google for dropping non-neon support
Same thing goes to Photoshpere - no neon: no love.
Don't try to update Google Now - the new version doesn't properly work without neon (not sure if this still applies?)
Download:
http://goo.im/devs/tonyp/non-neon-gapps
If you're interested in more details what parts I changed - here you go.
This will hopefully ensure that future gapps versions will get provided as well
to fix facelock: replace libfacelock_jni.so with non-neon lib (credits: Adam77Root)
to fix the keyboard closing: remove libjni_latinime.so
to fix google videochat: added libvideochat_stabilize.so, replaced libgtalk_jni.so with non-neon lib and removed libgtalk_stabilize.so
to fix TTS: replaced libpatts_engine_jni_api.so with a non-neon lib and GoogleTTS.apk with the apk from the teameos gapps package.
to fix Google Now and Voice Search I replaced the QuickSearchBox.apk with this one by Steady Hawkin.
Note that the newest Google Now version isn't compatible with non neon devices anymore, thus this version disables the auto-update.
replaced Talkback.apk with a working version from the eos gapps package.
Partial credits for steps 1-4 go to bubor who already started with a non-neon gapps package.
Then I reflected these changes in the 70-gapps.sh backup script.
That's important because otherwise updating the ROM will break the gapps!
Why? Updating the ROM does wipe /system - only the files which are in the script will retain.
This means that e.g. the libvideochat_stabilize.so will poof away and the libjni_latinime.so won't get updates anymore.
Additionally I removed the g.prop file in /system/etc to prevent the GooManager from trying to update the gapps package if new (neon) updates come.
To reduce the package size I completely removed the photosphere stuff.
Just a thought here: since our cpu does not support neon instruction set, wouldn't it be an option to patch the P990's kernel with an neon-emulator? This way, the neon instructions will be translated into something the cpu can process. Corrrect me if I'm wrong.
I'm saying this because I've seen something similar happen on Mac OS X, where version 10.8.x requires a cpu capable of SSSE3 (not SSE3) instructions. They have patched the kernel with an SSSE3 emulator so that it works on older hardware and AMD cpus.
Sent from my LG-P990 using xda premium
Robin2 said:
Just a thought here: since our cpu does not support neon instruction set, wouldn't it be an option to patch the P990's kernel with an neon-emulator? This way, the neon instructions will be translated into something the cpu can process. Corrrect me if I'm wrong.
I'm saying this because I've seen something similar happen on Mac OS X, where version 10.8.x requires a cpu capable of SSSE3 (not SSE3) instructions. They have patched the kernel with an SSSE3 emulator so that it works on older hardware and AMD cpus.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
I'm thinking about the exact opposite - try to disassemble the libs, replace the neon instructions and reassemble. Not sure yet how much work it would take though...
bugadani said:
I'm thinking about the exact opposite - try to disassemble the libs, replace the neon instructions and reassemble. Not sure yet how much work it would take though...
Click to expand...
Click to collapse
this will be an horrendous work. I've seen some projects trying to hack armv6 instructions into the newer armv7 packages - it's really hard as you have to do it in smali as Google won't release it's sources.
I'm extremely full with loads of projects currently - I'm still hoping some people will take this over and try to build a nicely working non neon gapps version. this only requires trial and error, no real technical knowledge. but the interest seems low
Sent from my LG-P990 using xda app-developers app
Developer or not... But since you said yourself that "this will be an horrendous work", allow me include a little something here.
Changelog:
* All apps updated to 4.2.2 versions
* Google Play Store updated to 3.10.14
* Google Play Services updated to 3.0.25
* Gmail2.apk (Gmail) and GoogleEars.apk (Sound Search for Google Play) removed since they are available in the Google Play Store
** May require uninstalling and reinstalling Gmail and Sound Search after flashing.
* Keeps previous version's Photosphere/Picasa sync install on Mako, Manta, and Tuna.
Click to expand...
Click to collapse
From the way I see it, this horrendos work wouldn't really pay off since the earlier version of Gapps has... well... more or less everything the so-called new version has. So why bother if I may ask?
Back to you sir
Soooo, I have been looking into this for the past few days. I think I have got an understand of this that is good enough to make this work.
Since you are working so hard on CM10.1, I'll be willing to put great effort into this. Already started out with some basics, but I am pretty confident that I can make it work by the end of this week.
Will do some proper testing when it has been finished, once everything has been worked out, I'll push it public so you all can have the joy of using it in whatever way you may please
natalya said:
Soooo, I have been looking into this for the past few days. I think I have got an understand of this that is good enough to make this work.
Since you are working so hard on CM10.1, I'll be willing to put great effort into this. Already started out with some basics, but I am pretty confident that I can make it work by the end of this week.
Will do some proper testing when it has been finished, once everything has been worked out, I'll push it public so you all can have the joy of using it in whatever way you may please
Click to expand...
Click to collapse
Any news on your project?
Well, I'm a little disappointed that no one else worked on this - it's basically using Google and trial and error.
Thanks goes to massimo who has offered me some help and did some tests
Anyways, I decided to take matters into my own hands now, as I want to release CM10.1 over the weekend and don't want people to complain because they flashed the wrong gapps packages.
@natalya: If there's anything else you discovered which isn't working please provide it, but as you didn't post what you did in almost 2 weeks now I didn't want to wait anymore.
Changes compared to the official package:
Fixed the aosp keyboard crashes
(note: swipe won't work on non neon devices, nothing I can do about that)
Fixed Google Talk videochat crashing
Fixed Faceunlock
Fixed Google Now & Voice Search crashes on non neon devices & restored hot-word detection
Fixed Talkback
Removed unuseful stuff
Let me explain the steps taken so others can learn what has been done and can update gapps theirselves.
to fix facelock: I replace libfacelock_jni.so with non-neon lib (credits: Adam77Root)
to fix the keyboard closing: I removed libjni_latinime.so
(note: this diables the keyboard swiping - it will never fully work on non-neon devices!)
to fix google videochat: added libvideochat_stabilize.so, replaced libgtalk_jni.so with non-neon lib and removed libgtalk_stabilize.so
to (partially) fix TTS: replaced libpatts_engine_jni_api.so with a non-neon lib
to fix Google Now and Voice Search I replaced the QuickSearchBox.apk and added the libgoogle_recognizer_jni_l.so lib from this one by Steady Hawkin.
Note that the newest Google Now version isn't compatible with non neon devices anymore, so this one disables the auto-update
replaced Talkback.apk with a working version from the above gapps package[/url].
Note the English TTS not working, see below.
Partial credits for steps 1-4 go to bubor who already started with a non-neon gapps package.
Then I reflected these changes in the 70-gapps.sh backup script.
That's important because otherwise updating the ROM will break the gapps!
Why? Updating the ROM does wipe /system - only the files which are in the script will retain.
This means that e.g. the libvideochat_stabilize.so will poof away and the libjni_latinime.so won't get updates anymore.
Additionally I removed the g.prop file in /system/etc to prevent the GooManager from trying to update the gapps package if new (neon) updates come.
To reduce the package size I completely removed the photosphere stuff.
As for the swipe keyboard this feature requires neon-support and will not work properly on our phone, no matter what.
Known bugs:
Google text to speech doesn't seem to work in English. fixed
Download:
http://goo.im/devs/tonyp/non-neon-gapps
If you already flashed another gapps package do format /system, reflash your ROM then reflash these gapps.
This is needed to ensure nothing remains broken from former flashes.
Please give some feedback for this gapps package.
If something doesn't work don't forget to attach a logcat
Okay, I managed to fix the Google-text-to-speech engine as well by replacing the GoogleTTS.apk with the one from the teameos gapps package.
I pushed the new version online and removed the old one.
All bugs I am aware of are now fixed, if you notice anything else that isn't working please give feedback
Time to clean up the OP.
tonyp said:
[*]Don't try to update Google Now - the new version doesn't properly work without neon.
Click to expand...
Click to collapse
Play store is offering me to update Google Search after installing your CM10.1 ROM and this gapps package. Is Google Now part of Google Search so I should avoid this update too?
ciarpame said:
Play store is offering me to update Google Search after installing your CM10.1 ROM and this gapps package. Is Google Now part of Google Search so I should avoid this update too?
Click to expand...
Click to collapse
You can update it and you can use it.
Sadly it has huge lags (as in it freezes from time to time and the waiting times can be taking forever sometimes)
Sent from my LG-P990 using xda app-developers app
For those who want to use the aosp-keyboard, Google recently released Google-keyboard (witch is similar to the aosp, but fully non-neon compatible)
In the US it should be available through the play store, for the others http://dl.androidnext.de/com.google.android.inputmethod.latin.apk
our 2x learns gesture typing
Thread cleaned up.
This is the dev discussion subforum so it's not the right place to ask about specific ROMs.
If you'll find out something new for the non-neon gapps package then you can post in here, everything else goes into the other sections.
Thank you!
P.S.: I've tried extracted the new lib (libjni_unbundled_latinimegoogle.so) from the Google keyboard - it's not compatible to the AOSP one included in ROMs.
If you want to include it into the gapps package you need to rename the apk to LatinIME.apk and add the lib, then it'll overwrite the AOSP keyboard.
(I'm too lazy to update the gapps package in here for a keyboard you can simply install).
I created a non-neon gapps package with the keyboard included.
It will replace the AOSP keyboard by the very similar google keyboard (that fixes gesture typing). Everything else is like tonyps-non-neon-gapps.
Download gapps-jb-20130427-nonneon-tonyp-keyboard.zip
All credits to Google, tonyp and the others mentiont in the first post.
Have fun!
P.S. @tonyp if you want you can put it on the gooserver to the other gapps.
Latest Google Now (26/06/2013) seems to work just fine. I'm not getting those crazy UI lags I got before, if I updated Google Now from the play store
Since the files from tonyp on goo.im are down, here is the working downloadlink for non-neon Gapps:
http://tonyp.basketbuild.com/downlo...on-gapps-/gapps-jb-20130427-nonneon-tonyp.zip
New google keyboard is available: link
DJNoXD said:
New google keyboard is available: link
Click to expand...
Click to collapse
Ah good that you're reviving this thread, I've been meaning to update it with some information.
I never intended to maintain a gapps package and won't do so.
So if someone wants to follow my instructions and offer updated neon-compatible packages for 4.3 and 4.4 go ahead.
The instructions should still apply, but things may have changed a little in the newer versions so they might needs some adaption (e.g. the Talk to Hangouts transition).
Personally I include a mini/tiny gapps neon compatible package in all my ROMs which only contains the most important apps.
I've created the package quite some time ago, it is fully open sourced and can (and already is) used by everyone.
https://github.com/tonyp/android_vendor_google
I update the repo on my own accord, if someone needs a faster update pull requests are always welcome.
But gapps are capable of updating theirselves via the play store, so this usually isn't needed anyways.
I would prefer if others are using my repo and sent pull requests instead of forking and forgetting about the origin, but that's of course your choice.
To include the gapps into your own build you have to add the repo to your manifest and add the following lines to a makefile.
(it doesn't matter which one as long as it's called - an obvious choice would be somewhere in the device tree):
Code:
MINI_GAPPS := true
$(call inherit-product, vendor/google/tiny_gapps_nonneon_tonyp.mk)
P.S.: @DJNoXD This isn't directed at you, I know you're already using my gapps repo in your roms, just a headsup for other potential devs.
tonyp said:
Ah good that you're reviving this thread, I've been meaning to update it with some information.
I never intended to maintain a gapps package and won't do so.
So if someone wants to follow my instructions and offer updated neon-compatible packages for 4.3 and 4.4 go ahead.
The instructions should still apply, but things may have changed a little in the newer versions so they might needs some adaption (e.g. the Talk to Hangouts transition).
Click to expand...
Click to collapse
Hi @tonyp, I hope it's ok to revive this thread again resp. to hijack it a bit from your original intention!? Even if the origin of my following NEON related questions is founded in my lag problems with CM11 2014/11/13 build by @gucky01
gucky01 said:
http://sourceforge.net/projects/lgo...m-11-20141113-UNOFFICIAL-p990.m1.zip/download
Here we go, guys! As promised, here the first build. It`s 100% Tonys work. So we have to thank him for his great work!
All the best to you!
Click to expand...
Click to collapse
I find they fit this thread much better than any other CM10.x/CM11/CM12 ROM XDA thread. Not just one but all of those ROMs are affected by the missing NEON instruction set of the Tegra 2 SOC.
How can one prove wether a current ROM does not call any NEON instructions? Is it sufficient to see that there are no SIGILL entries in the logs?
Let's assume a dev releases a ROM that initially does not call any NEON instructions. Is it possible that updates of Google apps introduce calls of NEON instructions making the ROM misfunctional/unusable?
AFAI understood your trick to assemble non-NEON gapps is to replace shared opjects ( .so files) that call NEON instructions by their (more or less) equivalent non-NEON shared objects. Could there be Google apps or third party apps that call NEON instructions in their core binary?
If so, our P990 will not able to run them, right? I'd like to assemble a list of apps that won't run without NEON support (is there still any list?).
Do calls of NEON instructions on systems that don't support NEON always result in FCs, hot re-boots, or BSODs? Other way round: can calls of NEON instructions on systems that don't support NEON also result in lag or even heavy lag? (gmail 5.0.1 uses to take 10 seconds to start in my recently installed CM11 after the cleanest install possible; I just left the BB and system data/cal un-touched).
I am looking forward for your reply, well-knowing that you don't use the P990 as your daily driver any more for a long time now.
I wish you all a good 2015!
Could anyone give a link for the working fapps for PA 12 by tonyp ..... I searched throughout XDA and throughout internet but couldn't find it .... I don't like gapps and that's why I'm searching for fapps .... I'm asking for fapps (NOT Non-Neon gapps) which might be similar to this http://forum.xda-developers.com/showthread.php?t=1715375
but this one is not working fully at present ...
Thanks in advance
Com'on guys..... 36 views and no reply so far ..... :banghead:
First read this: http://forum.xda-developers.com/showthread.php?t=2186251 then you will no, that there are no fapps :cyclops:
fapps was a very bad name for non-neon gapps.
For PA12 (which is based on Android 4.1.x) you need the gapps which are linked in the first post.
The thing is, that the gapps since Android 4.2.x aren't compatible with Non-Neon Devices. With Roms < 4.2 you can use the normal gapps.
I have already read that many times .... read there what tonyp says in the first post :
" P.S.: For the love of God, don't call them fapps - fapps is a foss (free and open source) package which uses OpenStreetMaps instead of GMaps and so on. "
That's why I'm searching for fapps and in order to avoid any confusion I also wrote that I don't need Non-Neon gapps but fapps....
Anyways thanks for the reply.....
Seriously !!!!!!!! Two Centuries of views (200 views ) and still no answer..... That's GREAT :banghead: :banghead: :banghead:
I didn't find a package, but this German article:
http://www.gamersglobal.de/news/62752/so-gehts-android-ohne-google
There you can find the alternatives to the Google apps.
If you need help understanding it, I can help you, but I think you can see what you can use instead of what.
http://forum.xda-developers.com/showthread.php?t=1715375&referrerid=0
JUMPhil said:
I didn't find a package, but this German article:
http://www.gamersglobal.de/news/62752/so-gehts-android-ohne-google
There you can find the alternatives to the Google apps.
If you need help understanding it, I can help you, but I think you can see what you can use instead of what.
Click to expand...
Click to collapse
Thanks.... I will try it .... translated the page online and so far no problems understanding it..... and by the way this page truly says that without gapps phone will be snappier and battery lasts longer... I have also experienced it ...
pandorious said:
http://forum.xda-developers.com/showthread.php?t=1715375&referrerid=0
Click to expand...
Click to collapse
Thanks, but I have already quoted this page in first post that it is not working fully currently.... This project has started about an year ago and is still under development.... I guess the developer doesn't get much time to develop it or whatever may be the reason but this project also looks promising and I'm already following it....
owais40 said:
Thanks.... I will try it .... translated the page online and so far no problems understanding it..... and by the way this page truly says that without gapps phone will be snappier and battery lasts longer... I have also experienced it ...
Click to expand...
Click to collapse
Would you share your experiences?
JUMPhil said:
Would you share your experiences?
Click to expand...
Click to collapse
OK here it is....
At the time of opening this thread I was on tonyp PA 12 and didn't install gapps (before that I used to install gapps on every new build, clean install).... It had now more free RAM and the phone was much more smooooother (add infinite o's to it in the middle ) than before with the same apps installed as before except gapps..... But there was obviously the lack of email client, play store, etc.... So after searching and from this thread also, I came to know of the alternatives... So my setup was :
1. Blank Store (from XDA thread mentioned above) and Aptoide ===>> instead of Play Store.
2. K-9 Mail ===>> instead of GMail
3. OsmAnd ===>> instead of Google Maps (2 & 3 from your German website. Thanks again man )
4. Browser ===>> Always used Opera / native CM browser and NEVER downloaded Chrome. So no problem here.
5. Calendar ===>> NEVER used any. I can remember my tasks (or at least write them down). So no problem here also.
6. Never cared about GTalk, Google+, etc... I don't use all this crap
But after tonyp released his 10.1 ROM with "minimum gapps" pre-installed, I took it as an opportunity to update my apps (which were a few - others I had already updated earlier via other Stores)... So I'm again planning now to remove gapps from this ROM and again gain my Privacy and ROM Smooooooooothness back ...
The Unlegacy-Android ProjectIntroduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy-Android was born.
Installation
It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs. As usual, 'espresso' goes for all non-3g versions, 'espresso3g' goes for all 3g versions.
Problems
- Occasional sound stuttering in some games
- No hwrotation (meaning the boot animation is landscape on p31xx). I don't consider this as a problem, as autorotation will take effect after bootup anyways... and most 7" tablets, like the Nexus 7 work this way as well.
- The 7.1 builds are experimental! Means: modem not working perfectly yet.
If you notice anything else, be sure to report it in this thread. While I'm kind of busy, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org
Always use the latest TWRP, to flash Android 7.x, you must use TWRP 3.0.3-0 or newer.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices. The aim of this project is to create a fast and stable ROM - although, one could use Xposed to add extra features.
As usual, feedback is appreciated
Want to support development? You can consider donating, I spent countless of hours with this
XDA:DevDB Information
Unlegacy Android Project, ROM for the Samsung Galaxy Tab 2
Contributors
Ziyan, Android-Andi
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Firmware Required: The latest bootloader for your device.
Version Information
Status: Beta
Current Stable Version: 4.4, 6.0
Created 2016-07-03
Last Updated 2017-10-22
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
siealex said:
One more note. DO NOT set up your Google account until you grant all permissions, otherwise you will be stuck on the initial setup.
Click to expand...
Click to collapse
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Ziyan said:
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Click to expand...
Click to collapse
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Bastiary said:
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Click to expand...
Click to collapse
No, at least not yet. I think that the big thing for this will be 3.4 in the near future - I made some very good progress with it, aside from camera not working yet, there are only minor problems remaining
Thank you for everything , dear friend ! And for the support of the old device , and what you are doing and Andi for us ordinary users .
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Az-09 said:
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Click to expand...
Click to collapse
Before every new Android release, we devs get all sorts of questions like this. I'd like to say it once and for all: there's no such thing as 'we do not see' the next versions and whatnot. People are being negative for some reason, but we always try and succeed in the end... I'm sure that if you start reading past posts, you'll find a lot of people saying that we1l never see Lollipop or Marshmallow due to the device being too old, lol.
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
radz_ said:
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
Click to expand...
Click to collapse
check download tab section.
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
pickmod said:
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
Click to expand...
Click to collapse
Yes, that's correct.
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Screeshots
Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
no need for this, it's aosp there isn't any custom features and everybody know how aosp looks
Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
Oh don't worry, I'm working extremely hard in the background almost since like a year... I know a lot about these devices (bought a P5100 specifically for testing 3G on the builds and kernels)
Feature list: well, this is AOSP, and I'd like to keep it this way. Imagine this like the stock ROM on the Nexus devices (with GApps flashed, of course).
Changelog: don't expect anything other than AOSP updates and hardware related fixes and updates - of course, I'm going to write a post each time I release an update, just like I do in the Galaxy Nexus thread however, it's unlikely that I'll add a changelog to the OP (I just don't see the usefulness in it).
Screenshots: will do, but then again, don't expect anything special. Stable and fast pure Android, that is AOSP. As a side note, it's Xposed compatible
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Thak you for your effort to keep tab 2 alive . Amazing work. Are RRO Layers compatible with this rom?
Ziyan said:
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Click to expand...
Click to collapse
Hi Ziyan,
I'm glad you mentioned this, as I thought that I was going insane this morning (or just slightly more insane than usual).
Just browsing the new "Unified" forum (to verify my subscriptions) and noticed that the "Dhollmen" threads could be clarified (just like the "Linaro" threads), for example ...
This thread: http://forum.xda-developers.com/showthread.php?t=2176563 could be titled: [KERNEL][P51xx][AOSP] Dhollmen Espresso
This thread: http://forum.xda-developers.com/showthread.php?t=2183830 could be titled: [KERNEL][P31xx][AOSP] Dhollmen Espresso
Just to avoid confusion (I freely admit that I am easily confused).
Thanks.
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Android-Andi said:
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Click to expand...
Click to collapse
Hi Andi,
I only suggested renaming the existing "pair" of threads (they both exist in the Unified Forum) ... Just like the "pair" of Linaro threads (that also both exist in the Unified forum).
The download links in (all four) of the threads (mentioned above) link to unique builds on AFH (for both P31xx and P51xx devices) in this forum: http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Sorry for all the edits (I put the blame on OCD).
Thanks.
mentat said:
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Click to expand...
Click to collapse
Done; I guess this is it then. Like the XDA forum admin said, the best way to handle moving both threads is to move them both to this unified section, and close one of them (preferably the one with the less posts). While we could merge them into one thread, the posts would get all mixed through the other threads posts (because of the date order) and we would lose any sense of a flow in the conversation...
Minimum Custom Recovery version?
@Ziyan @Android-Andi Thanks for bringing new life to this old tabs
Is there any minimum requirement for recovery for flashing this ROM? I'm running pretty old CWM v.6.0.5.1. Is it sufficient?
** This guide is depreciated, there is a new updated guide here**
If you are planning on using LineageOS 14 for this guide, you can bypass all of this except configuring location backends and battery optimization by heading to https://lineage.microg.org and downloading their ROM.
All download links as well as a link to a list of Open-Source applications to replace commonly used Play Store apps are in the third post.
*This will NOT work with MIUI Global, as the Play Store is already included in the ROM by default.*
I will be continuously updating this guide for everyone as I stumble upon more supported ROMs, more MicroG flashable zips, and other misc. edits. This is made with Android Marshmallow and Nougat in mind as it is all I have tested on, however this may work on older releases of Android with Xposed support or ROMs with Signature Spoofing. This has also only been personally tested on the XT1607 variant.
In order to sync calendars and contacts from your Google account, you must flash the Google Sync Addon by ale5000. If you want swipe gesture typing on the AOSP keyboard, you must flash Shadow53's swipelib.zip. Shadow53 also has a No-Gapps zip package that includes F-Droid, Firefox, and several other apps.
One final thing: This is not for everyone. There was a point in time I didn’t ever think I could go without the Play Store, but ever since I have I don't want to go back. There are numerous pros to switching to a Google-free android setup such as much better battery life, more privacy on your device, a world of open-source alternatives to popular applications, and more. If you have any questions, or if any of this seems daunting if you are newer to things of this nature, please do not hesitate to ask for help. I will try the best I can in my free time to help. Thank you for taking the time to read this, let’s go ahead and start.
*Disclaimer* Your warranty is now void if you modify your phone. I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Click to expand...
Click to collapse
*This first post is for ROMs without native Signature Spoofing support. A list of those with native spoofing can be found in the second post as well as the guide for ROMs that include native signature spoofing.*
What You'll Need:
1. Your Phone with at least 80% battery, preferably 100%.
2. A computer to transfer files to phone
3. You must have Root Access. This can be native root or Magisk root.
4. Your ROM of choice
5. Download the correct Xposed SDK and Xposed APK for your version of Android. The Xposed SDK version may differ for your device.
6. MicroG Unofficial Installer ZIP and Google Sync Addon (optional) by ale5000 or any of Shadow53's MicroG flashable files (download links in third post)
7. Your favorite backup method if you wish to back up such as Titanium Backup, MyBackup Root/Pro, etc.
8. Third Party App Store/APK downloader such as Yalp Store if not wishing to use all open source apps
9. A working Google account
Click to expand...
Click to collapse
Alrighty, let’s finally get into the steps.
1. Make sure you have downloaded the requirements.
2. If you wish, backup the data you want. This should not erase any files stored on an SD card, but I cannot guarantee.
3. Boot into a custom recovery, I am using TWRP
4. Use the standard wipe data options
5. Flash the files in the following order:
Your ROM of choice
MicroG Unofficial installer
Xposed SDK
Custom kernel if using one
6. Just to be safe and to avoid any potential complications, now reboot the device and set up the basics. Afterwards, boot back into recovery.
7. In recovery, wipe Dalvik/ART cache only (Not really required, I always recommend it though just to be safe)
8. Go into Settings —> Security —> Turn Unknown Sources on to allow for APK installs.
9. Install the Xposed Installer APK
10. Open Xposed, grant any permissions/root permissions if it asks for any. Go to download, and search for FakeGApps. Download and install. Next go into the Modules tab of Xposed, and check the box next to the module. Reboot to activate (A soft reboot may work, but I recommend a full reboot.) Installing this allows MicroG to bind to the system and spoof the required signatures.
11. Open MicroG in the app drawer, and allow all permissions it asks for. While in here, turn on Google Device Registration
12. After allowing all permissions, go into Settings. Go to Accounts —> Add Account —> Google Account. Sign into your Google Account. This is necessary to allow certain applications that require Google Play Services to work properly.
13. After signing in, head back into MicroG, go under Google Cloud Messaging and enable.
14. In MicroG settings, head to the UnifiedNLP settings. Under the Configure location backends section, open WiFi Location Service and select Mozilla Location Service and grant any permissions asked. Under Configure address lookup backends, select Nominatim.
15. Finally, in Settings, go to Location and change the mode to High accuracy.
16. Check MicroG's Self-Check to see if everything has been set up properly, and if so, you are good to go!
Click to expand...
Click to collapse
*This post is the steps for ROMs that natively support Signature Spoofing. There is a list at the bottom of this post of those that currently support it
What you will need:
Your Phone
The ROM that supports Signature Spoofing and the kernel of your choice
MicroG unofficial installer and (optional) Google Sync Addon by ale5000 or one of Shadow53's MicroG installers
Magisk Root Manager (Optional)
About 20-30 minutes of your time
Click to expand...
Click to collapse
Steps:
1. Backup anything you want to have backed up. I recommend backup up your Contacts and Calendar events if you have those synced to Google
2. Boot into Recovery on your phone
3. Perform a standard wipe in TWRP
4. Flash the ROM
5. Flash the chosen microG zip file(s)
6. (Optional) Flash Magisk and your favorite kernel
7. (For crDroid Only)If you are flashing crDroid, you need to head over to Settings --> Miscellaneous and turn on the Signature Spoofing toggle
8. Go into Self-Check in microG, and tap the text that says "System grants signature spoofing permission", and allow microG that permission.
9. Still in MicroG, head back to the main part of the app. Open UnifiedNLP.
10. Select the pre-installed location backends.
11. Sign in to your Google account if you wish
12. You're done!
Click to expand...
Click to collapse
Moto G4 Play ROMs with Native Signature Spoofing
crDroid v3.8.1 - Android 7.1.2
ViperOS Coral - Android 7.1.2
TipsyOS - Android 7.1.2
AEX - Android 7.1.2
AICP (@ki's build) - Android 7.1.2
Glassrom Official - Android 7.1.2
MicroG Project has released an unofficial fork of LineageOS 14 that now includes signature spoofing and MicroG components. You will not need to follow anything in this guide except configuring location backends if you download their LineageOS build. There is no Play Store functionality added, although F-Droid (an open source app store) is included by default. You can add the Play Store with a zip that Shadow53 provided on their website (link in post below) More info can be found on their website
Flashable Packages and App Replacements
There are several different MicroG flashable zip files to choose from. ale5000 has one that includes MicroG, several location backends, and the Play Store. Shadow53 has MicroG and several other zip files such as an F-Droid package, the Swipe Libs for gesture typing on the AOSP keyboard, and several more.
Downloads:
MicroG Unofficial Installer - ale5000
Shadow53's Downloads for MicroG, F-Droid, and more
Now alternatives to apps you might commonly use such as Twitter, Facebook, Gmail, etc. can be a bit difficult to find at first. I stumbled upon a list that a user by the name of Datenschutz has compiled on GitHub that has a good collection of alternative open-source applications. Also, you can alternatively download APK files of certain apps such as Netflix, Messenger Lite, etc. if you don't find a suitable replacement.
Some open-source apps that are found on F-Droid I use daily are:
Flym - RSS Reader
QK SMS - SMS App
Twidere - Twitter Client
Toffeed - Facebook web-client
Newpipe - YouTube player
K9 Material - Mail app
ApkTrack - Checks for updates on APKs installed
Hi,
a Google account isn't required for Google Cloud Messaging (but it is required for many other things).
Also the official Play Store and contact / calendar sync apk work with microG (if needed).
I have created some tools to help setup microG (they are in my signature).
ale5000 said:
Hi,
a Google account isn't required for Google Cloud Messaging (but it is required for many other things).
Also the official Play Store and contact / calendar sync apk work with microG (if needed).
I have created some tools to help setup microG (they are in my signature).
Click to expand...
Click to collapse
I will definitely take a look into this, thank you! Any success on Nougat at all?
fireball0093 said:
I will definitely take a look into this, thank you! Any success on Nougat at all?
Click to expand...
Click to collapse
I'm using microG on Nougat and KitKat, and I can say that it works perfectly (but I patch the framework for signature spoofing instead of using Xposed).
Moto G4 Play (Harpia XT1607) specific so I guess I am not too far off topic: Is there a Nougat ROM available that has signature spoofing built it?
Given my bad experience with Xposed on my old Galaxy Nexus, I really only want to use a ROM with signature spoofing built it. If I have to compile it myself that would be okay but it would be nicer to have a ROM with built-in support. And since I don't think Xposed runs on Nougat yet, that is not an option anyway.
For my old Galaxy Nexus I've been using the Unlegacy project, compiling my own ROM with the signature patches built it. But although I've see "official" Nougat ROMs announced for the G4 Play (LineageOS, AOKP, AOSxP, etc.) either I can't find a link to the correct source code/manifest files or, as in the case of LineageOS I can't get it to compile (complains of missing component(s) even though I've used the provided scripts to pull what should be all the needed items from my phone).
I really want to get back to the non-Google experience I have on my Galaxy Nexus using microG. Thanks for any help!
n76 said:
Moto G4 Play (Harpia XT1607) specific so I guess I am not too far off topic: Is there a Nougat ROM available that has signature spoofing built it?
Given my bad experience with Xposed on my old Galaxy Nexus, I really only want to use a ROM with signature spoofing built it. If I have to compile it myself that would be okay but it would be nicer to have a ROM with built-in support. And since I don't think Xposed runs on Nougat yet, that is not an option anyway.
For my old Galaxy Nexus I've been using the Unlegacy project, compiling my own ROM with the signature patches built it. But although I've see "official" Nougat ROMs announced for the G4 Play (LineageOS, AOKP, AOSxP, etc.) either I can't find a link to the correct source code/manifest files or, as in the case of LineageOS I can't get it to compile (complains of missing component(s) even though I've used the provided scripts to pull what should be all the needed items from my phone).
I really want to get back to the non-Google experience I have on my Galaxy Nexus using microG. Thanks for any help!
Click to expand...
Click to collapse
I am currently looking into hopefully a method for Nougat, give me about a day to see if it works for me.
@fireball0093: If you compile from sources there the patches here instead to patch the compiled code there are the tools linked here.
ale5000 said:
@fireball0093: If you compile from sources there the patches here instead to patch the compiled code there are the tools linked here.
Click to expand...
Click to collapse
@ale5000: What ROM are you compiling from source for a Harpia (I hope that will work on a xt1607 flavor)? Got a URI I can use for repo init?
Thanks!
@n76: I just given the link of the generic signature spoofing patch that should theoretically work on all ROMs, I haven't compiled any ROM.
ale5000 said:
@n76: I just given the link of the generic signature spoofing patch that should theoretically work on all ROMs, I haven't compiled any ROM.
Click to expand...
Click to collapse
Thanks, I have been able to successfully use that patch on my personal builds of the Unlegacy ROM (Marshmallow and Nougat) for my Galaxy Nexus.
I just haven't been able to successfully build a ROM, even without the patch, for my Moto G4 Play.
n76 said:
I just haven't been able to successfully build a ROM, even without the patch, for my Moto G4 Play.
Click to expand...
Click to collapse
Sorry, I can't help with this.
Hallo,
i found a list of Roms supporting signature spoofing in the MicroG Threat. CRdroid is availible for Harpia and it is listen in the ROMS-List. Have anybody testet crDroid 2.1 for Harpia with MircoG?
Links:
https://forum.xda-developers.com/android/general/index-list-custom-roms-offering-t3557047
https://forum.xda-developers.com/g4-play/development/rom-crdroid-v1-6-t3525141
gueschmid said:
Hallo,
i found a list of Roms supporting signature spoofing in the MicroG Threat. CRdroid is availible for Harpia and it is listen in the ROMS-List. Have anybody testet crDroid 2.1 for Harpia with MircoG?
Links:
https://forum.xda-developers.com/android/general/index-list-custom-roms-offering-t3557047
https://forum.xda-developers.com/g4-play/development/rom-crdroid-v1-6-t3525141
Click to expand...
Click to collapse
Nice find, thank you!
Looking at the crDroid source code repository at https://github.com/crdroidandroid it does look like the patch for signature faking is in there. (We should probably have the page at https://github.com/microg/android_packages_apps_GmsCore/wiki/Signature-Spoofing updated to include crDroid).
But I am a bit leary about trying the ROM linked to at https://forum.xda-developers.com/g4-play/development/rom-crdroid-v1-6-t3525141 as, despite the title of the XDA thread, it does not seem to be an official build. It looks like the official builds for the project are at https://androidfilehost.com/?w=devices&uid=23991606952610065 and are all built by "crdroidandroid" and there is no Moto G4 Play build there. The "[ROM][OFFICIAL][7.1.1] crDroid v2.1" links to a ROM built by SubhrajyotiSen on a different page so I am a bit hesitant to install it.
But this is interesting enough that I will try to build the ROM myself using the official sources from the crDroid project and see what happens.
it may be an inofficial Build, but it is mentioned on the G+ - Page of crDroid!
https://plus.google.com/communities...6/stream/d3e3f57f-b974-41f2-8740-97dbdd38056c
I went and installed crDroid here on the forums and also flashed the MicroG installer after flashing crDroid. I can confirm that signature spoofing is available and works. Under Settings, you just have to go to crDroid Settings, scroll down to Miscellaneous, and toggle Allow signature spoofing. Then go into the Self Check section in MicroG and tap "System grants signature spoofing permission" and allow MicroG to have that permission, and then the only thing you have to do to is configure the pre-installed location backends and you're good to go. I'll edit the second post and this thread to include this find, thank you @gueschmid
*Edit*
Actually, would people prefer me to edit this guide and leave it up as a Marshmallow-only guide and then create a second one for Nougat with our device? Just to keep it a bit clean
fireball0093 said:
I went and installed crDroid here on the forums and also flashed the MicroG installer after flashing crDroid. I can confirm that signature spoofing is available and works. Under Settings, you just have to go to crDroid Settings, scroll down to Miscellaneous, and toggle Allow signature spoofing. Then go into the Self Check section in MicroG and tap "System grants signature spoofing permission" and allow MicroG to have that permission, and then the only thing you have to do to is configure the pre-installed location backends and you're good to go. I'll edit the second post and this thread to include this find, thank you @gueschmid
*Edit*
Actually, would people prefer me to edit this guide and leave it up as a Marshmallow-only guide and then create a second one for Nougat with our device? Just to keep it a bit clean
Click to expand...
Click to collapse
Thanks for trying this out. I think I will have the time to follow your lead next week. It will be good to excise GApps from this phone.
VoLTE is important for me, is it working on this crDroid build?
n76 said:
Thanks for trying this out. I think I will have the time to follow your lead next week. It will be good to excise GApps from this phone.
VoLTE is important for me, is it working on this crDroid build?
Click to expand...
Click to collapse
I don't have a carrier that uses VoLTE, but I took a look in the Changelog on some posts and it seems to have support for it on crDroid
Updated the guide to include crDroid in the second post. I have been messing around with Tingle in my spare time but I cannot fully grasp the concept as I don't have much experience using tools like that. If I do succeed in the future, I'll edit that in as well.