Develop Bugs

Notificationcenter

How do I get my notificationcenter to look a bit like this instead of having a toolbar with standard 5 icons(wifi,bluetooth,gps,autoupdate and brightness)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Get JB 4.2.

joooe said:
Get JB 4.2.
Click to expand...
Click to collapse
I thought 4.1.1 had it too.
I'm stock and not very experienced to install a rom from here, seems very difficult.
I hope 4.2 soon comes from Google.

peterv6 said:
I thought 4.1.1 had it too.
I'm stock and not very experienced to install a rom from here, seems very difficult.
I hope 4.2 soon comes from Google.
Click to expand...
Click to collapse
A. It's the opposite of difficult. If you can read you are more than capable of flashing a rom.
B. 4.2 already came from Google. Where did you think it came from? Apple?

063_XOBX said:
A. It's the opposite of difficult. If you can read you are more than capable of flashing a rom.
B. 4.2 already came from Google. Where did you think it came from? Apple?
Click to expand...
Click to collapse
I read quiet well but I also read about how people brick their phones cause something goes wrong.
I mean an official one that I download and update thru my phone.

Well the official one has come from Google as well so if you haven't got it, chances are that your phone is updated by Samsung instead

mortenmhp said:
Well the official one has come from Google as well so if you haven't got it, chances are that your phone is updated by Samsung instead
Click to expand...
Click to collapse
Why does Samsung update the nexus as well as google?
We all have the same phone don't we?
I have android 4.1.1 and no update if I search.
Strange why we don't get the 4.2 all at one's?

peterv6 said:
Why does Samsung update the nexus as well as google?
We all have the same phone don't we?
I have android 4.1.1 and no update if I search.
Strange why we don't get the 4.2 all at one's?
Click to expand...
Click to collapse
Obviously you don't "read quiet well" if you have to ask. There are multiple variants of GNex, each dependent on a different provider for the update (Google, Samsung, Sprint and Verizon).

Just got jellybean OTA!!!

I checked in settings and there was an update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Zehlek said:
I checked in settings and there was an update
Click to expand...
Click to collapse
same here in montreal

i think we checked at the exact same time =)
was just about to post this!
edit:
on Telus

Its a pity you didn't check all the other threads that already mention this

pngface said:
Its a pity you didn't check all the other threads that already mention this
Click to expand...
Click to collapse
Hahahahah I was thinking the same thing lol
sent from my Nexus 7 while my SGS3 rests!

I guess the mods will take care of removing some of these threads

Sorry. You can delete. I didn't notice the other thread

Zehlek said:
Sorry. You can delete. I didn't notice the other thread
Click to expand...
Click to collapse
I'm yet to see a OTA for AT&T
I want to upgrade through recovery mode without rooting.
I have the i747 (not the i747M)

pngface said:
Its a pity you didn't check all the other threads that already mention this
Click to expand...
Click to collapse
Mods: can we have a "meh" button in addition to the Thanks button?

Anonymously_Unknown said:
I'm yet to see a OTA for AT&T
I want to upgrade through recovery mode without rooting.
I have the i747 (not the i747M)
Click to expand...
Click to collapse
For att the update is through kies i got an email from samsung saying that the update was not a ota
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Anonymously_Unknown said:
I'm yet to see a OTA for AT&T
I want to upgrade through recovery mode without rooting.
I have the i747 (not the i747M)
Click to expand...
Click to collapse
1.) Download and install Samsung Kies
2.) Plug your phone in.
3.) If you are on stock, Kies will notify you that you have an update available.
4.) Happy Flashing.

Please discuss the receiving of JB in the sticky thread
Thanks
FNM

new update from ATT

My S3 android version 4.1.1 ,I got a notification for ATT software update, my phone stock firmware and rooted , should I update thru ATT and if I update would my phone no longer rooted??? Thanks

Tonyng said:
My S3 android version 4.1.1 ,I got a notification for ATT software update, my phone stock firmware and rooted , should I update thru ATT and if I update would my phone no longer rooted??? Thanks
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. Put this in the Q&A thread.
2. This update came out months ago.

It's is just show up on my phone

Got the notification too but phone is unsuccessful on trying to upgrade from 4.1.1.
FWIW, I have the TWRP 2.5.0.0 bootloader and an unlocked/rooted stock ROM and the phone downloads 200+ MB of data and then reboots into TWRP. I then ask it to reboot into the system when it says the upgrade failed and boots me into 4.1.1 again.

I also just got the notification today.
I had previously had the 4.1.1 rooted stock ROM (the one that didn't trip the Flash counter) and was wondering if there was one for this update too.

unmesh59 said:
Got the notification too but phone is unsuccessful on trying to upgrade from 4.1.1.
FWIW, I have the TWRP 2.5.0.0 bootloader and an unlocked/rooted stock ROM and the phone downloads 200+ MB of data and then reboots into TWRP. I then ask it to reboot into the system when it says the upgrade failed and boots me into 4.1.1 again.
Click to expand...
Click to collapse
dragonx254 said:
I also just got the notification today.
I had previously had the 4.1.1 rooted stock ROM (the one that didn't trip the Flash counter) and was wondering if there was one for this update too.
Click to expand...
Click to collapse
if you need to update either go with customs roms with the same version but debloated, fixed and works really great or download the samsung stock firmware with Odin and you will go back to real stock with everything bloated and No ROOT

[Q] 4.1.1 vulnerable to Heartbleed, update options?

Both my S3 (SGH-i747M) are still on original 4.1.1 and since they have been working wonderful for me (if it ain't broke, don't fxt it, right?)...plus I don't do much with my phones.
After reading about the Heartbleed Vulnerability in 4.1.1, I'm thinking of updating to 4.1.2 instead of of the latest 4.4.2, but before I do that, can I get confirmation that:
1) from 4.1.2, I can go back to stock 4.1.1 100% for sure using Odin
2) Once updated to 4.3 or 4.4.2, there is NO way to go back to 4.1.1 due to both 4.3 and 4.4.2 have different bootloaders ?
3) if updated to 4.4.2 and since there is no way to downgrade to 4.1.1, the other option would be to use "CyanogenMod" as the last option, correct?
Thanks.

1) Yes, you can go back to stock 4.1.1 from stock 4.1.2 using Odin. I recommend doing this so you can take advantage of the free unlock method.
2) Yes, once updated to stock 4.3 or 4.4 bootloader, you cannot go backwards. Also, you can brick your phone if you attempt to load a 4.4 modem on a 4.3 bootloader.
3) CM ROMs must support your installed bootloader and modem.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
audit13 said:
3) CM ROMs must support your installed bootloader and modem.
Click to expand...
Click to collapse
Thanks audit13, you are great!:good:
For the 3) CM ROMs must support your installed bootloader and modem, I have all four Koodo 4.1.1/4.1.2/4.3/4.4.2 (pix attached), are these all OK for CM ROM?
Thanks.

Last time I checked, 4.1.2 bootloader worked fine with CM 10 and I think with CM11. Keep in mind that Cm10 had some issues with some apps and the front facing camera (never had an issue with Skype) as well as Bluetooth being flakey. Read up on it and try it out. You can always revert back to stock if it doesn't work out.

If you are concerned about Heartbleed you should check if 4.1.2 is vulnerable too. Its a pretty old build and i think we were already on 4.3 by the time it became a known vulnerability. I could be mistaken though, but you should check into it if that's a concern.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

Matt_7 said:
Thanks audit13, you are great!:good:
For the 3) CM ROMs must support your installed bootloader and modem, I have all four Koodo 4.1.1/4.1.2/4.3/4.4.2 (pix attached), are these all OK for CM ROM?
Thanks.
Click to expand...
Click to collapse
Some of the newer d2lte builds may need the latest bootloader to work. You can determine which bootloaders are supported by downloading the ROM, unzipping the ROM, and open the updater script in Notepad. The first few lines of the script will list the bootloaders that are supported.

Latest OTA for AT&T?

I am still stuck on firmware 1.58 due to S-ON and I thought AT&T was rolling out an update to Android 4.4.4 but my phone can't find it.
Does anyone know why or how to update the firmware to something newer if I have S-ON? Thanks.

AvatarOfFrost said:
I am still stuck on firmware 1.58 due to S-ON and I thought AT&T was rolling out an update to Android 4.4.4 but my phone can't find it.
Does anyone know why or how to update the firmware to something newer if I have S-ON? Thanks.
Click to expand...
Click to collapse
download the HTC Sync software and try doing a manual update. or you can just wait until the OTA gets pushed.

AT&T canceled the KitKat OTA because it was messed up. Not sure on the details, but I believe battery life was significantly worse.
Personally, I dumped AT&T's image and switched to the Developer Edition, and I've never looked back. However, if I needed to run AT&T's crap, I'd avoid their KitKat OTA and pray that they finally get around to releasing a Lollipop OTA instead.

jshamlet said:
AT&T canceled the KitKat OTA because it was messed up. Not sure on the details, but I believe battery life was significantly worse.
Personally, I dumped AT&T's image and switched to the Developer Edition, and I've never looked back. However, if I needed to run AT&T's crap, I'd avoid their KitKat OTA and pray that they finally get around to releasing a Lollipop OTA instead.
Click to expand...
Click to collapse
HTC hands over technically approved code to AT&T they can load their bloatware crap on it. AT&T takes code informs everyone update will role out the next day, loads bloatware...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OTA pulled Back technical difficulties.

jshamlet said:
AT&T canceled the KitKat OTA because it was messed up. Not sure on the details, but I believe battery life was significantly worse.
Personally, I dumped AT&T's image and switched to the Developer Edition, and I've never looked back. However, if I needed to run AT&T's crap, I'd avoid their KitKat OTA and pray that they finally get around to releasing a Lollipop OTA instead.
Click to expand...
Click to collapse
Can I switch to the developer edition if I have S-ON?

AvatarOfFrost said:
Can I switch to the developer edition if I have S-ON?
Click to expand...
Click to collapse
No.