yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] theholyfork:
So I sent my phone in to HTC to get repaired, got an email today saying it'd cost me either $185 to get it repaired and sent back, or $35 to get it sent back, not fixed or anything. Here's what the repair tracking said:

Repair Description

We have diagnosed your device and have determined that due to the following reason(s), your device is out of warranty:

•	Case Damage not covered by warranty

In order to properly repair your device, the following action(s) will need to be taken which will require payment due to the out of warranty diagnosis:

•	Replace Device Main Board

When I called to get my phone repaired, the guy said it was under warranty until the 28th of January (3 days ago), but since I called before that, it'll be under warranty even if it gets there after.

The amount of case "damage" was incredibly small, and I don't really need it to be replaced, and replacing the device main board sounds more of a manufacturers defect, not something I did, considering I never opened the phone up, and it would turn on (though I could be wrong).

From what I'm reading, I'm being charged because of the case damage, and if that wasn't there, I wouldn't be charged. So does anyone know if I can have them JUST replace the main board so I don't get charged?

I'd rather not pay $185 to get this repaired, and I don't want to pay $35 to have them tell me something was wrong with it, since I already knew that.

If I do decide to pay $185 to get it repaired, would replacing the main board also replace the eMMC chip?

Thanks
[LG Optimus 3D] jess3d:
hi, i have a problem with this roms.

if i install V20a on my phone works fine.

but when i install v21a or B i lost 3G connection and the phone only works with GSM.

someone nkows what happen?
[Galaxy S I9000 General] sajidmkhan:
Source Androidpolice
[Galaxy S I9000 General] kristaman:
...nice news :)
[Galaxy S I9000 General] rax22:
Seems like a nice mid-range phone. Wonder if with 768Mb RAM this will get ICS?
[Galaxy S I9000 General] iLpirLa:
Probably.. But this probably means we can stop hoping for ics on 9000/9001 :(

Inviato dal mio GT-I9001 usando Tapatalk
[Galaxy S I9000 General] got-petrol:
they have released this because it will get ics and they want more of your money
[Galaxy S I9000 General] ak:
fantastic news ...

fantastic news ...
[Galaxy S I9000 General] saqibniaz:
good news .... :)
[Galaxy S I9000 General] viperrobert:
fantastic news ...
[Galaxy S I9000 General] change63:
In my opinion it isn't as beautiful as the normal sgs/+.
[Galaxy S I9000 General] Sami Kabir:
dude its 768 mb all right but only 555 mb is user accessible....
[Motorola Droid RAZR] prking07:
hey guys, dont know if its been posted but using sqlite editor on my razr i got to disable the stock lockscreen by going to settings storage(motorola one),settings.db, settings, and chaging the value of line 67(screen_lock) to 0. No more lock screen!!! also i woul like to know what these other lines mean?

tether_reverse_nat_enabled 0

ice_isenabled 1

deblur_isenabled 0

bua_isenabled 0

thanks! ;)
[Motorola Droid RAZR] p_vhd:
Why all the burden? I simply installed "Tasker" and defined a term to set the keyguard off. And it works like a charm. Now I can use custom lockers such as Go locker.:)
[Motorola Droid RAZR] Szadzik:
I used No Lock from the Market and it worked fine. Now I use the widget of Elixir 2 and that works fine too.
[Motorola Droid RAZR] prking07:
jumm no burden. i takes like 5 second to do in sq lite and stays, u can uninstal sqlite after and it will stay. some people prefer no lockscreen at all. ;)
[Motorola Droid RAZR] p_vhd:
Ok. Here is the problem: I have no "line 67"in that destination! (I have two "settings storage"s, but only one of them includes settings.db and there is no -id 67 in it). Is it possible? Am I doing anything wrong?

Tasker has failed setting the keyguard off for some unknown reason. I used "no lock", but no success either.

Edit: Nevermind, found it. but under the line id_2744
[Motorola Droid RAZR] photobuddha:
This link will show you how to use the ice_isenabled http://xdaforums.com/showthread.php?t=1732332

bua_isenabled is back up assistant

deblur_isenabled disables your blur accounts
[Samsung Galaxy Nexus] Jezz_X:
Hi guys I was just wondering if I unlock and root my stock GSM Nexus, not installing CWM or any custom roms at all just keeping it stock (aside from Superuser, root). Does that stop or affect the OTA updates from google at all.

I did a search but its all basically about putting on CWM and flashing roms and pretty much all rooting help apps I found seem to want to install cwm as well so I'm curious if once I root it is my only way of updating is manually flashing roms myself
[Samsung Galaxy Nexus] Sweerts:
http://xdaforums.com/showthread.php?t=1441478
[Samsung Galaxy Nexus] Jezz_X:
Ahh damn my search skills must suck but I still have to say that the answer was a little vague too

I guess it means your fine and update will work as long as you don't go modding the original files ?
[Samsung Galaxy Nexus] Laynee1:
The thing is that i asked this question several times, and every time i get different answer..

I have also rooted my phone and unlocked bootloader, without any custom cWM or custom rom.. I have changed bootanimation (its in system, so its outside sdcard).

Will i be able to get OTA update, to see it and to install it ?

Thanks in advance
[Samsung Galaxy Nexus] savage6:
You should still get your OTA updates. They may break the root on your phone though but thats not really a big deal.
[Samsung Galaxy Nexus] efrant:
You get a different answer because there are a lot of people who have no clue what they are talking about, passing on wrong information.

First of all, there is a difference between "getting" an OTA update notification, and having it install. Those are two separate things. You will get the OTA update notification. Whether or not it will install depends on many things, and it changes with every update. The update has a series of "asserts" or verifications that it runs through to make sure all the files it is going to update are there. You wanna know which files it checks? Don't be lazy - open up an OTA zip file and look at the updater-script file and go through it. There you will see yourself what files need to be stock. Doing it yourself is the only way to learn. Trusting a bunch of xda members who don't know what they are talking about is not the way to learn...

Having said all that, having an unlocked bootloader or having root will in no way impact your ability to receive OR install an OTA update.
[Samsung Galaxy Nexus] Laynee1:
Thanks to both of you... The thing is that i really look forward to get 4.0.3 .. I dont want to flash custom roms, i want it all stock .. Im not asking about ETAs or smt.. Im just wishing for 4.0.3 . I heard that a lot of things are settled into 4.0.3.. Lags are gone, bugs are fixed.. :)
[Samsung Galaxy Nexus] efrant:
Unlocking or rooting does not mean you are going to flash custom ROMs...
[Samsung Galaxy Nexus] jd1001:
The only thing that will affect OTA is when you load a custom recovery onto the phone. THAT'S THE ANSWER!

Edit - These things also can affect OTA

Modifying or removing a file that is checked/patched.

Having a different radio installed.

Having a different bootloader installed (possibly).

Having a different kernel installed.

Have modified your build.prop to show a different version.
[Samsung Galaxy Nexus] Laynee1:
Ye i know .. I have unlocked bootloader and rooted phone.. But i dont want to flash any custom rom.. I wanna keep it stock.. Just , im saying i cant wait for OTA 4.0.3
[Samsung Galaxy Nexus] adrynalyne:
..and an incorrect one at that. That is not the only thing.

Having a custom recovery will:

Prevent being able to install the OTA

Not stop the ota notification or being able to download it.

Other things that will break your ability to install an OTA, even if you do not have a custom recovery loaded (you can still get notified and download):

Modifying or removing a file that is checked/patched.

Having a different radio installed.

Having a different bootloader installed (possibly).

Having a different kernel installed.

Have modified your build.prop to show a different version.

You can install an ota if you modify the udapter-script if you know what you are doing even in the above scenarios (using a custom recovery).
[Samsung Galaxy Nexus] jd1001:
Well thanks for correcting me eventhough I wasn't actually wrong in what I said.

Thanks for adding those bits too I had no idea that other mods could affect OTA although I have read here a few times that the bootloader won't affect OTA. There should be an actual topic on this because with all the information floating around it is confusing.
[Samsung Galaxy Nexus] danger-rat:
Just a nuance in your choice of words...

Having a custom recovery will not prevent you from installing an OTA, but it will prevent the OTA from installing automatically on its own - you can still manually flash it through your custom recovery...

The second list should be items that "may" affect OTA, rather than "will", since it is dependent on the individual updater-script...

I think we're on the same page though...
[Samsung Galaxy Nexus] jd1001:
Totally agree! Sometimes it's just frustrating becaus eeveryone thinks they know the right answer when in actual fact people post rubbish that is incorrect. I am guilty of it too but I always go back and edit when I make a false statement.
[Samsung Galaxy Nexus] adrynalyne:
No. Any signed ota package...the above will affect it. Going by what JBQ said, where every ota should include radios...I'd say I worded it ok.

Also, there is a darn good chance that the custom recovery will stop the install even manually...if it checks the recovery version for an update. That is fairly common. That said, if you remove asserts and know what you are doing, then sure you can flash manually.
[Samsung Galaxy Nexus] jd1001:
This is the sort of uncertainty I am talking about. We should create a new topic and nail it down finally!
[Samsung Galaxy Nexus] adrynalyne:
Here is a way to nail it down:

If you have modified your system in any way aside from rooting, then your chances of being able to install an ota update are greatly diminished.
[Samsung Galaxy Nexus] jd1001:
Ha ha ha sorted!
[Samsung Galaxy Nexus] efrant:
No OTA update to date has checked the recovery. In fact, every OTA update to date has forced a flash of the stock recovery.
[Samsung Galaxy Nexus] jd1001:
Here we go again!
[Samsung Galaxy Nexus] efrant:
No one has to take my word for it. Try it yourself and prove it to yourself. Every OTA update copies two files to your /system that are responsible for flashing the stock recovery on every boot: /system/recovery-from-boot.p and /system/etc/install-recovery.sh (if I remember correctly). The recovery partition is not verified by the OTA update.
[Samsung Galaxy Nexus] jd1001:
Hey, wasn't saying you were wrong! Just so much info here that it becomes very difficult to get a factual answer. Everyone says something different. Would love something official.
[Samsung Galaxy Nexus] efrant:
Official? Like from Google? You will never get that.

If everyone actually looked at the updater-script file in the OTA update, we wouldn't be having any discussion on this. Everything is in there: what it verifies, what it patches, what is replaces, etc. Once you take a look, you will see exactly what you can do, and what you can't. Stock recovery or custom, they both use the information in the updater-script. The stock recovery forces you to use a signed package, while a custom recovery allows unsigned packages. Both will flash the update package, but the stock one will flash it automatically, while a custom one requires you to boot into the recovery and find the package and apply it yourself.
[Samsung Galaxy Nexus] jd1001:
Cool dude, well if we never had this discussion I never would have heard what you just said. Going to look at that updater-script myself.
[Samsung Galaxy Nexus] efrant:
I'd be happy to answer any question if it is not clear, once you go through it. (Even though I'm at Disney with the kids now! :D )
[Samsung Galaxy Nexus] jd1001:
Ha ha I am going there with my daughter in a few weeks. Wow you can go to disney and answer technical Android questions??? Hats off to you! Enjoy.
[Samsung Galaxy Nexus] danger-rat:
Well, both efrant and myself have pulled apart updates and rebuilt them for the N1. I made a habit out of it, so that people could flash updates without losing recovery (or even root, depending on the update). I also build my own custom gapps and update packages, etc.

Take what you want a myth or fact, but I'll stand by efrant's word...
[Samsung Galaxy Nexus] :
Hate to throw in a brand new angle on this convo but I'll do it anyways.. And I understand that an official ota update to 4.0.3 is not available yet and we have no idea what it might or might not consist of so a good bit of what is being said is speculation.. And I myself plan to wait and read for a nice dev to provide a safe CWM flashable 4.0.3 that won't break root/ custom recovery.. But since we are being curious.. OTA RootKeeper? I have personally used it on the SGN to backup root and unroot (stream a digital copy of "Horrible Bosses" from Flixster) and then restore root with no problems..
[Samsung Galaxy Nexus] efrant:
You can certainly wait, but all it takes is adding a line in the updater-script file. Certainly doesn't take a dev to do that... :)

Haven't used it personally, but it sounds like it would work.
[Samsung Galaxy Nexus] adrynalyne:
Gosh, that must be why I said there is a good chance and not 100% chance. This isn't my first rodeo.

It all depends on how the custom recovery is being made to stick every boot.
[Samsung Galaxy Nexus] adrynalyne:
Deleted and started over because we (efrant and I are both partially incorrect).

Custom recoveries only stick, if you modify the ramdisk of the kernel (common), which makes your ota failsauce.

Another method is removing the recovery and sh file for it. This may allow for an ota to install in these circumstances. However, what I said still stands. A custom recovery means its unlikely your ota will install for the above kernel reason, which is a very common method.

Here is why efrant is partially incorrect however, and a stock recovery will not install over the other one.

#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/platform/omap/omap_hsmmc.0/by-name/recovery:2048:268fea81d30b7c8f09534e5f9bf69e3373666a06; then
log -t recovery "Installing new recovery image"
applypatch EMMC:/dev/block/platform/omap/omap_hsmmc.0/by-name/boot:4171776:155f3f835402701b847b9c0ee90bb10c74b343fb EMMC:/dev/block/platform/omap/omap_hsmmc.0/by-name/recovery f0d5fd4a3d46cfef20d113637d475631475f3bc5 4509696 155f3f835402701b847b9c0ee90bb10c74b343fb:/system/recovery-from-boot.p
[B]else
log -t recovery "Recovery image already installed"[/B]
fi

That means if the applypatch doesn't take place due to not finding the correct, it knows a recovery image is already installed and stops the flash.

So unless you guys are running roms that ONLY delete the recovery sh file and use 100% stock ota kernel, there is no chance stock recovery will flash.

If the custom recovery process ONLY deletes the sh file, then its likely that on the next boot after patching, you will lose custom recovery.

If you use a custom ramdisk in your kernel to keep your custom recovery installed, stock recovery will not flash, nor will the ota proceed.

So we were both right and wrong.

It is true, a custom recovery can stop your chances of installing an ota.

It is also true that the ota can overwrite the custom recovery.

It all depends on how the custom recovery was installed to keep it from being removed every boot.
[Samsung Galaxy Nexus] :
I will continue to read and try to figure out what that line of code might be, at this time I am unfamiliar with any programming and dont have any basic knowledge as to writing or changing any amount of code myself.:( This is my first Nexus device and I have only had it for a week so I still have much to learn! I am reading as much as I can but I do work in a tax office and we all know what that means this time of year!! lol. Thank you for your reply.:)
[Samsung Galaxy Nexus] efrant:
This (above) is all what I was trying to say. An OTA update WILL install, without modification, on a stock ROM and kernel, but with a custom recovery.

Edit: assuming of course you didn't modify any of the stock files the update checks.

Edit: and the stock recovery will replace the custom one in this case.

This is what I disagree with.

Everything else you posted I agree with.
[Samsung Galaxy Nexus] Jezz_X:
So basically it comes down too

stay with Stock recovery, Don't modify (you can add) any files outside the fake sdcard (whatever its called), and you should be fine with a OTA update
[Samsung Galaxy Nexus] efrant:
If you want to over-simplify it, I would do it this way: Stay with stock boot image, stock ROM with no modified system files (you can add files), and you should be "fine with an OTA update". If you have a stock recovery, the update will install automatically. If you have a custom recovery, just boot into it and install the update.
[Samsung Galaxy Nexus] ascariz:
let's make it simpler. if UNLOCK BOOTLOADER and ROOT ONLY, can receive and install OTA update. right? ;)
[Samsung Galaxy Nexus] efrant:
Right.

Having an unlocked bootloader has NO IMPACT WHATSOEVER on your ability to receive and install OTA udpates.

Having root has NO IMPACT WHATSOEVER on your ability to receive and install OTA udpates.
[HD Mini General] Superhelmi:
Hello,

I flashed my Hd mini with the NAND Version of Photonic.

There is a problem, I can`t take a incomming call.

The Display stays black and no Softkey is working.

After the Phone stopps ringing the Display and the Keys are working again.

Superhelmi
[HD Mini General] pravarth:
Does that happen all the time or just once in a while?

Try pressing the power button when the call is ringing.

If that doesnt work then reboot the phone and see if it works.
[HD Mini General] Superhelmi:
Hello,

it happens not every time but quite often !

When it hapens, the phone don`t react to Softkeys or Powerbutton.

A reboot didn`t solve this.

Superhelmi
[HD Mini General] peter08po:
same with me, when there's a call incoming, the screen appears nothing but the phone rings as usual

any solution yet? :confused:
[HD Mini General] schlund:
sd or nand boot ?

if sd, sounds like a register is not cleared...
[HD Mini General] Superhelmi:
Hello Schlund,

I installed the Nand Version.
[HD Mini General] k5570:
I have same problem, sometime I can't pick up phone call,

but it is still not work after stopps ringing so I need pull battery out to restart my phone.

I using CM-7.2.0
[HD Mini General] Superhelmi:
Hello,

It seems that a factory reset after instalation can solve the Problem.

It has no freezes since 2 days!

edit:

just postet and then the next freeze :-(

Superhelmi
[HD Mini General] B4tou:
Hi there,

I have the same Problem. Tryed SD and now the NAND version it's the same Problem with both Versions.

First of all i thought it happens when I'm making a call and recieve one afterwards but i could nout reproduce that. Than I thougt it might be the Ringtone, but no matter which one I choose there is noch difference.

I have no idea what to try else :(

That's really a pity because the build works fine except of this matter.

By the way... Danke Schlund für den tollen Port. :cool:
[Galaxy S I9000 Q&A, Help & Troubleshooting] sagarthaker:
Hi,

I have recently flashed Onecosmic ROM RC 3.1 on my mobile.

I was going through the list of system apps, I have come across one app which seems to have Chinese name.

I am not sure, what this app is and what is does.

Does anybody have any clue on this.

Image attached. Thanks in advance.
[Galaxy S I9000 Q&A, Help & Troubleshooting] rax22:
It's PinyinIME.apk, Chinese input. Pretty sure freezing or removing will just remove Chinese input from the keyboard methods
[Galaxy S I9000 Q&A, Help & Troubleshooting] sagarthaker:
Thanks for the info.
[T-Mobile Sidekick 4G] Franzferdinan51:
I found a post on rootzwiki where krylon360 is working on cm7 for our phones http://rootzwiki.com/index.php?/topic/586-[WIP]CM7-for-SK4G take a look and let's give this man some support for going where no man has gone before!
[T-Mobile Sidekick 4G] AFAinHD:
I think you mean for NOT going where no man has ever gone before, krylon actually never got his sidekick so he never actually started workin on the ROM. Looks like we still are going to have to pray to the people at Samsung to release the source code bfore they stop supporting our device.
[T-Mobile Sidekick 4G] wolfepakt:
Dude,

That is an ancient post. Krylon stopped working on the sk4g long ago.

Sent from myDarkSide4g CM7.2 using Tapatalk Pro
[T-Mobile Sidekick 4G] pintek:
gundangit got my hopes up :c
[T-Mobile Sidekick 4G] LinuxAssailant:
#set excitement=1

YES!!!

#set excitement=0

NO!!!!!!

We always have each other...

http://xdaforums.com/showthread.php?t=1400509&page=3
[Huawei Ideos X6] kshitij_bhatt:
i jst found thins link can anyone explain if its possible to get on our phone too ;)

http://www.qualcomm.co.in/products/augmented-reality
[Optimus One, P500, V General] aayushARM:
Hi Guys! I am trying to modify the framework-res.apk of my bro's Micromax A70 with PNGs from trettet's CosmicExperia ROM. This Q is abt. A70, but related to P-500, so I think you guys can help me out.:) I've searched & tried everything, but nothing seems to be working. Its been more than 2 weeks here messing up and I've tried almost EVERYTHING possible and useful I came across.

I replaced those btn_check buttons, radio buttons, zoom in-out buttons, not. icons including battery, Wi-Fi, GPS, data and other such. The point is, I've replaced them accurately, deleted the extra PNGs and the no. of PNGs are same in both original and Modded apk. Moreover I've checked each and every PNG with their names and also, each *.9.png is properly 9-patched...!!!

Here's what I tried to change them:-

First tried APK-multitool, the apk got compiled succesfully, but after replacing it with original one, I am getting crash at the boot up.

Again, i searched for the prob., and got that APK-multitool doesn't seem to work correctly with sys apps and has bugs in compiling process. So I tried apktool(apktool.jar), and manually decompiled apk with commands, made changes and again recompiled, but got the same results.

NOTE:-In both the above cases, i tried unsigned as well as signed apks, also I Zipaligned the signed apk.

For replacing APK:-

I tried creating update.zip, but after flashing, I simply get crash at boot up!! :(

Next, I tried to include the framework-res.apk in ROM itself. Replaced the framework apk with modded one and again built it with kitchen, flashed it, but that didn't work even...........!!!:eek:

Finally, I tried a "reframe.sh" script for replacing apk with the terminal, but no luck still......:( :mad::mad:

NOTE:- I didn't/can't try ADB Push, 'cause i don't have phone with me......:(

What can be the problem?? Am I missing something?? PLZ. guys help me out, I am really fried up with the F*****ing problems and its all getting REALLY WEIRED here:confused:!!! HELP REQUIRED ESPECIALLY FROM DEVS AND THEMERS!!!!!!!

Thanks In Advance.....
[Optimus One, P500, V General] aspee:
used 7-zip and copy paste all images from drawable-mdpi
[Optimus One, P500, V General] aayushARM:
That I tried first of all....... That's not the solution, the problem is much more complicated........
[Optimus One, P500, V General] aspee:
I once port a70 and change framework images didn't got any such error
[Optimus One, P500, V General] aayushARM:
Which things you did??? Same as i've described above???????
[Optimus One, P500, V General] aspee:
Yeah somewhat
[Optimus One, P500, V General] aayushARM:
Do you remember which rom's framework you modded???
[Optimus One, P500, V General] aspee:
Stock
[Optimus One, P500, V General] aayushARM:
I am too modding framework from a custom rom, based on the stock one.....

It worked for you, but why not for me?? Can't understand!!! What do you think the problem is???

AND, DEVS, PLEASE LOOK AT THIS MATTER!! I REALLY WANT HELP!!!!