yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] rayiskon:
u haven't been reading through this thread right? :eek:
[Samsung Galaxy Nexus] bozzykid:
They still show the screenshot with the JB search bar. It is not a fake. It just means they removed the message.
[Samsung Galaxy Nexus] jcurtis369:
edit: yes i have been following this all day and was never able to get the message but clearly you can see that the wallpaper is different and the search bar is different as well

---------- Post added at 04:29 PM ---------- Previous post was at 04:27 PM ----------

ok i see what your saying i was just never able to get that message and i even tried right after he posted
[Samsung Galaxy Nexus] FredFS456:
Do you really think that Engadget and AndroidPolice, AndroidCentral, DroidLife, and others would post this without checking with the Play Store for themselves? I don't want to cause a flame war here but this is not fake. It has been confirmed multiple times.

EDIT: Whoo 100 posts.
[Samsung Galaxy Nexus] bozzykid:
It's not a fake, I saw the message as well.
[Samsung Galaxy Nexus] Jorge787:
And people ask why I didn't wait for the Galaxy S3 and bought a Nexus.
[Samsung Galaxy Nexus] jcurtis369:
Ill believe it when its on my phone. till then its all rumors and thats all this is until we can get some official proof
[Samsung Galaxy Nexus] andQlimax:
Sdk api to write apps are always the same, they add new API of course, but old API works for new and old os releases...

The problem is not the sdk API..but is the number of lines of code they change on aosp.. manufacturer are slow because have to re-code they ****ty customization on the os, but mainly readapt the changes for their hardware...because the code Google release on the aosp ONLY work on the nexus, every manufacture have to a lot of work to port it on their phone..

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] bozzykid:
This is true but HTC and Samsung have eased off their enhancements to much of the lower level stuff as of late. Frankly, these quick updates may force these manufacturers to make less changes to the code which is good for users. In a way the failure to update devices is a win for Google as it means more devices with software closer to stock (since it is difficult to keep updated with a small amount of resources OEMs have).
[Samsung Galaxy Nexus] adrynalyne:
Google brings out new proprietaries when they change API version. That is my reason for concern. When Google last updated the API, it busted some of the proprietaries for us.
[Samsung Galaxy Nexus] FredFS456:
I meant "it's not fake" as in the leak isn't fake. The OP in this thread didn't photoshop the screenshot that he posted. I'm not claiming to know that Android 4.1 Jelly Bean is coming next week or anything, although it does seem like it at this point.
[Samsung Galaxy Nexus] jcurtis369:
it is starting to seem like that. yes the words are gone now but the wallpaper on gnex is still different. i just think its weird that the words are gone now but they aren't fixing the pictures. that is the only thing i see that might be fake about this is the words describing the gnex. even if it is fake i dont really care cause now im getting pretty anxious for next week :D
[Samsung Galaxy Nexus] mick3444:
Does anyone know how the sprint and or the verizon model will be handled by rom developers? Is it easy and fast for them to convert/port the gsm bulid to the cdma phones? In other words, will the cdma models see jellybean in the form of a custom rom promptly after the source is in aosp?
[Samsung Galaxy Nexus] adrynalyne:
Port. What an ugly word. No, we won't port.

You will get it as quick as the GSM users if the ICS ril props work under JB. If not, it will be a bit longer, until we find a workaround, bandaid, or see a leak. It might be a bit longer for Sprint, as it requires even more proprietaries than Verizon does.
[Samsung Galaxy Nexus] mick3444:
Do you mean that sprint phones will be able to use what is posted in aosp or that devs can quickly change and add the necasary files for it to work on the sprint model if indeed google did not change the ril files?
[Samsung Galaxy Nexus] adrynalyne:
I mean use what is on AOSP. All the CDMA and LTE code is already there, I cannot foresee them removing it in the future.

The real debate/scandal is those damnable proprietaries and redistribution licenses.

Barring any props incompatibilities, it should be a simple repo init, repo sync, and make.

When I mentioned Sprint, they require some proprietary apks for certain things (like mms). Also, the Verizon ril props won't work for Sprint. So there could be a delay, but only if the ICS props do not work for JB or if the Sprint apks do not work under JB.
[Samsung Galaxy Nexus] BeerChameleon:
Knowing that we have you bigrushdog and other very awesomely talented developers i don't doubt that it will be no longer then a week or 2 :laugh:
[Samsung Galaxy Nexus] msedek:
Well I got this picture of what its supposed to be JB if you look closely the clock says 25:10... Broken clock or release date?

Source: http://phandroid.com/2012/06/20/did-we-just-get-a-sneak-peak-at-jelly-bean-in-google-io-screenshot/
[Samsung Galaxy Nexus] TonyLeMesmer:
Star Trek reference, 26 hour day. Majel on the way?
[Samsung Galaxy Nexus] SocialReject:
Yeah, that explains it all.

/sarcasm

Sent from the future.
[Samsung Galaxy Nexus] adrynalyne:
Or neither and its not a real screencap ;)
[Samsung Galaxy Nexus] Beamer9408:
Man I don't know if I can stay up that late...
[Samsung Galaxy Nexus] isitalex:
Nice find by the OP, look forward to finding out more about JB.

On a side note, got to love threads on software updates... boom 10 pages down in an evening, lots of over excited adults acting like its their first Xmas (me included:silly:)
[Samsung Galaxy Nexus] nebrando:
+1

Definitely agree. If getting a 2 year contract, I think a Nexus device is a must!!
[Samsung Galaxy Nexus] zapikoe:
Hopes these rumors circulating, could be debunked in few days, ahead
[Samsung Galaxy Nexus] rickatnight11:
I'm calling it now. The release after JB will be called...

Key Lime Pie
[Samsung Galaxy Nexus] IINexusII:
yup, the Nexus 7" tab would be the first TABLET with 4.1 and the Gnex would be the first PHONE with 4.1 :D
[Samsung Galaxy Nexus] adrynalyne:
I think that has been called many times.
[Samsung Galaxy Nexus] rickatnight11:
Hey, I feel clever. Just did a Google search, and apparently that's been "tipped" already. I did it all by myself, mommy!
[Samsung Galaxy Nexus] ham4ever:
nice google

good news :laugh: some new update and Devs are excited :good:
[Samsung Galaxy Nexus] adrynalyne:
LOL :D
[Samsung Galaxy Nexus] Bond007mgm:
Can't wait for Google I/O I've been holding off for 2 years to buy a tablet, and now soon I will and I'll have 4.1 on my nexus soon. This will be a good month (or maybe next month). :D
[Samsung Galaxy Nexus] dadoc04:
i hope there is a 10 inch nexus tab as well

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bozzykid:
I'm pretty sure the initial Nexus tablet will only be 7" as they are trying to push back against Kindle Fire sales. We will probably see 10" tablets on the play store later this year. Of course, who knows if they will be Nexus devices.
[Samsung Galaxy Nexus] infazzdar:
I see Jelly Bean as being an "S" upgrade.

Minimal front-end improvements while focusing on back-end and performance things.

We'll probably see Majel, and hopefully an improved "Monitor Mode" as stated above.
[Samsung Galaxy Nexus] subxero123:
Stupid

Still waiting for my 4.0.1 nexus to take its first step

This phone sucks
[Samsung Galaxy Nexus] ÜBER™:
Don't feed the troll

Sent From My Sprint Galaxy Nexus
[Samsung Galaxy Nexus] rabidrotty:
Just root and flash yakju. Oops fed the troll
[Samsung Galaxy Nexus] BlackMiracle:
Short question: does this mean there will be no new Nexus Phone? I'm kinda waiting for it.
[Samsung Galaxy Nexus] subxero123:
Would've done that by now if I knew how to

I liked the part where u were helpful

Oh wait...
[Samsung Galaxy Nexus] xXDLD511Xx:
Hate the search bar. =/
[Samsung Galaxy Nexus] bozzykid:
Most likely later this year there will be multiple new Nexus phones. But I wouldn't expect that until Q4.
[Samsung Galaxy Nexus] ÜBER™:
I would come back with some smart remark... but I can't feed trolls.

Sent From My Sprint Galaxy Nexus
[Samsung Galaxy Nexus] adrynalyne:
Wasn't that a rumor last year too?
[Samsung Galaxy Nexus] adrynalyne:
http://www.google.com/search?hl=en&...0.199.522.0j3.3.0.cish..0.0.gDuop1wOUrQ&mvs=0

Note the search terms.
[Samsung Galaxy Nexus] chw2006:
I do like that wallpaper.
[Samsung Galaxy Nexus] BlackMiracle:
Well my HTC Desire is almost two years old now and I'm thinking of getting the new one.

The Xperia S is just too big, I do like the size of Xperia P but since it has a tiny 1305mAh battery, I don't think it would be a good choice though. HTC One Series looks good too, the One X is, again, too big and the One S seems to be a great choice BUT I live in Asia and HTC is NOT offering the S4 CPU for One S in this region (they're giving S3 instead) I feel like paying for an old CPU with the same price. And I'm not interested in Samsung phones at all.

Any comments?
[Samsung Galaxy Nexus] dr.m0x:
Why are you asking this in a forum for a Samsung phone?

Sent from my Cyanogenmodded GNex
[Samsung Galaxy Nexus] rabidrotty:
Google wugs gnex root tool download it read the instructions and go. Its very simple even a barely functional retard like me can do it. If u have any questions pm me I'll give u my # and walk u through the process over the phone. But make sure u back up all ur stuff ie pics vids music docs etc on ur pc
[Samsung Galaxy Nexus] funkyblue04:
Half the time I think these so called "leaks" are really a marketing strategy.

BTW, I hope ICS drivers can be used with Jelly Bean. No excuse then for slow updates from manufacturers who have already released ICS. Will help with custom ROM's too. I'd hate to have to see everyone start again.

Were drivers from 2.0 able to be used on 2.1?

Thanks :)
[Samsung Galaxy Nexus] arzbhatia:
Android 4.1 Jelly Bean Search widget face-lift -

- Oops! Sorry didn't know it was uploaded already!
[Samsung Galaxy Nexus] adrynalyne:
Clock update too ;)
[Samsung Galaxy Nexus] brian_o'fish:
It's a conspiracy

Google got wind that Cyanogenmod is preparing to release an official CM9 for the GNex, and now they dangle a next-version-coming-soon carrot in front of eveybody in the hope CM9 will be delayed some more.

Of course, I'm totally serious. Really.

:silly:
[Samsung Galaxy Nexus] CyberBulletz:
Dear Lil Jones,

For your attached image, you need to sensor the Url as well, bro.

The insider can still catch you using some query parameters.
[Samsung Galaxy Nexus] onthecouchagain:
It's times like this that reassure me I made the right decision passing on the GSIII. :fingers-crossed:
[Samsung Galaxy Nexus] harveydent:
Unlikely in this case, since it was the OP who stumbled upon it, and it might have been there for some time. It was only "leaked" to the media when us xda'er started flooding the tech blogs with "tips"

Unless, of course, if the OP was a Google plant

:puts on tin foil hat:
[Samsung Galaxy Nexus] chw2006:
That might not be the release date of Jelly Bean. Rather, it could be the release date of the next Nexus phone.
[Samsung Galaxy Nexus] adrynalyne:
I think you are reading too far into a render. If you stare long enough, you can see an image of Jesus in the wallpaper too. :p
[Samsung Galaxy Nexus] Joshua Talley:
I have a Galaxy Nexus because it's a Nexus, not because of Samsung. I'd rather have HTC or Sony, because I like their hardware. The Xperia S isn't very available in the US (similar to the One X). The One S was tempting, but I want WXGA in that size (or smaller!). For $400 unlocked, the Galaxy Nexus was a good compromise for me, but from previous poor Samsung experience, I was reluctant to give them more money.
[Samsung Galaxy Nexus] bmg1001:
+1 and thank god I went with a Nexus and not an S3.
[Samsung Galaxy Nexus] plisskenn:
Why? I've had the nexus for 6 months and I'm ready to preorder the s3. I hope the S3 can satisfy me until the next upgrade.
[Samsung Galaxy Nexus] adrynalyne:
Why not? He apparently values the Nexus for reasons you do not.

Different stokes, and all that.
[Samsung Galaxy Nexus] plisskenn:
I suppose. I have one for Verizon I'd sell for $350 out of contract.
[Samsung Galaxy Nexus] msedek:
You suck
[Samsung Galaxy Nexus] nicknowsky:
better get one while u can that Galaxy Nexus Ban is serious. If you google it, you dont get any direct links
[Samsung Galaxy Nexus] @rbiter:
Yes he does.

butter and jelly please...
[Samsung Galaxy Nexus] PlayGrandPa:
Maybe a month later than the source releasing

Maybe
[Samsung Galaxy Nexus] ArclightX:
You think you're pretty fancy huh??!!??

Well consider you're self one-up'd!

!!! BAM !!!
[Samsung Galaxy Nexus] adrynalyne:
Show off!
[Samsung Galaxy Nexus] ArclightX:
LOL, Milk coming out of my nose LOL.... :D
[Android Q&A, Help & Troubleshooting] baokiem1:
Help me, who is Vietnamese i8160 Rom yourself up for with, thank you all, I find that not:confused:
[Android Q&A, Help & Troubleshooting] baokiem1:
Help me !!!!! I need the help of the Pro XDA, there are Vietnamese DXLE1 rom 2.3.6 of galaxy ACE 2 up for yourself with.
[Android Q&A, Help & Troubleshooting] soraxx:
No ROMs yet
[Desire HD Accessories] Moscow_97:
After 170h working

View attachment 1145730

My phone was very lagged

View attachment 1145748

So now I'm on blackout without lags.
[Optimus One, P500, V General] Aragornn46:
The problem is that my phone usually charges to about 55% and that takes 7-8 hours and even more.

The problem is that when it gets to about 55% it stops and gets to 8%,then it might go charge by itself back to 55%,but sometimes I have to plug the cable again...

Right now I have it charging via usb to my laptop,and it was at 7%,now after about 40 minutes of charging it's at 6%!!

I used cyanogenmod untill now,right now I'm using the ICS version for optimus one.So it behaves the same on both...I don't understand where it's the problem...it shows it's charging,sometimes it charges but sometimes not...or it just stops at 55%-60%...
[Optimus One, P500, V General] bluespoon4:
You could try wiping battery stats from your recovery, I don't know if that'd work though. Otherwise, it sounds like a hardware problem, it could be your cable or maybe even your phone. If it's still under warranty you should reflash the stock firmware with kdz (that way they won't know you rooted it) then bring it in to LG or whoever you bought it from.
[General Questions and Answers] streamck:
Hi!

I want to change my current phone (Sony Ericsson W995) to nice smartphone.

Wish list :cool:

screen size min. 3,5 inch

good quality (materials)

good camera (iPhone 4S rules ^^)

good performance with multitasking

microSD slot, if less than 16 GB of internal memory

long support (updates)

I would like to browse the internet a lot and play games. Budget: 2500 PLN (585 EUR/739 USD/472 GBP).

Sorry for my bad English language.

Cheers.
[General Questions and Answers] winny54:
you're very rich !!

you can buy the galaxy sIIor sIII

or a htc one s or one x

the best androphone of the moment !!
[Galaxy S III Q&A, Help & Troubleshooting] krohnjw:
So the Samsung Clock is force closing when passing it an alarm intent from NFC Task Launcher. I need someone with an S3 to capture that logcat output and send it to me so I can see if I can fix it. Any takers?

Edit:

I made a quick APK, no NFC tag needed - anyone can test this, I just need the logcat output. The following APK should make the S3 clock app crash when it's run (in theory). I need to know why (logcat output would be really helpful).

APK in the 4th post

http://xdaforums.com/showpost.php?p=27742575&postcount=4
[Galaxy S III Q&A, Help & Troubleshooting] krohnjw:
Anybody :) I can create a quick APK to simulate this if anyone wants to do it but lacks NFC tags.
[Galaxy S III Q&A, Help & Troubleshooting] adchesney:
I have S3 and have NFC tags...if you tell me EXACTLY what to do, I will help.

ANDREW
[Galaxy S III Q&A, Help & Troubleshooting] krohnjw:
I made a quick APK, no NFC tag needed - anyone can test this, I just need the logcat output. The following APK should make the S3 clock app crash when it's run (in theory). I need to know why (logcat output would be really helpful).

In case you are curious about nefarious activities, here's the code:

public class ClockTestActivity extends Activity {
@Override
public void onCreate(Bundle savedInstanceState)
{
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
}

public void setAlarm(View v)
{
Intent intent = new Intent();
intent.setAction(AlarmClock.ACTION_SET_ALARM);
intent.putExtra(AlarmClock.EXTRA_HOUR, 3);
intent.putExtra(AlarmClock.EXTRA_MINUTES, 25);
intent.putExtra(AlarmClock.EXTRA_SKIP_UI, true);
startActivity(intent);
}
}

Edit: Capturing logcat output:

If you have ADB set up you can merely plug the device in and issue:

adb shell logcat > debug.log

This will dump all output to this file. Run the app, hit OK on the crash. Break the dump (ctrl-c) and send the log file.

If you don't have ADB set up you can use something like aLogcat (https://play.google.com/store/apps/details?id=org.jtb.alogcat). Install and start that. Same as above, run the application and let the clock app crash. Go back into aLogcat and send the log (can reach me at gmail, krohnjw) or attach it here.
[Galaxy S III Q&A, Help & Troubleshooting] adchesney:
Email sent with attachment...I hope I've done it right.

ANDREW
[Galaxy S III Q&A, Help & Troubleshooting] krohnjw:
You did, thank you. Now to see if I can get it sorted out. If anyone is curious here's the exception that's causing some perfectly valid code to crash on this device.

E/AndroidRuntime( 4529): FATAL EXCEPTION: main
E/AndroidRuntime( 4529): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.sec.android.app.clockpackage/com.sec.android.app.clockpackage.alarm.HandleSetAlarm}: java.lang.NullPointerException
E/AndroidRuntime( 4529):	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1970)
E/AndroidRuntime( 4529):	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1995)
E/AndroidRuntime( 4529):	at android.app.ActivityThread.access$600(ActivityThread.java:128)
E/AndroidRuntime( 4529):	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1161)
E/AndroidRuntime( 4529):	at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 4529):	at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 4529):	at android.app.ActivityThread.main(ActivityThread.java:4514)
E/AndroidRuntime( 4529):	at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 4529):	at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 4529):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:993)
E/AndroidRuntime( 4529):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:760)
E/AndroidRuntime( 4529):	at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 4529): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 4529):	at com.sec.android.app.clockpackage.alarm.HandleSetAlarm.onCreate(HandleSetAlarm.java:54)
E/AndroidRuntime( 4529):	at android.app.Activity.performCreate(Activity.java:4562)
E/AndroidRuntime( 4529):	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1053)
E/AndroidRuntime( 4529):	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1934)
[Galaxy S III Q&A, Help & Troubleshooting] Game4set:
Hey krohnjw! Were you able to figure out the issue and a work around? I also have an app that sends an alarm intent and I'm hearing issues from users with Samsung devices (it works perfectly on all other devices) and I can't really pinpoint the issue (I only have a Galaxy Tab 10.1). One user told me that he has a Galaxy Note With ICS 4.0.4 (Touchwiz) and one person wrote a review saying that the app was being funky on his GSIII with the preinstalled alarm app anddd I got a ANR report from a GT-I9100M (which after a quick Google search shows that it's a GSII) . This is pretty confusing and a bit frustrating since I don't have the issue right in front of me. Hopefully you can shine some light on this issue :/
[Galaxy S III Q&A, Help & Troubleshooting] krohnjw:
yeah. Send me a pm. I'm a bit busy tonight but I can send you over the relevant info by tomorrow evening most likely.
[Galaxy S III Q&A, Help & Troubleshooting] Game4set:
PM sent!
[Nook Color Q&A, Help & Troubleshooting] mateorod:
Well, my Nook appears to be in trouble.

The long and the short of it is that it got wet. Not too wet, but wet.

It boots but whatever I boot to crashes. This includes sdcard installs. The ROM completes the boot, and I can sometimes even open the app drawer, but it crashes before I can interact with it in any meaningful way.

All ROMs complain of "System process" and Wireless issues, with FCs.

I cannot get adb to recognize the device anymore. lsusb does find the Google Inc. entry, though. When I try and run adb devices (ubuntu), it returns ?????? and says insufficient permissions. I have, in response, set up the 99-android.rules in etc/udev/rules.d but it still cannot connect. I have also tried to quickly access the android terminal in the brief period I am allowed before the device crashes with no luck. My goal with this was to try fdisk -l.

The sdcard never mounts while in the ROM, and the emmc storage appears completely wiped.

However, I was able to see I had the correct files in /rom once, so those are there.

Thinking that the wireless chip might be the problem (as when even when I return to stock the set-up fails there, well, until it crashes again...) I tried to just turn off Wifi in 7.2. But as I unchecked the box, right under the setting just displayed "error"

CWM appears to be working EXACTLY as it should, including mounting the sdcard and allowing me to choose update zips.

The uboot and the uboot menu work as well.

I have tried flashing CM7, 9 and stock, as well as booting from sdcard in CM9. All flash and boot normally, but crash.

I have done the 8x reboots, succesully, but when the B&N set-up begins, I cannot connect to wireless. Which would be okay, in the long run, but it then crashes, which is not okay.

I was hesitant to reveal that it got wet, because I can see this being written off as a hardware issue (which it may be, don't get me wrong). But the fact that CWM works and the ROMs boot sure look like software problems to me.

I have tried flashing just about everything that looked promising. I have not dd any images, because I cannot get adb to work, and don't have any idea which partitions are in what shape.

Any suggestions?
[Nook Color Q&A, Help & Troubleshooting] MISRy:
Position the unit upside down with the SD flap open. Blowdry it from the bottom up on medium several times over a couple of days. If it's still doing it after that you can probably eliminate moisture as a cause.
[Nook Color Q&A, Help & Troubleshooting] dparrothead1:
old cell phone trick

Fill a bowl with rice (uncooked).....the rice will draw the moisture out.
[Nook Color Q&A, Help & Troubleshooting] DizzyDen:
you can also submerge it in ispropol rubbing alcohol... is what we use to clean electronic components... it will combine with the water... also used for water in gas on a car ;)
[Nook Color Q&A, Help & Troubleshooting] mateorod:
Whoa, isopropyl alcohol. I feel like that would take some stones...

I have already put it through a 30 or so hour rice regimen (if that is true, even. It makes some kind of weird intuitive sense, which is usually the kiss of death...)

I have it standing up now and will see about a little air dry method while I investigate where to find the alcohol.

It didn't get submerged, it was lying on a counter and a glass got knocked over. I grabbed it right up, and then left it off like I said.

It boots, CWM works, but since it has been set all the way back to stock and all iterations have the same issue I am fearing the worst...

Thanks for the ideas...any and all welcome!