yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Nexusaurus:
So far, I think that this new update (JB 4.3) bring some small performance boost, small but some at least.But I have two ongoing issues that bother me and I wonder if only happens to me or they are common issues among GNex 4.3 users. My GNex is running pure AOSP with no root or any other modification, just pure Google experience.

The first one is when you have many apps running, 5 or more, and you press the multitask button and a black line appears up in the screen. When you swipe the apps to close them, the black line goes down until it disappears. It seems is some kind of display glitch. My screen was OK before the update and in fact, my screen has no dead pixels or something, the black line just appears within this scenario. I encourage you to try a replicate this bug whenever possible.

The second one is about the stock SMS app,which appears to drain a lot of battery juice because is the second process consuming more battery just after the screen. The thing is that I barely use the SMS app as I have Whatsapp installed and I have no need of another SMS client. In fact, I use Whatsapp extensively and that process is one of the last using battery juice. I remember perfectly that the stock SMS app didnt appear in 4.2.2 or prior. I'm not a programmer but I have a vast knowledge in gadget and electronics in general, as I have a degree in Engineer in Computational Systems and Electronics. I said this because you can be completly sure that I know this is not some kind of misconfiguration or some app misbehaving. This is something that the Android system itself is causing.

Thanks in advance for your time and I hope these bugs ( so far) are being replicated and can be solved.
[Samsung Galaxy Nexus] madd0g:
Messaging app is draining because of some rogue MMS. Factory reset helps. As a matter of fact, you'll have rarely issues if you factory reset after any update.
[Samsung Galaxy Nexus] furious78:
I think I'm seeing the display glitch you are talking about. I'm running a custom ROM with 4.3, and with the Quick Settings mod, when I pull down, I'm seeing the quick settings glitch into this black line as it changes into the standard notification area.

---------- Post added at 03:58 PM ---------- Previous post was at 03:53 PM ----------

I'd say another major bug seen across many 4.3 ROMS is data dropping. Blue bar turns gray when switching networks, and you end up having to wait for it to come back or toggle airplane mode.
[Samsung Galaxy Nexus] tomktsang:
I can't install any APK files after the update....
[Samsung Galaxy Nexus] DroidOnRoids:
Did you enable Unknown Sources under Security?
[Samsung Galaxy Nexus] madd0g:
PUBLIC SERVICE ANNOUNCEMENT : It's not a bug, if it's happening to YOU and not many others.
[Samsung Galaxy Nexus] Nexusaurus:
Well, thats why I'm asking.

Besides, my WiFi connection is behaving weird, because in 4.2.2 my WiFi radio was active all the time, even when my screen was in sleep mode, but now if I leave my phone in sleep (locked screen) after few minutes, the WiFi signal drops. The same for when I get over my house back from work, my WiFi doesnt automatically connect when my phone is in sleep, just after I unlocked. Even sometimes I have to go to the WiFi settings to force a restart on the WiFi radio and only then I connects.

This wasnt happening in 4.2.2 and I havent installed or uninstalled apps. Like I said before, I'm running stock AOSP just as Google intented.
[Samsung Galaxy Nexus] rbrenart:
Non-working apps

Anyone keeping a list of apps that don't run in 4.3 somewhere, or would that be ROM specific?

I'm having trouble with

Evernote

Need for Speed: Most Wanted

Music widget on lockscreen

HBO Go
[Samsung Galaxy Nexus] Sharks8:
Still having the stock browser bug when using fullscreen mode. It bothers me, Quick controls is so great and the browser really smooth

Envoyé depuis mon Galaxy Nexus en utilisant Tapatalk 4 Beta
[Samsung Galaxy Nexus] xdabilly:
Did you turn on WIFI Optimization?
[Samsung Galaxy Nexus] sl4y3r88:
Having the same issue..Well, the dropouts while the phone was asleep were there in 4.2.2 due to the ARP offloading issue that still not fixed. But as you mentioned "my WiFi doesnt automatically connect when my phone is in sleep, just after I unlocked. Even sometimes I have to go to the WiFi settings to force a restart on the WiFi radio and only then I connects" That's something new in 4.3 and its annoying!!
[Samsung Galaxy Nexus] Matteo Mit.:
Not alone yet!

For your problem, see (and give your vote) here: https://code.google.com/p/android/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars&groupby=&sort=&id=58230
[Samsung Galaxy Nexus] NCguy:
Stock 4.3

Add:

Chrome

Chrome beta

Voice dialer using bluetooth
[Samsung Galaxy Nexus] Bruce777:
I'm getting data drops too.
[Samsung Galaxy Nexus] furious78:
What kinds of issues with Chrome? Chrome is working fine for me.

---------- Post added at 10:27 AM ---------- Previous post was at 10:22 AM ----------

I'm curious if you're running toro or maguro. I've seen lots of reports of data dropping on stock-ish custom roms for toro, but then I think I saw mention of a stock maguro install having data drops. If the latter is the case, then Google dropped the ball here with drivers somehow.
[Samsung Galaxy Nexus] Nexusaurus:
This is what I meant. i just took a screenshot a few minutes ago.

This happens only when the running apps are far more that the size of the screen, then when you swipe them to star closing, a black bar appears over the upper app thumbnail but quickly disappears

EDIT: it seems that this doesnt only happens to me.

http://www.youtube.com/watch?v=f4M9GFoxUN8

EDIT 2: This a known issue it seems. This post in WWW.ANDROIDCENTRAL.COM by some user seems to have the very same issue too.

http://forums.androidcentral.com/google-nexus-4/302383-4-3-recent-app-bug.html

At least I already know that this is happening to other people too, but I would want to know if this is posted in the official bug reporting forums by Google. I dont know how confirm this, and I hope some experienced user here can help us and check this out please.
[Samsung Galaxy Nexus] NCguy:
I'm on stock 4.3 and am having two problems. First the voice dialer has reverted back to where it doesn't understand names any longer using bluetooth. Secondly, I can't run chrome or chrome beta very long before my device gets wonky and I must reboot an/or clean cache. For some reason Chrome actually messes up my wifi to where the wifi will hang up, run slow and eventually not pass data. Chrome beta eventually loses the function of the chrome back key. Firefox seems to work without issues on 4.3 but I far prefer chrome when it works.

BTW, I just got a new Nexus 7 on 4.3. Chrome seems to run great on that platform.

---------- Post added at 08:26 PM ---------- Previous post was at 08:14 PM ----------

Should also add, bluetooth seems to be really impacting wifi now when they are on together. My speed tests are cut by at least 50% and look like the rocky Mountains when bluetooth is also connected. Reminiscent of the early days of android. Must be something to do with BT low energy?
[Samsung Galaxy Nexus] Nexusaurus:
People having this issue can star the tracking bug report from Google here:

https://code.google.com/p/android/issues/detail?id=58872&thanks=58872&ts=1376282625
[Samsung Galaxy Nexus] krialix:
micro lag

while i was using stock 4.3, settings menu has a micro lag (scrolling down is a bit laggy) :confused:
[Samsung Galaxy Nexus] Wolfglance:
Reply deleted.
[Samsung Galaxy Nexus] mjmauro484:
I also can not download HBO go from play store. I haven't tried to find a version on xd stripa and Anyone keeping a list of apps that don't run in 4.3 somewhere, or would that be ROM specific?

I'm having trouble with

Evernote

Need for Speed: Most Wanted

Music widget on lockscreen

HBO Go

yet.

B.
[Samsung Galaxy Nexus] blackhand1001:
Yeah. Its in cyanogenmod as well. Something is locking up the main thread for the app for a moment.

My biggest issue is the WiFi auto scan issue.
[Samsung Galaxy Nexus] Ed V:
For the wifi problem try this...

http://xdaforums.com/showpost.php?p=45330625&postcount=22

.
[Samsung Galaxy Nexus] blackhand1001:
Its not that it won't connect or drops connection. The phone doesn't autoscan after going into deep sleep even after waking up. It won't scan again until you open the WiFi network list or toggle WiFi off and on.
[Samsung Galaxy Nexus] Ed V:
It looks like I have 2 wifi problems than, the grayed out and the not automatically switch from data to wifi when i come home, i have to do the same as you, toggle wifi off and on again otherwise it stays on data, i'm gonna test that link today and hopes it works :)

.
[Samsung Galaxy Nexus] Ed V:
Well, it didn't work :( I think we have to wait till google comes out with a fix.

.
[Samsung Galaxy Nexus] Vekhez:
Was having some Wi-Fi issues. Reflashing the radio fixed it for me!
[Samsung Galaxy Nexus] Cnoxs:
Guys for now I have not found bug :p .
[Samsung Galaxy Nexus] shadowam:
No bugs for me too
[Samsung Galaxy Nexus] DarkFox002:
I flashed both version of 4.3 when they came out, I also did a factory reset because I was having some issues.

In my area I roam on 2 different GSM networks after 4.3 I would have no Data when roaming (bars were greyed out too).

I looked up issues with 4.3 and saw that people were flashing 4.2.2 radio on to the Nexus 4's so I followed the instructions but used Galaxy Nexus radio for 4.2.2.

This fixed my issue, to bad I didn't see any warnings that turning my Nexus to unlock mode in fastboot would also wipe it.
[Samsung Galaxy Nexus] NCguy:
I would say you are very lucky unless someone very reliable told you it was ok to flash a radio from another phone. From my understanding, this is a common way to permanently brick your phone.
[Samsung Galaxy Nexus] tshelby73:
When I first got my used Verizon nexus I flashed the normal radios for my cdma radios when returning to stock. everything worked fine but no signal. So flashing wrong radio not necessarily cause a brick. Felt like an idiot with the Verizon guy trying to get it connected.
[Samsung Galaxy Nexus] NCguy:
No it won't necessarily do it, its just one of the more common ways it happens.
[Samsung Galaxy Nexus] DarkFox002:
No I found the radio for my phone version and used that one instead of the one in the instructions for Nexus 4.
[Samsung Galaxy Nexus] NCguy:
Ahh. For some reason I thought your meant you had an N4. Sorry about that.
[Samsung Galaxy Nexus] djboi2011:
anyone thought about integrating aokp ribbons with halo? meaning, when you launch an app from ribbons it opens in windowed mode?
[HTC Amaze 4G] steve1041:
I was considering rooting my HTC amaze and am new to all this. What's the best and easiest way? Also, does this affect if I want to trade my phone in on an upgrade? Thanks for all the possible help.
[HTC Amaze 4G] SuperAfnan:
Hello!

Well then best way to root in my opinion is to use hasoon2000's toolkit in the development section of the amaze.

If you need to return your amaze or trade it, I would suggest unrooting it by flashing a RUU. A RUU brings your device back to stock. Stock basically means 'unmodified'. Right now you're on the stock rom.
[HTC Amaze 4G] sam@xda29:
[/COLOR]

+1

---------- Post added at 06:49 AM ---------- Previous post was at 06:45 AM ----------

To root your phone use hasoon's aio toolkit.

And than unlock your bootloader through it .

After flash 4ext touch recovery and than flash supersu to gain root access !!

And ya to unlock your bootloader you'll need unlock_code.bin which you will get from htcdev.com.

Go there and unlock your bootloader !!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheelzz:
I own a i747M Galaxy S3 on the Rogers network, and I'm interested in rooting my device to install CM 10.1 ROM. I would like to clear up my questions and concerns fully before attempting something that if preformed wrong, could damage - or fully brick - my device.

A few of my XDA resources:

SIII ROOT/ROMs/TOOLS

Noobs Guide to Root, Flash, and More

Stock ROM Firmware

Questions &/or Concerns:

In regards to the Firmware downloads: Which download do I choose under the Rogers section in order to get the complete factory image of the Rogers S3?

Is it worth it to do the CWM method that avoids triggering the Flash Counter?

More questions will likely come as I remember.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
From one of your links to install rogers firmware pre rooted, you want this firmware which was the first from Rogers section http://www.androidfilehost.com/?fid=23017610006234402

Here is where you can download the 4.1.2 rogers stock un-rooted firmware. The first one labeled RWC is for Rogers Wireless. http://samsung-updates.com/device/?id=SGH-I747M

Personally I do not worry about the flash counter because you can install 'Triangle Away' and reset the counter from here http://xdaforums.com/showthread.php?t=1494114
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheelzz:
So the link that I labelled stock ROM is actually for rooting?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
No, that's just for getting back to stock. In your first link S3 root rom.... you have a forum that had. ' no tripping flash counter'. This is stock firmware with root injected already. If you flash that with odin, you will have root. http://xdaforums.com/showthread.php?t=1739426
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheelzz:
Oh, thanks. Should I just use the Samsung link for the stock ROM? In my link it has like 3 different files under the Rogers section. Is that root a good one? I am not sure if there are different roots.

Is flashing a rooted file with oden the best way to root?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
The absolutely simplest way for you to get root is to flash this in odin.

http://download.chainfire.eu/269/CF-Root/CF-Auto-Root/CF-Auto-Root-d2can-d2vl-sghi747m.zip

It will give you root access without reinstalling the whole rom. If you want instruction on how to use this file, here is the source link. http://xdaforums.com/showthread.php?t=1963790.

After installing this you can download Rom Manager from the play store to install CWM

At this stage don't worry about your flash counter. You can reset it to 0 later.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cwarep:
AT&T GS3 memory problem

I hope I'm putting this in the correct forum on this website. If not will someone guide me to the right place?

After rooting my AT&T GS3 and loading lots of apps and doing backups, I noticed it was running out memory. When viewing the Storage and available space on the phone it indicated the bulk of memory was taken up by "Miscellaneous files". I connected the phone to my computer and with Windows Explorer navigated to my phone. Once there I saw, as I suspected, it appeared the problem with my phone's internal memory being almost all used up was because I had done way too many backups, some with the phone's backup and some with other apps with backup capabilities. Figuring I could take care of that easily enough, I used my computer's Eraser program I erased several of the older backups. After disconnecting the phone, rebooting, etc. I went into the phone's Settings & Storage to see how the memory then looked. The phone shows that I now have Available space of 8.43 GB, because the Miscellaneous files space went down from about 11GB to 2.03GB. Here's my problem... even though the phone Storage indicates I have all kinds of available memory, I get errors when existing apps try to download updates to apps and some new apps telling me there is not enough memory available. Short of restoring the phone to pre-rooting and then having to reload all my apps and re-root, is there a way (using CWM or other) to get the phone to re-recognize the available memory? If someone could give me a link to where to answer is I would be very grateful
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
If you have successfully installed CWM, try wiping cache, and then wipe dalvic cache. Dalvic cache is in the 'advanced' section under wipe menu. This will force android to reload all the app memory and may fix your issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheelzz:
If I want to root in order to run custom ROMs such as CM, should not use auto root?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
All root is created equal. You can use auto root for any rom. Stock or CM10. If you use the auto roor method that I suggested you will not have issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheelzz:
Do you know a good download for Google Apps?

Thanks, will reply back later with any issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
This Gapps package has all the Google apps for Android 4.2.2. You would flash this after installing CM10.1

http://goo.im/gapps/gapps-jb-20130301-signed.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheelzz:
That package should work fine for the latest stable version of CM 10.1 for my device, correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
Yes sir, that is correct. When you click that link you will see the info for it stating that it is the Google apps for 4.2.2 which is CM10.1

You can also see this link for confirmation. http://wiki.cyanogenmod.org/w/Gapps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cwarep:
Wiping caches

Thanks BCSC for the assistance. I did a wipe on both caches, but after re-boot the phone still gave me memory errors when apps tried to update. But that's OK, because I installed another backup from my external SD card (1 of 4) and it looks like the memory problem went away. I was going to go through a re-install of each of backups to see if I happened to have made a rooted one before the memory filled up. I got lucky because the first backup on the list did the trick. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheelzz:
Is ODEN 3.07 the latest?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheelzz:
Oh, my bad, the auto root includes a custom Odin for the auto root.

I am just wondering, what's the difference between using the auto root and using normal odin such as the method in the noobs root guide? More steps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheelzz:
As for installing CWM through ROM manager: it prompts me to select my device and the only S3 there is MetroPCS.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
Press menu button and you will see 'show all devices.' You will find it in there
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheelzz:
I think I am just going to start over. Although, I flashed that stock link you sent me earlier, and I still have superSU.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
Why are you starting over? You can find your device by pressing the meny button and opening menu saying 'show all devices'
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheelzz:
Well, I flashed that kernal to unroot, although it appears to still be rooted (superSU).

Another problem, I flashed CWM through odin (which turned out to be old, 5.5) and the installation of CM 10.1 kept failing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
To update to CM10.1 you need the latest recovery. You can update it through Rom Manager or by using the process in post 6 in the following link. Rom Manager is your easiest way but the link will give you the touch version of recovery.

Post 6 for touch recovery http://xdaforums.com/showthread.php?p=43604963#post43604963

Here is where you can download the latest Touch recovery. http://www.clockworkmod.com/rommanager
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheelzz:
So if I download from that site instead of the app, I update it as in the root guide? If I use the app, I can just update the normal version?

As for root/superSU - is it possible that the kernal flash did actually un-root my device, and the superSU program stays installed in a deactivated state?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheelzz:
I installed and flashed the newest CWM through ROM manager and now my phone boots, shows a samsung logo than stays on a black screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
Enter CWM and you can either wipe data/factory reset, or attempt to install CM10.1 if you have already put the file for it on the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheelzz:
how do I boot into it from the phone (I used ROM manager with the old version)? The Power+Vol Down+Home just puts me into download mode.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
Power + vol UP + home will get you into recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheelzz:
Does the same thing: Vibration, samsung logo (with some breif blue text in the upper left corner of screen) and than black.

EDIT: Text appears to say recovery booting.

EDIT2: Even when I try to boot normally or DL mode, the phone does the same thing (including the blue text).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
If you can not get it into recovery mode or boot, your option is to re flash stock in Odin via download mode and try again. Keep trying, you'll get it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheelzz:
I cannot get into DL mode. Damn, I'm screwed.

EDIT: Finally managed too get into DL mode. So I should flash the kernal file from that samsung updates site?

Also, is it fine if I flash the stock files with the autoroot version of ODIN?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
Yes. Odin flashing the stock image from samsung-updates will work. You will not need to auto root.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheelzz:
I was meaning could I use the version of ODIN that is supplied with the download of the CF auto Root to flash the stock kernal? It seemed to work. I have my phone running and CWM 6.0.3.1 running, I get an error (Status 7) when trying to install CM 10.1.2 zip from my external SD card.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
Status 7 is usually an indication of an incompatible rom. Try flashing this CM10 zip in recovery http://get.cm/get/jenkins/36976/cm-10.1-20130805-NIGHTLY-d2att.zip. As for your other question, Odin 3.07 is what I use for any flash. I dont remember exactly which one is included with Autoroot.

Here is something I found about the status 7 error. http://highonandroid.com/android-roms/how-to-fix-status-7-error-with-cwm-recovery-on-rooted-android/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheelzz:
Yeah, I figured that out via this article on XDA, and I'm now happily running Android 4.2.2 via CM 10.1.2. I should be fine, right? Why does that problem arise when I used the file that is designated to work with Rogers, AT&T, etc devices?

What is a good way to back up my entire installation in case a future install goes wrong and I don't want to start fresh?

Thank you for all the help dealing with my (noob) issues, many thanks have been given (literally, I maxed out the daily limit)!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BCSC:
Glad to hear that you got it. I'm not entirely sure why it sometimes doesn't work. Its a bit funny. You're good to go now. The safest way for you to back everything up is in CWM you will see an option to backup/restore. What you want to find is the Backup to External SD option. This way even if you somehow mess up and have to wipe your internal SD, you will have a back up that stays un harmed. You also have the option to restore via external. Happy Roming. Here's your first thanks as well. Welcome to XDA!