yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Realmprotector:
Technically by rooting or flashing a custom ROM you have voided your warranty but by restoring it back to stock ROM they shouldn't notice that anything has been modified assuming you are using the correct ROM for your country / mobile provider and device and it's been unrooted.
[Android Q&A, Help & Troubleshooting] ganeshrnet:
Re: How to retrieve warranty of samsung galaxy pro before giving for service

Sir,

Thank you for your reply. But my question is is there any sort of flash counter in this handset model? if so how can i reset it?
[T-Mobile Samsung Galaxy S II SGH-T989] PsychoKilla666:
Hi, I am wondering if it is possible to rip the tiny Google Now app from the Optimus G as well as their QuickMemo integration. I am guessing the QuickMemo might be bound to the OS though, just like so many Sense features are for HTC.

On that note do any Devs know if it is possible to port LG ROMs to Hercules or is this pretty much impossible like with Sense?

http://www.viddler.com/v/87263024?secret=55663590
[Android Q&A, Help & Troubleshooting] 98Slowstang:
Im in the process of looking for a android tablet but all of the ones i seem to see use a different ipod style charger for them, unlike most of the android phone's where a micro-usb is used. I was just wondering if anyone knows any good android tablets that use a micro-usb as a charger and not just for data transfer.
[Android Q&A, Help & Troubleshooting] kr0n1c:
AFAIK Nexus 7 is the only one that uses micro usb
[Android Q&A, Help & Troubleshooting] 98Slowstang:
thank you for the answer i guess i will just have to take one with a different charger as i like the nexus 7 but i dont like the fact that it doesent have a memory card slot
[HTC One S] Sinistah_:
Last night I experienced this problem when automatic backlight wasn't on. Now today its not turning on at all. I has called t mobile and they had me reset my phone and it fixed it. Rhett said it was a software problem. Now, I wake up this morning ans its just off...

I received this phone through the insurance.

I would just call it quits, and get another but I already rooted the phone.

Is there a way to fix this? Should I flash Rom to see it it'll fix this problem since supposidly its a software issue?

And if its just my phone how do I unroot it properly...

Or do I need to since it is a hardware problem

Also can I master reset my phone without messing it up if its rooted
[HTC One S] HidaKureku:
if you have to reset, do it through the custom recovery you installed. and i would try a custom rom first, just to see if it is software. but since insurance claim phones are refurbs 90% of the time it is possible that it's hardware related
[HTC One S] Sinistah_:
So how would I go about sending it back if its hardware related. Do I unroot n send back
[HTC One S] el_smurfo:
Are you sure that it's just not dark enough? Try covering the black area above the screen with your finger...mine light up.
[HTC One S] HidaKureku:
or just turn off the auto brightness. i have mine off and my screen brightness low, gives me about an hour more of battery life. and you can unroot, but it will always say tampered in the bootloader. but if it's hardware related i.e. flashing a custom rom doesn't fix it, then the warranty should still cover it. just flashed the stock rom and relock the bootloader and never mention that it was rooted
[HTC One S] Sinistah_:
When I Turned off auto brightness when I got the phone that's when the problem arrised... It would only work when it was on. I factory reseted my phone and it was fine. Wake up this morning and its not working half the time, it works for now but sometimes it doesn't. I'll try switching roms.

I Turned off auto brightness so it can't be that.
[LG Optimus 2x] weeo:
Hi,

I need some guys with the O2X on ICS CM9 to test my flashable zip. This is a beta and in next release is the Theme.

DO NOT distrubute as its not finished.

Just test and report back of what works and doesnt

http://www.mediafire.com/?d7ji292fzdb5wys - link
[LG Optimus 2x] weeo:
Thanks FettleifIsMyUserName for trying it,

Regarding the theme is will update it with the framworkres from CM9 with a SIII theme on it aswell as SystemUI

THIS IS A BETA TEST. It will be updated again with fixes
[LG Optimus 2x] FettleifIsMyUserName:
theme ?

---------- Post added at 08:21 PM ---------- Previous post was at 08:16 PM ----------

oh sorry looked ver the flashable zip gonna get back to ics and flash :D

---------- Post added at 09:14 PM ---------- Previous post was at 08:21 PM ----------

wow nice wor dude, after a quick test it the bootanimation is really laggy, the samsung sound is working launcher is working great no lag at all :D s voice is there and working kinda. the samsung apps is not there but for now this is realy awesome :D thanks for great work

---------- Post added at 10:06 PM ---------- Previous post was at 09:14 PM ----------

oh little update, the s voice is working perfect now :D

---------- Post added at 10:18 PM ---------- Previous post was at 10:06 PM ----------

oh just tought of something maybe you shuld change the stock wallpaper app too stock sgs3 wallpapers?
[LG Optimus 2x] stefantumi:
The Link does not wirk
[LG Optimus 2x] FettleifIsMyUserName:
because he said when he uploaded it, it would only be avalible in 2 hours
[LG Optimus 2x] weeo:
+1. It will go up officially soon with Beta release for public
[LG Optimus 2x] FettleifIsMyUserName:
when ?, just wondering because i loved the test Version :D
[LG Optimus 2x] weeo:
Next week the latest…
[LG Optimus 2x] FettleifIsMyUserName:
ok thanks for letting me know :D
[LG Optimus 2x] weeo:
Ill give it to you quicker tough for final release testing
[LG Optimus 2x] davibs:
Let me now please guys, this is a rom or a theme?

And if it's a theme for what is it?

It have s voice? ( PLEASE SAY IT HAS WORKING ** )

Thanks!
[LG Optimus 2x] weeo:
Its a add on to any ICS ROM. And yes Svoice works. Its a mod for the SIII apps and soon the framework so your ICS ROM will be themed too. Try it.
[LG Optimus 2x] FettleifIsMyUserName:
it is a flashable zip containing samsung galaxy s3 apps like the launcher s-voice (that works ;D) weather, days and stuff like that (sadly it does not work D: ), all the audio files like lockscreen unlock sound etc and a bootanimation :D
[LG Optimus 2x] davibs:
Awesome awesome!!!
[LG Optimus 2x] hypnos17:
Con anyone post screens? Thanks

Inviato dal mio GT-I9001 con Tapatalk 2
[LG Optimus 2x] FettleifIsMyUserName:
here is launcher with theme from play store :D
[LG Optimus 2x] davibs:
Release date?? **
[LG Optimus 2x] FettleifIsMyUserName:
what do you mean :confused:
[HTC Desire S] poled:
Does this hboot makes more complicated to flash roms? I've read that is not possible to format system/lib, so some roms have to be changed. How to delete system/lib then?

Is it advised to stay on that hboot or should be downgraded or s-off?
[HTC Desire S] FuzzyBlacken:
As far as i know only few latest ICS based ROMs require new HBOOT. I am on Fallout 5.0, worked fine with older HBOOT 6.98.2000 (Revolutionary root)
[HTC Desire S] amidabuddha:
You can stay on that hboot and use 4EXT Recovery to format /system/lib. It will remain empty when you flash a ROM that is not supporting it so there is nothing to worry about

EDIT: I may be wrong, just saw the post in Scanob thread. But you can test it. Make a nandroid backup (and/or put a ROM on the SDcard), wipe /system/lib from recovery and reboot. If the ROM boots then it is true (/system/lib cannot be wiped). If does not boot (then /system/lib is wiped) reboot back to recovery: "adb reboot recovery" - you need USB debugging enabled in ROM and adb drivers on the PC or with the 3 key combo (hold Vol Down + Vol Up + Power) and restore the backup or flash the new ROM
[HTC Desire S] yaonos:
Can anyone confirm that /system/lib can't be wiped or formated with hboot 2.02.0002 ?

I'd like to try the stock ICS update but I'm afraid that the RUU will replace my hboot (2.00.0002 unlocked) with hboot 2.02.0002.
[HTC Desire S] 2009joseph:
htc desire s rooted s-on

==========================================================================================================

hello sorry to bother you

well i have a htc desire s with s-0n rooted with HTCDev.com. hboot 2.00.0002

well i have got cwm and backed up my rom.and flashed others no problem but with loading a rom i had to go into command promps and flash a boot.img. well no problem there as i downloaded roms with a boot.img with them.now i want to go back to my original stock rom and load it it loads ok but when i load the boot.img it dose not work.i got the boot img from the back up that i made of my stock original rom.

please help as i would love to know whar i am doing wrong cheers
[HTC Desire S] yaonos:
Did you try to flash your boot.img in CLI with fastboot like you did when you installed your cutom ROM ?

Edit : Your question has nothing to do with the subject of this thread (Hboot 2.02.0002 ).
[HTC Desire S] Thobber:
The RUU ICS Update installs:

hboot: 2.02.0002

radio: 3831.19.00.110

This also prevents me from updating cause i´m also afraid that rooting and installing custom roms won´t work afterwards.

Is there an opportunity to downgrade from 2.02.0002 to another hboot and install a previous RUU to root it via revolutionary for example?
[HTC Desire S] Pesvardur:
I'm no expert but, I have HBoot 2.00.0002. HTC dev unlocked. And I have had no problem flashing any rom. I have tried Andromadus, Flinny, NK111, Codename android, and I'm currently using Jelly Time R15.0 as my daily use rom.
[HTC Desire S] yaonos:
I'm not afraid of not being able to root my DS after the ICS RUU. I would be able to unlock the hboot again, flash ext4, then install SuperSu from the recovery.

I'm just afraid that the 2.02.0002 hboot will make it difficult for me to install custom ROMs in the future if this hboot restricts effectively the acess to /system/lib. But I would also like to try the new radio of the ICS RUU.

The alternate path I'm considering to follow is downgrading my hboot, S-OFF by revolutionary, flash hboot 2.00.2002, then flash stock ICS using a PG88IMG.zip where hboot and recovery would be removed.
[HTC Desire S] maniche04:
CUSTOM ROM > Stock ICS from RUU > CUSTOM ROM

Had no problem with the Custom Rom installation..
[HTC Desire S] BillGoss:
Yes, this hboot makes it more complicated to flash ROMs because you have to flash the kernel - boot.img - separately using fastboot. But if the ROMs all share the same kernel, then you can skip this step.

The hboot has the extra system/lib partition, but that is only used by the latest stock HTC GB OTA and the HTC ICS RUU. Custom ROMs generally don't use it.

This partition can be formatted, for example using 4EXT, just like the other partitions.

Sent from my Nexus 7
[HTC Desire S] miwanr:
How about flashing RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199476_signed.exe over current Hboot 2.02.0002 with custom ROM?
[HTC Desire S] androvoid:
I personally found that it couldn't flash custom roms without s-off due to being unable to write the /system directory. I had to downgrade the RUU so that I could get S-OFF with revolutionary in order to be able to. If you are upgrading with the ICS stock ROM you won't need to, but you will need to re-lock your hboot to flash the RUU
[HTC Desire S] teadrinker:
Not able to write the /system directory? Never heard that one before...
[HTC Desire S] vrxj81:
Yeah, I have hboot 2.02.0002 with htc dev unlock and I can write to /system without issues.

Must be something else wrong.
[Motorola Photon Q 4G LTE] JavaTiggy:
So I was coming from an EVO 3D and accidentally restored "Wifi Access Points" using Titanium Backup *root and now my wifi wont turn on. If its not too much trouble can anyone please use Titanium Backup to make a backup of this entry and post it here so i can try to restore the stock info to get my Wifi working again? It would be greatly appreciated!!!
[Motorola Photon Q 4G LTE] JavaTiggy:
well i went the long route and reset my device and now i need to restore all my apps again..but wifi is working :)
[Samsung Galaxy Nexus] retskrad:
Hey guys, came across this great article about jelly bean and I wonder what you guys think about it. I really agree with some of the points he makes.

http://www.androidpolice.com/2012/09/18/ux-things-i-hate-about-android/
[Samsung Galaxy Nexus] gbarayah:
Read this article as well and yes he does make some good and valid points. However, Android is still a work in progress according to Matias Duarte. As much as Jelly Bean has improved the user experience there is still a ways to go to polishing the OS.

Here is a good follow up article you might want to check out:

http://www.androidcentral.com/duarte-i-m-third-way-where-i-want-be-android
[Samsung Galaxy Nexus] Cilraaz:
He makes some good points, but also shows that he doesn't seem to understand Android programming at all.

If you open something within an app directly from a widget (his Gmail example), then obviously the back key would go one layer higher within the app. Opening an email from a widget layers home->gmail->email, not home->email.

Also, icons opening the "wrong" app. He uses Maps and Latitude as an example. Well, considering that Latitude is built on the Maps framework (and presumably calls an instance of Maps in order to operate), it makes complete sense that opening Maps would open the active Latitude session when one exists.

Other items just seemed like whining. For example, the section regarding the Google Voice icon. He makes the base assumption that people use it primarily for texting when texting is certainly not the primary function of the app. The app's primary function is voicemail, followed closely by VOIP calling. Texting is easily a tertiary function, even if it has been embraced by the community. [Edit: As mentioned below, I was incorrect regarding VOIP, which would make texting the secondary function of the app.]

Don't get me wrong. There were some good points, but I was shaking my head through a lot of that article.
[Samsung Galaxy Nexus] Zepius:
there is no voip from the google voice app itself. when you make a call with it, it basically calls the GV number + the number you are actually wanting to call.
[Samsung Galaxy Nexus] Cilraaz:
My mistake. I assumed it was VOIP rather than call-chaining, based on the app prompting if Voice should be used for international calls. So at that point, texting would become the secondary function.

Thanks for the info.
[Samsung Galaxy Nexus] qwer23:
Although you are totally right, you have to look at it from a consumer's point of view. And they won't think "hey, of course the back button goes to the underlying Gmail menu", they'll think "wtf.? I was on the home screen before I tapped that mail on the widget. Why did it take me into the Gmail overview now?"

The same is even more true for Latitude. It is obvious for us tech-enthusiasts that Latitude is just more or less a part of maps. But I guess most other people never even give a thought to this, so they're just confused why the Maps icon would open a (seemingly) completely different service.

Also I'm sure the author of the article knows all this as well as anybody. But he tries to look from the consumer's point of view.

To the article: I mostly agree with his points. Play store not remembering my scroll position and the different sizes of some icons (and even more the almost overlapping icon names sometimes) are things that bugged me too. But mixed UI designs and that calculator bug are just things that happen if you roll out such a major update with significant UI changes. It's nothing I get even slightly mad about.
[Samsung Galaxy Nexus] Cilraaz:
I can understand it from a consumer's point of view, but how would it be resolved programmatically? If we start requiring a pointer to where a screen was opened from, you increase the memory footprint of every app. It might also cause some problems with app deconstruction. In the Gmail example, pressing the back button deconstructs the single email instance, but if a pointer were to tell it to go back to the home screen because we got to it from a widget, do we deconstruct the base Gmail app also? What if the widget puts you 4 layers into an app? Not only would the pointers again add to the app's memory footprint, but we have the deconstruction issue on a larger level.

I'm not the greatest programmer (especially in Java), but the "inelegant" way that it works now seems to have a few positives for both devs and users.

Again, I understand the consumer side of things, but is Maps opening Latitude more confusing than having Maps kill off Latitude? The user would then just try to re-open Latitude and be confused as to why the prior instance wasn't running. If Maps wouldn't kill off Latitude, then it would have to create a second instance of itself, which again has a negative impact on the app's memory footprint.

------------

I understand a general "hey, it should work like this instead", but there are plenty of reasons why it works the way it does now. Android might be able to get "perfect" functionality, but it would likely require some dumbing down of multitasking (either more process suspension instead of true(r) multitasking or the memory manager would be more likely to kill off background processes). I don't at all doubt these are discussions going on at Google, though.
[Samsung Galaxy Nexus] qwer23:
Thanks Cilraaz, you really shed some light upon the deeper reasons for the sometimes odd behaviour of the back button and app layers. I'm no programmer at all, so I didn't know all this would add to the memory footprint of the apps and would affect developing in such a major way.

After reading your post I suggest we can be happy with some minor incosistencies and enjoy true multitasking instead of dumbing down our phones :) Again thanks for your nice clarification!
[Samsung Galaxy Nexus] AmericanCon:
Some good stuff in this thread.
[Samsung Galaxy Nexus] crixley:
"complains about back button not taking him home, doesn't use home button"
[Samsung Galaxy Nexus] pfmiller:
That's not what he complained about. He complained about the back button behaving inconsistently.
[Samsung Galaxy Nexus] PrixPrax:
I find it actually works very logically. If i click on one email in my widget to read it and then use the back button to go back, it makes sense to be taken to my inbox so i can read more messages, instead of being taken back to home screen and selecting a new email from there. Its more practical in case you get like 10 emails at one, which won´t fit in the widget all at once anyway. If i wanted to go back to the home screen, hey there is the home button.
[Samsung Galaxy Nexus] pfmiller:
That sounds like one corner case where the behaviour works in your favor, that doesn't mean it's right. It used to work better. For example if you have Navigation open, and select and email from the notification then you are brought to the email. Then when you hit back it brings you to your Inbox (which you have no reason to go to) then when you hit back again it brings you to your home screen. In previous versions of Android when you hit back from the email you are reading it would take you directly back to Navigation. That is what you most likely want, and that is what the Android documentation says should happen. But all too often it does not.
[Samsung Galaxy Nexus] tameracingdriver:
Totally agree with this article. I love Jelly Bean, and Android, but ultimately, it lacks a hell of a lot of polish. This is where iOS is still leagues ahead (and for that matter, so is WP7/8), I forgive it because it is a very open and powerful platform, but it is still a platform for the techie, and has a long way to go before it is as friendly and approachable as its rivals IMO.

The same sorts of arguments have been leveled at PCs for years and are equally valid.

Like it or not, most people AREN'T techies and this is why the likes of Apple are so successful, because they understand this and bring out an OS that is generally intuitive to average joe. Ironically I find some of the ways their software works confusing in places (particularly OSX) but that is more down to my "techie" approach and being set in my ways, as most techies are.
[Samsung Galaxy Nexus] e34v8:
Well, he has some valid ponts, but most of the time, he is wrong. Especially for the back button.
[Samsung Galaxy Nexus] HinotoriBR:
Could you please tell me how he is wrong, specially if Android documentation says that the function of back button is X, and, sometimes you get Y, sometimes you get Z, and sometimes you get X?

Either document that back button has a bunch of functions that no one knows until you use it in a given context with a given app, or, give it a consistent behavior (and I'm not discussing which one would be better).... It is understandable when 3rd party software doesn't behave 100% as documented, but, built in phone apps should be consistent and provide the same experience...
[Samsung Galaxy Nexus] MikeyMike01:
Great article. A lot of those things drive me nuts, the icon size and back button in particular.
[Samsung Galaxy Nexus] Chrono_Tata:
Another annoying thing the back button does is, for example, if you have been using the Play Store before, then you open an app that links to a Play Store page. Once you have seen the page and press back, rather than it taking you back to the app, the back button will just traverse through all the pages that you have been looking at on the Play Store in your previous session.
[Samsung Galaxy Nexus] Jubomime:
Yeah I found that amusing as well.
[Samsung Galaxy Nexus] Il_Tene:
Maybe the "back" button should be replaced by a "higher level" (hope it's the right term :D ) button. Maybe in this case his function would be more logical.

However I agree on almost every point in the article
[Samsung Galaxy Nexus] MikeyMike01:
Or they could just make it work properly. The back button works in WP7 just fine and it's rather handy.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Il_Tene:
Someone at google HQ must have read the article because with the last maps update latitude icon is disappeared :D
[Samsung Galaxy Nexus] Fire n mage:
The play store bugs get to me the most.
[Samsung Galaxy Nexus] blame2:
Play store not remembering your place drives me ape ****.
[Samsung Galaxy Nexus] zAlbee:
Just because this is the way it works right now doesn't make it the right way. It can be resolved programmatically with some well-thought out APIs and careful consideration of corner cases. Of course it can. This is what software design is about.

The memory overhead of an extra pointer is minuscule. The system already needs to keep a global stack of the recently used apps (that's the only way the Back button can work). The app may or may not also keep a local stack of most recent screens within the app. If an action takes a user from one app to another, the system should notify the new app that it needs to change the Back button behaviour from "go up a level in its own app" to "Back out of this app" . I understand what you're saying is that the only current way to do #2 might be to "quit" the app, which would be wasteful. I am sure there are ways around it. I believe Browser almost does it perfectly right now.

If you go from

1. App A

2. Click Link B -> Browser App (you already have N tabs open, so this opens in new tab N+1)

3. Click Link C (still in browser)

4. Click Link D (still in browser)

Each time you press Back, you go up a level, and after 3 presses, you're back in App A. The browser has not "quit", or at least if it did, it did not forget your state. Reopening Browser preserves the original N tabs you had open.

This proves it can be done. If it turns out that apps need to add extra API to support this, fine. Google can set a good example. Yes, if the Android system dictated what the Back button does at all times, then things would be simple and consistent. But we want to give developers freedom to decide what it does, and that means consistency requires cooperation from devs and Google. Now, compare to iOS. They don't even have a Back button. ;)