Related
I HATE mini apps on my Galaxy Tab 10.1...
That feature alone is enough to make me want to return the device.
Seriously? Why would Samsung want to decide for me my what apps I want at my finger tips? Then not only that, they use their own cheesy versions of available apps. I have already found the solutions I want to use through my Android phone. I want to carry over the same apps to the tab so that my experience is a little less fragmented.
The "mini apps" constantly get in the way. I'm brushing against the bottom bar causing the apps to pop up... none of which I ever use, completely unintentionally. Annoying! If I could only decide what apps showed up!
Total pain in the REAR!
Then Samsung loads on a bunch of unnecessary software. I HATE having 5 apps that do exactly the same thing on my device... The abundance of music players is asinine. Having three book programs (none of which you can remove) is stoopid.
Why can't you get a piece of hardware without the software all screwed up by the vendor these days?
Why is root necessary every time I put my hands on an Android device to make it useful?
Why can't I purchase an Android product with a Google backed Vanilla version of the current OS installed?
Why?
Why?
Why?
I'm so pissed that this $600 tablet requires an additional 15 dollars in apps and a good 6-12 (or more) hours of set-up time and research to get it properly rooted and operating the way I like it.
Sorry... that made me feel so much better.
Maybe an ipad would have been a better choice for you. I like tinkering with my toys so I chose the tab.
I HATE mini apps on my Galaxy Tab 10.1... do YOU?
Click to expand...
Click to collapse
I may have opened the mini apps tray 3-4 times unintentionally (in the 10 weeks I have the tablet) and I use the "calculator" mini app quite regularly. So no, they don't bother me but I wouldn't miss them if they were gone either.
SGPMan said:
Maybe an ipad would have been a better choice for you. I like tinkering with my toys so I chose the tab.
Click to expand...
Click to collapse
Them there are fighting words...
I enjoy tinkering as well. I have loved customizing my original Incredible and now Incredible 2. They have an excellent following with a lot of very reputable ROM "artists". However, their original UI wasn't that bad to start with. And with the CM nighties, my phone is near perfect.
With the Galaxy Tab 10.1, my initial experience (3 days) I have found it to be laggy and glitchy, which I was shocked about. I want this tab to work for me, but it seems that I'm trying awful hard to make this work. I think it's the fact that my phone is setup so well and runs so well... I figured the tablet would be so much better. I set my expectations high, only to be disappointed so far.
I have rooted and removed a bunch of unnecessary apps, but haven't figured out how to remove that dam mini app bar. As far as custom ROM's go... I haven't loaded any since I am still trying to figure which has the best reputation for stability and speed.
I am trying to figure out something, other wise by Thursday this thing is headed back to Best Buy. Sad thing is... I don't want an apple device, but if that's what is comes to, then I will retire my Android phone as well to keep everything streamlined. Sucks!
gokpog said:
I may have opened the mini apps tray 3-4 times unintentionally (in the 10 weeks I have the tablet) and I use the "calculator" mini app quite regularly. So no, they don't bother me but I wouldn't miss them if they were gone either.
Click to expand...
Click to collapse
I use Real Calc regularly, a donate (paid) app which can handle higher level math functions. I wish I could just substitute it in place of the basic Samsung/Android version.
Agree with you, mini-apps are boring me every time i wanna play a fullscreen game, like "fruit ninja thd"... This "rolling dock" is not a great feature.
SGPMan said:
Maybe an ipad would have been a better choice for you. I like tinkering with my toys so I chose the tab.
Click to expand...
Click to collapse
Actually, the reason most of us choose Android is that we aren't forced into "one man's vision" and have the ability to choose for ourself. The mini-app bar forces us into one company's vision. I have to agree with the OP about this.
We should at least have the ability to turn it off.
Meh...it's there, it's unobtrusive, and at least my experience with it is that I really have to try to get it to come up when I want it. Have never accidentally brought it up. Sometimes the calc and the memo pad are useful.
Can't see why people hate it so much.
MMcCraryNJ said:
Meh...it's there, it's unobtrusive, and at least my experience with it is that I really have to try to get it to come up when I want it. Have never accidentally brought it up. Sometimes the calc and the memo pad are useful.
Can't see why people hate it so much.
Click to expand...
Click to collapse
So...
Try a vs party on "Fruit Ninja THD", you'll see ^^
Just hide the status bar with this:
http://forum.xda-developers.com/showthread.php?t=1265397
problem solved!!!
I actually don't mind having mini app tray. I use task manager, calculater and memo pad for taking notes from web regularly. The only thing I don't like is accidentally hitting the screenshot button. But I totally agree with the original post. An option to turn it off would be nice.
Personally I like them. Two of them I use on a daily basis. Most of the others occasionally.
JHeal77 said:
As far as custom ROM's go... I haven't loaded any since I am still trying to figure which has the best reputation for stability and speed.
Click to expand...
Click to collapse
Task360/Phantom "In Paris"
v.2 works great for me, but v.4 is coming "soon"(tm)
http://forum.xda-developers.com/showthread.php?t=1284355
Really not a massive fan of them being there tbh, but I don't accidentally press the button (not like the screenshot one...grr!) and I don't use the apps in it. I just ignore it and get on my way.
If there was an option of getting rid of it though, I would.
I found this thread while searching for a way to at least configure this menu bar... unfortunately it looks like the whole thing is embedded in the ROM and the only way to hide it is to patch the ROM and/or completely replace it (thanks for the links in the thread).
I fully agree with the OP on a lot of his rant. This is an awesome peice of hardware that comes out of the box with some insanely bad software. I'm still deciding on what launcher to replace the stock version with, but so far both Go and Launcher Pro are tons faster, more configurable, and better looking than the laggy default version that doesn't even let you use the full display.
The status bar menu is kind of a nice idea, but the execution is terrible. If I could configure what apps and quick commands I wanted on the menu and easily hide it, it would be a great feature.
But as it is, the choices of what to put there seem really bizarre. I can't for the life of me figure out why "screen shot" was deemed important enough for most users to justify space on an "always on" menu. I have to routinely go delete unwanted screenshots taken by accidentally brushing that menu option.
The choices of what to put on the quick launch app menu are even worse. Holding the "home" button on the main menu for a couple seconds pops up the task manager so why do I need a whole other button dedicated to pulling up this app? The world clock is just plain terrible compared to other clock apps. The calander is alright, but there are better widgets out there that serve the purpose better than a quick launch menu. The memo and calculator are again terrible and need to be replaced by 3rd party apps so you should be able to replace them on this menu too. The music player is the only one of the apps that serves my purposes, but again there are better 3rd party apps and you should be able to configure what is on a system wide quick launch bar.
From the perspective of an average consumer the out-of-box experience is fairly poor due to the OEM software rather than the hardware or system software. It should be easy for a user to fix this with simple market based apps and configuration options rather than having to apply warantee voiding ROM patches and rooting the OS. Allowing OEM's to "lock" bad software is a really bad policy. If an OEM wants me to use their software, they should develop or license best in class versions of those apps rather than locking the software on the system and forcing me to root the system to get rid of poor quality software.
You can disable all of these functions with some XML editing if it really annoys you that much
I'd happily do all these changes for you for a little donation of just a couple of quid
Try one of the sweet new cm9 kangs, I'm on the 7500 version. So much better then tw honeycomb.
I Agree!!
hate it so much, but now on overcome rom,
its at least slightly less annoying. just ever so SLIGHTLY.
at least in this rom, a swipe upward wont activate it.
wont disturb me during fruit ninja.
but still sometimes press it when i wana press spacebar.
stupid piece of crap tray.
the motorola xoom already has ICS.
samsung will be the slowest tab to get it cos of this touch widz.
Sometimes i feel sorry for samsung.
i have a hunch there is some kind of conspiracy goin on at the back,
where google force manufacturers to implement their own skin. (why else would samsung waste effort to make rubbish that people dont want?)
and google can sell their overprice nexus device to make money.
just imagine, if samsung can sell or upgrade the galaxy S2 and note with the pure and stock vanilla android, and upgrade them to ICS without touch widz, would anyone buy galaxy nexus?
nexus has lausy hardware. last gen GPU and horrible camera. (not due to the 5MP, but generally a weak camera compare to S2 and note)
Luv'em why we have android
Pop up windows that are independent of screen, getting closer to desktop experience. I would like to swap some out but overall, (calc, note, calendar, calculator, & music player) work great. Allow true multitasking.
I just installed OverSkreen which gives me a windowed web browser on top of screen. I really like them.
I am on an ICS KANG version by Mabalito
http://forum.xda-developers.com/showthread.php?t=1461240
With this ROM, I don't have a bottom row of mini apps.
I am using GO Launcher EX HD
http://golauncher.goforandroid.com/2012/03/go-launcher-hd-v1-0-beta/
With the launcher, I able to hide the bottom bar whenever I want.
This is awesome when I watch video and play games
Sorry Guys,
As there doesn't seem to be a whole lot of interest in this project and as no one stepped forward to assist, I'm afraid I'm going to have to abandon this project.
Thanks for following.
___________________________________
OK Guys,
I've run into a bit of a brick wall and need some input from other developers. One of the required APKs from the Q needs a class not included along with my CM9 or Samsung stock roms. The class appears to be called "android.os.UpdateLock". So how do I go about ripping the class out of the Nexus Q rom and injecting it into CM9? Any help would be very appreciated!$!
--------------------------------------------------------------------
Hello All,
The Project
I'm looking to embark on a project to rip out the cloud function from the Q and install it on any android device. I want the cloud streaming of "Google" music and movies without the $300 expense.
The Progress
As of today I have the Nexus Q Deodexed, ripped out several apk files including the Nexus Q "Launcher" HubBroker.apk. I've merged the apks along with the fonts and lib folders of /system and my Galaxy Tab now boots up and runs like a Q. Primary issue outstanding is, the Nexus Q app won't detect the "galaxy Q" through bluetooth. I assume that some functions of the Q are sitting either within the bluetooth libs or that the Nexus Q has a specific bluetooth address that the app needs to see before detection.
My next attempt will be to try taking apart the Nexus Q apk and either changing its bluetooth search criteria or removing it completely. Second to that if anyone out there has a Q and has it setup on their phone, I could use the /data/data folder to extract more information about how it works. Or even better if someone knows what config file is generated on the actual nexus Q when it's set up for that first time.
You can already do that on most android devices. The Q just takes it to the big screen conveniently.
The function of being able to control the Google queue of device A from device B, C, D etc does not exist. Or at least I'm not aware of an app that does that.
I believe that I've tracked down the apk that does it on the nexus but I need to deodex the apps and can't seem to find a tool that works. Anyone out there deodex this rom yet?
JoeJonnyBoy75 said:
Hello All,
The Project
I'm looking to embark on a project to rip out the cloud function from the Q and install it on any android device. I want the cloud streaming of "Google" music and movies without the $300 expense.
The Progress
As of today I have the Nexus Q Deodexed, ripped out several apk files including the Nexus Q "Launcher" HubBroker.apk. I've merged the apks along with the fonts and lib folders of /system and my Galaxy Tab now boots up and runs like a Q. Primary issue outstanding is, the Nexus Q app won't detect the "galaxy Q" through bluetooth. I assume that some functions of the Q are sitting either within the bluetooth libs or that the Nexus Q has a specific bluetooth address that the app needs to see before detection.
My next attempt will be to try taking apart the Nexus Q apk and either changing its bluetooth search criteria or removing it completely. Second to that if anyone out there has a Q and has it setup on their phone, I could use the /data/data folder to extract more information about how it works. Or even better if someone knows what config file is generated on the actual nexus Q when it's set up for that first time.
Click to expand...
Click to collapse
This is a pretty nice project and there is nothing like this happening in Android now, besides the nexus Q. I'd like to see a future port of it to Google TV devices
auad said:
I'd like to see a future port of it to Google TV devices
Click to expand...
Click to collapse
Would love to have this functionality in an APK for me Google TV. Don't see why it wouldn't work, well other then no bluetooth on the Revue....
Still very interested in this thread regardless of GTV. I will be following your progress. Thanks!
.
I'm looking for this as well.
I have 3 spare HTC EVO's, and they all have HDMI out. I would like to be able to just plug them into the TV and use my other phones to control them / play music / etc. Maybe even throw XBMC on them with the ability to control from another phone..
They're slower, and less memory..but it may be doable.
Did anyone dig into this? I'd like this for the latest port of Android for a Raspberry Pi and willing to do some of the (noob)stuff myself.
That would be awesome to use any HDMI equipped phone along with the Nexus Q functionalities. I'm really interested.
I guess the problem with the missing API is that the Nexus Q runs android JB and he tried with a cm9.
Vettekult said:
I guess the problem with the missing API is that the Nexus Q runs android JB and he tried with a cm9.
Click to expand...
Click to collapse
Not true, Q runs ICS...
Let me know...
what I can do to help. If you give me a run down on what you would like me to try as far as pulling files from the q or my connected devices just shoot me a PM and i'll give it a shot. I too would love to add this functionality to my spare devices laying around.
I've been interested in this since day one as well. IT is what has me almost ready to fork out the money on more then one occasion. I have a party coming up and it would be fun to have my N7 as the Jukebox.
The Class issue, I'm not sure about. Here is some info that might get it started.: http://www.itcsolutions.eu/2011/08/...te-a-new-activity-class-with-manifest-editor/
AND:
http://stackoverflow.com/questions/5012004/adding-a-new-class-to-android-project
It looks like it is something created with the app. Since you cut/pasted the apk into system it may not have been installed. But I'm thinking that it is something else. Some where in the android system lib's it is probably installed. Since this was a device dedicated to this purpose, they were able to install it into the system and the app calls it. I'm slowly learning to write apps (very slowly) so I am not sure beyond this, or even about this for that matter.
I do have a question. It looks like you pulled some system apps and put them in your galaxy tablet. I think a better test would be to basically replace all the /system contents of say a N7 (galaxy tab may work) with those from the Q. Then once it works, cut down the files until it stops. Then with a list of what is needed to make it work we could get down to the nitty gritty.
My guess is some more knowledgeable devs, like those who got Google Now working, would have a better idea.
I'd love to see a third party app do the jukebox function, I think a issue is license certificate (DRM) for the multiple users. I don't understand how the user is associated/authenticated for the music. One Question is if a user Ques up music then leaves does it cause that music to not be able to be played or will it still play once it's been que'd? My guess is the app just organizes the music/user who is next then when it's their turn it streams from their device in real time... but I'm really not sure about this.
joeavery2 said:
I've been interested in this since day one as well. IT is what has me almost ready to fork out the money on more then one occasion. I have a party coming up and it would be fun to have my N7 as the Jukebox.
The Class issue, I'm not sure about. Here is some info that might get it started.: http://www.itcsolutions.eu/2011/08/...te-a-new-activity-class-with-manifest-editor/
AND:
http://stackoverflow.com/questions/5012004/adding-a-new-class-to-android-project
It looks like it is something created with the app. Since you cut/pasted the apk into system it may not have been installed. But I'm thinking that it is something else. Some where in the android system lib's it is probably installed. Since this was a device dedicated to this purpose, they were able to install it into the system and the app calls it. I'm slowly learning to write apps (very slowly) so I am not sure beyond this, or even about this for that matter.
I do have a question. It looks like you pulled some system apps and put them in your galaxy tablet. I think a better test would be to basically replace all the /system contents of say a N7 (galaxy tab may work) with those from the Q. Then once it works, cut down the files until it stops. Then with a list of what is needed to make it work we could get down to the nitty gritty.
My guess is some more knowledgeable devs, like those who got Google Now working, would have a better idea.
I'd love to see a third party app do the jukebox function, I think a issue is license certificate (DRM) for the multiple users. I don't understand how the user is associated/authenticated for the music. One Question is if a user Ques up music then leaves does it cause that music to not be able to be played or will it still play once it's been que'd? My guess is the app just organizes the music/user who is next then when it's their turn it streams from their device in real time... but I'm really not sure about this.
Click to expand...
Click to collapse
Ok so here is some more detailed info for those of you still following the project.
HubBroker.apk is the app that is for all intents and purposes the "launcher" for the nexus Q. It will install on the Galaxy Tab and Nexus 7. It takes over your "home" and replaces it with a picture of the Nexus Q and a welcome sign. This app looks to be only the launcher as it doesn't do anything if you tap on it. Also having the app running doesn't allow the Nexus Q app (from your phone) to find the device.
So I assume that that the Q is controlled via bluetooth to get it setup and running. Including configuring the Wifi, network settings, etc. Oddly enough the app does send a request to android system to turn on the bluetooth and changes the bluetooth device name to Nexus Q.... The ... part is a odd string of characters that I assume is used in case you happen to have multiple Nexus Q's.
Now as just having the app doesn't seem to work (Phone finding the Q). I've replaced all the bluetooth libs with the ones from the Q. Still nothing. I've migrated all the other APK files and then I get FCs all over, and still no connection. I haven't tried replacing the whole system yet, but I assume the hardware differences would be to great. The only other piece of the puzzle I have yet to attempt it merging the kernels or at least the init parts of the kernel relating to bluetooth.
If you have any questions though let me know. I've been up and down this thing.
Why don't we just flash the img on an old phone and see if that works?
zAo_ said:
Why don't we just flash the img on an old phone and see if that works?
Click to expand...
Click to collapse
For that to work we'd need to get a device with similar hardware (CPU, Chipset, etc.) Not only that but it would need to have the same MTD setup unless I'm mistaken.
Actually I'm going to give that a try with the nexus 7. I'll let you know what happens, won't be till tonight though.
JoeJonnyBoy75 said:
For that to work we'd need to get a device with similar hardware (CPU, Chipset, etc.) Not only that but it would need to have the same MTD setup unless I'm mistaken.
Actually I'm going to give that a try with the nexus 7. I'll let you know what happens, won't be till tonight though.
Click to expand...
Click to collapse
Cool, Thanks.
Sent from my Galaxy Nexus using xda premium
JoeJonnyBoy75 said:
For that to work we'd need to get a device with similar hardware (CPU, Chipset, etc.) Not only that but it would need to have the same MTD setup unless I'm mistaken.
Actually I'm going to give that a try with the nexus 7. I'll let you know what happens, won't be till tonight though.
Click to expand...
Click to collapse
Galaxy nexus has very similar hardware. Someone should try porting it.
Sent from my Nexus 7 using xda premium
If someone still interested in the project, i'm very interested in it, i have a galaxy nexus (almost same hardware) so we can give it a try, im also a android developer, so if it need to build some apk for it to work, i could give a shot.
Anyway, if there is someone interested just post here and we do all we can to make that work.
edit: Only one problem, as I'm out of USA, i need the q apk to test if it will connect or not. I cant download from play store.
I'm sure there will be so many people interested in it. I just think that not to many of them enter this category on forum
I also need the nexus q image so I can flash it. I tried searching it but didnt find
Alright, So we've seen Firefox running on Android Wear, however we can't enter any menus due to no softkeys on the device. I have been trying to install apps such as "Virtual Button Bar" and SoftKeys for Root Users onto the watch and they install and run. But only the home button works. Neither the back or menu button seems to work in any application.
Has anyone else attempted to get some softkeys for controls in unsupported apps that may be able to enlighten me more on why these keypresses seem to be ignored by the OS..
ShadowEO said:
Alright, So we've seen Firefox running on Android Wear, however we can't enter any menus due to no softkeys on the device. I have been trying to install apps such as "Virtual Button Bar" and SoftKeys for Root Users onto the watch and they install and run. But only the home button works. Neither the back or menu button seems to work in any application.
Has anyone else attempted to get some softkeys for controls in unsupported apps that may be able to enlighten me more on why these keypresses seem to be ignored by the OS..
Click to expand...
Click to collapse
With LMT all the keys that can get on-screen are working just fine in apps that support them but the problem is the app can't be launched (FC-most probably because it has an action bar) so you can't edit the buttons or the size of them, they just work but are over sized.
Ranomez said:
With LMT all the keys that can get on-screen are working just fine in apps that support them but the problem is the app can't be launched (FC-most probably because it has an action bar) so you can't edit the buttons or the size of them, they just work but are over sized.
Click to expand...
Click to collapse
I wonder if you can install LMT on your phone, customize it first, then go to /data/data/... or an appropriate location to grab the config and push it into the watch.
I'm also considering buying a GW, so if this somehow works, please let me know.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
I wonder if you can install LMT on your phone, customize it first, then go to /data/data/... or an appropriate location to grab the config and push it into the watch.
I'm also considering buying a GW, so if this somehow works, please let me know.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
Yes ofc it will work but the problem with that is that it will take a lot of time to customize the settings right for the watch and each time you copy the files to data/data remember that you will need to set the right permissions, owner and SELinux context for each and every file and considering that currently SELinux contexts can differ from one device to an other and from one ROM to an other that will be really time consuming and hard as you will have to find an app on your watch that has the same types of files to see the SELinux contexts for each of them.
To say it short yes you can do that but it will probably take you at least 1 day and I don't have the time or patience to do that and I doubt many people on this forum will but ofc if you do buy a G Watch have a go at it and tell us just how much time you've wasted.
Ranomez said:
Yes ofc it will work but the problem with that is that it will take a lot of time to customize the settings right for the watch and each time you copy the files to data/data remember that you will need to set the right permissions, owner and SELinux context for each and every file and considering that currently SELinux contexts can differ from one device to an other and from one ROM to an other that will be really time consuming and hard as you will have to find an app on your watch that has the same types of files to see the SELinux contexts for each of them.
To say it short yes you can do that but it will probably take you at least 1 day and I don't have the time or patience to do that and I doubt many people on this forum will but ofc if you do buy a G Watch have a go at it and tell us just how much time you've wasted.
Click to expand...
Click to collapse
Hmm, I doubt it would take that much effort, because I've tried manually moving config for some other apps without even touching the permissions, and they seem to fix that automatically. System apps don't like that way, though.
But seeing how Android Wear hates ActionBar, thus making many of my apps unavailable, I don't know if I'd still buy one. Yes I do want something Android on my wrist, but if it's just time-telling and Google Now (which is not even available here in China), then I'm not paying that chunk for it.
What apps do you have, then?
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
Hmm, I doubt it would take that much effort, because I've tried manually moving config for some other apps without even touching the permissions, and they seem to fix that automatically. System apps don't like that way, though.
But seeing how Android Wear hates ActionBar, thus making many of my apps unavailable, I don't know if I'd still buy one. Yes I do want something Android on my wrist, but if it's just time-telling and Google Now (which is not even available here in China), then I'm not paying that chunk for it.
What apps do you have, then?
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
Well you are talking about moving configs to the same phone I guess? Also if not were you on android 5.x+ cause if yes SELinux has became really strict, to the point that if you mess up some contexts on any file in the data partition you could even get a bootloop (happened to me) or have all your apps disappear and be unable to install any app until you fix up the SELinux context (again happened to me), which you will have to do using adb in that state if you don't happen to have and file manager with root capabilities installed in /system/app or /system/priv-app.
Also to answer your question: yes most normal android apps don't work but there are some that do, even some games and some are even really playable, moreover there are enough useful android wear apps out there, I don't know what you plan to use your watch for but for me it does way more than enough, after all it's a watch, it's not like I'll ever want to spend a lot of time looking at it doing anything but I can do some fast reading on it when I need (not like I'll ever read a whole book on it, that's why I have an android e-book reader or even my phone in the worst case scenario), browsing the internet fast (ofc it needs to be connected to a phone with a data connection), receive and send messages, reject calls, even some light or not so light gaming, even things as Temple Run 2, can play music when I don't have my phone using a bluetooth headset/speaker), the only thing I miss is a full office suite, really, I am writing a novel at the moment and never know when I get some inspiration and have to write down what I have in my mind pretty fast so I don't forget, would love to just be able to write on the watch and not have to take out my phone for that.
Also I would suggest that if you have the money you should go with a watch that has wi-fi like the G Watch R or Urbane cause then you will be able to use the internet without a phone, also the screen of the G Watch is really bad in the sun, I had a Sony Smartwatch 2 before and that was way more limited software wise (and for that reason had a battery life of over 1 week) but the screen was miles ahead, I could see everything in powerful sun light without even setting the brightness to the maximum, on the G Watch I can barely see anything with the brightness at maximum in not so powerful sun light.
Does LMT contain the menu button by default? I could care less if it's a little oversized (as long as it's not to big for 150-175 DPI), but I'm about to reset my watch using the restore tools because I screwed up root while trying to get SoftKeyz (EDIT: I believe was the name of the softkey app I was trying to make work, can't remember and just finished resetting) to work correctly.
Ranomez said:
Well you are talking about moving configs to the same phone I guess? Also if not were you on android 5.x+ cause if yes SELinux has became really strict, to the point that if you mess up some contexts on any file in the data partition you could even get a bootloop (happened to me) or have all your apps disappear and be unable to install any app until you fix up the SELinux context (again happened to me), which you will have to do using adb in that state if you don't happen to have and file manager with root capabilities installed in /system/app or /system/priv-app.
Also to answer your question: yes most normal android apps don't work but there are some that do, even some games and some are even really playable, moreover there are enough useful android wear apps out there, I don't know what you plan to use your watch for but for me it does way more than enough, after all it's a watch, it's not like I'll ever want to spend a lot of time looking at it doing anything but I can do some fast reading on it when I need (not like I'll ever read a whole book on it, that's why I have an android e-book reader or even my phone in the worst case scenario), browsing the internet fast (ofc it needs to be connected to a phone with a data connection), receive and send messages, reject calls, even some light or not so light gaming, even things as Temple Run 2, can play music when I don't have my phone using a bluetooth headset/speaker), the only thing I miss is a full office suite, really, I am writing a novel at the moment and never know when I get some inspiration and have to write down what I have in my mind pretty fast so I don't forget, would love to just be able to write on the watch and not have to take out my phone for that.
Also I would suggest that if you have the money you should go with a watch that has wi-fi like the G Watch R or Urbane cause then you will be able to use the internet without a phone, also the screen of the G Watch is really bad in the sun, I had a Sony Smartwatch 2 before and that was way more limited software wise (and for that reason had a battery life of over 1 week) but the screen was miles ahead, I could see everything in powerful sun light without even setting the brightness to the maximum, on the G Watch I can barely see anything with the brightness at maximum in not so powerful sun light.
Click to expand...
Click to collapse
Thanks for compiling such a long response for me :thumbup:
As my signature says most of my devices are on 5.1. Moving some game saves across devices works nicely, though moving contacts database involves modifying owner and permission, but not SEL context - to be honest, I don't even know that ever matters.
Sure I don't have many things in mind when it comes to "what to do with GW"... Back when I was using the Gear, I had quite some apps on it, but most of the time I use it as a timekeeper. But not being compatible with ActionBar is so shocking - I can't imagine how many apps I've used on the Gear so nicely won't work with GW, the most important of which are Greenify, LMT and Root Explorer. Looks like I still have to do much research before I decide on a purchase.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
Thanks for compiling such a long response for me :thumbup:
As my signature says most of my devices are on 5.1. Moving some game saves across devices works nicely, though moving contacts database involves modifying owner and permission, but not SEL context - to be honest, I don't even know that ever matters.
Sure I don't have many things in mind when it comes to "what to do with GW"... Back when I was using the Gear, I had quite some apps on it, but most of the time I use it as a timekeeper. But not being compatible with ActionBar is so shocking - I can't imagine how many apps I've used on the Gear so nicely won't work with GW, the most important of which are Greenify, LMT and Root Explorer. Looks like I still have to do much research before I decide on a purchase.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
I just looked at your signature and now I know why you had no problem with moving data from one device to an other: all your devices are running CM so they will all use the same security contexts but CM's security contexts are different from normal stock AOSP's contexts and both are different from the contexts used in Samsung TW ROM's, I can bet that if you try to move the data to a stock nexus or some other device running a manufacturer ROM or an other custom ROM than CM (most do use the same contexts but some don't) you will get into problems. SELinux contexts seem to be now just as important as permissions, sometimes you can get around with the wrong owner but if you have wrong Permissions or SELinux contexts you might mess up more than what you were changing.
Also about the app compatibility thing....I don't really miss many apps that I run on my normal devices, the only one I can actually think of is Titanium Backup (and an office app as I said), I found a good replacement for root explorer in MiXplorer, greenify is totally un-needed and wouldn't be too useful even if it worked (I'm actually not sure if it does or not, to me that layout looked like the action bar is either a non-default implementation so it might work without it) because the xposed installer doesn't work (FC-same reason, action bar) but I think xposed could work if someone adapted the installer (doesn't seem to me that the OS-level differences are so big, it's more of the framework), didn't yet try but just for a lol will flash the xposed lollipop zip and see if I can still boot.
An other option for you might be to buy a Gear S, as far as I can see there is some development going on towards running (initially) android wear on it and further afterwards full android.
Ranomez said:
I just looked at your signature and now I know why you had no problem with moving data from one device to an other: all your devices are running CM so they will all use the same security contexts but CM's security contexts are different from normal stock AOSP's contexts and both are different from the contexts used in Samsung TW ROM's, I can bet that if you try to move the data to a stock nexus or some other device running a manufacturer ROM or an other custom ROM than CM (most do use the same contexts but some don't) you will get into problems. SELinux contexts seem to be now just as important as permissions, sometimes you can get around with the wrong owner but if you have wrong Permissions or SELinux contexts you might mess up more than what you were changing.
Also about the app compatibility thing....I don't really miss many apps that I run on my normal devices, the only one I can actually think of is Titanium Backup (and an office app as I said), I found a good replacement for root explorer in MiXplorer, greenify is totally un-needed and wouldn't be too useful even if it worked (I'm actually not sure if it does or not, to me that layout looked like the action bar is either a non-default implementation so it might work without it) because the xposed installer doesn't work (FC-same reason, action bar) but I think xposed could work if someone adapted the installer (doesn't seem to me that the OS-level differences are so big, it's more of the framework), didn't yet try but just for a lol will flash the xposed lollipop zip and see if I can still boot.
An other option for you might be to buy a Gear S, as far as I can see there is some development going on towards running (initially) android wear on it and further afterwards full android.
Click to expand...
Click to collapse
Hmm, you got a good point there. I also move data between one of the CM phones and the TF300TL tablet, but SEL is nonexistent in Android 4.2, so I guess you're right.
Gear S is way out of my reach - if I had that cash I'd buy a ZenWatch, a 360 or even an Omate TrueSmart without hesitation. But thanks for letting me know all this anyway - I choose not to look at GW and Android Wear at this moment.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
Hmm, you got a good point there. I also move data between one of the CM phones and the TF300TL tablet, but SEL is nonexistent in Android 4.2, so I guess you're right.
Gear S is way out of my reach - if I had that cash I'd buy a ZenWatch, a 360 or even an Omate TrueSmart without hesitation. But thanks for letting me know all this anyway - I choose not to look at GW and Android Wear at this moment.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
You could instead look at a Gear Live then, it at least has a heart rate sensor and a way better screen for outdoors and at least in my country it is in the same price range as the G Watch (actually cheaper) but yes, I can't totally recommend android wear as it is right now, it's good enough (at least for me) but I can also see why a normal pure android watch could be way better yet I have faith that this will change.
Also I really can't recommend the Omate or any other MediaTek smart watch as 1st most of them have no resistance to water whatsoever, 2nd they have no support from and 3rd the firmware on them has so many security holes and other flaws it looks like a schweizer.
EDIT: I forgot to say that if you want full android you could search for a SmartQ Z-watch, as far as I know that is a pretty good one and also pretty cheap (on pandawill when it was on "last time sale" it was sold for 30$ and I am talking about the normal not the lite one, the lite one isn't worth it) but I don't think it will be updated anymore, yet android 4.4 is pretty good compared to other android smart watches.
Ranomez said:
You could instead look at a Gear Live then, it at least has a heart rate sensor and a way better screen for outdoors and at least in my country it is in the same price range as the G Watch (actually cheaper) but yes, I can't totally recommend android wear as it is right now, it's good enough (at least for me) but I can also see why a normal pure android watch could be way better yet I have faith that this will change.
Also I really can't recommend the Omate or any other MediaTek smart watch as 1st most of them have no resistance to water whatsoever, 2nd they have no support from and 3rd the firmware on them has so many security holes and other flaws it looks like a schweizer.
EDIT: I forgot to say that if you want full android you could search for a SmartQ Z-watch, as far as I know that is a pretty good one and also pretty cheap (on pandawill when it was on "last time sale" it was sold for 30$ and I am talking about the normal not the lite one, the lite one isn't worth it) but I don't think it will be updated anymore, yet android 4.4 is pretty good compared to other android smart watches.
Click to expand...
Click to collapse
Z Watch? No thanks, I've tried that *before* the Gear, and I sold it within a week and lost $15 in the process - crappy 1GHz MIPS which is not only slow but also lacks compatibility for almost everything I throw at it - not even a custom launcher or a weather app would work. Omate's MTK is indeed unfavorable, and that's why I haven't already got one. And there aren't many people who sell Gear Live here. Which leaves me zero feasible choice.
I guess I could call it an end to my hunt of smartwatches, until something like Neptune Pine (but thinner and lighter) shows up. Thanks for helping me analyze the situation all this time!
AndyYan said:
Z Watch? No thanks, I've tried that *before* the Gear, and I sold it within a week and lost $15 in the process - crappy 1GHz MIPS which is not only slow but also lacks compatibility for almost everything I throw at it - not even a custom launcher or a weather app would work. Omate's MTK is indeed unfavorable, and that's why I haven't already got one. And there aren't many people who sell Gear Live here. Which leaves me zero feasible choice.
I guess I could call it an end to my hunt of smartwatches, until something like Neptune Pine (but thinner and lighter) shows up. Thanks for helping me analyze the situation all this time!
Click to expand...
Click to collapse
Well the compatibility thing has changed as ingenic released a compatibility layer (something like libhoudini for intel CPU's) so as far as I can see from a friend's Z Watch it can run almost anything one would throw at it (ok, anything a bit rational, only apps that can actually be useful on a watch) but yes that CPU is not the fastest and the firmware is not really optimized enough so you would need a custom ROM and perhaps some RAM management script like L Speed to get it lag-free yet I can say my friend's z watch behaves pretty well on Dj Droid, it wasn't really lag-free the 2 weeks time we exchanged watches so I could test it but that's just cause I was using xposed and quite a few modules and also had about 100 apps installed, the lag wasn't really the problem for me, the annoying thing for me was the app load times, it would take me up to 1 minute to launch a 3d game.
This being said I would still recommend you to wait for something better, smartwatches right now are good but I see a lot more potential and I am sure in a few years we will see amazing ones, perhaps as good as our older phones in regards to app compatibility and flexibility, who knows, perhaps they'll even be as powerful as our current phones (as far as it goes phones in 1 year will probably be much powerful than our current phones so anything's possible).
EDIT: I also forgot to say that many apps have been adapted for MIPS since then so even without the compatibility layer there are enough apps working on the Z Watch.
The info about the issues provided as on 2017 September 13.
The text was last edited on 2019 August 24.
Hello.
Sorry for mistakes in my poor English.
I had used every day LOS14.1 and RR5.8.3-5.8.4 custom ROMs for Samsung Galaxy S2 (model: GT-I9100) for more than 2 months in the middle of 2017 and this is my serious test report:
1) When you will get an incoming phone call, receive a message via cellular network or a file via bluetooth then Galaxy S2 with the custom ROM will rings and vibrates but the screen can be fully dark for several seconds without any notification about it.
This bug almost does not exist in RR 5.8.4.
2) Multiple issues are with the smartphone storages (internal and external).
a) Some apps can do not work with the smartphone storages. They can start to work with storages after the smartphone reboot or after few reboots only.
The same bug is in the Resurrection Remix ROM 5.8.4. The screenshots attached to this message proof the existense of this bug in RR 5.8.4.
b) Only during my attempt to use the custom ROMs LOS 14.1 and RR 5.8.3-5.8.4 on Samsung Galaxy S2, I lost the 1 file (it was the important file to me) on an external microSD card and yet file explorer apps start to show the 2 suspicious unerasable zero size files in file listings there, which I can not delete nor rename nor even copy - file explorers to continue to show they in file listings still today after years on my microSD card. It is interesting that these zero size undeletable files was discovered not in an upper directory but instead deep in the old different long directories on my microSD card. Thus, may they was implemented hiddenly as masking labels there for a reason remained unknown.
c) Impossible to appoint an user installed file explorer app as a default file explorer for pick-up files from another programs. For instance, when the smartphone user want to send a file via Skype then there is always only the file explorer opens with the poor and uncomfortable interface, which implemented in the custom ROM as default forever. And only then from its ugly interface the user can choose one of other installed file explorers for using they once for find and pick-up a file.
The famous FX File Explorer app does not work with the default internal folder 'Documents'. The app also can not delete a group of selected files on an external SD card.
The RR 5.8.4 ROM haves even 2 implemented file manager apps which work smooth but they both have poor UIs with limited functions.
Factually, do not providing Android APIs correctly the custom ROM developers refuse to use user installed apps fullfledgely but instead they compel the users of their ROMs to use only an ersatz bloatware soft implemented by the ROM developers in the custom ROMs.
3) The big battery drain after every reboot and a significant battery drain in general.
As more media files (videous, images include offline map tiles, sounds) are in the internal or external storage (an microSD card) of smartphone then more extensive battery drain Galaxy S2 will suffer after every reboot and after some operations with access to storages. This bug appears in both ROMs: in Lineage OS 14.1 and in Resurrection Remix 5.8.3 - 5.8.4.
For instance, if 128GB microSD card almost full of various videous and photos is in the smartphone then it becomes very hot for more than 1 hour after every reboot!
Some my futher research reveals that the high temperature with the battery drain caused by the dubious activity of Media Storage app implemented in the Lineage OS based ROMs hiddenly. This app finds and analises all media files (and may more) by unoptimized and uneffective way creating and saving big hidden databases, wasting CPU, a battery and an internal storage.
Unfortunately, disabling of this dubious hidden app leads to the smartphone loses functionality partly.
Please, pay in opinion that this bug produces the same traces as usually produced by some hidden virus activity: excessive scanning of user files, an unexpected load on the hardware, eventual draining of the battery...
4) Multiple lags (short freezes) are at various programs interfaces using. A main Android 7 menu is more or less smooth only.
For instance, Skype app version 8 has lags to several seconds in its menu.
Also the smartphone touchscreen is more sensible with the latest original Samsung's firmware (Android 4.1.2) rather than with LOS 14.1 or RR 5.8.4.
On another hand, Galaxy S2 with LOS 14.1 or with RR 5.8.4 scores more points in AnTuTu test but it is only mostly due to becoming of supporting F2FS and yet getting additional points for an newer additional rendering engine.
5) Sometimes over-the-air updates becomes impossible due to already after downloading an update file the smartphone then displays an error message 'Unable to reboot into recovery'. For instance, this bug appears after 2nd August 2017 and 23th August 2017 updates.
6) Camera1 and Camera2 APIs do not provided correctly. Some serious camera apps report about it clearly by a message and then close. Another camera apps are buggy.
I just will give few examples...
All videous recorded with a mono sound only but can be saved as allegedly with a stereo sound.
The famous A Better Camera app by Almalence loses all its settings unexpectedly time to time and becomes as its first launch again. This bug does not exist in RR 5.8.4 but instead there is another bug with A Better Camera app: it can not record videous with scene mode setting. And it is very sad due to the app can significantly improve the camera in our old device specially for photo and videorecordings in low light conditions (it can be reached by choosing manually ISO800 and then the Fireworks scene mode).
The implemented in the ROM the Snap camera app is very weak with the ugly uncomfortable interface.
7) There is a trouble to enter the year manually in the data settings in a portrait mode due to number of years limitation. The same bug was in RR 5.8.3 but it was fixed in RR 5.8.4.
This bug does not exist in a landscape mode.
8) It can send and receive only the very limited kinds of files via bluetooth, which filename extensions are listed among a poor list of files recognised by the custom ROM itself (not by user installed apps). Factually, it is like an unwanted blocking filter at the bluetooth.
For instance, you can create an effective compressed .zipx archive file by the WinZip app for Android OS on Galaxy S2 but you will be unable to send such archive file via bluetooth. And you will be unable to receive such files too.
Many file extensions do not recognized by the custom smartphone ROM: among they are modern Opus music format, RAR archives and etc, etc. You will be unable to send or receive they via bluetooth.
The same bug is in RR 5.8.4.
Please, pay in opinion this issue does not seem as a mistake of the ROM developers but just opposit: it seems more as an unwanted blocking filter specially implemented on the bluetooth. And their reason for it remains unclear and suspicious.
9) There is an implemented feature to record a phone call but there is not an option to record all phone calls automatically. Instead only after hand up there inside the tree of dialer settings appears a hidden option which allow manually start to record the current call. So, if you want to record the call then only already during the call you need to go into the dialer menu tree and activate this hidden option, which is uncomfortable.
Moreover, external apps for phone call recordings does not work properly with this ROM (they do not record sounds from another side).
The same bug is and in RR 5.8.4.
10) The famous SuperSU root tool by ChainFire does not compatible with Lineage OS 14.1 for Galaxy S2. And apps which require only the SuperSU root can do not work properly.
The same bug is in the Resurrection Remix 5.8.4.
11) The small window with the text 'MTP host error' appears in the screen foreground like a ghost.
The same bug is in RR 5.8.4.
12) The settings menu haves a white background everywhere and it causes wasting of short lifetime span of pixels of OLED display triggering yet the additional unwanted battery drain and provoking an eye strain.
Unfortunately, a wallpaper does not change it.
There is not a simple option in the settings menu for just to change its white background to black.
It is not a bug but it is a significant disadvantage of the Lineage based ROMs - specially the Resurrection Remix ROM, which haves miltiple various settings and options but except needful simple this one.
13) The official Lineage OS bug tracker does not accept bug reports by easy way. Instead it requests a registration in advance via a full user name and other personal data, which can be sensitive and used by unappropriate way. It does not allow the registration via the World famous and trusted Google+ or Facebook social networks. Moreover, sometimes the bug tracker does not work and have an announcement about sheduled technical maintenance on a web-hosting side.
14) The ROM developers do not fix even well known simple bugs like described here at the points 8 or 9.
Talking very softly: some XDA forum users (include moderators) also do not welcome for public bug reports in proper topics of the XDA forum. It seems like they conceal the existence of many bugs and only lure new people to become victims of the buggy ROMs. And I did started this topic for stop it.
I do not know what their purpose is exactly.
But after some time observation it is possible to determine that someone actually regularly 'dilute' proper topics on the XDA forum by short luring messages in parrot style like 'I had installed it and it is great!' Unfortunately, such kind of simple messages are just alluring fakes high probably.
The another short trap parrot messages are like that 'It runs fast and smooth!'. The deception there is that it attracts only by the Android 7.1.2 menu appearance on the old device for purposes like a brag but really conceal that the whole device with this ROM becomes unreliable for serious fullfledge using.
I was attracted by topics on the XDA forum about Android 7.1.2 for Samsung Galaxy S2 (model: GT-I9100) and I had lost more than 2 months period installing latest Lineage OS 14.1 updates and Resurrection Remix ROMs 5.8.3 - 5.8.4 and I had decided that the last official Samsung's firmware with Android 4.1.2 is not ideal but much reliable on Galaxy S2 rather than LOS 14.1 or RR 5.8.4.
15) The custom ROMs does not provided as a single useful full package unlike it was with a Samsung's official firmwares. Actually, things, which called Lineage OS 14.1 or RR 5.8.4 for Galaxy S2, are main parts of unresonant firmwares only. It means that in a case of installing such firmwares the user discovers many disadvantages of they and after asking questions on the XDA forum he gets endless tips like: to find in the internet and install other necessly parts and yet to make very specific technical adjustments manually or even experiment with they. All it can be interesting and feasible for the smartphone entusiasts but not for an ordinary user.
For instance, some messages on the XDA forum suggest to download and install the special version of Kernel Adiutor app then run it and experiment with its settings for make the smartphone runs smooth because the ROM developers did not preselect best settings and did not adjusted they before as default values. Moreover, you will need to find in the internet and install separately yet a modem firmware for a better signal, the Substratum app and a proper theme just for make the screen background black everywhere and etc, etc.
Factually, Lineage OS 14.1 and Resurrection Remix 5.8.3 or 5.8.4 ROMs for the Samsung Galaxy S2 smartphone are not 'Plug&Play' kind of firmwares. They are unfeasible for an average user.
Please, pay serious attention: an user of these buggy custom ROMs can get a negative impact to his behavior (even to his mental health) and to his business.
JaLoou said:
[...]last official Samsung's firmware with Android 4.1.2 is not ideal but much reliable on Galaxy S2[...]
Click to expand...
Click to collapse
Obvious obviousness.
Custom ROMs are not meant to replace commercial firmware, but so that the community can learn and be happy to discover new things.
The screenshots, published with this message, proof the big battery drain after reboot and yet just after charging without even using the Galaxy S2.
I had experiment specially:
after the middle of a night I had swithed off my smartphone, I charged it to 100%, unplugged then I switched it on and leaved immidiately for several hours while I sleeping to late morning.
Then I got the varios battery stats and saved it on the 3 screenshots.
So, everyone can see that the battery lost 39% from full charge without the smartphone being used by the user for several hours.
Moreover, there is a big battery drain just after every charging without the smartphone using and 4th screenshot proofs it too.
And later in response to some nit-pick criticism about this battery consumption test then I had attached yet here a 5th screenshot of the same stand-by battery test on my device swithing on after a full charge but with Samsung's latest official firmware with Android 4.1.2. So, 5 screenshots here give a full picture for compare easy the custom ROMs and Samsung's latest official firmware with Android 4.1.2 in the terms of power consumption.
You can see it clearly that Samsung's latest official healty ROM with Android 4.1.2 consumes not only much less power in stand-by mode but also it consumes power for another purposes at all mostly for cellular network only while the suspicious custom ROMs like LOS 14.1 or RR 5.8.3-5.8.4 consume the enormous big amount of power like crocodiles at stand-by mode for the unwanted excessive file scanning on the user's smartphone!
The next screenshot proofs the bug of inability to install over-the-air updates (after a firmware update file already downloaded the smartphone shows the error message 'Unable to reboot into recovery').
Please keep in mind that none of the developers gets paid for his work. Complaining about bugs not being fixed like this appears disrespectful to me.
Thanks anyway for the thread, might help some people to decide whether to give this ROM a shot or not.
A big thanks to the XDA-Devs for this ROM which I have on my phone since 2 months.
In this time, I haven't been able to "seriously" use my phone. Everything is working except the bugs mentionned above, but the phone has become soooo slow... and some issues with battery life also. Sometimes the device just gets hot in my pocket for no reason, drains half the battery in a few minutes (though I have done the "calibration").
Every action becomes a hassle, but works in the end. It's like using Windows 95 on a 486.
So: nice if you want to try out stuff, but no to recommended for every day use IMHO.
BenjyTec said:
Please keep in mind that none of the developers gets paid for his work. Complaining about bugs not being fixed like this appears disrespectful to me.
Thanks anyway for the thread, might help some people to decide whether to give this ROM a shot or not.
Click to expand...
Click to collapse
Concealing many bugs the ROM developers did lured me (and many others) as free unpaid beta-testers for their unreliable ROM.
Moreover, the bug tracking functions in Lineage OS and Resurrection Remix are not clear and suspicious. Persons who manage it can get easy a various sensitive information about the smartphone users and can use this data by unappropriate way.
If sort the all known bugs then it is possible to reveal easy that the most part of they haves access to user files on the smartphone. These bugs are:
- the unwanted blocking filter at bluetooth,
- excessive user files scanning,
- wrongly provided Android APIs accompanied with attempts to constraint the users to use only the bloatware ersatz file managers implemented in the custom ROMs and an ugly bloatware ersatz camera app.
The bugs mentioned above are well known but did not fixed for a long period of time. And it triggers really an assumption that they can be specially implemented in the custom ROMs for get a full control over the user files without the user knowledge about it. By another words they are not the unfixed bugs but they are the traces of hidden viruses implemented in the custom ROMs.
These viruses can be ordered and paid masking via chains of proxies by an interested party. Ordered viruses and vulnerabilities can be easy implemented villaintly inside some of many allegedly useful patches on every stage in a long way from an initial open publication of Google's Android source code to a last compilation for get a firmware binary file for a target gadget model.
The device Samsung Galaxy S2 was sold over 40 millions (according to Wikipedia). High probably several millions (may even decades of millions) are remain in use today. And they are an attractive target for an interested party.
Moreover, viruses implemented in a firmware almost impossible to determine by an antivirus software.
The party interested in productions of infected custom ROMs can be also discovered easy by researching and proper sorting the several users of the XDA forum, which was indicated in the hostil activity: they was against the public exposures of serious issues in the custom ROMs, they did tried masked to blackwash me and they lure really new people to become unwill victims of the unreliable custom ROMs. The convinced persons are all have same specific feature...
Unfortunately, one of the XDA moderators forbid to explain about it futher.
But what I allowed to tell here is that any custom ROM development can be supported by a party interested in a mass distribution of viruses hidden in firmwares.
Complaining about bugs not being fixed like this appears disrespectful to me.
Click to expand...
Click to collapse
Fully disagreed, as long it's constructive critism it helps other to see what is currently working and what not to easier decide to switch to the ROM or not. The main reason is (I asume) to show the list of bugs, which make sense cause the specific LOS thread not shows the current issue, or you need to go trough each comment separately.
I'm glad we still getting updates and **** but some bugs are years old and just migrated because no one seriously took a closer look at it, so I'm happy that this thread exist to share the experience and to list the known issue.
Here you are, not the developers, not doing the right thing.
You want everything at once, and what you did for it.
https://forum.xda-developers.com/showpost.php?p=73346796&postcount=1814
CHEF-KOCH said:
Fully disagreed, as long it's constructive critism it helps other to see what is currently working and what not to easier decide to switch to the ROM or not. The main reason is (I asume) to show the list of bugs, which make sense cause the specific LOS thread not shows the current issue, or you need to go trough each comment separately.
Click to expand...
Click to collapse
Exactly what I wrote in the second half of my post
I understood the purpose of this thread. What I said just refers to two or three sentences the OP posted. Thank you and goodbye.
JaLoou said:
In this message I only want to publish screenshots, which proof just one of many stupid bugs in Lineage OS 14.1 (Android 7.1.2) for Samsung Galaxy S2 (GT-I9100) smartphone.
As you can see sometimes an user is able to press link 'connect' after entering even 5 symbols of password for WiFi!
But an user is denied of possibility to connect to a WiFi hotspot if he did entered a password of 8 symbol length!
Or 9 symbols and etc, etc!
I did received and installed new updates for Lineage 14.1 every week but NO one known bug was fixed include this one.
Click to expand...
Click to collapse
First of all, Please don't use !!!!!! It looks like you offend people!! Even people who tries to help you!
Secondly, the issue isn't an issue of i9100. It is an issue of the ROM, meaning on all devices. A device maintainer maintains his devices when something changes in the ROM (changes in LineageOS and Android google sources) to keep it up to date.
Thirdly, have you ever connected with your dummy passwords to the Wifi Access Point? Or are you just trying to find "stupid" bugs?
There is a validation mechanism depending on the used security type of the Access Point which is auto detected
WPA2 PSK => minimal password length is 8 WEP
WEP40/104/128 => valid lengths 5, 13, 16 or HEX-values valid lengths 10, 26, 32 and ofcourse 0-9 A-F as allowed characters
If you want to help, try to configure your WIFI access points and verify LineageOS's behavior when configuring with WPA2 PSK/WEP.
Also look in JIRA if the issue is already reported. I saw this issue last week about wifi-password for example:
https://jira.lineageos.org/browse/REGRESSION-912?jql=text ~ "wifi password"
---------- Post added at 06:46 PM ---------- Previous post was at 05:55 PM ----------
Here are my comments on your reported bugs.
1) When you will get an incoming phone call or receive a message then your Galaxy S2 will ring and vibrate but the screen can be fully dark without any notification about the call.
I'm aware of this symptom. The problem is memory and running background processes. Having to much apps installed (Facebook, instagram, snapchat, etc) causes the OS to memory swap when the phone-app must be active. ART uses more memory than Dalvik.
2) Some programs can not work with an external SD card. They can start to work with it after reboot or after few reboots only.
Which programs? The solution is probably using emulated storage.
3) Galaxy S2 with Lineage OS 14.1 becomes hot with a big battery drain for some significant period of time after every reboot. So, rebooting trying to make installed apps work properly you can just quickly fully empty your battery and finish on it.
This is a known issue and can't be resolved. Android 7.1.2 takes more boottime than 4.1.2. The CPU is constantly at 1200Mhz during boot and several minutes after boot because of apps starting up. Our 1600mah battery can't cover this 'boot'-drainage multiple times. It needs 'resting' time to stablelize (like a car battery). Try the app Battery Log to see how the CPU at max speed is pulling the voltage down.
4) The famous FX File Explorer app does not work with the default internal folder 'Documents'.
When you will delete a file on an external SD card this app may not delete it but just rename the file to hidden only (a name started with a dot).
There is another file manager app implemented in the ROM but its interface seems very poor and uncomfortable.
I don't know what the issue with this App. A possible issue could be that we don't use emulated storage
5) Sometimes there is impossible to connect to a password protected WiFi hot-spot due to the link 'CONNECT' in the WiFi menu remains inactive (gray coloured) after password typing 8 symbols or more. This bug appears constantly at a connection with some password protected WiFi hotspots only. And it can become a serious unexpected trouble if you are on the go and in a need to connect to a new hot-spot.
This is by design. Validation depends on used security WEP/WPA2 PSK
6) Camera1 and Camera2 api do not provided correctly. So, camera apps are buggy.
For instance, the famous A Better Camera app by Almalence loses all its settings unexpectedly time to time and becomes as its first launch again. Yet there are another troubles with A Better Camera app.
The implemented in the ROM the Snap camera app is very weak with the ugly uncomfortable interface.
A great of effort has been made to make the legacy Camera api's work in the framework for legacy devices like our i9100 since google dropped its support. It is not perfect and probably never will be. Expect same issues later on in Android O.
7) There is a trouble to enter the year manually in the data settings in a portrait mode due to number of years limitation. This bug does not exist in a landscape mode.
Use small display view. We have a very low-res phone for 2017
8) There is an implemented feature to record a phone call but there is not an option to record all phone calls automatically. Instead only after hand up there inside the dialer settings appears a hidden option which allow manually start to record the current call. So, if you want to record the call then only already during the call you need to go into the dialer menu and activate this hidden option, which is uncomfortable.
Moreover, external apps for phone call recordings does not work properly with this ROM.
Was there ever a automatic recording option in the ROM? We need to investigate some apps why it fails recording.
9) The famous SuperSU root tool does not compatible with Lineage OS 14.1 for Galaxy S2. And apps which require only the SuperSU root can do not work properly.
It is still an issue I think. Please see http://www.lineageosrom.com/2017/01/download-supersuzp-and-su-removalzip.html
10) The small window with the text 'MTP host error' appears in the screen foreground like a ghost.
Our old kernel needs some patches, but it is unclear which patches.
11) The official Lineage OS bug tracker does not accept bug reports by easy way. Instead it requests a registration in advance via a full user name and other personal data, which can be sensitive and used by unappropriate way. It does not allow the registration via the World famous and trusted Google+ or Facebook social networks. Moreover, sometimes the bug tracker does not work and have an announcement about sheduled technical maintenance on a web-hosting side.
12) The ROM developers do not fix even well known simple bugs like described here at the points 5 or 7.
Seems they also do not welcome for public bug reports in proper topics on the XDA forum. It seems like they conceal the existence of many bugs and only lure new people to become victims of their buggy ROM. And I did started this topic for stop it.
I do not know what their purpose is exactly.
But after some time observation it is possible to determine that someone actually regularly 'dilute' proper topics on the XDA forum by short luring messages like 'I had installed it and it is great!' Unfortunately, such kind of simple messages are just alluring fakes high probably.
The another short trap messages are like that 'It runs fast and smooth!'. The deception there is that it attracts only by the Android 7.1.2 menu appearance on the old device for purposes like a brag but really conceal that the whole device with this ROM becomes unreliable for serious using.
I was attracted by topics on the XDA forum about Android 7.1.2 for Samsung Galaxy S2 (model: GT-I9100) and I had lost 1 month period installing latest Lineage OS 14.1 updates and Resurrection Remix 5.8.3 and I decide that the last official Samsung's firmware with Android 4.1.2 is not ideal but much reliable on Galaxy S2 rather than LOS 14.1 or RR 5.8.3.[/QUOTE]
I'm using 2 S2's as daily drive. One for work and one private. I don't have many big apps installed and use my s2 also as car navigation using waze or Google maps. Yes sometimes you have to be patient for a 6 year old device.
Hello.
It is good that the ROM developer had come here in this topic at least.
First of all I do not offend all people. I help Galaxy S2 users to do not fall in the trap, in which I had falled already after being lured by false messages on the XDA forum about allegedly the existence of good ROM Lineage OS with Android 7.1.2 for i9100...
But the ROM is very buggy actually.
For second, all bugs which I described in this topic do not exist in the Samsung's official firmware for Galaxy S2 but only in Lineage and Lineage related ROMs like Resurrection Remix 5.8.3.
JaLoou said:
Hello.
It is good that the ROM developer had come here in this topic at least.
First of all I do not offend all people. I help Galaxy S2 users to do not fall in the trap, in which I had falled already after being lured by false messages on the XDA forum about allegedly the existence of good ROM Lineage OS with Android 7.1.2 for i9100...
But the ROM is very buggy actually.
For second, all bugs which I described in this topic do not exist in the Samsung's official firmware for Galaxy S2 but only in Lineage and Lineage related ROMs like Resurrection Remix 5.8.3.
For instance, with Samsung's official firmware I was able to connect to the exact 2 WiFi hot-spots (as in the screenshots published before) and to many more. But with Lineage 14.1 (and RR 5.8.3) I'm unable to connect to the same 2 WiFi hot-spots. This is enough.
It does not matter which security use this 2 WiFi hot-spots. I was able to connect to them before with the Samsung's official firmware and now I'm unable to connect to them with Lineage.
Before I was able to enter the proper passwords to them. Now I'm unable to do it.
Click to expand...
Click to collapse
In my opinion, you are making a cardinal mistake comparing Stock Android with version 4.1.2 with custom ROM version 7.1.2.
Each of these versions represents a far different operating model in the hardware layer.
But test yourself, if you have enough free time.
ze7zez said:
In my opinion, you are making a cardinal mistake comparing Stock Android with version 4.1.2 with custom ROM version 7.1.2.
Each of these versions represents a far different operating model in the hardware layer.
But test yourself, if you have enough free time.
Click to expand...
Click to collapse
I'm explaining about bugs exactly. They are simple stupid bugs in the Lineage ROM for Galaxy S2, which people face with.
It is also clear that the ROM developers conceal bugs only instead of fixing they.
I had attached the screenshot to this message, which proofs the bug with a manual inability to enter the current year correctly in a date settings at a portrait mode due to an unwanted limitation of number of years available for choose from.
JaLoou said:
Hello.
It is good that the ROM developer had come here in this topic at least.
First of all I do not offend all people. I help Galaxy S2 users to do not fall in the trap, in which I had falled already after being lured by false messages on the XDA forum about allegedly the existence of good ROM Lineage OS with Android 7.1.2 for i9100...
But the ROM is very buggy actually.
For second, all bugs which I described in this topic do not exist in the Samsung's official firmware for Galaxy S2 but only in Lineage and Lineage related ROMs like Resurrection Remix 5.8.3.
For instance, with Samsung's official firmware I was able to connect to the exact 2 WiFi hot-spots (as in the screenshots published before) and to many more. But with Lineage 14.1 (and RR 5.8.3) I'm unable to connect to the same 2 WiFi hot-spots. This is enough.
It does not matter which security use this 2 WiFi hot-spots. I was able to connect to them before with the Samsung's official firmware Android 4.1.2 and now I'm unable to connect to them with Lineage Android 7.1.2.
Before I was able to enter the proper passwords to them. Now I'm unable to do it.
The WiFi hot-spot 'Net 48' haves the password of 10 symbols length. So, it is not WEP secured exactly. But with Lineage Android 7.1.2 I unable to connect to this hot-spot now but before I was able to connect to this hot-spot with the Samsung's official firmware Android 4.1.2 quickly and without any delays.
Click to expand...
Click to collapse
That's important information you describe about the wifi. Please determine which security and password you are using so we can reproduce the issue. The Name of your sid doesn't matter.
rINanDO said:
That's important information you describe about the wifi. Please determine which security and password you are using so we can reproduce the issue. The Name of your sid doesn't matter.
Click to expand...
Click to collapse
Found the bug! It was introduced in linageos since April 27th. https://github.com/LineageOS/androi...mmit/9663c3179fad5e7de7bf4bf31e40649749f33861
The newly introduced faulty input validation is incorrect for WEP. It should not distinguish hex values or plain characters on input. I will create a fix for this.
Some serious camera apps report clearly about the wrong implementation of Camera2 API in Lineage 14.1 for Galaxy S2. I had attached screenshots to this message for proof it.
Hello.
The bug with entering password for connect to some WiFi hot spots, which about I did reported here few times, this bug was fixed or such reporting was my mistake and I really sorry for that. Now I'm able to connect to the 2 WiFi hot-spots, to which I was unable to connect before. Probably, both WiFi hot-spots are WEP secured with passwords of 10 (decimal) symbols length.
Please, excuse me for disturbance about this bug. Probably, I was mistaken due to I did not know about password lenghts limits to 5 and 10 (decimal) symbols in the WEP.
Very sorry.
But another bugs in the ROM continue to exist and they need to be fixed.
JaLoou said:
Hello.
The bug with entering password for connect to some WiFi hot spots, which about I did reported here few times, this bug was fixed or such reporting was my mistake and I really sorry for that. Now I'm able to connect to the 2 WiFi hot-spots, to which I was unable to connect before. Probably, both WiFi hot-spots are WEP secured with passwords of 10 (decimal) symbols length.
Please, excuse me for disturbance about this bug. Probably, I was mistaken due to I did not know about password lenghts limits to 5 and 10 (decimal) symbols in the WEP.
Very sorry.
But another bugs in the ROM continue to exist and they need to be fixed.
Click to expand...
Click to collapse
It is ok. No bad feelings. The very confusing password length has been removed in the official. It was not in Google's android source anyway and the LOS team has merged my commit.
Other good news, I found a workaround to get the camera scene-mode working! It is possibly a bug in the camera firmware which resets the scenemode when the camera starts streaming. It will be in the next official build. As far as I can reproduce, the actual 'night vision'-mode is fireworks.
rINanDO said:
It is ok. No bad feelings. The very confusing password length has been removed in the official. It was not in Google's android source anyway and the LOS team has merged my commit.
Other good news, I found a workaround to get the camera scene-mode working! It is possibly a bug in the camera firmware which resets the scenemode when the camera starts streaming. It will be in the next official build. As far as I can reproduce, the actual 'night vision'-mode is fireworks.
Click to expand...
Click to collapse
Hello.
The semi night vision trick for videorecording by A Better Camera app is to choose manually ISO800 and then choose the scene mode 'Fireworks'.
For more brightness enhancement you can yet choose the 'Cloudly' white balance preset.
I have an old small app, which updates the camera firmware on i9100. I had attached this app to the message. May it will help to someone.
I'm a noob but I think the problem with A Better Camera app is not in the camera hardware but somewhere close to a memory (RAM or flash). And I will try to explain it:
if I launch A Better Camera app for a first time then it shows a simple introductive help on its screen.
If I close the app and run it again then it does not shows the intro help at next launches. It is ok.
But if I press the home button for long time then I get a list of recent apps on the screen and if I scroll it up and clear all the recents list
then only A Better Camera app loses all its settings and becomes like at its first launch (there an introductive help appears again after the app launch).
This bug was not with the Samsung's official firmware Android 4.1.2.
A Better Camera app can improve the camera of our smartphone significantly for video recordings at low light conditions. Moreover, A Better Camera app provides the best DRO-mode among other camera apps, IMHO. It is like a second life for the old camera of our smartphone. So, please pay attention to fix the bug with A Better Camera app.
Hey!
Long time lurker, first post
I have the Motorola Nexus 6, Chainfire Rooted, Android 6
I did initially upgrade to Android 7 but it was not stable for what I currently doing (more below)
I have a app I am running that is linked to Google (Google Play specifically)
I have ~15 different Google IDs, and I have created 15 user profiles on my phone (had to do some root editing to enable that)
open build.prop
Code:
# Multi Users
fw.max_users=15
fw.show_multiuserui=1
I can change users and the app launches and runs as desired
This has been working great for the last year +/-, the only caveat is that it uses a crazy amount of space (all of the google apps etc.)
So I am wondering if their is a easier way to accomplish this that does not create a full phone profile for each app (similar to the Samsung Secure file app? I have been told this works, but have not tested) or if their is a way to slim down the additional profiles and remove the apps that are not needed (without messing up the stability of the main profile or the alternate profiles)
Any suggestions or ideas are appreciated - thanks! :highfive:
Some more information on the stability issues I encountered with Android 7 (initial package, did not test beyond that)
- Notification bar did not support more than ~8 users
- Users beyond 8 were unresponsive and would not load / switch
I think the Samsung App I referenced is called Secure Folder
androidauthority.com/samsung-secure-folder-google-play-store-779156/
I am not sure if their is a similar app in function for non-Samsung devices
eris667 said:
Some more information on the stability issues I encountered with Android 7 (initial package, did not test beyond that)
- Notification bar did not support more than ~8 users
- Users beyond 8 were unresponsive and would not load / switch
I think the Samsung App I referenced is called Secure Folder
androidauthority.com/samsung-secure-folder-google-play-store-779156/
I am not sure if their is a similar app in function for non-Samsung devices
Click to expand...
Click to collapse
Android devices are not made to handle that many profiles. It was made for a max of 5. Anything more and you will find instability.
There are tons of app lockers so to speak.
I have tried a few of the clone / parallel type apps in the PlayStore - but not much success
- Most only support 2 profiles
- In testing it doesn't differentiate the Google Profile (i.e. the clone loads the default Google Profile, vs the alternate)
If anyone has a recommendation I will gladly experiment
I am probably on the extreme edge here with 13 active profiles (most people are probably closer to 1-3 I would guess)
Ideally I would love to find a solution that:
- reduces the size of the existing profiles (staying on Android 6)
- an alternate way to manage the Google IDs (migrating to Android 7)
My current setup (while working) prevents future device / software upgrades, and currently I am "out of space"
eris667 said:
I have tried a few of the clone / parallel type apps in the PlayStore - but not much success
- Most only support 2 profiles
- In testing it doesn't differentiate the Google Profile (i.e. the clone loads the default Google Profile, vs the alternate)
If anyone has a recommendation I will gladly experiment
I am probably on the extreme edge here with 13 active profiles (most people are probably closer to 1-3 I would guess)
Ideally I would love to find a solution that:
- reduces the size of the existing profiles (staying on Android 6)
- an alternate way to manage the Google IDs (migrating to Android 7)
My current setup (while working) prevents future device / software upgrades, and currently I am "out of space"
Click to expand...
Click to collapse
Nothing you can do. It is the way multi users setup on android.
Not sure why you would need so many profiles but my only suggestion is get a device with more storage.
I am going to try "Parallel Space" and "App Cloner"
it looks like Parallel Space can manage a separate Google ID maybe I can clone that x15 (lol)
eris667 said:
I am going to try "Parallel Space" and "App Cloner"
it looks like Parallel Space can manage a separate Google ID maybe I can clone that x15 (lol)
Click to expand...
Click to collapse
You will still run into the memory issue. There was an OS that focused on something like that but it went belly up as no one really used it and it was plagued by issues on both rom and Google side.
Good luck.
Hmmmmm checking Internal storage differences (i.e. is this any better then the profiles I currently have)
I currently have a 32Gb device, at 29.58Gb Used (phone is calculating storage locations)
Will add more detail and do some additional testing,
I created 2 clones, to establish approximate usage size
I have not had any stability issues with either method so far
eris667 said:
Hmmmmm checking Internal storage differences (i.e. is this any better then the profiles I currently have)
I currently have a 32Gb device, at 29.58Gb Used (phone is calculating storage locations)
Will add more detail and do some additional testing,
I created 2 clones, to establish approximate usage size
I have not had any stability issues with either method so far
Click to expand...
Click to collapse
Be careful. Android has issues when the internal storage starts getting more then 50% full. It will slow down, lag out and have stability issues. Android developers advised never to get more then 35% of device memory full.
Still playing around with it
initial comparison User Profile ~517mb, Parallel Space ~84mb
I have 12 profiles + my main profile (other 3 profiles were not created)
6204mb vs 1008mb = 5196mb saved space
My 32Gb Nexus has 25.98Gb max, to get into the 35% range I should have 9.09 Gb Free?
I need to do some additional testing - and maybe a fresh wipe to Android 7
arghhhhh......
I found (3) old FlashFire backups, ~8gb free now, an additional ~5gb free when I remove the profiles
all said I will probably do a Titanium Backup on a few things a perform a full reset to clean up some trash I have accumulated
Android 6 runs great for me (on this device), still debating if I should go to Android 7 in the near future
Appreciate all of the comments and ideas!