if you care most about a near AOSP experience... - Galaxy S II General

I've got a bit of a dilemma.
I'm tied between a Nexus S (850Mhz SLCD) and an SGS2.
The most love i have for my Captivate is when my user experience gets closer to AOSP.
I like the GB launcher, GB Keyboard, the ability to run custom roms, modems and kernels. Swype does nothing for me, nor do any of the Samsung apps.
I realise the SGS2 is only new - and is almost twice the phone (at least performance wise) that the Captivate/Nexus S is - however is it looking like we will have the same freedoms as the i9000 and their derivatives? Or is the Nexus S really the way to go if you want total control over your handset?
I'm not a dev, but i love to tinker, tweak and take the best of each component to make my experience, mine

1randomtask said:
I've got a bit of a dilemma.
I'm tied between a Nexus S (850Mhz SLCD) and an SGS2.
The most love i have for my Captivate is when my user experience gets closer to AOSP.
I like the GB launcher, GB Keyboard, the ability to run custom roms, modems and kernels. Swype does nothing for me, nor do any of the Samsung apps.
I realise the SGS2 is only new - and is almost twice the phone (at least performance wise) that the Captivate/Nexus S is - however is it looking like we will have the same freedoms as the i9000 and their derivatives? Or is the Nexus S really the way to go if you want total control over your handset?
I'm not a dev, but i love to tinker, tweak and take the best of each component to make my experience, mine
Click to expand...
Click to collapse
Well, the SGS2 appears to have no significant locks in place, as you can easily flash a custom ODIN file with an unsigned kernel or ROM. Yes, a warning triangle shows if you do this, and a counter is incremented, but that is easily reset...
It's not got the full AOSP experience yet, but that's something I can look at when mine arrives... There is kernel source, and very basic android source, though not a full tree by any means...

1randomtask said:
I've got a bit of a dilemma.
I'm tied between a Nexus S (850Mhz SLCD) and an SGS2.
The most love i have for my Captivate is when my user experience gets closer to AOSP.
I like the GB launcher, GB Keyboard, the ability to run custom roms, modems and kernels. Swype does nothing for me, nor do any of the Samsung apps.
I realise the SGS2 is only new - and is almost twice the phone (at least performance wise) that the Captivate/Nexus S is - however is it looking like we will have the same freedoms as the i9000 and their derivatives? Or is the Nexus S really the way to go if you want total control over your handset?
I'm not a dev, but i love to tinker, tweak and take the best of each component to make my experience, mine
Click to expand...
Click to collapse
sorry to hijack your thread, but where did you find the nexus s with the SLCD screen and 850mhz 3g? i didnt think that version existed and i'm interested. ATT compatible obviously.
oh and to answer your question, an AOSP ROM is still not known yet if it will truly be possible or not. at least this time around some more of the source code was released, but its not everything so nobody knows for sure yet how in depth a ROM dev can go.

RogerPodacter said:
sorry to hijack your thread, but where did you find the nexus s with the SLCD screen and 850mhz 3g? i didnt think that version existed and i'm interested. ATT compatible obviously.
Click to expand...
Click to collapse
http://www.mobicity.com.au/samsung-google-nexus-s-nextg.html

Related

Customizing vs. N1

So I may jump ship from the N1 to the Vibrant. On the N1, in less than ten minutes I can run a nandroid backup, flash a new kernel, new radio and a new rom. In another 3-4 minutes, I can switch back. I've literally switched kernels >3 times/day before. How much different will things be on the Vibrant? Is it harder to do these things? Is there as much risk?
Thanks
right now no one knows, there is no custom kernels, custom recovery, custom roms, etc
There are custom roms and you can easily root the device...but it will obviously take some time to reach N1's customization...
I've had my G1(I know, not the N1) since day 1, and I've been flashing roms since day one. The only reason I flashed roms was because I felt the G1 was lacking in a lot of things. Now that I have the Vibrant, I feel like there's no need to flash a different rom. It's already pretty fast, and I actually like the touchwiz UI. The UI doesnt completely take over the Android interface, it's more like adding extra little features.
ultra spikey said:
I've had my G1(I know, not the N1) since day 1, and I've been flashing roms since day one. The only reason I flashed roms was because I felt the G1 was lacking in a lot of things. Now that I have the Vibrant, I feel like there's no need to flash a different rom. It's already pretty fast, and I actually like the touchwiz UI. The UI doesnt completely take over the Android interface, it's more like adding extra little features.
Click to expand...
Click to collapse
Exactly, plus the Black/Blue color scheme is far better looking to me over stock Android. TouchWiz is not like Sense or previous generations of the skin and that's a good thing.
Ill second that. I am really enjoying my touch wiz interface and I didn't think I would. That being said I miss my app drawer that slid up from the bottom.
Sent from my SGH-T959 using XDA App
I don't know much about flashing to different ROMs yet, but I can give you an overview of the TouchWiz experience from my viewpoint.
Coming from an iPhone, I really like TouchWiz 3.0. And believe me when I tell you: that was their goal with the UI. It screams Apple, in layout and function. But of course, it ultimately feels a bit like an imitation in some areas. I feel like they rushed TouchWiz 3.0 out of the door.
The Clocks and Alarms app is much better than the iPhone's, which is something I was not at all expecting. It's really quite nice. The calendar app is about on par, in terms of layout. The upper hand is that this syncs OTA with Google's cloud services. The music player is very 'iPod-like', but is ultimately a rush job (embedded album art does not work very often and so forth).
All things considered, it's a really nice UI for Android.
That said, there are some really basic functions which did not make the transition from stock Android. For example: you cannot fully edit contacts in the 'Contacts' app. You cannot delete them, you cannot add custom ringtones. Coming from the iPhone, where I had meticulously completed the profiles of every contact with an obscene amount of info and custom ringtones, this is annoying.
There are a few 'little things' like that, which really matter to me. And this has kind of soured the experience for me, making me second-guess my decision. To be honest, I'm still sort of on the fence over this of the N1 as my iPhone replacement.
The grey area for me is in Android 3.0's release. Google has stated that they're going to overhaul the UI. The idea is that they want to make it more user-friendly, to make the use of custom skins less prevalent. Well, I'm all for this. Trouble is: will these handset manufacturers adopt it, considering their vested interests in their custom experiences?
Samsung's UI is definitely my favorite out of Sense, MotoBlur and the lot. But I'd be lying if I said that I didn't wish for a Nexus One for the security of owning the only unlocked stock device.
Hope that helps...
Give it some time and stock Android will be on the Vibrant. Thats the great thing about Android and Xda.
Yeah, I really love the idea of xda and the amount of support that all of these devices receive from the community. Of course, the trouble is: if you root for a custom rom - even if it's stock Android - the N1 is the only solution for getting OTA updates regularly. With stock Android on the Galaxy S, you're going to have to re-flash every time the ROM is updated. Not the end of the world, but definitely irritating.
Running a JB/Unlocked iPhone, I'm used to dealing with work-arounds, and waiting for hacks. That's the price I paid for using a non-carrier phone. I couldn't accept the automatic updates from Apple, and this became a mild annoyance (reinstalling everything and so forth). But when you decide to 'play nice' and own a carrier-specific phone, you kind of want the experience of timely OTA, non-hacking-related updates that simply update your device, without first wiping it clean.
Know what I mean?
I'm still not sure if I'm going to keep my Galaxy S, or buy an N1 while there's still time (the 'rumors'? of the N1's touchscreen issues are really all that held me back). But either way, I hope that all devices have some way to experience the latest and greatest from Google.
The touchscreen is bad on that phone especially when it comes to multitouch. I'm sure you've already seen the videos comparing the two touchpads and the Vibrant's touchscreen is SO accurate... multitouch included.
Jon C said:
Yeah, I really love the idea of xda and the amount of support that all of these devices receive from the community. Of course, the trouble is: if you root for a custom rom - even if it's stock Android - the N1 is the only solution for getting OTA updates regularly. With stock Android on the Galaxy S, you're going to have to re-flash every time the ROM is updated. Not the end of the world, but definitely irritating.
Running a JB/Unlocked iPhone, I'm used to dealing with work-arounds, and waiting for hacks. That's the price I paid for using a non-carrier phone. I couldn't accept the automatic updates from Apple, and this became a mild annoyance (reinstalling everything and so forth). But when you decide to 'play nice' and own a carrier-specific phone, you kind of want the experience of timely OTA, non-hacking-related updates that simply update your device, without first wiping it clean.
Know what I mean?
I'm still not sure if I'm going to keep my Galaxy S, or buy an N1 while there's still time (the 'rumors'? of the N1's touchscreen issues are really all that held me back). But either way, I hope that all devices have some way to experience the latest and greatest from Google.
Click to expand...
Click to collapse
While its a little early to be 100% yet but Android hacking is a lot different than iphone hacking. The iphone is a closed system and you have to wait till its broken open to update. Android is already open when its released. As for OTAs if Cyanogen supports the Vibrant then there is an app to download and install new updates. Typically if you stay with the same developer, like Cyanogen, then you don't have to wipe when there are updates.
After froyo 2.2 all my touch screen problems was gone.
Sent from my Nexus One using XDA App
So untrue after froyo 2.2 those problems was fix the nexus one is a awsome phone.and I believe the same for the vibrant.
Sent from my Nexus One using XDA App
Can you do me the world's biggest favor?
Would you make some YouTube videos, showing the multitouch tests of your N1? I so, so, so, would love to own one, but I have zero tolerance for faulty hardware. I've been researching this stuff since the N1 launch, and it's the only thing holding me back from purchasing that device.
'Multitouch Vis Test' is probably the easiest way, but if you can think of others to test with, that would be great.
Jon C said:
The music player is very 'iPod-like', but is ultimately a rush job (embedded album art does not work very often and so forth).
.
Click to expand...
Click to collapse
I haven't used my iPod Nano 4th Gen in some time, I find that the N1 is handling my music needs just fine. But if I had a nickel for every time album art was hosed on my iPod Nano I would not have a mortgage anymore...
hah2110 said:
So I may jump ship from the N1 to the Vibrant. On the N1, in less than ten minutes I can run a nandroid backup, flash a new kernel, new radio and a new rom. In another 3-4 minutes, I can switch back. I've literally switched kernels >3 times/day before. How much different will things be on the Vibrant? Is it harder to do these things? Is there as much risk?
Thanks
Click to expand...
Click to collapse
First you must know that the process is completely different. For right now most roms are installed through the Odin process. This process completely wipes all of the information on the phone (including apps and settings) and then installs the new rom. So you will have to backup your apps and settings every time you change roms (Titanium backup would work but it's not always fool proof). Second all roms are going to be based off of Samsung code. That means no Sense roms, no stock roms (well you can get the stock launcher but your dialer and notification bar will always be touchwized), and no froyo until Samsung releases there own version. This has been true so far with all previous Samsung phones and looking at the development with the I9000 it seems to hold true for the Galaxy S. All this does put you at less risk of bricking your phone but it does mean you also have less chance of serious customization. Also with limited source code for the I9000 (there are some drivers that are not source code but actually compiled) it's very difficult to just plop roms on from other sources.
psychoace said:
First you must know that the process is completely different. For right now most roms are installed through the Odin process. This process completely wipes all of the information on the phone (including apps and settings) and then installs the new rom. So you will have to backup your apps and settings every time you change roms (Titanium backup would work but it's not always fool proof). Second all roms are going to be based off of Samsung code. That means no Sense roms, no stock roms (well you can get the stock launcher but your dialer and notification bar will always be touchwized), and no froyo until Samsung releases there own version. This has been true so far with all previous Samsung phones and looking at the development with the I9000 it seems to hold true for the Galaxy S. All this does put you at less risk of bricking your phone but it does mean you also have less chance of serious customization. Also with limited source code for the I9000 (there are some drivers that are not source code but actually compiled) it's very difficult to just plop roms on from other sources.
Click to expand...
Click to collapse
Why can't CM do his thing?
cm is trying to port cyanogen to the vibrant. in fact ive read that the vibrant and the droid x are his 2 top priorities so it will come soon enough. and once he gets it done we will probibly see a bunch of roms based of cyanogen
blazewit said:
cm is trying to port cyanogen to the vibrant. in fact ive read that the vibrant and the droid x are his 2 top priorities so it will come soon enough. and once he gets it done we will probibly see a bunch of roms based of cyanogen
Click to expand...
Click to collapse
I have yet to see any information confirming any of that. First on his twitter he only seems to be working on the Evo right now. Second I doubt he would work on the Droid x until it's rooted (which most likely will be never). Last I have seen only a small pattern of talk about someone in conversation with Cyanogen about allowing a Galaxy branch of the CM code for use with the Galaxy S. Problem is this doesn't solve the issue of not having source code for a few drivers. This does not even attack the issue of getting the rom onto the phone. So don't hold your breath for any of that.
yea your right it was just one site claiming that cm is working on the vibrant,from what i can tell gothdroid and a bunch of other g1/dream devs are working right now for custom recovery and porting cm6 and froyo asop

Whats up with the roms lately?

I just wanted to get a feel/consensus on peoples opinion of the third party rom scene for the EVO. I started my XDA days back with a tilt, and have been loyal to HTC since then.
The EVO is simply the best phone out there at the moment, IMO. But the roms seem to be very lacking in actual substance and it's a bit disappointing.
Almost every rom I've looked at here has been so customized and themed they are really just eyesores. It was normal on all my other devices to have some of the roms that were being produced be like this, but not all. I've been really impressed in the past with HTC roms. Dutty is one of my favorites.
The only 2 current exceptions I've found are CM and Fresh, and since some of us refuse to use sense, it really only leaves one choice.
CM is awesome, and the work that goes into it is really really amazing. There isn't a bunch of customization to the UI, it's left up to you what you want to do for how your phone looks. It's a rock solid foundation to build upon, and it would be awesome to see more roms in that form.
Thoughts? Am I missing something?
This is the wrong section, the General section would be the appropriate section for this.
this should be in general, but i agree it seems that lots of roms out there are just customizations of existing roms, a color change here and there. There really isnt anything major to differentiate between sense roms, except for 3 or 4 big ones, and then there is CM rom, and the roms based of CM seem like just themed version of CM, but who knows i mean im not a developer, maybe theres only so much one can do as far as development.
easedrop said:
--
The EVO is simply the best phone out there at the moment, IMO. But the roms seem to be very lacking in actual substance and it's a bit disappointing.
--
Thoughts? Am I missing something?
Click to expand...
Click to collapse
Better get started developing.
What else do you want the ROM's out there to do?:
OC: Check
Undervolt: Check
AOSP Builds: Check
Open Source 4G: Check
De-odex: Check
Wide Variety of Themes: Check
Open Source FM Radio: Check
Wireless Tether: Check
Wired Tether: Check
Gingerbread: Check
AND THE LIST GOES ON...
What I'm trying to say is, unless your speaking specifically about HDMI, there's really not a lot left to be desired that can't be had from these phones until Honeycomb hits.
I mean, CM even supports SIP accounts natively...among the millions of other small details that are so amazing.
Even DLNA can be had through a simple app...what's left for you to want so badly that your phone cannot do already?
My point is, is that most devs are not going start over from scratch just for the heck of it, when something so close to optimum potential has already been reached.
Sent from my 4G-Toting, Lightning Smoking, Gingerfied, Cyanogenmodded EVO: Please stand back!
Itotally disagree. I mean, some, yeah, you're right, but look at the mods done to the more popular roms. Not just theming but tweaks, custome apps, etc.
What more do you want form a ROM?
And while, true, some people are married to CM, some are more into Senseui, some Miui.
Everyone has different tastes, and from what I se eon here, there's something for just about everyone.
Thread moved to General.
As per your questions, devs make roms based on their personal taste and, in many cases, general feedback from the users. There are many plain, stock rooted roms out there, and many tutorials in case you want to make your own as well. Also, you can easily theme any rom to your liking. I hope this answers your concern.
i think the ROM's on the evo are pretty strong. My criteria is, do the majority if not all ROM's improve upon stock? Yes. Do the majority if not all the dev's support their ROM's and upgrade in a timely manner? Yes Do the majority if not all the dev's have themes/mods available for their ROMS? Yes. Are there more than one style of ROM's to choose? YES 1. Sense 2. AOSP - MIUI 3. AOSP - CM 4. AOSP - Liquid metal
easedrop said:
I just wanted to get a feel/consensus on peoples opinion of the third party rom scene for the EVO. I started my XDA days back with a tilt, and have been loyal to HTC since then.
The EVO is simply the best phone out there at the moment, IMO. But the roms seem to be very lacking in actual substance and it's a bit disappointing.
Almost every rom I've looked at here has been so customized and themed they are really just eyesores. It was normal on all my other devices to have some of the roms that were being produced be like this, but not all. I've been really impressed in the past with HTC roms. Dutty is one of my favorites.
The only 2 current exceptions I've found are CM and Fresh, and since some of us refuse to use sense, it really only leaves one choice.
CM is awesome, and the work that goes into it is really really amazing. There isn't a bunch of customization to the UI, it's left up to you what you want to do for how your phone looks. It's a rock solid foundation to build upon, and it would be awesome to see more roms in that form.
Thoughts? Am I missing something?
Click to expand...
Click to collapse
There are way more. Click my signature and you'll see
my EVO is way cooler than yours
Except your link is broken...
easedrop said:
Am I missing something?
Click to expand...
Click to collapse
Yes. MIUI.
the OP ... is expectiong way too much....
you do relize for most.. this is a good little hobby..
so is done around free time...
you want more... you do it! I dont have the skills to even try.
I do appreciate the ones that can... and do.
there are a lot of phones out in the market. and not all phones even have a dev community.. and if they do, it aint that big.
so there are different levels of dev support from phone to phone.
EVO, is way up there in the level of quality devs and community support.
Fixed my sig, forgot i changed the link. But there are a Sh*t ton of choices, my count is at 144 thus far
_MetalHead_ said:
Yes. MIUI.
Click to expand...
Click to collapse
+1... this.
I've had 4 Android phones:
Evo
G2
MyTouch 3g Slide
Moto Cliq
This forum has more roms, kernels, mods, themes, etc than all 3 of my prior phones combined. Every time I hit the dev section I'm a kid in the candy store. There's fully functioning roms that work with everything and a few that I'm excited to see get better, like MIUI getting 4g.
There's very few phones out there with this much dev support, my friend has an LG vortex. Go find the LG vortex section of the forums. They don't exist.
My point, you have to do some digging but there's something here for everyone. If there isn't, make it! We could always use another dev to try to topple the big dogs.

Give me one reason I need an unlocked bootloader.

Other than these two:
Overclocking
Loading modded roms
I mean let's all be honest, even if you undervolt and remain stable, any overclocking that will allow noticable performance, will have just as much noticable effect on the battery. And these are mobile devices. Battery should be considered top priority, not speed.
And what's the deal with wanting to load all these custom roms? Are they significantly better than stock, Adeo, or gingerblur? What do we need to load a fully custom rom for? Are they lightning fast and extend battery life by 100%? I guess I just don't get it. Deodexing and visual mods can be done without an unlocked bootloader.
Basically what im trying to say is. What is everyone *****ing about?
Sent from my Atrix using XDA App
As far as I know, there is no way to unlock the Atrix's bootloader. It is encrypted. You may check the xda's frontpage, there is news several weeks ago regards to the Moto's bootloader.
mccoy007 said:
As far as I know, there is no way to unlock the Atrix's bootloader. It is encrypted. You may check the xda's frontpage, there is news several weeks ago regards to the Moto's bootloader.
Click to expand...
Click to collapse
I think you missed the purpose of the thread. He is not asking HOW to do it, only WHY you would need to, other then overclocking or loading ROMs.
Honestly, it does make a big difference. Battery life can be very substantially increased in many of these roms. They both over and under clock processors to maximize the life. It's possible to get gingerbread on the inspire right now through custom roms because the boot loader isnt locked. It's possible to completely remove sense, whereas we have to live with motoblur. There really are a lot of reasons. Honestly, look at what Xda is all about, it's android development. Just take a look at the atrix dev forum vs the inspire one. Phones with a strong development community tend to live far longer because they can upgrade the os long after the company stops trying. The original g1 was only officially upgraded to 1.6 (I believe) but Xda has a few 2.2 roms that actually run pretty solid.
Tl:dr the list goes on and on of reasons that you want an accessible boot loader.
Ability to load a custom recovery menu. Nandroid.
it's simple dude. people do it because they can.
Besides the fact you would get work and support from the awesome devs here another good reason would be most phones have their shortcomings.Most of the time this can be fixed in the software.The awesome devs here are able to in most cases get it sorted out within a week or 2 whereas if the phone manufacturer or carrier is gonna do something about it your gonna wait 6 months to get an update. A prime example of this was the rediculously low external and earpiece speaker volume on the inspire.On max volume it was just too low. Now the rom chefs can cook up custom roms with 20% volume increase.
The 2 reasons you want to exclude are the main points. It's like saying "other than drowning; what's the point of learning to swim".
i want android 2.3.3 , can i ? no! i have to wait to an official update from motorola.. why ?!
i want htc sence in motorola , can i ? no !
we love to play and change things.. uman nature
seh6183 said:
Other than these two:
Overclocking
Loading modded roms
I mean let's all be honest, even if you undervolt and remain stable, any overclocking that will allow noticable performance, will have just as much noticable effect on the battery. And these are mobile devices. Battery should be considered top priority, not speed.
And what's the deal with wanting to load all these custom roms? Are they significantly better than stock, Adeo, or gingerblur? What do we need to load a fully custom rom for? Are they lightning fast and extend battery life by 100%? I guess I just don't get it. Deodexing and visual mods can be done without an unlocked bootloader.
Basically what im trying to say is. What is everyone *****ing about?
Sent from my Atrix using XDA App
Click to expand...
Click to collapse
Your first question says "ignoring custom ROMs..." and your second question says "What about custom Roms..." so I'll address the second question.
ROMs. Gingerbread. AOSP. Stock Android. Kernels.
Another consideration in favor of ROMs is the continuation of support by the dev community even after the manufacturer has EOL'ed a product. You still see the Dream (G1) getting roms with new features even though the phone has been effectively dead for a while now.
It is always in the phone manufacturer's and the carrier's best interests to kill off support to get you to buy the newest, latest device.
daveop said:
Just take a look at the atrix dev forum vs the inspire one. Phones with a strong development community tend to live far longer because they can upgrade the os long after the company stops trying.
Click to expand...
Click to collapse
I love my atrix.. but I visited the Inspire 4G dev forums... and.. yeah I got a little bit jealous. lol
I hope the few devs we have don't end up leaving and can crack this bootloader!!!!
s1mpd1ddy said:
I love my atrix.. but I visited the Inspire 4G dev forums... and.. yeah I got a little bit jealous. lol
I hope the few devs we have don't end up leaving and can crack this bootloader!!!!
Click to expand...
Click to collapse
I know what you mean. That's one thing I like/liked about my FUZE: there was a pretty active dev community, at least until the HD2 came out.
I'm planning on getting an Atrix on Monday and this is making me think about getting an Inspire instead. I guess I'll get the Atrix and if it blows I can take it back, get an inspire, and pocket $100.
Wow is this seriously a question?
Nandroid backups, AOSP ROMs like Cyanogen where you get updates every NIGHT if you wish from the source Android build so it'll always be the latest version - no waiting for Motocrap. Battery life is usually way better, TONS of tweaks (being able to tweak my color balance of the screen, gamma levels, haptic feedback behavior, autobrightness levels and thresholds, lockscreen and messaging gestures, etc). That's all before even mentioning performance increases like overclocking, deodexing for themes, ext4 modifications for faster I/O. There's just way too many things to list but if you've never experienced a phone that has custom ROMs (especially Cyanogen) then I can see why you don't miss anything, but if you have, like me, you'll probably never want to settle for an Android phone that doesn't allow custom ROMs.
custom roms is reason enough...like dinan said if you ever used them you would understand. pretty much all the problems that people are having with the atrix could be solved if our devs had access to the bootloader.
I do see the importance of having continued support after moto leaves the phone behind. And it would be nice to have a dev make a rom to fix the coloring on the Atrix screen. Also I didn't realize that updates to custom roms come so often and that they had that much support.
I am starting to see now.
Sent from my Atrix using XDA App
mccoy007 said:
As far as I know, there is no way to unlock the Atrix's bootloader. It is encrypted. You may check the xda's frontpage, there is news several weeks ago regards to the Moto's bootloader.
Click to expand...
Click to collapse
Luckily, there are a few other people working on the bootloader (I hope), as it is signed, not encrypted; there is a difference.
My phone before the Atrix was the TytnII, and the only reason I was able to keep it as long as I did was because of custom ROMS. If they are able to increase the performance of this phone the way they increased the performance of my 300Mhz/128MB RAM TytnII, then I will be giddy as a school-girl.
Do I need an unlocked bootloader? No, I absolutely love my phone the way it is right now, as this is my first Android, so I don't know what else is possible.
Battery life?
I am running a test of a custom kernel for my captivate. I turned off everything and wanted to see how long it would last.
No wifi or data (no sim card installed) it ran idle for 11 days.
Custom Kernel with no wifi or data its going to last about 50 days. (based on current estimate as im still testing it)
Just an FYI, there are devices with locked bootloaders that have custom ROMs. This includes the X10, which has a Gingerbread ROM. The issue is getting a newer Android build to work with a stock kernel. Unlocking the bootloader is key to building custom kernels but there are methods for getting custom ROMs without a custom kernel.
Developer support.
/thread
-Sent from my Galaxy Tab
Athailias said:
Battery life?
I am running a test of a custom kernel for my captivate. I turned off everything and wanted to see how long it would last.
No wifi or data (no sim card installed) it ran idle for 11 days.
Custom Kernel with no wifi or data its going to last about 50 days. (based on current estimate as im still testing it)
Click to expand...
Click to collapse
Well this isn't exactly a real world situation. Who's to say that you're not running the cpu at 1mhz with the screen powered off 24/7. wouldn't you prefer to test under load and real use?
Sent from my Atrix using XDA App

Where the hell are those AOSP ROMs?!

I'm starting to be really pissed off, what's problem with N3? I don't get it, i saw kondik's photo on twitter like 2 months ago and yet there is no even nighty nighty build or ultranighty, nothing. Other devices like G2, Z1 got AOSP long time ago.
tafmasterpl said:
I'm starting to be really pissed off, what's problem with N3? I don't get it, i saw kondik's photo on twitter like 2 months ago and yet there is no even nighty nighty build or ultranighty, nothing. Other devices like G2, Z1 got AOSP long time ago.
Click to expand...
Click to collapse
Developers have lives. plus if you read CMs site and blogs and posts you'll see that schoolwork comes first for a couple of them, plus they probably won't bother with the Note 3 until KitKat is released... If you are that desperately craving AOSP why did you buy a Samsung device? A company that is notoriously slow with updates/ROM stuff etc.... - Just sell it and go buy a Nexus.
Aosp stands for android open source project. Aka stock android.
Sent from my HTC first using xda app-developers app
radicalisto said:
Developers have lives. plus if you read CMs site and blogs and posts you'll see that schoolwork comes first for a couple of them, plus they probably won't bother with the Note 3 until KitKat is released... If you are that desperately craving AOSP why did you buy a Samsung device? A company that is notoriously slow with updates/ROM stuff etc.... - Just sell it and go buy a Nexus.
Click to expand...
Click to collapse
That's the answer. Samdung has an absolutely horrible history in the Open Source community, and it's not getting better anytime soon. Anybody who wants AOSP/CM ROMS should NEVER buy a Samdung device.
They do make great devices, but they have the worst attitude toward the dev community, routinely providing incomplete and/or outdated sources and/or the absolutely bare minimum required for a questionable level of GPL compliance, and they'll never provide userspace drivers, which is where 90% of the problems are in supporting their devices.
It's just a reality, and anyone hoping for full compliance and an open and friendly attitude toward AOSP/CM community is delusional.
donalgodon said:
That's the answer. Samdung has an absolutely horrible history in the Open Source community, and it's not getting better anytime soon. Anybody who wants AOSP/CM ROMS should NEVER buy a Samdung device.
They do make great devices, but they have the worst attitude toward the dev community, routinely providing incomplete and/or outdated sources and/or the absolutely bare minimum required for a questionable level of GPL compliance, and they'll never provide userspace drivers, which is where 90% of the problems are in supporting their devices.
It's just a reality, and anyone hoping for full compliance and an open and friendly attitude toward AOSP/CM community is delusional.
Click to expand...
Click to collapse
Give me an SD Card option or at least 64GB option and I will do it asap, that's all i ask, i don't even need removable battery and 5.7 inch screen, just SDCard or bigger storage option and powerful processor(Snap 800 is fine!). Please don't tell me about "mighty cloud services" i want normal storage for my music.
But guys tell me one thing, there is no such thing like Galaxy Note 2 google edition and there is a CM rom, there is no LG G2. Sony Z1 and others Google edition roms, and they have CM or any other stock android variations literally DAYS after release, note has none, totally, literally, NOTHING. Why no love for note ? I really don't get it. :crying:
Few people are ready to give up the support for S-Pen and adopt AOSP based roms. Besides the S-Pen is the main reason people buy the note series.
I actually bought the phone because it makes an awesome reading device. I only used s pen to try it out. i yet have to find the killer feature I would use it more often for.
I'm rooted, added a different launcher and some widgets and it comes now pretty close to what I wanted. If you want other roms, be patient. It took long for the razr HD but I finally put pacman rom on it. So I'd say it comes down to what you really want. If the latest FW is top priority you have to live with small onboard memory. I prefer the big screen and have all my apps and music right on the phone on a 64gb sd card including navigation and maps. I can't stand all this cloud stuff for different reasons, the biggest one being privacy. But these are just my 2 cent.
Mikegrmn said:
I actually bought the phone because it makes an awesome reading device. I only used s pen to try it out. i yet have to find the killer feature I would use it more often for.
I'm rooted, added a different launcher and some widgets and it comes now pretty close to what I wanted. If you want other roms, be patient. It took long for the razr HD but I finally put pacman rom on it. So I'd say it comes down to what you really want. If the latest FW is top priority you have to live with small onboard memory. I prefer the big screen and have all my apps and music right on the phone on a 64gb sd card including navigation and maps. I can't stand all this cloud stuff for different reasons, the biggest one being privacy. But these are just my 2 cent.
Click to expand...
Click to collapse
Pretty same as me, i just need storage for all my music and i was really tired because my iphone 4 32GB was almost always fullfiled to the max, I hate deleting and need to choose between tracks. The S-Pen is working, i don't know what's about that, note 2 has tons of AOSP ROMs and many peoples are fine with that.
tafmasterpl said:
Give me an SD Card option or at least 64GB option and I will do it ASAP...
Click to expand...
Click to collapse
Same reasons here. But big screen in a small frame was what sold it. Almost got the oppo, but besel and weight made note3 the best hardware. Figured the snapdragon would make this device fully aosp supported, but so far no love.
SPen..? I've got gmd pen gestures, papyrus, better screenshot, etc. I can easily have all the "tw functions" i need on an aosp rom. Samsung has nothing that I can't get better versions of through play
Imagine this hardware and omnirom.. I can't wait, and as soon as an alfa is out I'm on it..
Mikegrmn said:
I actually bought the phone because it makes an awesome reading device. I only used s pen to try it out. i yet have to find the killer feature I would use it more often for.
I'm rooted, added a different launcher and some widgets and it comes now pretty close to what I wanted. If you want other roms, be patient. It took long for the razr HD but I finally put pacman rom on it. So I'd say it comes down to what you really want. If the latest FW is top priority you have to live with small onboard memory. I prefer the big screen and have all my apps and music right on the phone on a 64gb sd card including navigation and maps. I can't stand all this cloud stuff for different reasons, the biggest one being privacy. But these are just my 2 cent.
Click to expand...
Click to collapse
Where did you download the pacman rom form i can find it for the s3, but not the Note3?
The dev community seems to be struggling at the moment (at least with this and the Motorola moto g).
It's a sad time when you have to buy a phone with the possibility of never being able to leave stock firmware (luckily moto g is almost vanilla)
Sent from my XT1032 using XDA Premium 4 mobile app
ninja75 said:
Where did you download the pacman rom form i can find it for the s3, but not the Note3?
Click to expand...
Click to collapse
Pacman is not for the Note 3 yet. I wrote that it took a while until it came to my Motorola Razr HD.
I would absolutely LOVE an AOSP stock rom for my Note 3. Something like the google play edition of the S4 would be perfect... really surprised this has not been done yet, especially with the hardcore specs of the Note 3, hopefully OmniROM will provide our needs!
Mikegrmn said:
Pacman is not for the Note 3 yet. I wrote that it took a while until it came to my Motorola Razr HD.
Click to expand...
Click to collapse
Thanks, this is the only thing holding me back from getting the note 3

Stock Android possible?

Been many a yore since I've been on Android consistently, been out-of-the-loop since the earliest days.
Just curious, is it technically possible to get a "Nexus-like" experience on a device like the Note 4 nowadays?
I'm attracted by all the sw/service benefits of a Nexus device, but I really love the hw of the Note 4*...
Is it possible to have "the best of both worlds" or close? I realise it's not an option so early in the device's life-cycle, but later perhaps?
Thank-you.
*Also considering the Note Edge (more research needed), but not 100% sold on it yet, unless someone can make a compelling case
jalyst said:
Been many a yore since I've been on Android consistently, been out-of-the-loop since the earliest days.
Just curious, is it technically possible to get a "Nexus-like" experience on a device like the Note 4 nowadays?
I'm attracted by all the sw/service benefits of a Nexus device, but I really love the hw of the Note 4*...
Is it possible to have "the best of both worlds" or close? I realise it's not an option so early in the device's life-cycle, but later perhaps?
Thank-you.
*Also considering the Note Edge (more research needed), but not 100% sold on it yet, unless someone can make a compelling case
Click to expand...
Click to collapse
What you want is a rom based on AOSP (like cyanogenmod). It has the advantage of being nearly stock android with updates nearly as fast as google can push them out. It is much much quicker than carrier updates. Plus, AOSP is community/google supported so you can count on updates long after the carriers stop supporting your phone. This support is what allows kitkat to run on a galaxy s2 or a barnes and noble nook. lol.
So the catch to all this is you MUST have an unlocked bootloader. ATT and verizon are out because they have locked their bootloader.
On the note 3, people who had the tmobile note 3 (unlocked bootloader) had kitkat months and months before the ATT touchwiz kitkat was pushed by ATT.
But I'm not worried all that much about carriers not supporting my phone...
I usually buy unbranded/unlocked (i.e. outright: it makes more sense in my country -not USA), I imagine the same -or similar- applies to ODM/OEM's?
How far out are they (AOSP-based ROMS like CM) exactly from being stock Android?*
Are there many major differences, or only some minor ones, what are they exactly?
Thank-you/goodnight, bed time, 2am!
*i.e. what we have on Nexus devices
^Anyone? Thank-you!
P.S.
How do we delete posts, it says "EDIT/DELETE" but I can't find delete anywhere!?
jalyst said:
How far out are they (AOSP-based ROMS like CM) exactly from being stock Android?*
Are there many major differences, or only some minor ones, what are they exactly?
Thank-you/goodnight, bed time, 2am!
*i.e. what we have on Nexus devices
Click to expand...
Click to collapse
It's as close as you can get, almost to the point of being the same. I honestly can't think of any major differences. My wife went from CM to a nexus 5 and she new exactly where everything was. My nexus 7 interface looks like my cm11 nook tablets.
Apart from the UX though, what are all the major (or minor) services/functionalities you lose?*
I mean mostly compared to stock Android that's found on the latest Nexus devices, but I guess also compared to Samsung's spin.
Also, you missed this post...
http://forum.xda-developers.com/note-4/help/stock-android-t2882646/post55566887
Finally, any idea how to delete posts?
Cheers mate!
*Given that mircury isn't sure on this point, can someone else please have a crack.
The main issues with going to AOSP are the inferior camera app and the lack of multiwindow support. With the big Volantis tablet coming out soon, Google may finally bake some multiwindow support into "L", and maybe devs can use the RAW access APIs to fix the camera, but I wouldn't expect miracles out of the box.
If you do want AOSP, you'll probably want to get a Qualcomm-based Note instead of an Exynos one - for various reasons a lot of the dev goes quicker on the Qualcomm platform. Not sure which will be the standard version in your country.
s44 said:
The main issues with going to AOSP are the inferior camera app and the lack of multiwindow support. With the big Volantis tablet coming out soon, Google may finally bake some multiwindow support into "L", and maybe devs can use the RAW access APIs to fix the camera, but I wouldn't expect miracles out of the box.
Click to expand...
Click to collapse
That's literally it? That's nothing if that's all there is!?!
I'm used to hanging out mostly on quite esoteric/hack-ish platforms, so if that's all I have to deal with, "no biggy".
If you do want AOSP, you'll probably want to get a Qualcomm-based Note instead of an Exynos one - for various reasons a lot of the dev goes quicker on the Qualcomm platform. Not sure which will be the standard version in your country.
Click to expand...
Click to collapse
Yeah I suspected that might be the case, I haven't checked that yet, I'm in Australasia/Oceania, Australia specifically.
I hope I've lucked out there, IIRC the international version (i.e. not local/telco-centric) usually is Qualcomm isn't it?
And this post???
http://forum.xda-developers.com/note-4/help/stock-android-t2882646/post55566887
Also, anyone know how to delete posts?
Thank-you.
...
*BUMP* @ anyone
TY/GN
No need to bump your post 3 times. I would suggest you go on youtube and watch some video reviews. You will find that it is very much nexus like with no features lost.
Pretty sure you'll lose any proprietary stuff. Like the heartrate sensor...etc...especially the special uses for the S-Pen.
SiNJiN76 said:
Pretty sure you'll lose any proprietary stuff. Like the heartrate sensor...etc...especially the special uses for the S-Pen.
Click to expand...
Click to collapse
He's talking about the difference between stock android on a nexus device and aosp. The stock rom from Samsung is a totally different ballgame.
mircury said:
No need to bump your post 3 times.
Click to expand...
Click to collapse
Bumped twice, both with healthy time gaps. Going to YT won’t get this addressed:
jalyst said:
But I'm not worried all that much about carriers not supporting my phone...
I usually buy unbranded/unlocked (i.e. outright: it makes more sense in my country -not USA), I imagine the same -or similar- applies to ODM/OEM's?
Click to expand...
Click to collapse
Or this…
jalyst said:
How do we delete posts, it says "EDIT/DELETE" but I can't find delete anywhere!?
Click to expand...
Click to collapse
jalyst said:
^Anyone? Thank-you!
Click to expand...
Click to collapse
You forgot this one in your list.
Well, that was more than day earlier, but aside from that, able to address the 2 points above?
SiNJiN76 said:
Pretty sure you'll lose any proprietary stuff. Like the heartrate sensor...etc...especially the special uses for the S-Pen.
Click to expand...
Click to collapse
Is that the only notable proprietary stuff that will go?
And is it unlikely that the AOSP community will eventually add support for such things?
mircury said:
He's talking about the difference between stock android on a nexus device and aosp. The stock rom from Samsung is a totally different ballgame.
Click to expand...
Click to collapse
No I'm talking about all 3, i.e...
If I switch to AOSP (CM etc) what features will be missing* compared to: (1) stock on Nexus devices, & (2) stock Android for the Note 4.
Although I'm mostly interested in the former...
As I can easily work out the latter once (if) I have a Note 4, simply by using Samsung's flavour of Android for a while.
*& what bugs will I encounter
jalyst said:
Well, that was more than day earlier, but aside from that, able to address the 2 points above?
No I'm talking about all 3, i.e...
If I'm to switch to AOSP what features will I be missing* compared to stock on Nexus devices, & stock Android for the Note 4.
Although I'm mostly interested in the former...
As I can easily work out the latter once (if) I have a Note 4, simply by using Samsung's flavour of Android for a while.
*& what bugs will I encounter
Click to expand...
Click to collapse
So we've basically established in previous posts that AOSP = Nexus features wise. No need to hash that out again.
Compared to Samsung's stock rom there is a TON of stuff and even more stuff when compared to Samsung's stock rom after each carrier has had it's way with it.
1. Multi windows
2. all the Spen features (Some spen features can be added back. See thread in note 3 forum.)
3. Tmobile wifi calling
4. Touchwiz
5. Different Notification pull down.
6. Different settings menus.
7. Carrier Bloatware
8. 4K recording not available in stock AOSP. Some have used Oneplus camera app. (Camera app not as good as Samsung's stock)
9. HDMI out not working.
10. NFC not working on some builds.
11. All the Samsung specific apps like milk music and SBeam.
12. Tethering limitations on the Carrier version stock (This is a big one)
I'll add more as I think of them...
mircury said:
So we've basically established in previous posts that AOSP = Nexus features wise. No need to hash that out again.
Click to expand...
Click to collapse
But have we really? Not so sure about that. What's been put forward so far doesn't seem iron-clad conclusive.
Compared to Samsung's stock rom there is a TON of stuff, and even more stuff when compared to Samsung's stock rom after each carrier has had it's way with it.
1. Multi windows
2. all the Spen features
3. Tmobile wifi calling
4. Touchwiz
5. Different Notification pull down.
6. Different settings menus.
7. Carrier Bloatware
8. 4K recording not available (Camera app not as good as Samsung's stock)
9. HDMI out not working.
10. NFC not working on some builds.
11. All the Samsung specific apps like milk music and SBeam.
12. Tethering limitations on the Carrier version stock (This is a big one)
I'll add more as I think of them...
Click to expand...
Click to collapse
Cheers buddy...
Don't care about what carriers may or may not add, I'll most likely be getting one that isn't carrier-based.
Even if I do get one from a carrier it won't be a US-based one, it'll most likely be from Telstra, & IME it never adds anything of value.
jalyst said:
But have we really? Not so sure about that. What's been put forward so far doesn't seem iron-clad conclusive.
Click to expand...
Click to collapse
I thought we did. lol. I don't know how much clearer we can get. Google controls AOSP. It is stock android through and through. Go read up on what AOSP is and then read what CM is.

Categories

Resources