yashsingh1/xdaforums huggingface dataset:
[Asus  Eee Pad Transformer Prime] amaectpo:
The approximate meaning of the letter:

Dear Google, on the situation around the Asus Update Prime think you should think about signing contracts with manufacturers which will be clearly spelled out itochno release date updates for the devices. For example, support for 18 months, an upgrade to the current version of the software, not later than two months after the release of this update. Just include the update is not just Android version but also the kernel and other components. It is also worth thinking about what would have forced manufacturers written on the box and guarantee that if the device has full support for me or not. Example - Asus Prime Supports 18 months with full updates. And the Asus T300 - poderzhku 18 months of updates at will and capabilities of the manufacturer. And also consider the possibility to oblige the manufacturer to return the money to customers in cases of non-fulfillment of obligations.

Until such measures will be taken of the situation repeated with the updates and will be the velocity of nedovolvstvo users.

As an example of buying a memory device for $ 1000 (Asus Prime in Russia, and so worth it), and indicated that the device will be upgraded to the new version of Android, I get a device in which the GPS is not working (yes Asus has released an external GPS for Prime, but whatever it I have to go pick up the other end of town, but in Moscow it will take about 2 hours) and after the update constant problems with the browser and other applications. Also, Android has been updated to version 4 and version of the kernel remains the same, which also imposes limitations.

Dear Google you need to treat all serezznostyu customer support.

What do you think is it worth to write such a letter?
[Asus  Eee Pad Transformer Prime] jan3586:
Google is giving away android for free to the manufacturers. The ball is on the manufacturers to update their device or not. They cannot also control moneyback guarantees because all they provide is the android os. Write a letter specifically for Asus.
[Asus  Eee Pad Transformer Prime] sputnik767:
As I said before in other threads, such is the nature of open source. You can't force anyone to do anything. Best you can do is vote with your wallet, and needless to say, Asus will not see another dime from me. Your other choice, and a much better one when comparing with the prime, is an iPad.
[Asus  Eee Pad Transformer Prime] Cernunnoz:
This is not Google's responsibility, they don't hire manufacturers to create devices for them. They simply make Android. You should contact Asus, not Google. And before you do, no offense... But please have someone check your spelling, or your letter will be discarded after the first sentence...
[Asus  Eee Pad Transformer Prime] foxmeister:
Not wholly true! Google do have a fair degree of leverage over Android licensees via distribution of GApps, which are not part of AOSP.

Google could make regular updates to the OS a condition in the license to distribute GApps and access the Android market. Whilst this will mean nothing to the Shanzhai manufacturers, it would be a very big deal to the large OEMs.

Regards,

Dave
[Asus  Eee Pad Transformer Prime] htcplussony:
That 18 month Google update alliance died a long time ago. The best they can do unless they manage the entire update process like wp7/8/win8 is keep the apps separate from the os and keep updating those.
[HTC One X] techmatlock:
I had ota 1.26.401.2 on my phone prior to my phone messing up and then not recovering. Ran two different RUUs, one that was a downgrade image and the other was the same image that was on my phone (1.26.401.2). Both failed with an error 140: bootloader version error. Then I downloaded and ran a newer image through RUU (1.28.401.9), and it successfully flashed to my phone.

Now I have an updated hboot which actually pisses me off because if someone finds an exploit in a prior version and there's not any way to downgrade hboot, then I'm effed. I know I shouldn't be crossing my fingers anyway for s-off, but like to think that there's a good chance. Why did RUU give me those errors?
[HTC One X] hopscotchjunkie:
The error indicates that the bootloader on the phone is a newer version than the one in the RUU being flashed. That explains why the downgrade image failed, but you shouldn't be getting that when flashing the same version as is on the phone. Although you say you originally had "ota 1.26.401.2"; that version was the shipped software version not an OTA upgrade. The first OTA released was 1.28.401.9, so if you had installed an OTA since getting the phone it would have actually been 1.28, which would explain the 1.26 RUU failing as well. Other than that there's no reason I can think of for that to happen.
[HTC One X] EddyOS:
Exactly as stated, without S-OFF you can't go down an HBOOT version - you can only match or increase it
[HTC One X] techmatlock:
Yeah I had the factory shipped software 1.26.401.2. Never installed an ota update, so I'm confused why 1.26.401.2 ruu failed giving me error 140. Kind of sucks, whatever I'll get over it. :mad:
[HTC One X] TiborKusic:
Give me the link for 1.28.401.9 I need it man please, my phone is broken so please :)

help help help help
[HTC One X] dlutysy:
The same problem
[HTC One X] BenPope:
Back up your ROM. Then ensure the device is locked:

fastboot oem lock

Run:

fastboot getvar version-main

To check you have a '401 device and then flash either the 2.17.401 RUU or the 3.14.401 RUU (if you want Jelly Bean).

The hboot I'll be updated, but we're not getting S-Off, and really, there's no need for it.
[HTC One X] .Jake.:
Same problem with my HTC One X

I am having the same problem with my HTC One X when trying to run RUU. I have tried 3 different RUU's for my Optus HTC One X (CID Optus001),

RUU_ENDEAVOR_U_ICS_40_Optus_AU_1.26.980.3_Radio_1.1204.90.13_release_251942_signed,

RUU_ENDEAVOR_U_ICS_40_Optus_AU_1.28.980.10_Radio_1.1204.103.14_release_258004_signed,

RUU_ENDEAVOR_U_ICS_40_Optus_AU_1.29.980.11_Radio_1.1204.105.14_release_260560_signed.

I bricked my phone and I have no ROM because it broke when I was messing around with backups, recoveries, etc... If I start the phone normally it stops at HTC Quietly Brilliant.

I can flash a recovery at any time, but I have tried multiple CWM Recoveries to try to mount USB Storage so I can install a ROM but USB storage would not successfully mount, it would just say sdcard0 shared-unmounted.

I have flashed the stock recovery.img and relocked the bootloader, then tried to install those 3 RUU's with no luck.

Bootloader reads:

ENDEAVORU PVT SHIP S-ON RL

HBOOT-1.36.0000

CPLD-None

MICROP-None

RADIO-5.1204.162.29

eMMC-bootmode: disbaled

CPU-bootmode : disabled

HW Secure boot: enabled

MODEM PATH : OFF

Nov 16 2012, 18:32:39

I ran 'fastboot getvar version-main' and it came back with

version-main: 3.14.980.27

finished. total time: 0.009s

Any help at all would be much appreciated as I need my phone working again ASAP.

Thank you. :o
[HTC One X] Mr Hofs:
Stop spamming stuff in other threads while you have your own ! It's so annoying

http://xdaforums.com/showthread.php?t=2658434

People waste their time here while you get your answers there !

Use this info for future reference.
[Galaxy Note GT-N7000 General] Lyserjik:
Hello people!

My Galaxy Note has a month of life and i use the stylus a very lot. Form me it's the perfect method of text input, but not all that glitters is gold.

Sometimes when i draw a word it happens that the handwriting recognition process stops working, so i draw words and words but with no way to convert them into full operational text. The only way is to reboot the device.

I write but no line of suggested words appears on top of the writing pad.

I have stock Gingerbread 2.3.6 and it all works smoothly.

Have you any idea on how to solve my problem?

Thank you in advance!
[Galaxy Note GT-N7000 General] Lyserjik:
Bump!

I hope that someone can come across and help me find a solution.

Thanks again!
[Galaxy Note GT-N7000 General] dr.ketan:
First try this

Go to setting - language - keyboard - samsung keyoard, there will be a reset setting available, reset it. ( i dont remember exact path if slight change in GB, as i m right now on ICS)

If not work then

You can download same ROM and flash using PC Odin
[Galaxy Note GT-N7000 General] jerkysans:
I have the same qualms when I updated to ICS. The handwriting recognition completely bombed. Before it reads my handwriting 8 out of 10 times correctly, now I would be lucky if it gets it right 3 out of 10 tries. I gave up on this and just downloaded SwiftKey X. you should, too!
[Galaxy Note GT-N7000 General] GNote_ph_user:
I suggest that you try out 7Notes by mazec. It has superb handwriting recognition... puts the built-in one to shame. It's readily available in the Play store.

I've been using it for a while now (since it was also recommended by someone here), and find it faster to use than the keyboard alternatives.
[Android Development on Bada] yasotharan13:
Android 4.0.4 ICS on samsung wave I S8500 ROOTED

Its been hardly a week now Android on Samsung wave 1 S8500 is Rooted

yes you heard me, its ROOTED, that means more functionality from your Samsung wave phone.

thanks to xda Devs they have created a new zImage for your android

The touch calibration has been made, so the left part of your screen which was facing touch issues is resolved now.

Steps

1) Copy and replace this zImage in your phone memory with this one here >> http://data.hu/get/5295695/zImage (Use the “Lassú letöltés” button in mid page to download).

2) use unlocktroot tool to root your wave >> http://www.unlockroot.com

3) Download unlockroot tool from above link and install

4) Connect ur android on samsung wave to pc, make sure usb debugging is on

5) Click on root

6) it will ask to install a driver, click on install driver anyway , the second option (in win 7)

7) Wait for root to complete

3) Done

Enjoy

DONATE ME

http://xdaforums.com/donatetome.php?u=4667743
[Android Development on Bada] ashiq7:
done

everything is ok but cant overclock more than 1gzh....
[Android Development on Bada] Soxix:
It seems that the overclock possibilities depend on the programm you choose (due to processor recognition I would say).

So try several programms. If it still doesn't work try to change the device name to GT-I9000 Galaxy S.
[Android Development on Bada] zmajster01:
ok, but are you sure is it "GT-I9000 Galaxy S" ? becouse i read build.prop of Froyo(previous wavedroid) and here is write only "GT-I9000", so i rewrite this, but some apps don't work still(quadrant benchmark works, Tegrak overclocking don't work). Have you another idea?
[Android Development on Bada] Soxix:
No your right it is "GT-I9000". I should have had a "," between. I said Galaxy S only to inform.

Anyway maybe those apps doesn't work also on galaxy S, do they ?

To overclock there is also the possibility to modify kernel, but I don't know how to do that, maybe we can take the setting from the old overclocked kernel and apply them in the new one ?
[Android Development on Bada] zmajster01:
yes, yes, i agreed, but i too shor to do this, maybe wavedroid team made some magic for us noobs :) (not everybody, just me)
[Android Development on Bada] blachy123:
unlockroot donst recognize my phone any idea what should i do ?
[Android Development on Bada] Soxix:
Did you install the drivers properly ?

Can you specify a bit more ?
[Android Development on Bada] blachy123:
nvm i fixed it
[Android Development on Bada] ATMOSF3AR:
Be sure to get USB Debugging On !!
[Android Development on Bada] ~MaX~:
can anyone upload the unlockroot program? download not working anymore
[Android Development on Bada] coties:
http://mediafire.com/?b4m6swdddnq5bd9

http://www.putlocker.com/file/DA0F15FD0CC74682
[Android Development on Bada] deeps_17:
i think you should have given credits to me!

i was the one who posted this procedure on badahub.com

and i also happen to be the editor of that site

you have copied word to word from my post on how to root wave

you need to give credits
[Android Development on Bada] yasotharan13:
i didn't get any credits otherwise didn't thing about credit.

this is only for ics users.ok
[Android Development on Bada] deeps_17:
wt do you mean by ics users

you are enjoying root coz of my tutorial

and u dun give a mention about my name also

you are disgusting man

seriously

learn some ethics and come
[Android Development on Bada] yasotharan13:
i searched web and give this information.this is not serious matter.

who have s8500 thats mean ics user
[Android Development on Bada] cyber kamikaz:
@yasotharan13

If you didn't write this tutorial you must give credits or at least write the source from where you got this.

@deeps_17

yasotharan13 didn't claimed that he had written this
[Android Development on Bada] adfree:
http://badahub.com/2012/07/android-4-0-4-ics-on-samsung-wave-i-s8500-rooted.html

No idea, I can't see exact date...

@ deeps_17

Maybe we have few more important problems, as 1 Copy & Paste Tutorial...

Please forgive us. :angel:

Then concentrate on more important stuff...

Like writing new Tuts, more infos...

Internet is living from Copy and Paste. :good:

Otherwise we would read long long Credits...

Credits goes to my Mom, my Dad, my Grandma who has born my Mom and my other Grandma who has born my Dad...

.

.

.

.

.

I thank ""God"", who has made the earth, where we are all living... etc...

Also I will thank Edison, the Inventor of Glühbirne... that I have light in my Room... :D

Now serious... few of our German Forum members think you are the man who ported Android to Wave... :D :D

P.s.: Sorry that I have written God... it is short word.

I have no religion. :o

Please, better back to Topic.

Android Port is NOT finished.

We need our energy...

Best Regards
[Android Development on Bada] yakub234go:
LOL:laugh::good:
[Android Development on Bada] khozhi:
Not working

Its not working, unlockroot does not detect my phone eventhough I have run USB debugging.

Can help?

Is this only work for Bada 2?

Can I have a full tutorial on this? as I didnt find any Zimage file to replace. Thanks,
[Nexus S Q&A, Help & Troubleshooting] jedijuice:
I have not posted here but great at Linux. I understand the term crack flasher, takes me back to the day I sold... a crack head will do anything or say anything.
[Nexus S Q&A, Help & Troubleshooting] albundy2010:
I am trying to figure out wtf this thread is about. The title....the body....wtf is right
[Nexus S Q&A, Help & Troubleshooting] OllieArmageddon:
I do believe he is still on crack...
[Nexus S Q&A, Help & Troubleshooting] simms22:
he just wants some jelly bean to flash, thats all.
[Nexus S Q&A, Help & Troubleshooting] bangkokguy:
Better he cracks a jelly fish to slash... huk... :)
[Nexus S Q&A, Help & Troubleshooting] greg2826:
The Ban Hammer is coming after ya mate ...
[Nexus S Q&A, Help & Troubleshooting] 309041291a:
HANG ON! I THINK I'VE BEEN ABLE TO DECODE THIS TEXT! Here's what I've pulled from this message....

I think he's talking about the partially working JellyBean ROM in our NS GSM development section. And he is referring to the title "crack flasher". Apparently its a term crack dealers are familiar with. When he said "I remember when I sold....", I believe he was literally talking about a time when he used to deal crack. Then he closed up by making a joke that crackheads are crazy and will say or do anything (even if that means lying, cheating, etc) for crack. This ties directly to a joke or disappointment towards the ROM. The ROM isn't fully functional so maybe he is trying to connect the developer to a crack head in the sense that they'll do anything for a "drug". The symbolic "drug" that the DEV has is getting people to flash his ROM and get posters, even though it isn't finished (because the DEV lied in the OP's opinion).

All in all he was just making a poorly written joke about the title in the thread that pertains to the JellyBean port.

You're welcomed fellow forum members. Now we can all sleep easier tonight. The OP's message will no longer plague our heads with confusion.

:D

Sent from my Nexus S
[Nexus S Q&A, Help & Troubleshooting] stellar:
[insert futurama meme here]
[Nexus S Q&A, Help & Troubleshooting] veyka:
I laughed all the way to the close button.

Closed due to being so off topic that it almost makes the topic seem off topic.
[Off-topic] mikef:
So, about to pass out on the keyboard yet again, I thought, what better way to end the night but to make a new thread on XDA? What to do though...so tired and just want to say good night...so

Good Night XDA, bed is calling and I will be back tomorrow morning early, I promise. I won't leave you alone for long.
[Off-topic] mikef:
ib4l - just in case Archer wanders through here....:fingers-crossed:
[Off-topic] Prawesome:
In before the closing of the thread,since ib4l is too mainstream :p

Sent from the year 3000 using a SGA where sheep's are not present.
[Off-topic] K.A.:
Out before the lock.. :p
[Off-topic] mikef:
Good Morning XDA!
[Off-topic] veeman:
Lock before the in.

Sent from a thingymajig that sends things.
[Off-topic] roofrider:
Wow, this hasn't been closed yet?
[Off-topic] Archer:
Alright, alright. I can see you're all chomping at the proverbial bit for someone (like me) to jump in and close this.

In fairness, we don't need a thread to say good night and good morning to each other, do we? So let's do this thing...

Thread closed.
[Galaxy S II Q&A, Help & Troubleshooting] stupidflanders1:
Hey guys,

I know this thread already exists in this forum but has come to an end with no solution and since its kinda very important to sort this issue to be able to use my phone I thought ill start fresh for some input from the experts.

I have a Galaxy S2 I9100 rooted with a custom ROM(slim ICS 4.1 when the issue started) and it started randomly freezing when unlocking the screen and normal use .but since last week it wouldnt let me make or receive calls as the phone freezes and reboots 10-20 secs into the call..i updated to 4.2 with the hope of resolving this but tht didnt work..I have changed kernels and ROMS(resurrection, cm9 release build)..though the dialer did work for calls on resurrection ROM the proxomity sensor wouldnt work..

so i tried going back to stock sammy ICS (XXLPH) and then the dialer would work but again without the proximity sensor and the samsung tests also confirmed that the sensor wasnt registering...

am rooted now and back to slim 4.2(dont like the look of sammy) with siyah kernel 3.2.2...the dialer and proximity sensor don work..the rest of it is all fine..

Ive done all the wipes each time ive installed a new ROM...also done kernel wipes before installing Kernels..

I think its not a ROM/hardware problem but well it could be but hope to get it sorted through the normal techniques..I cant return my phone for repairs as it was in mint condition bot second hand in UK without warranty papers..

Any help would be highly appreciated..thanks

EDIT: It seems the proximity sensor is to blame for this problem as i found out through other posts..and also i can make and receive calls with the headset/headphones plugged (in which case i assume the phone doesnt try to activate the proximity sensor)..

For now i would like to know how to disable the proximity sensor on the phone..I have tried inserting the gsm.proximity.enable=false in the build.prop editor using the ROM Toolbox lite app n rebooted...but that din seem to work...is there any other way to do this??pls help
[Galaxy S II Q&A, Help & Troubleshooting] 3dawg:
I am having EXACTLY the same issue as reported here and it's driving me mad. Did you ever find a fix for it?
[Galaxy S II Q&A, Help & Troubleshooting] stupidflanders1:
proximity sensor and screen brightness sensor

I havent managed to find a solution as yet..it seems the proximity sensor and the screen brightness sensor(which are on the same PCB i think as per the unassembling video) have a hardware fault and might need repairing..

Some kernels i think maybe bypass using the proximity sensor if its not working..for now I am back to the SLIM 3.2 ICS rom..It doesnt switch off my screen on call and also no auto brightness adjustment but rest all works ok so am using it for now before i get the hardware repaired..

also the resurrection rom v 2.5.1 works fine in the same manner(havent tested many others..CM7 release build doesnt work)..or you can try that script in build.prop to disable the proximity sensor..

check how it goes..
[Galaxy S II Q&A, Help & Troubleshooting] 3dawg:
How about CM9? Do these problems disappear on CM9? CM9 was working well for me but the home key and lock screen never worked. I applied all the common fixes to the keystr file but it never made a difference so I switched to slimics which worked. Then I discovered these annoying call screen off and waking problems :/
[Galaxy S II Q&A, Help & Troubleshooting] stupidflanders1:
proximity sensor and screen brightness sensor

I tried checking with the testers for the Slim ROMS..regarding differences in kernel or anything for slim 3.2 and 4.2(3.2 works while 4.2 doesnt) but they couldn't tell me what was the exact problem or the differences that should affect in this case..I haven't tried a CM9 ROM yet but it could work..The kernel for the resurrection ROM is siyah kernel but when i tried that kernel with the slim 4.2 ROM that still didn't work for calls as the phone rebooted.

Have you managed to find a replacement cost for the proximity sensor? also does your screen brightness sensor work?
[Dell Venue] prasad12ka4:
All credits to the original poster / creator:

This has been tested on Dell Venue (CM7)

http://xdaforums.com/showthread.php?t=1429126
[Galaxy S III Q&A, Help & Troubleshooting] spodie:
Will we ever get the GoogleWallet?? the store rep said it had it....... Lie!!!

Will there over be a way???l
[AT&T Samsung Galaxy Note I717] thegoob:
My phone wasnt charging and then once it hit 10% it started charging again, it shows its charging but it was still decreasing its outputting 6300mAh any suggestions?
[AT&T Samsung Galaxy Note I717] kinghorsey:
Charging via USB or AC?

With the cable it came with or another?

I know mine barely charges at all through USB but charges fairly quickly while actually plugged into an outlet.
[AT&T Samsung Galaxy Note I717] knoxster:
I learned over time the tricks of charging this puppy.

For example, while my Ford has a USB port in the car it's primarily for playing tunes off a USB device. If I use the actual phone while plugged into this port ... it actually just about holds steady.. it doesn't charge a single drop.

I drove for 2 hours recently with the phone screen OFF and plugged into this port. It gained 2%. I've since learned that if I had a 'charge only' cable with the correct pins shorted out, it might charge faster in the car ... of course, I would lose the ability to play tunes thru the USB connection -- but that's ok, I'd just use Bluetooth.

And not all AC chargers are created equal.. I've learned that part too.
[Hardware Hacking General] usstemp:
what tools do i need to learn how to hack hardware, specifically, the antenna on the galaxy s3?
[Hardware Hacking General] ourtut:
The only real way you can learn about hardware hacking is hands on experience. Go out and get a og Droid or something to mess with. You will learn what you can do. Read anything you can get your hands on! Get a rotary tool and learn to use it on scrap plastic or metal. Learn the hardware of phones and how it all works together and what it does. Ask questions, answer question (make friends here on xda). For the antenna thing, on most devices the antenna is not to be messed with as manufacturers already have it in the ideal location and configuration. Like in the HTC rezound all the antennas are in the back cover.

Hope I helped :)