Ok now I'm a "noob". I know nothing of coding or building but I do know basics of Android flashing and modifying from the work of amazing developers here.
Problem is I can't understand certain things about why Google makes such decisions with their stock os and being a noob with what's approaching a year with android (first device was a HTC one x but currently own a s3) I've usually avoided making a post like this to avoid the flame from users who don't even know the answers themselves but just love to yell noob and go do some searching But over these 8 months i have but to no avail. So here goes
1. Why doesn't Google support Facebook contact sync even though HTC and Samsung (may be others buy I only owned these 2) and on their jellybean updates as well. I read somewhere hat it has to do with api but if so why does everyone (I know) use it but them?
2. Why doesn't the stock gallery app support gif images?
3. Doesn't want cyanogenmod using multi window but Samsung can with no public threats made?
4. What do they have against large storage volumes(32-64gb/expandable memory)
5. Why do they not do a pc host update. I mean like how apple has updates through iTunes. I don't mind questioning 3rd party manufacturers like Samsung or HTC but I mean come on why do they NEED to wait for carriers to push an update to phones they provided the code for (I use that loosely)
Those are the five questions that just tug at me when using an aokp based rom as I love the speed but hate the absence of functionality and other questions that I'm curious about.
Thanks in advance and please don't flame me
Sent from my GT-I9300 using xda app-developers app
large storage devices
"It's a conspiracy, man!"
Read somewhere that Google wants to know everything about you. So, having no expandable storage on their devices will force you to find "cloud" based storage, preferably with any of Google's services.
I don't care, as long as it is not Apple.
Cuz HTC and Samsung have different GUI.. Samsung has Touchwiz while Htc has Sense..
Sent from my GT-I9300 using xda premium
Concerning question 4 it's not a question of size... as you know..
It's a question of filesystem format. Exfat used for 64gb cards is Windows proprietary, so only available with Sammy Rom, as they bought the right to use the license. As long as no(open) source is available, official cm and others won't provide compatibility.
And yes, Google phones, nexus ones are sold without sdcard, to push cloud use up. And Google develops mainly for... Google.
CHEVYbarracuda1 said:
Cuz HTC and Samsung have different GUI.. Samsung has Touchwiz while Htc has Sense..
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I'm guessing you don't understand what I asked
Related
from http://galaxys2.samsungmobile.com/html/feature.html it looks like it won't be...
On Device Encryption
Play it safe with a security solution that enables the protection of mobile data without the need to sacrifice speed and functionality. The Samsung GALAXY S II is the first Android smartphone to adopt powerful encrypted hardware, minimizing the use of security software and applying encryption technology to the hardware itself, greatly accelerating security protection and achieving superior performance
Click to expand...
Click to collapse
this looks like a bit of a deal-breaker given samsungs poor update schedule.
I really hope they're not talking about an encrypted bootloader, although I seriously doubt they would state that as a feature.
sold my n8 1 month back and waiting for s2 with nokia 6300 and 3120 classic in my hand. so its better to wait buddy
MarkusPO said:
from http://galaxys2.samsungmobile.com/html/feature.html it looks like it won't be...
this looks like a bit of a deal-breaker given samsungs poor update schedule.
Click to expand...
Click to collapse
This is about the functionality targeted at improving security for integrated business applications.
However, The issue as I see it is that if they do not also lock bootloader and ability to install custom root-level stuff out using hardware encryption, then any hardware encryption of user-space stuff is pointless. I predict they either lock it, or if they're clever, to diffuse hackers and modders interest in cracking the encryption they might allow you to unlock it at cost of removing the ability to integrate with business apps. (or other way around or poss with a sandbox of some kind)
crypticc said:
I predict they either lock it, or if they're clever, to diffuse hackers and modders interest in cracking the encryption they might allow you to unlock it at cost of removing the ability to integrate with business apps
Click to expand...
Click to collapse
of those two options, which one offers the fastest turnaround to market, so therefore cheaper to produce and faster to make money from? i wouldn't doubt samsung to completely lock this.
which imo goes against androids openness. you may as well have a custom crappy samsung operating system on it that's semi-compatible with android.
i thought google wanted to clamp down on skins completely? or is that just for tablets?
MarkusPO said:
of those two options, which one offers the fastest turnaround to market, so therefore cheaper to produce and faster to make money from? i wouldn't doubt samsung to completely lock this.
which imo goes against androids openness. you may as well have a custom crappy samsung operating system on it that's semi-compatible with android.
i thought google wanted to clamp down on skins completely? or is that just for tablets?
Click to expand...
Click to collapse
It's true that it's probably cheaper, but at the same time not as many will buy it, so in the end it might be a loss to them.
Of course it will be flashable...theres nothing we cant set free on xda... ..really...dont worry about it.
Sent from my GT-I9000 using XDA Premium App
rixsta said:
Of course it will be flashable...theres nothing we cant set free on xda... ..really...dont worry about it.
Click to expand...
Click to collapse
I'm assuming you don't own a Milestone or a Droid X
Guys could it be possible that s2 might have nand lock plus encrypted bootloader? Any ideas?
If it is the case then it will spell lotz of trouble for us as then even rooting will be a trouble....
And if by encrypted hardware.....does that mean that it will be difficult to find suitable drivers which will make cheating the bootloader difficult and also voids the kexec method employed in bypassing the x10 bootloader?
rixsta said:
Of course it will be flashable...theres nothing we cant set free on xda... ..really...dont worry about it.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Or an atrix.......
sent from my nook color
I gave a look at xda threads of those two phones. Everything you can dream of is availlable (last RC4 of cyanogenmod 7, among a lot of other roms).
For what I understood, the only real issue is modified kernels?
If this is the kind of limitation we are talking about, that's fine with me.
qsdf55 said:
I gave a look at xda threads of those two phones. Everything you can dream of is availlable (last RC4 of cyanogenmod 7, among a lot of other roms).
For what I understood, the only real issue is modified kernels?
If this is the kind of limitation we are talking about, that's fine with me.
Click to expand...
Click to collapse
Without kernel voodoo sound, bln, etc are not possible.
qsdf55 said:
I gave a look at xda threads of those two phones. Everything you can dream of is availlable (last RC4 of cyanogenmod 7, among a lot of other roms).
For what I understood, the only real issue is modified kernels?
If this is the kind of limitation we are talking about, that's fine with me.
Click to expand...
Click to collapse
No custom kernels is a HUGE problem. Kernels are written for specific android versions. You can't run Android 2.3 (or even 2.2) on a 2.1 kernel (we had this problem with the motorola milestone). This means you have to wait till the manufacturer starts developing or else you are STUCK. So really, it is a huge limitation. Also, if the manufacturer doesn't support things like a swap partition, you will never be able to get it.
Hi there,
I am looking to buy a new (mid-to-high-end) android device, which will be my primary mobile platform for the next two years.
I expect that there would be several Android version updates during this time-frame, and I definitely want to get them all, as soon as possible.
Furthermore, I would like to compile the OS (including the kernel and the drivers) for the device myself.
My question is, what do you think, which vendor and model should I choose for this?
Which vendor has the best track record regarding publishing the kernel sources, and all the software components required to run the software properly?
I am considering Galaxy Nexus, which is guaranteed to run AOSP, since it comes directly from Google. However,
a) One can not compile all the stuff needed for GNex from source; some binary drivers are still needed. (They are provided by Google in binary form.(
b) The device is kind of dated now; I would prefer something a bit younger. (Maybe this is not the best time to get a new device, since we are in the middle of a Nexus release cycle?) Judging from the hardware, I like the more modern Sony Xperia S or HTC One S better, but I am afraid that their software situation will not be able to keep up with the Nexus line.
What do you think?
Should I stick to Nexus, or are there better alternatives, from the software availability/freedom perspective?
Thank you for your help:
Csillag
You can try what I did.... Search through.all the forums and sub forums to see which was the busiest and go with that model. : D
BROKKANIC said:
You can try what I did.... Search through.all the forums and sub forums to see which was the busiest and go with that model. : D
Click to expand...
Click to collapse
May I ask when did you run this search, and what was the result?
Sent from my ZTE-BLADE using XDA
csillag said:
May I ask when did you run this search, and what was the result?
Sent from my ZTE-BLADE using XDA
Click to expand...
Click to collapse
Your best bet would be to wait for the next nexus. Other then the nexus other devices are not promised updates early if at all and most of the software is closed source. The nexus is the only one built for AOSP.
Sent from my Inspire 4G using Tapatalk 2
I've seen a little bit of talk about this now that we have some AOSP ROMs and personally would like to see this happen but I know that if I just go make a request to someone like the Cyanogenmod team I'll probably not get a response or just be told they're considering it and that's it(I could be wrong). So I'm making this thread to find out just how many people are interested in this and figure out how we should get a hold of whoever can make it happen.
I don't want to get a bunch of people to just start mass email/post/calling anyone into submission. These dev's are already doing a lot of great things for us and I don't want to ruin that. I would really rather give Google an idea of how many people want this feature or already have it through one of Samsung's ROMs and would like to keep it with AOSP so that maybe they won't give the AOSP dev's such a hard time.
So go ahead and chime in if you want multi-window for AOSP and if you know who we should get a hold of or have a good idea of how we should go about asking or if you're a dev who's tired of people always asking for features and just wants me to shut up.
In case you haven't seen cornerstone it's similar to Samsungs multi-window. http://www.onskreen.com/cornerstone/
In case you haven’t heard the story between Google and Cyanogen about cornerstone yet. http://www.geek.com/articles/mobile/samsung-adds-multi-window-despite-threat-from-google-2012109/
and https://plus.google.com/100275307499530023476/posts/ViCME1bb8F6
I want
Sent from my SCH-I605 using xda app-developers app
yes please!
Sent from my Sprint Galaxy SIII on AOKP
I would love it, the best ROMs are gonna be stock, but the multi window feature in touchwiz is keeping me from stock, so this would be perfect
Sent from my SCH-I605 using xda app-developers app
+1
Sent from my unlocked & underclocked Galaxy Note 2
No thanks. CM isn't going to risk it. Google allows CM to use their proprietary apps and gives CM users access to the market and other Google services. If multi-window modes are going to risk that relationship then I don't want it.
th0r615 said:
No thanks. CM isn't going to risk it. Google allows CM to use their proprietary apps and gives CM users access to the market and other Google services. If multi-window modes are going to risk that relationship then I don't want it.
Click to expand...
Click to collapse
I understand that and I know that's why CM didn't pursue it before but I think that now that Samsung has gone ahead and made multi-window available it gives us a good precedence, especially if they start using it on more phones than the note 2, like the S3. I think the big thing would be making it only work for apps that specifically state that they work with cornerstone the same way that Samsung does. I know it's a small amount of apps right now but once it hits a certain point most developers would hopefully make it standard when they make their apps and the ones that won't play nice with odd screen sizes can be left to run full screen. I'm just hoping that if they implement it they can use the same flag in apps that Samsung does so that so that app devs have a little more of a reason to make their apps use it for multi-window on AOSP and sammy ROMs.
I haven't found an app that doesn't work. Haven't really tried with games but did check a few with no problems. It works Google should roll it out.
Sent from my SCH-I605 using Tapatalk 2
I think in this case Google is too worried about catering to the lowest denominator - ie. the people with smaller less known android phones rather than beasts like the S3/Nexus 4/DNA/Note 2 and their misguided complaints that their new device can't run the core OS properly.
I asked Entropy about it in IRC a couple nights ago but he said it really makes no difference even with Samsung implementing Multi window. I looked into cornerstone but it seems a bit outdated. It was last updated 10 months ago.
Sent from my SPH-L900 using Tapatalk 2
It hasn't be updated to work with Jelly Bean yet, they are still working off of ICS source.
Thanks slick_rick and imnuts glad to hear some input from a developer. I've done a little research and haven't found any JB ROMs using it so darn. Unless it gets updated or if anyone thinks that Samsungs multi-window can be ported to non touch-wiz roms. I should go see if I can get a hold of anyone at onskreen to see if they have any plans on updating.
I was chatting on the #TWRP IRC with Tassadar, who came up with a mod for some Nexus devices to allow TWRP to manage multiple ROMs from within recovery, essentially a multiple boot option. This reminded me of Boot Manager, which was an app that allowed some older devices to run multiple ROMs, by storing versions of them on the SD card and switch between them with a simple reboot through the app.
Tassadar mentioned that his mod was ported to the HTC One, which can be found here: http://forum.xda-developers.com/showthread.php?t=2460886
I would like to know if it would be possible to port this amazing mod to our device as well. It seems a LOT is involved, and per Tassadar, some skills are needed which I do not currently possess. I do have my build box set up to build TWRP, so I can at least help on that end, but with the actual code, I don't have the know-how. Per Tassadar, this is what's needed:
Tassadar from #TWRP said:
You'll probably need at least some knowledge about C and how kernel boots on ARM devices. It can work without the kexec patch, but it won't be able to boot different kernel for each rom
Click to expand...
Click to collapse
He directed me to this page: https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
That's his guide for porting it. You'll notice one big shortcoming right off the bat, as it relates to our device: "It only supports devices with storage in /data/media/. Physical SD cards are not supported because of how slow and generally awful they are, but some devices have "fake" /sdcard on separate partition, which is not supported as of yet."
So, some definite coding adjustments will be necessary to get it working on our device with our non-emulated internal storage, or, for the very adventurous, external SD card.
I'm willing to coordinate the project if anyone has the skills necessary to help. So, please, if you're interested in this, let's make it happen!
Another option would be to update the Boot Manager app. The source for that is here: https://github.com/init2winitapps/BootManager
Wooooow, will definitely steady, so remember evo3d, but unfortunately since to ics, are not supported,..because the dev busy.,cool
hopefully soon realized
:thumbup::thumbup:
Sent from my EVO using Xparent Green Tapatalk 2
One of the guys that was with PAC was working on this for a different device just a couple months back. I'm looking through hangouts history right now to try and get a hold of him. I'm with you, this would be awesome. From what I know of it, it's above my pay grade, coding wise.
Sent from my EVO using Tapatalk
I've been wishing in one hand and $h!&&ing in the other in hopes for this to be a reality for our device. So far you guys know what I've come up with Would be excited for this to become a reality.
Definitely would be nice. Would save the constant backup/wipe/flash/wipe/restore hassle. I'll gladly contribute as much as I can to this project once I see where some of you guys stand..... since my only recovery experience in recovery is porting smelkus to the wildfire s. Definitely on board though.
I'll C what I can do. I mentioned something's in the dev chat a lil while back.
Sent from my EVO using xda app-developers app
I have been running this on my Nexus 7 for a couple months. its really nice to have as I test and flash ROMs all the time without having to mess with my daily. You do have to install a custom version of TRWP so that it has the advanced section with the multirom items in it so that you can wipe and flash the second rom without disturbing the "internal" rom (main rom). There is also a multirom app that can que and add roms from within the OS. It will also install Ubuntu touch as the second rom.
I miss boot manager too bad I know nothing about how to update this! Good luck guys!!!
Sent from my EVO using XDA Premium 4 mobile app
My evo is just sitting there collecting dust so if you need a tester let me know...
So...I just got an Android ~5 days ago. My friend told me to root the phone and get plain Android on it instead of HTC's bloated modified version of it. I'm not a newbie to SSH and managing linux via prompt (I assume rooting the phone is what that means?..) Anyway, I have no clue what I'm doing. I've been an iPhone user for...~2 years. I'm completely new to Android.
Can anyone start me on the right path, maybe give me some explanations as to what I'm actually doing? Does this void my warranty with Best Buy (probably...jailbreaking the iPhone does, but recovering from that is easy-peezy..)
I'd like to tinker with my phone, but it seems so much more complicated to fix the phone if I make an oops than doing so with an iPhone does.
Thanks in advance.
Assuming you have the DNA, as that is the section you are in, there is quite a few helpful threads already. Check the sticky posts, they usually link to helpful threads.
With the speed of the quad core phones, debloating isn't needed as much as before, but rooting does have it's ups and downs.
I found that AOSP (pure android) based roms compared to sense (HTC software) are a little mote buggy and not as fluid. They feel snappier, but really aren't.
Try some sense based roms before going full aosp on this device. Take it from me. My old devices, I would run only AOSP, but after usi.g sense 5 on this phone, it has so.e good HTC only features.
Sent from my DNA using my mind.
I'll echo Uzephi, give sense a try first. If you really want to tinker make sure to make a nandroid in recovery. You will probably need to use either moonshine or rum runner to do what's called s-off your phone first. That will also root it. I've found the easiest way to do that is to boot to a live USB Linux, then you don't have to deal with driver issues. If you have windows 8 or 8.1 64 bit there have been fastboot issues with drivers seeing the phone for some users, myself included. Give us some more info on what your PC set up and phone OS versions are and we can help some more when and if you want. Have you gotten the latest OTAs.
Sent from my HTC6435LVW using xda app-developers app
My PC is a Windows 7 Ult and my Phone is HTC Droid DNA (Android v4.2.2 and Sense v5)
Thanks guys for the replies. I have no clue what this Android jargon is mostly, can I get some clarification or where I can read about it? Thanks a bunch.
jake6177 said:
My PC is a Windows 7 Ult and my Phone is HTC Droid DNA (Android v4.2.2 and Sense v5)
Thanks guys for the replies. I have no clue what this Android jargon is mostly, can I get some clarification or where I can read about it? Thanks a bunch.
Click to expand...
Click to collapse
Android 4.2 is the base operating system and HTC customized it to their liking, which they call Sense, and you have version 5 of Sense.
jake6177 said:
...I have no clue what this Android jargon is mostly, can I get some clarification or where I can read about it? Thanks a bunch.
Click to expand...
Click to collapse
Android phone manufacturers like to give their phones a specific look and feel, which is why android phones can look so different. This modification/augmentation of the base android software environment is commonly referred to as a UI (user interface), or Skin.
The term 'skin' is a terrible over-simplification, but it gets the point across. The vanilla Android software environment is, for many, quite boring, and not as powerful as it can be. Companies like HTC and Samsung incorporate cool animations, graphics, and sounds effects, as well as software that takes advantage of their camera's capabilities.
HTC's UI is called Sense
Samsung's is called TouchWiz Motorola's used to be called Blur (don't know if it still is)
Sent from my dlx using Tapatalk
If you're brand new to Android, I would just use the phone as it is now without rooting or putting a custom ROM on it. Once you're comfortable and familiar with Android then you can decided if you want to root and rom.
jake6177 said:
My PC is a Windows 7 Ult and my Phone is HTC Droid DNA (Android v4.2.2 and Sense v5)
Thanks guys for the replies. I have no clue what this Android jargon is mostly, can I get some clarification or where I can read about it? Thanks a bunch.
Click to expand...
Click to collapse
Rooting is akin to jailbreak, gaining control of your phone. You can root your phone (get root directory access) and still remain completely stock for your Rom.
I personally have had the best experience with sense based roms. Your experience may differ depending on what you use.
If you want to use mobile hotspot on your phone without paying subscription then rooting is a must.
Linux used to be a must to root. Now there are windows based options, I used moonshine.
Sent from my dlx using Tapatalk
Correct me if I'm wrong, but I'm pretty sure you don't have to pay extra to use your phone as a mobile hotspot if you're on a capped data plan. I think only unlimited data folks are expected to pay extra to use that feature.
Sent from my dlx using Tapatalk
That might be right. I've got the unlimited data. My co workers with company phones also have to pay for the hot spot.
Sent from my dlx using Tapatalk
BBEgo said:
Correct me if I'm wrong, but I'm pretty sure you don't have to pay extra to use your phone as a mobile hotspot if you're on a capped data plan. I think only unlimited data folks are expected to pay extra to use that feature.
Sent from my dlx using Tapatalk
Click to expand...
Click to collapse
ldw213 said:
That might be right. I've got the unlimited data. My co workers with company phones also have to pay for the hot spot.
Sent from my dlx using Tapatalk
Click to expand...
Click to collapse
Yes, correct, capped data is forbidden by law to charge for mobile hotspot, unlimited data is chargeable.
Edit* At OP, Sense is the king flavor of android, stick unrooted for a while as you won't really see a need for it yet, unless you want to go and throw on different ROM's and try them out, which in that case def. go and try viperDNA (best sense ROM avail.) AOSP/CM based ROM's are still a WIP and are ok to use but you will miss out on everything sense (sense apps, widgets, features, and even some hardware features)
Gaining root is becoming the sys admin of the phone, you would be able to read/write to the system partition of the phone and execute system privileged commands that are more for the hacker/modder/enthusiast (not normal user, you really wouldn't find a use for that type of stuff, the only app that would serve you good is "Titanium Backup" that does require root but it basically backs up all of the apps and their data)