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.
Hi
I had the day off, and decided to have a play with the Kitchen to see what I could come up with. After following the instructions on theunlockr.com I decided to base my rom on the OpenFire v.2.3 rom. Any issues that rom had, mine will have.
I have added a few things and changed a couple of things, but in the end, this is my first rom for a device I do not have myself. I have an HTC Desire, but noticed that the Wildfire isn't getting as much love, hence that choice. I hope to get a better understanding of what it takes to make a proper custom rom at some time in the future.
Removed:
Launcher2
Added:
Launcher Pro
Titanium Backup
Rom Manager
Fancy Widget
From the OpenFire v.2.3 post:
NO HTC APPS DO NOT WORK ON THIS ROM AND I WONT TRY TO PORT THEM (but if you try and suceed please tell me and I will maybe include them!)
This ROM is from the android source there is no HTC apps or extra apps from the start it do come with spareparts and dev tools from android source. At the moment it seems a bit slow I think that is due to animations, animations can be turned of in spareparts or in the settings menu.
Features:
- Froyo aosp 2.2.1
- Root + superuser app
- Busybox
- No htc apps!
- Some google apps
- Multi language
- Darktremor Apps2SD
- Patched market
- Usb & WIFI-thetering
- JIT
- 3 in 1 reboot menu
- It may make your phone explode! (You have been warned)
Bugs / Not working:
- Video recording working (but, bad quality)
- Cant import contacts from SIM ? no read/write acess to SIM ? (can anyone confirm or deny this?)
TODO:
- Get rid of above bugs
- HTC-camera (maybe)
Thanks to:
HCDR.Jacob - for the kernel and vendor
Yopsi - for sharing package with google apps.
danne_jo - for APN stuff, and for hosting to my ROM
Sympnotic - For his patched market app
AnantK123 - For pointing out a fix for the camera app
acavella - For hosting / making a homepage dedicated just for OpenFire
Notes:
NO HTC APPS DO NOT WORK ON THIS ROM AND I WONT TRY TO PORT THEM (but if you try and suceed please tell me and I will maybe include them!)
To get app2sd to work you need an ext partition when you have that you might have todo a full wipe and reflash the ROM to get app2sd to work
When you boot up first time choose "com.android.provision"
Anything you want to know about OpenFire can be found at the OpenFire website.
CFH [Wildfire] v1.0 Fault Log
Download:
CFH [Wildfire] v1.0.zip (58 MB)
Due to posting restrictions, I am unable to post links to the Rom. I will post it as soon as possible.
In the mean time, please leave comments below.
Thanks
Chronicfathead
Reserved for future use
Reserved for future use
What did you change? We don't need roms like those. Everyone can customize his installed rom like he wants.
Why don't you stick to a phone you have and help projects that just need help instead of reinventing the wheel over and over again?
no offense, just my personal oppinion
bl1nkk said:
What did you change? We don't need roms like those. Everyone can customize his installed rom like he wants.
Why don't you stick to a phone you have and help projects that just need help instead of reinventing the wheel over and over again?
no offense, just my personal oppinion
Click to expand...
Click to collapse
None taken.
I've had my desire for a while, and decided to root it about a month ago. I have now installed a custom rom, and I'm enjoying the fiddling around. I don't have too much knowledge, apart from experiences gained in the last week or so.
I tried talking a colleague into installing a custom rom, but he said there weren't too many for the Wildfire, so I said I'd have a play. I'm treating it as a learning curve, as I've always been interested in programming, but never really had the time. I have created a (very) small program for the Mac, and have written a few batch files but thats as far as I've taken it.
In an afternoon I've set up a Linux VM, installed all the needed software and had a play to see what I can realistically do. I see this as a first step. I'm trying to talk the wife into a Wildfire so I can have one to play with!
If the consensus is I should delete the thread, then so be it.
Chronicfathead.
When using stock ROM, my mini can determine my native language. Ex like when typing message, just talk. But after switching to custom, cannot found that features. Tried checked in Input Languages, also not find. Google also not found. Install Keyboard for ICS also no luck. Someone can try to help me.
Tq
That's why it's called custom rom, the cooker of the project add some features, and remove others such as interface and keyboard languages, some crappy built-in apps (those whose seems useless in his point of view).
wherefore there where you downloaded the custom rom, you must first read the changelog before proceeding, to avoid complaining later
So if you can live without those missed features, and coexist with your new life
you will need google apps (aka. gapps) to have market and gmail account.
download them from here:
http://www65.zippyshare.com/view.jsp?locale=fr&key=94227110
then flash them via CWM recovery (mount system before proceeding).
abdovar said:
That's why it's called custom rom, the cooker of the project add some features, and remove others such as interface and keyboard languages, some crappy built-in apps (those whose seems useless in his point of view).
wherefore there where you downloaded the custom rom, you must first read the changelog before proceeding, to avoid complaining later
So if you can live without those missed features, and coexist with your new life
you will need google apps (aka. gapps) to have market and gmail account.
download them from here:
http://www65.zippyshare.com/view.jsp?locale=fr&key=94227110
then flash them via CWM recovery (mount system before proceeding).
Click to expand...
Click to collapse
Tq bro. I did it but nothing changes. Tried install ginger keyboard but language still not appearing.
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!
Hi there,
i want to use my old Samsung Galaxy Note as Tablet for my little daugters. To protect the Phone (and also my daughters), i want use the multi user feature to be able to install Apps with my accounts and let her start only less alowed apps.
I always try some Custom ROMS with Android 4.2 or higher. But all of them without the Multiuser feature.
Could anybody provide me the name of a Custom ROM that provide the multi user function ? I found a old thred, that Revolt should support that. But the Version of the Revolt ROM that i found, was without this feature.
cu, Thiemo
starwhooper said:
Hi there,
i want to use my old Samsung Galaxy Note as Tablet for my little daugters. To protect the Phone (and also my daughters), i want use the multi user feature to be able to install Apps with my accounts and let her start only less alowed apps.
I always try some Custom ROMS with Android 4.2 or higher. But all of them without the Multiuser feature.
Could anybody provide me the name of a Custom ROM that provide the multi user function ? I found a old thred, that Revolt should support that. But the Version of the Revolt ROM that i found, was without this feature.
cu, Thiemo
Click to expand...
Click to collapse
There are device related problems with multiuser support (Small /data partition and no emulated internal storage).
This could be changed in an rom but this would make all other roms incompatible without manual repartitioning.
This is also the reason why I have removed it some time ago from my lollipop rom
Hi Bauner,
thank you for that Information. Now i understand why i could not found a ROM with this feature.
Regards, Thiemo