yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] :
good news for the galaxy nexus, for what it's worth....

http://www.androidauthority.com/and...-nexus-4-nexus-7-nexus-10-server-logs-199908/
[Samsung Galaxy Nexus] slayr76:
If that's the case there's no point even owning a nexus device anymore if the best google can do is offer a year an a half worth of updates, if google want to lose their loyal nexus owners then their going about it the right way, iPhone might be my next phone if google does this, sure beats buying a new android phone every year just to get the software updates, good money maker for google an their phone manufacturers but bad for the consumer an everyone thought apple were greedy for selling iPhones at high prices, rather pay $1000 for an iPhone an receive lifetime updates than buy a new phone every 6 months or each year, next time you think the gnex or lg n4 is a sweet deal at a cheap price just remember you will only get a year or 2 at best before Google pulls the plug on updates for it.
[Samsung Galaxy Nexus] 5pace:
ALL HAIL THE ANDROID LEAD DEVELOPER, THE DECIDER FOR ALL THE RELEASES!

Read this: Android 4.3 (Jelly Bean?) spotted running on Galaxy Nexus, Nexus 4, Nexus 7 and Nexus 10 in our server logs

Please consider other's posts before making statements, you cannot speculate without having any evidence to back your point up (in such cases only).
[Samsung Galaxy Nexus] forever_lol:
nice but what's huawei doing there?
[Samsung Galaxy Nexus] Mach3.2:
Totally taken out of context. Assumptions.

My fault for making it too vague, our phone probably won't see anything official after 4.3, face it..

My "statement" is too vague. It's vague because i did not read the question properly and i though it's phrased as whether the gnex will see future updates after 4.3...

Sure it's my fault for not reading the question more carefully, I admit it, but flaming me over a 1 word reply? Does it makes your epeen longer?
[Samsung Galaxy Nexus] 5pace:
My dear sir, XDA does not work this way, a word can change the direction of the whole thread and here's a clear example of it.
[Samsung Galaxy Nexus] Mach3.2:
So it's okay to flame on XDA , noted.
[Samsung Galaxy Nexus] 5pace:
Wow! You really have issues picking the right sense up. Please re-read all the posts I wrote.
[Samsung Galaxy Nexus] mattpedigo:
There's not any evidence that's conclusive in the slightest. Those bloggers make a few bucks to drum up clicks with rumors, circumstantial nonsense, and no background in journalism. When walking into a newsroom, there's generally a code of ethics posted from the RTNDA. Among the most important is truth. As the RTNDA states it:

"Professional electronic journalists should pursue truth aggressively and present the news accurately, in context, and as completely as possible. "

I know what these bloggers do to write stories because I did it for a bit before I realized I was spitting on everything I learned in journalism. Most of their "sources" are other blogging websites. You can depend on their stories about as much as you can depend on rain in the Mohave.

Not you, nor anyone else on XDA, has any evidence for either side, whether it be 4.3, 5.0, Jelly Bean, Key Lime Pie. There isn't evidence unless that evidence is traceable without a doubt back to a reliable source (which is not nor will ever be an Android "news" site).

And who cares? It's fun to discuss, speculate, and dream. But to get sassy over something as insignificant as a different opinion is not needed here.
[Samsung Galaxy Nexus] 5pace:
I find your point / short story convincing. But, spreading idea among other people that our device won't receive next version of Android isn't speculative at all, it's just as bad as publishing rumors on a blog with having no idea what's going on around you. These things just turn the positive / speculative direction of the thread into negativity and sometimes fills people with anger.

On a side note; Isn't 'speculation' all about presenting your point / guessing future without an evidence which generally involves positivity and personal gains.
[Samsung Galaxy Nexus] Mach3.2:
Stop deceiving yourself, face it, the gnex is not probably not going to receive anything official after 4.3, it's already pretty sluggish on 4.2.2..

Try loading GB on the Google Dev Phone..
[Samsung Galaxy Nexus] Lesicnik1:
If the Galaxy Nexus won't be able to run anything after 4.3, there won't be any more low end single core devices, then.
[Samsung Galaxy Nexus] :
Screw KLP and 8 core blah blah blah. How about make the battery life revolutionary?! That's what I want most :D
[Samsung Galaxy Nexus] mattpedigo:
I agree 100%. Software and hardware should start running more efficiently. The better the process for creating the processors, the more energy efficient and task efficient they will be. We shouldn't have to have 8 cores to run the operating system on a phone. That's just ludicrous. Think about Intel's desktop chips. Today's dual cores are running better than 8 core Xeons just a few years ago.
[Samsung Galaxy Nexus] msavic6:
The iPhone 5 has awesome battery considering the size of its battery, with only 1440mAh it beats out the majority of it android phones in battery life. Sure the screen is smaller and the OS is restricted but it still does quite well. I'm hoping Google is able to reduce android's power consumption, continually increasing the size of batteries is just a temporary fix.
[Samsung Galaxy Nexus] moshe22:
I recently had my Galaxy Nexus repaired. They replaced the USA port and screen. Not sure if they replaced the motherboard or not.

One thing I have noticed and would like to point out is that. It came with 4.1.1, I decided that I was going to stick with it because it was so smooth compared to 4.2.2 but I updated anyway and to my surprise I haven't had any lag problems now. I don't know if the upgrade from 4.1 to 4.2.2 have anything to do with it because it updated straight to 4.2.2 or if they change something hardware wise with a revision of something.

My next phone will probably be an iPhone. Because of the Ecosystem plus quality.
[Samsung Galaxy Nexus] madd0g:
http://m.gsmarena.com/android_43_running_on_several_devices_shows_up_in_server_logs_-news-5954.php
[Samsung Galaxy Nexus] Mach3.2:
The OMAP 4460 is showing it's age, a Pentium 4 can't compare to a LGA 1155 Celeron right..

Stop deceiving yourselves.

Beamed from my Maguro.

---------- Post added at 07:59 AM ---------- Previous post was at 07:56 AM ----------

What Google need to do is improve on software optimisation with the hardware, not chunking out new releases...

It's like trying to play battlefield 3 with drivers from a year back before the game came out...

Beamed from my Maguro.
[Samsung Galaxy Nexus] mattpedigo:
Apple has managed to keep phones relevant beyond 18 months. And Microsoft kept old computers in the upgrade cycle.

I don't think anybody is deceiving themselves by hoping an 18 month old phone with a decent, albeit dated, set of specs stays software updated.

Android invented this "you're too old so we hate you" mentality and it is the fact that people keep upgrading like when they're told that keeps it going.

No other software vendor has been so flagrant in its attempts to force people to buy new hardware as Google. I think people who expect a Nexus (aka Google) branded device to have more than a few years of updates are being reasonable not ignorant.

What's ignorant is seeing that you're getting shafted by a company whose soul existence is fueled by profits and then defending their cause.
[Samsung Galaxy Nexus] Soldier 2.0:
I imagine it is being tested on the Gnex and depending on how well it performs they will make the decision to release it or not?

Sent from my Galaxy Nexus GSM
[Samsung Galaxy Nexus] speedyink:
You know if you researched before you started spewing crap you wouldn't sound like an idiot.

Ok here's some simple logic to maybe help you out. What is the current required specs for 4.2.2?

800mhz Single Core, 512MB of ram. There is a version of it available for my Xperia Play (1ghz single core, 512mb ram) and it runs fine enough for people to play high end games on a device from early 2011 (the lack of ram is just starting to get in the way for the brand new games)

In what universe is it acceptable to make your OS go from requiring 800mhz single core snapdragons to quad core or beastly dual cores? In ONE version jump? Google would be shooting themselves in the foot if they decided to murder efficiency with a dull butter knife like you're suggesting.

Thankfully Google's engineers have thought about this a little more than you have.
[Samsung Galaxy Nexus] forever_lol:
TIOMAP 4460 is obviously an obsolete piece of technology according to 2013 standards (it wasn't top notch even in the second half of 2012). The difference between GNex and Nexus S in terms of CPU/GPU wasn't that huge as it between Nexus 4 and Gnex today.

Still I have no doubts it'll handle 5.0 but with the level of android optimization we have now I don't think it's gonna be very impressive performance. Well we'll see. I hope i am wrong. Another question is how far can software (with JVM on the top) optimization go, how much better it can be. GB run better than froyo on my old htc legend. ICS was more laggy than GB on S2. JB is by far snappier than ICS on Gnex.
[Samsung Galaxy Nexus] turdbogls:
i agree with you man. our Gnex will be able to run the next big version no problem. phone companies are going to keep releasing lower end phones with single core processors and 1GB of ram, and they are going to use the latest version of andorid they can get. sure, for the next 6 months or so, that is probably 4.2.2.....but in a year, that will be 5.0 (or whatever the next big version is) yes, it might not be blazing fast or super smooth like a quad core beast of a phone will run the OS, but it wont be a dog, and lag, and be full of bugs. companies know better than to do this. and people know better than to expect optimal performance from a free phone.

I'm sticking to the G-nex officially getting the next big version of android.
[Samsung Galaxy Nexus] josip-k:
Here's my opinion.

I think we'll get 4.3 update officaly,and maybie KLP. Or,maybie 4.3 update will be KLP. No one knows yet. But,we will get new versions unofficaly that's what i'm 100% shure. Think about it,how much older devices still get unoffical updates,and they're too weak to even run gingerbread. Proof?

I own an Xperia x8. Last offical update was eclair,and it came with donut.

Versions:donut-offical

Eclair-offical

Froyo-unoffical,fully working

Gingerbread-unoffical,but offical cm7

ICS-unoffical,fully working(camera even works,and FM)

Jellybean-unoffical,fully working,smoother than GB and ICS

BUT we are talking about the device that is three years old,and has sh*tty ardeno 200 gpu,128mb of ram,and 600Mhz processor. Cmon.

Jellybean got smoother on it,because android is more and more optimized and smoother.

So i think our phone is still a beast,and will be a beast for many more years. So,untill our phone wont be able to handle new android versions,or if it dies and i cant fix it,i wont change it,no way.
[Samsung Galaxy Nexus] AntonyStark:
Hopefully this Jelly Bean is the Perfect Jellybean, and solves all the issues and runs better, and more phones end up running JB, but I still think what's next will barely run on this, but by then the low end phones will be like a G Nex Like a G Nex....

Having 3 Jelly beans suggests what's next is way beyond, and we got to be honest this isn't a way beyond phone.

But in less than 2 weeks we will have some answers and all we have all said will mean nothing we will just be all waiting for 4.3 notifications, I haven't seen Takju and Yakju everywhere for a while lol
[Samsung Galaxy Nexus] Langduscher:
Great discussion eheh :D:good:

My 2c:

4.2.x doesn't leave much room for custom rom devs to be very much destinctive - in fact; how I use my Gnex I'm thinking of downgrading it back to the latest 4.1.2 AOKP build because that way my phone was MY phone - very distinctive! (Services as Play Store & Google Now aren't near as supported as to USA customers for example over here - in fact Gooogle treats us as morons:eek:)

That said: my wife's Galaxy S has never be running as great as it has since a 4.2.2 custom rom! :cowboy:

So - will my Gnex be running 4.3 Key Lime Pie or 5.x Lusty Lollipop or whatever? Sure it will!

Will it still satifsy my needs and usage? Who cares?

I will be able to run the OS 1 way or another and I WILL try it! Just because I CAN. The wholehartedly reason I got a Nexus device in the 1st place: because I CAN. Not because I WILL or MUST.

Just have fun out there allrighty (AND: it's a ****!ng phone......just supposed to be convenient) :good:
[Samsung Galaxy Nexus] mattpedigo:
But do you think Lusty Lollipop will satisfy your wife?
[Samsung Galaxy Nexus] Langduscher:
What do you think? Worth the upgrade? Your avatar looks shocked, what's the story on Lust Lolliop then??! :laugh:
[Samsung Galaxy Nexus] daniil1410:
My previous phone was Samsung Galaxy 5, which you probably haven't heard of. Thanks to porters it has CM7 to CM10.1, MIUI and many other roms, despite that samsung updated it officialy only to froyo.

So, I think that the GNex will receive updates to 4.3, to 5.0 and maybe even to higher versions. But even after that this is xda and we will get ports to Android 20 at least.

P.S. I love how you start hating on Google for not updating our phone without even knowing what will happen.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Sux0r:
Hello.

I want to disable PIE control for the rom [ROM][★DarkFantasy™★ ][4.2.2][P31XX][DF-1].

Ive read but couldnt understand some, Its a great rom thought but i need the nav bar back.

~THanks.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] squ89r97:
just had a quick look on google (what a tool :silly:) and can you try holding down your power button until the menu comes up and press disable expanded desktop? see if that works.

oh and what did you read, that you couldn't understand?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] techpal:
go to settings - system- power menu - expanded desktop- status bar visible

then press power button and click Full screen (pie)
[Samsung Epic 4G Touch] garwynn:
DISCLAIMER:

Your device, your responsibility. I am not liable for anything you flash, including this.

As a result you'll probably want to read the rest of the thread and at least be aware of what you're flashing.

You've been warned.

JB Kernel + Agat's tRec for SPH-D710 (Sprint, Boost, Virgin)​

Features:

Updated Linux Kernel

Additional Governors

USB Mass Storage, ADB functioning in recovery

Additional partitions added in backup strategy

Screenshots:

None

Latest Builds:

Sprint (GB27):

[KERNEL][JB][SOURCE][SPR] GB27 + Agat's (SXTP Developers)

Virgin (GB28):

[KERNEL][JB][SOURCE][VMUB] GB28 + Agat's (Rwilco12 Android Forums)

Boost (GC01):

[KERNEL][JB][SOURCE][BST] GC01 + Agat's (SXTP Developers)

Flash Instructions:

3) Boot to Odin Mode and flash via Odin.

Summary Changelog:

v0.5.0 - Resolved last issues with recovery.
v0.4.1 - Avoids reboot due to Hotplug.
v0.4.0 - Added back governors
v0.3.0 - Updated to Linux 3.0.71
v0.2.0 - Updated Linux Version
v0.1.0 - Initial

Source:

Sprint GB27 Github Repo: https://github.com/garwynn/D710SPR_GB27_Kernel

Virgin GB28 Github Repo: https://github.com/garwynn/D710VMUB_GB28_Kernel

Boost GC01 Github Repo: https://github.com/garwynn/D710BST_GC01_Kernel

Ramdisk Repo: https://github.com/garwynn/D710_jb_initramfs

Agat's Recovery Repo: https://github.com/agat63/E4GT_JB_recovery

Credits:

Steve Kondik (Cyanogen) for CM development and jf common work

The CM maintainters who continue to improve CM along with Mr. Kondik

Agat63 for his long standing recovery for the E4GT. May it stay as long as there's one in use.

...and of course! You, the community, for your support as well! Thank you!

NOTE:

All previous versions that I have worked on will no longer be supported.

Support for this thread will be as time allows, which may not be much.

We've done what we wanted to - leave the E4GT with some very good stuff.
[Samsung Epic 4G Touch] robrooter:
Thats great stuff. Great job garwynn :) thanks to all whom worked hard on them. Will test sprint variant now for you.

E4GT Rom-a-holic. Running anything that looks cool at the time ;)

"This is the Droid I have been looking for!"
[Samsung Epic 4G Touch] btoddweber:
As will I sir...thanks

in a comadosed jellyverse
[Samsung Epic 4G Touch] cerj:
Thank you Sir.
[Samsung Epic 4G Touch] cdss:
Awesome, thanks
[Samsung Epic 4G Touch] third son:
Perfect!

How sweet it is!
[Samsung Epic 4G Touch] g_ding84:
This is awesome. Thank you.

Anyone get this MD5 for the .tar?

db9e1eb713ec7a1a9d7fa960e8f90c84
[Samsung Epic 4G Touch] robrooter:
So it is working nice. Loaded per Mobil odin...re started crisp.

Have opened all 60+ apps and fooled round. Started just fine. Wifi sync is fast...3g working. I don't have 4g so can't test. So far its awesome. :beer: :thumbup:

E4GT Rom-a-holic. Running anything that looks cool at the time ;)

"This is the Droid I have been looking for!"
[Samsung Epic 4G Touch] btoddweber:
Ditto on the post above..reboot and rec all apps even pd..

in a comadosed jellyverse
[Samsung Epic 4G Touch] dschachm:
4g connected, then disconnected. I went into settings, scanned and then it connected. Went to window at got 8mb down, 2mb up. Gps locked to within 10 ft.
[Samsung Epic 4G Touch] garwynn:
I should also give fair notice... with JB out and it being the final release (from notes I have read) these will be my last foray into E4GT development. I will continue my work on GN2 and am planning on hitting the GS4/GN3 hard this year.

The goal will be to leave the E4GT with the best possible based on what we have... and now with JB we have a lot!
[Samsung Epic 4G Touch] robrooter:
Thanks for the heads up.

E4GT Rom-a-holic. Running anything that looks cool at the time ;)

"This is the Droid I have been looking for!"
[Samsung Epic 4G Touch] dschachm:
Thanks for your work on this. Any idea if you will add in governors and under clocking?
[Samsung Epic 4G Touch] garwynn:
Yes. Once I get the Linux version current I will work on that next. That way I can work on the same for 4+ kernels
[Samsung Epic 4G Touch] boXerrumble:
Just curious. Did Samsung remove the line of code that triggers the emmc bug in the ICS kernels?
[Samsung Epic 4G Touch] dschachm:
Awesome.
[Samsung Epic 4G Touch] garwynn:
Their official patch is in now. A little different in coding but same result as we were already doing... disabling secure erase/trim. Just done by eMMC ID now.
[Samsung Epic 4G Touch] fredrick1213:
Just tested moving apps to sd via Titanium Backup. On stock kernel it would cause apps to disappear but I'm happy to say that all apps are in tact. Great work Garwynn!
[Samsung Epic 4G Touch] WhiteZero:
Any chance someone can upload a mirror of the tar? The main link is blocked at my work... :S

Otherwise, I'll just have to wait 8 hours! lol
[Samsung Epic 4G Touch] Sloth:
Just to confirm because I have been away from the E4GT forums for a while this is a SAFE JB recovery?

Thanks to Garwynn and Agat :D you guys rock

TIA BD619
[Samsung Epic 4G Touch] kobridge:
Thanks for hardworking!

My suggestion is, we may need the multiple test versions of kernels added by only 1 or 2 additional kernels each. Just like you said, once we identify the kernel causing the problem, then we can try to add all other kernels except the troublesome kernel.

I think we may need some tester to do this.

Again, thanks Garwynn!
[Samsung Epic 4G Touch] Mattix724:
I did some extensive testing for the Zio when Adryenline built the kernel. I spent a couple long nights on irc testing every build. I can do the same for the E4GT.
[Samsung Epic 4G Touch] jaxon01:
I installed Comadose after the kernel. I was not aware that it would make a difference which order they were installed. There should not be a problem with the new Comadose v1.3 Variant either way. Goddly removed the tweak that was not compatible with the extra governors in 0.3.0.

Sent from my SPH-D710 using Xparent Cyan Tapatalk 2
[Samsung Epic 4G Touch] Mattix724:
The original 1.3 is what I have running with 0.3.1
[Samsung Epic 4G Touch] jaxon01:
I have not tried 0.3.1 because I was under the impression that the extra governors like pegasusq and conservative are not in it. I have always gotten better battery life with either one of those than ondemand.

Sent from my SPH-D710 using Xparent Cyan Tapatalk 2
[Samsung Epic 4G Touch] MoHoGalore:
KO/Garwynn - Absolutely mean zero disrespect when I say this - If you decide to take the step to multiple test builds, I second Mattix for identifying volunteers but ask you limit the releases to known testers and builds. Just limit the ring to streamline response time and checklists.

Again - no disrespect meant, just a thought.
[Samsung Epic 4G Touch] garwynn:
Well, I heard Hotplug had issues so we'll do that last.

So I'd suggest the following order:

1) Re-enable all stock

2) Re-enable SMARTASS2

3) Re-enable LAGFREE

4) Re-enable HYPER

5) Re-enable LULZACTIVE

6) Re-enable KTOONSERVATIVE

7) Re-enable HOTPLUG

We'll do each in the 0.3 range to figure out what's good for 0.4.x

MoHo - as these are tests and we have 0.3.0 and 0.3.1 to cover the extremes I think we can just let them loose to the public. But I'll be looking to Goddly and Kobridge to report back on the status of their tweaks along each way.

If everyone's OK with this let me know and I'll start #1(0.3.2 is next increment) today.
[Samsung Epic 4G Touch] leaderbuilder:
Sounds good to me. I'll keep testing what ever you put up when I can. Running between sites all day. Little better than being stuck in the bowels of server room.
[Samsung Epic 4G Touch] Mattix724:
I suggest that all testers have Comodose, 4-Cyl, and kobridge tweaks on their SD cards.

1. Flash a clean install of GB27.

2. Flash one of the tweak packages.

3. Flash the kernel.

Rinse and repeat until all tweak packs have been tested on each of the incremental kernel updates.
[Samsung Epic 4G Touch] kobridge:
Because we have the CWM kernel working already, we don't need to worry about much.

Things to test -

1. bootloop - flash the new kernel and check if it goes to bootloop and report. If it goes to bootloop, just go to recover mode and flash the another test kernel.

Pre-requisite - init.d support and my 41tweak_kobridge tweak file in init.d folder (or test any other init.d tweak which was known not working on 0.3 kernel)

2. if it does not go to bootloop, just go to romtool box and check the govenor is showing up and about to set it up. Reboot and check your phone boots with new governor.

3.After the reboot, if you have the same governor you changed in step 2, go to step 1 and test other kernels.

For anyone who want to test more intensive governor test, that would be the second phase.

For now, I'm quite busy with another stuff. So, I couldn't help the test now....
[Samsung Epic 4G Touch] garwynn:
Steps 1-3 (0.3.2, 0.3.3, 0.3.4) are up in tar format.

Cranking out the rest as fast as I can.

*Edit*

Half of the test kernels are done.

Still cranking 'em out....
[Samsung Epic 4G Touch] Goddly:
Ill do what is needed and will test whatever is necessary ..

Also like to test

- External_sd card mounting issues , My trouble was with the V.01, Moving large files (rom) from my pc via ES explorer to External_sd , which resulted in lock up and re- boot (no loop) 3x same result Transfered to internal with no issue. Also was not an Issue on stock kernel.. Ive since upgraded, Im on v0.3.0 to test the governors and their workability, and have yet to try large file transfer, though i had requested someone try moving a large file from Internal to External to determine if it indeed is a slight mounting problem, but have not received any conformation yet. I aploogize for not doing this myself yet but i am away from home atm.

lemme know guys, ill give up to date information upon subsequent releases...
[Samsung Epic 4G Touch] garwynn:
If it happened on v0.1.0 that was pure stock on the kernel side. Means the issue was in the ramdisk side. We'll need to talk to Agat63 on that.

Update:

All possible test cases are up on the SXTP Developers thread. If it's a governor one or more cases should nail it down.