App not working on Samsung - Android Q&A, Help & Troubleshooting

Hi,
I've written an app which I tested on my Nexus 7 (2013,stock), Nexus 5 (stock), OnePlus One (stock cos12.1)and the emulator without any problems. It also works on a Xperia Z3.
However, two friends of mine are using a Samsung device and both tell me that the app is immediately force closing.
Since I don't have any Samsung device for testing, I'm currently out of ideas on how I can check what's causing those force closings.
The app is compiled for a minimum sdk of 19 with the Android Studio and I'm using one main activity with different fragments.
I hope someone is able to give me any hint about what may cause the force closings (I can provide more information if needed)
thanks in advance ,
KBanause

Related

[CLOSED] Export Q Function to Any Android Device

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

Issues with Cloning Android to Identical Devices

Hey guys,
I have an issue I'm facing at the moment. I have purchased 3 Samsung Galaxy Nexus devices for my family, and one for myself. I wanted to setup all our devices for them and pre-install essential apps for them, and lay it out in a way which makes each device identical so that my family (which is new to Android) can all get the same easy experience from their devices, rather than everyone getting a different LG/Samsung/HTC device and having to deal with differences in skins every time someone phones me with a question about their device.
Here is what I have done:
1. Unlocked bootloader, root, installed CM10.1.2 + gapps onto my own personal device. Clean install, wiped everything.
2. Setup android with a temporary Gmail account, installed about 20 apps, setup the homescreen, changed a few settings for simplicity, change wallpapers, etc.
3. Once I was satisfied, I removed the google account, rebooted to recovery (CWM 6.0.3.2) and made a Nandroid backup which was later copied to my home server.
4. Unlocked Bootloader, rooted and installed CM10.1.2 + gapps on all the other devices, booted the device then transferred the Nandroid backup from my home server to each of these other three devices. Restore the backup, reboot, all seems fine so I setup new individual google accounts, and away I went. Everything works fine, at least so it seems.
Now the issue is that I'm having came a day or two after I got everything setup on each device. At the moment I'm having serious issues with the Google Play Store and Push Notifications. Almost all devices intermittently have issues with this. The play store issue I'm getting is [RPC:S-5:AEC-0], and prevents me from downloading or updating apps. Push notifications is not working either. For example, Google hangouts notifications don't notify me of messages on devices intermittently unless I manually check the app. Same goes with facebook and snapchat notifications. Very annoying. Tried all sorts of fixes such as removing the Google account, rebooting and adding it again, but no luck.
It seems like there is some sort of conflict with each device, but I don't understand why. I changed the Android ID on each device hoping that would help, but still no luck. If anyone could offer an explanation why this issue is occurring I would love to hear it!
Cheers.
Edit: Tried making a titanium backup of one device and moved it to a rooted Galaxy S2 running CM10.1 nightlies, and no such issue. Also, updated one nexus device to the latest nightly, still no fix. Hopefully this information will help someone be able to point out the problem somewhere.
Okay, so I've been playing with a couple of these devices today, and by removing a google account, rebooting the device and then adding the google account again, it makes the play store work on that device, but breaks functionality on the other devices. Would someone with a low-level understanding of Android care to explain why this is?
I'm going to try doing a factory reset on one of these Nexus devices and restore a Titanium Backup and see if that helps, unless anyone has any suggestions?
The different accounts are linked to the play store separately, you are best off to just downloaded each app and set up each phone with its own gmail account. I know it sounds time consuming but it would take less time than you've been spending already.
As you learn more about android there are lots of ways of doing almost exactly what you want here, but learning right now will take less time and effort than downloading 20 apps to three different phones
Sent from my Nexus 4 using xda premium
demkantor said:
The different accounts are linked to the play store separately, you are best off to just downloaded each app and set up each phone with its own gmail account. I know it sounds time consuming but it would take less time than you've been spending already.
As you learn more about android there are lots of ways of doing almost exactly what you want here, but learning right now will take less time and effort than downloading 20 apps to three different phones
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks for the advice, but at the same time I'm using my family as guinea pigs to test whether it's possible to clone devices like this, as I'm in charge of the IT department at our organisation and I suggested it may be possible to deploy a large number of identical rooted android devices through the organisation (probably around 30-40 devices to start with). At this stage though, there seems to be some issues with doing this. Would you be able to point me in the direction of how I could clone Android to several devices, or at least deploy an identical setup to several devices? Perhaps I'll need to customize my own ROM based on Cyanogenmod? Chances are I'll be having to support different hardware as well. This may include the Galaxy Nexus, Nexus 4, Xperia Z and the LG Optimus 4X HD.
Well the absolute best way, in my opinion, would be to create your own ROM.
And by this I don't mean you need to learn how to port or build from source (at least not at first) just some simple zipkanging will do for something like this
Take the ROM.zip, open it, take out apps and such you don't want, add it the ones you do, rezip and sign
Now flash this to each phone and they will all have the same ROM and can just add their Google account.
Now if you want to have certain settings or the system ui look different than this you will need to learn how to decompile some apks and edit xml files, but start slow, do what is easy and what you can't figure out let me know and I'll try to help
Sent from my Nexus 4 using xda premium
demkantor said:
Well the absolute best way, in my opinion, would be to create your own ROM.
And by this I don't mean you need to learn how to port or build from source (at least not at first) just some simple zipkanging will do for something like this
Take the ROM.zip, open it, take out apps and such you don't want, add it the ones you do, rezip and sign
Now flash this to each phone and they will all have the same ROM and can just add their Google account.
Now if you want to have certain settings or the system ui look different than this you will need to learn how to decompile some apks and edit xml files, but start slow, do what is easy and what you can't figure out let me know and I'll try to help
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thought this might be the case.
Is it relatively simple to copy the changes I make to one ROM (eg for a Galaxy Nexus) for another ROM (eg. for a Nexus 4)? Is there some sort of Android virtual machine I can test or build this in?
Not simple at all, I was referring to multiple phones of the same type. Its easy to create identical ROMs to be flashed between 30 n4s or 30 genexs, but to create the same identical ROM to work in both types of phones would require source builds matched to each device tree
Which if you know little about android, java, c++ etc, then you have a real long journey ahead of you.
If you want to have an identical ROM (based off one already in existence) be flashed to 30 identical phones this is relatively easy depending on what all you want
Like I said, start small, learn what's easily obtained, then try for something bigger
Sent from my Nexus 4 using xda premium
demkantor said:
Not simple at all, I was referring to multiple phones of the same type. Its easy to create identical ROMs to be flashed between 30 n4s or 30 genexs, but to create the same identical ROM to work in both types of phones would require source builds matched to each device tree
Which if you know little about android, java, c++ etc, then you have a real long journey ahead of you.
If you want to have an identical ROM (based off one already in existence) be flashed to 30 identical phones this is relatively easy depending on what all you want
Like I said, start small, learn what's easily obtained, then try for something bigger
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
The idea was to use CM10.1 as a base and simply add in some apps + app data and change some settings. Setting up the homescreen in a certain way would be part of that. The Galaxy Nexus, Nexus 4, Xperia Z, and LG Optimus 4X HD all support CM10.1 stable.
If I setup a device the way I want it, would it be possible to extract some of these custom configurations from the live device to a flashable ROM?
Just because there is the same ROM for each phone doesn't mean they are exact, but in your case probably good enough. But the change you would make would be to each individual ROM (on computer not on phone) and then flashed these new versions of your ROM to each phone.
You can not make changes to your phone when running the os and extract these changes and flash them to another phone easily, near impossible to do it to a different phone make
Like I have been saying, take a ROM, open it up on PC, change what you need, flash to phone. The simpler the changes the easier it is to do. This will have to be done on a case by case basis if you are doing it to multiple types of phones
Now if you give me a list of what you want to change exactly there may be a few things you can do on your phone but in reality this is the harder way, doing all the work on PC is the easier way
Sent from my Nexus 4 using xda premium
Yes, I understand that. I think what I'll have to do is record the changes I make to one ROM in a changelog of some sort, and then simply recreate these changes manually to other ROMs. Through the PC of course.
demkantor said:
Just because there is the same ROM for each phone doesn't mean they are exact, but in your case probably good enough. But the change you would make would be to each individual ROM (on computer not on phone) and then flashed these new versions of your ROM to each phone.
You can not make changes to your phone when running the os and extract these changes and flash them to another phone easily, near impossible to do it to a different phone make
Like I have been saying, take a ROM, open it up on PC, change what you need, flash to phone. The simpler the changes the easier it is to do. This will have to be done on a case by case basis if you are doing it to multiple types of phones
Now if you give me a list of what you want to change exactly there may be a few things you can do on your phone but in reality this is the harder way, doing all the work on PC is the easier way
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well for example, here are the outdated and rough changes I need to make to the settings (this is just a note of the changes in the settingsof the ROM to make it run way I wanted on the device). Attached it as a PDF as I couldn't copy the formatting.
Most of that should be doable by decompiling systemui.apk and settings.apk, somewhat time consuming and depending on your experience a steep learning curve, but should be able to do it
Sent from my Nexus 4 using xda premium

Beta Testers Needed: Windows Phone XBMC Remote Client

I have been developing a remote control client for Windows Phone for a while now. I am now opening up beta program so that it can be tested heavily. It'd be great to have feedback from the XDA community. Here are a few details and some FAQs about beta testing. If you're absolutely sure that you want to be a tester, jump directly to the bottom of this post.
What should I expect from this beta?
Well, you should expect what you generally expect from beta software. Cutting edge, burning hot software with new features and a few bugs here and there. Specifically, you might run into some memory management issues, but they shouldn't stop you from trying it out.
What do I need to be a beta tester?
Patience and tolerance: You should understand that the app might behave unexpectedly sometimes.
A Windows Phone 8 device: That's where you test the app.
XBMC: You need to have XBMC running somewhere on your network. That's what you're trying to control using this app.
A Microsoft account: You will need to have a Microsoft Id associated with your phone to be a beta tester.
How do I become a beta tester?
Just give me your Microsoft Id here. I won't sell it to anyone. I won't spam either.
How do I report issues?
You may create an issue on Github here.
You may post it on this thread.
You may contact me over the twitter at @akshay4000.
At times Google+ can be a good choice.
Can I contribute to the code?
I'm glad you asked. Here is the Github repo: https://github.com/akshay2000/XBMCRemoteWP. Fork it, fix something, make some commits and make a pull request. I'll be glad to take contributions. Just make sure that the code is pretty.
Again, here is the link if you want to be a beta tester: http://bit.ly/1iW5c3z
Thank you all for the support.
Well, your app crashes and brings me back to the main screen, after adding the IP of my xbmc.
Samsung Ativ S
WP8.1 preview
Sent from my Samsung Windows Phone 8
assyriska said:
Well, your app crashes and brings me back to the main screen, after adding the IP of my xbmc.
Samsung Ativ S
WP8.1 preview
Sent from my Samsung Windows Phone 8
Click to expand...
Click to collapse
Just pushed an update. Check back in a few hours. That should fix it. Oddly enough, same app worked fine when deployed from my local machine, but crashed when downloaded from marketplace.
So, if this new version crashes, we know that store is messing with it.
Updated your app but it still crashes.
Sent from my Samsung Windows Phone 8
assyriska said:
Updated your app but it still crashes.
Sent from my Samsung Windows Phone 8
Click to expand...
Click to collapse
Sorry about that! At this point, you're probably losing the patience, but I've pushed another update. And I'm certain that this will solve it. Please, give it a try. Version should be 1.0.0.2 - the latest one.
Edit: Just checked. The latest version goes without any crash. Can you verify that?
Without a crash but I am not able to connect the app with my xbmc (raspberry pi). With other app I have no problem to connect.
Sent from my Samsung Windows Phone 8
assyriska said:
Without a crash but I am not able to connect the app with my xbmc (raspberry pi). With other app I have no problem to connect.
Sent from my Samsung Windows Phone 8
Click to expand...
Click to collapse
If you have password set up on XBMC, the app might not connect. Update is being pushed out which will fix this. Update the app in a few hours. Sorry for the trouble. Till then you can test the app by disabling the passwords.

[Q] Screencasting apps

I am looking for screencasting apps that don't require root. Found the free Recordable and made a quick recording of my N9 homescreen http://youtu.be/0yz4-3nMMW8 However, the setup of Recordable is rather tedius, so can anyone give me a tip for other screencasting apps that work on N9? Thanks.
Screen Recording apps
Found Mobizen - No Root & Free - no activation process needed for screen recording http://youtu.be/eHCX-YKBujc and http://goo.gl/cT7AWW
I would not recommend any application that requires an activation via a PC. Most of them work similar as the Android Screenshot Library and basically just regularly take screenshots. This was needed to programmatically get access to the screen content of unrooted devices running Android versions prior to Lollipop. Luckily, Lollipop finally introduced an API that allows apps to ask the user's permission for recording the screen. As this is an official API, it works much faster than previous solutions, and is far easier to set up.
Thanks FD_ Are you saying that all the other apps, that so far only worked with Root, from now on will work with Lollipop without Root? (assume some slight modification of the apps might be necessary)
OK, my Nexus 9 and Nexus 7 (2012), both have Lollipop and work with Mobizen. So I tried Wifie's Galaxy PAD S 10.5 running KitKat 4.4.2, and Mobizen works, without having to be activated after each reboot of the tablet. (there was an initial involvement of the PC in the set up the account, though)
Not sure exactly what your requirements are but this app works really well on my N9
.https://play.google.com/store/apps/details?id=com.hecorat.screenrecorder.free
Yes, got the tip about AZ Screen Recorder last night, installed it and it seems at first glance to be as good as Mobizen. Will check it out a bit more. Thanks georgios73
Quick look at AZ Screen Recorder http://youtu.be/JIVONhhd55w and companion http://goo.gl/qn8vWT Free, No Root and No Activation Procedure!
Seems that with Lollipop there are plenty of new apps coming that do not require root, such as Mirror Beta https://play.google.com/store/apps/details?id=com.koushikdutta.mirror and Lollipop Screen Recorder https://play.google.com/store/apps/details?id=com.rivulus.screenrecording
Made a quick video about WhatsApp on PC using Mirror Beta http://youtu.be/7saIcH0GBUI
I'm always using the SCR (on <5.0 , root required) and SCR 5+ (>5.0 , no root required) from iwobanas
Thanks, did not know that SCR no longer requires root for Lollipop. Guess there will be still more...
Sent from my Nexus 9 using Tapatalk
georgios73 said:
Not sure exactly what your requirements are but this app works really well on my N9
.https://play.google.com/store/apps/details?id=com.hecorat.screenrecorder.free
Click to expand...
Click to collapse
I use that. Pretty good software. Works really well for me.

[Q] Things missing from Android

I love android. I am a Nexus 6 & 9 user and in the past I was a Galaxy Note user. No matter how great and better (to my opinion) android is in comparison with other mobile OS, there are some things that are missing and seem so crazy to be missing.
Of course me and you all (maybe the 5% of all android users ??) we can play with custom roms, mods and etc, but all the other users, especially the Nexus line users, find these things missing.
1) there is no stock file browser
2) there is no battery percentage on the home screen, without the need to swipe down
3) there is no Wi-Fi direct !!!! There is an option in Wi-Fi advanced options, but whenever I tried it with my Nexus 9 & 6, there was no success
4) there is no clear all in the multitasking menu, and before 5.X.X, with a reboot of the device the background process would clear, now they won't close until you close them. Imagine having to swipe 30-40 times to clear everything.
5) In the era of phablets, there is no split-screen!! 6 inch Nexus 6, and 9 inch Nexus 9 have no split screen to take advantage of these features.
Is Google ever planning to implement these features? Especially 1-4 seem to be EXTREMELY simple in an implementation level.
**As I already mentioned, I can find solutions for most of these problems (if not all), but I am wondering if Google is ever gonna bring these things by default to all Nexus users, so non experienced users will enjoy them as well**
The Nexus line was meant for developers from day one. Not the common users. Google isn't changing that policy.
It's why Samsung is the largest brand.Every single thing you mentioned comes as a default feature on their high-end devices. In fact, multiwindow was their invention. The NotePro 12.2" even supports 4 windows simultaneously.
And you've not seen Mutlitasking until you've tried Penwindow. (depending on which Note you had you may or may not already have.)
Sent From My Samsung Galaxy Note 3 N9005 Using Tapatalk
ShadowLea said:
The Nexus line was meant for developers from day one. Not the common users. Google isn't changing that policy.
It's why Samsung is the largest brand.Every single thing you mentioned comes as a default feature on their high-end devices. In fact, multiwindow was their invention. The NotePro 12.2" even supports 4 windows simultaneously.
And you've not seen Mutlitasking until you've tried Penwindow. (depending on which Note you had you may or may not already have.)
Sent From My Samsung Galaxy Note 3 N9005 Using Tapatalk
Click to expand...
Click to collapse
I tried out Note 1,2 & 3, and yes you are right. All those things are already in Samsung devices. Even more, they have something even stronger than WiFi direct, that uses mobile data if necessary to increase the speed (if needed). I agree that nexus is meant to be used by developers, but Google changed that character from the Nexus 7 2012 and Nexus 4, by advertising and promoting it through low prices in general public. I remember that I had a hard time to find Galaxy Nexus 32GB in my country and I went to Galaxy Note N7000, but after the 3d Nexus phone (Galaxy Nexus), nexus phones (and tablets) went balistic on line with many many people wanting to buy them.
Btw, I did not know that on pro 12.2 you can have 4 windows! wow! that is true multitasking indeed !
Thank you for your answer mate
petkyrk said:
I love android. I am a Nexus 6 & 9 user and in the past I was a Galaxy Note user. No matter how great and better (to my opinion) android is in comparison with other mobile OS, there are some things that are missing and seem so crazy to be missing.
Of course me and you all (maybe the 5% of all android users ??) we can play with custom roms, mods and etc, but all the other users, especially the Nexus line users, find these things missing.
1) there is no stock file browser
2) there is no battery percentage on the home screen, without the need to swipe down
3) there is no Wi-Fi direct !!!! There is an option in Wi-Fi advanced options, but whenever I tried it with my Nexus 9 & 6, there was no success
4) there is no clear all in the multitasking menu, and before 5.X.X, with a reboot of the device the background process would clear, now they won't close until you close them. Imagine having to swipe 30-40 times to clear everything.
5) In the era of phablets, there is no split-screen!! 6 inch Nexus 6, and 9 inch Nexus 9 have no split screen to take advantage of these features.
Is Google ever planning to implement these features? Especially 1-4 seem to be EXTREMELY simple in an implementation level.
**As I already mentioned, I can find solutions for most of these problems (if not all), but I am wondering if Google is ever gonna bring these things by default to all Nexus users, so non experienced users will enjoy them as well**
Click to expand...
Click to collapse
Just to comment on multitasking/recent apps, there isn't a need to clear all as Android has significantly improved how this is handled. Only a small part of the tabs you see in lollipop recent are actually running. Android will automatically close apps to keep the appropriate amount of free RAM available. By "closing all", you are actually causing a longer start time when you reopen the app and causing apps that auto run to restart. Thus causing more battery drain and system resource consumption.
Helpful articles:
http://www.androidtipsandhacks.com/...ndroid-and-why-you-shouldnt-most-of-the-time/
http://www.makeuseof.com/tag/ram-boosters-task-killers-bad-android/
Evolution_Freak said:
Just to comment on multitasking/recent apps, there isn't a need to clear all as Android has significantly improved how this is handled. Only a small part of the tabs you see in lollipop recent are actually running. Android will automatically close apps to keep the appropriate amount of free RAM available. By "closing all", you are actually causing a longer start time when you reopen the app and causing apps that auto run to restart. Thus causing more battery drain and system resource consumption.
Helpful articles:
http://www.androidtipsandhacks.com/...ndroid-and-why-you-shouldnt-most-of-the-time/
http://www.makeuseof.com/tag/ram-boosters-task-killers-bad-android/
Click to expand...
Click to collapse
Thanks for that, how stupid of me, all these years I was fanatic about closing all apps as soon as I was done with an app. But in the long run yes you are right, it does actually consume more resources this way.

Categories

Resources