yashsingh1/xdaforums huggingface dataset:
[LG Optimus 2x] BUFUMAN:
Hmm which rom do u use?
[LG Optimus 2x] obaidr:
I use Miui 1.9.2 with baseband 1035.21_20110725 and RIL 0725.
[LG Optimus 2x] koboltzz:
Any ETA to next release? :)
[LG Optimus 2x] kiljacken:
Nope. We currently aren't doing that much xD We're a tad lazy at times, and I think we deserve to be able too :)
[LG Optimus 2x] koboltzz:
Okay then ;)

Where can I get the kernel release BEFORE 901?
[LG Optimus 2x] smokeweedevery:
^in the first Thread;)
[LG Optimus 2x] -sandro-:
than why do the first post say to re-apply the kernel on every nightly update? Seems like it would restore the cm7 kernel

I can't upgrade nor go back to cm7 :confused:
[LG Optimus 2x] BUFUMAN:
hmm dont know dude.

this was the only way for me to get the new kernel.

I wiped, reflashed, updated the vorrkernel over market. checked all the flags, flashed manualy after this procedure.

and now its ok.
[LG Optimus 2x] blackcmos:
im a bid new in flashing android roms and kernels,

but im using miui 1.9.9 and tried to flash this kernel, dalvik wipe and cache wipe, but it didnt do anything.

Some ideas what i did wrong?
[LG Optimus 2x] notthesun:
if you want to use this kernel on miui use manual flash through recovery...the app not works good on miui rom...bye
[LG Optimus 2x] grognaz:
sorry if this has been asked befire but i tried to undervolt with setcpu and it doesnt apply the voltage. is this not working yet in the latest kernel or do i need some other app to undervolt?
[LG Optimus 2x] kiljacken:
Undervolting is disabled on purpose
[LG Optimus 2x] blackcmos:
i did, but i still kept the same kernel, but i will try again soon...
[LG Optimus 2x] grognaz:
thanks, any specific reason for that?
[LG Optimus 2x] HerrKuk:
Probably so people wont undervolt it too much and then complaint about the unstable kernel...
[LG Optimus 2x] kiljacken:
Exactly, but I actually have to correct myself. It was disabled, but currently it's just not working :)
[LG Optimus 2x] grognaz:
ok, thanks a lof for the info:D
[LG Optimus 2x] MaXmeOliver:
Can this be used with the latest nightly #146?
[LG Optimus 2x] temasek:
Yes.........
[LG Optimus 2x] vadonka:
flashing to the cm7 #146 via CWM working perfect
[LG Optimus 2x] -sandro-:
hello,

this might sound stupid.

When I had 127 nightly and this kernel I got around 3300-3500 in quadrant benchmark.

Now with nightly 146 + latest kernel I get no real improvement. It scores same as stock cynogen. Around 2600-2800. I noticed that the benchmark "hangs" for 2 seconds in I/O "file system writing", before I remember that step was about an instant

It could be a cm7 thing...but does it happen to you too?

I'm using null scaling 216-1000mhz
[LG Optimus 2x] hobs0n:
Are there no links for versions above 802? Since updating/installing vorkernel doesn't work with the vorkernel application anymore :)
[LG Optimus 2x] temasek:
0901

http://minus.com/mFaAT7sfd
[LG Optimus 2x] kiljacken:
Or you could just enable manual flashing in the app, and it will download and configure for you :)
[LG Optimus 2x] temasek:
Sorry for the posted link. I checked your dropbox don't have 0901 so I just helped out.
[LG Optimus 2x] vadonka:
in the latest version (0901), the max cpu speed is limited to 1100mhz. it is right?
[LG Optimus 2x] temasek:
Yes that's the max.....for now.
[LG Optimus 2x] hobs0n:
Ah thanx man :) feels bad when the phone ain't running vorkernel =)
[LG Optimus 2x] kiljacken:
You know you want this :D First O2x to go over 5k in quadrant (Documented atleast)
[LG Optimus 2x] vivmar:
LOL you right...when and where the link?????:D
[myTouch 3G, Magic Android Development] carz12:
Well since I was already compiling everything else I thought I'd try out compiling Clockworkmod.

For new radio 6.35 sapphire only

It works great and has many more options than any of our other recoveries.

I have a zip file posted, it is not a zip to flash from recovery, unzip it, it has the fastboot binary and the recovery in there.

cd to the folder you unzipped to:

to just boot to it and check it out,

fastboot boot carz-clockworkmod-3.0.2.8-recovery.img

to flash it,

fastboot flash recovery carz-clockworkmod-3.0.2.8-recovery.img

carz-clockworkmod-3.0.2.8-recovery.zip

md5sum 0571916b96e83af43a7cd3a684838d28
[myTouch 3G, Magic Android Development] blizard80:
amazing work :)

will try ir later!

thanks
[myTouch 3G, Magic Android Development] ntphuong:
Tks man, great to have this

Will try it soon
[myTouch 3G, Magic Android Development] danielgek:
i'ts perfect

tested and aproved :)

you are the man
[myTouch 3G, Magic Android Development] Sleeepy2:
Sweet thanks, downloading it now.
[myTouch 3G, Magic Android Development] stiker:
nice work!
[myTouch 3G, Magic Android Development] Ntadeusz:
Super, I tested.
[myTouch 3G, Magic Android Development] Unkjcr:
Working great and nice features carz!! ROM Manager works along with this recovery right? :)
[myTouch 3G, Magic Android Development] Sleeepy2:
I like the Orange, very nice.

Does the restore for this work if I just move a regular nadroid to the right location?

It doesn't look like ROM Manager works with this recovery :(

hmmm, any suggestions, I want to back up my current rom, install clockwork then restore my backup. It's not exactly straight forward as I am using custom MTD.

So steps would need to be

1. Backup

2. Flash this recovery from fastboot

3. Flash MTD recovery patch and wipe/everything

4. Reboot into recovery for the MTD to be complete

5. Some special magic for my nadroid...???

Figured out the magic, just move the files from the nadroid backup to the clockwork location.

6. Restore from step 5.

7. Reboot....
[myTouch 3G, Magic Android Development] Bladyle:
Which kernel are you using? It's work fine on OR too, but no any big difference from Ra's 2.2.1 ..
[myTouch 3G, Magic Android Development] carz12:
there is a 2.2.1 ra recovery for our phone?
[myTouch 3G, Magic Android Development] Unkjcr:
Yup, you can find it in Bladyle's signature. It works pretty fine indeed! It has almost every features that your clockworkmod recovery has. :)

http://www.multiupload.com/S7TW1LMHBO
[myTouch 3G, Magic Android Development] xc1943:
will try ir later!

thanks

:)
[myTouch 3G, Magic Android Development] rcaridade:
The restore doesn't seem to work...

I have a working "Diet Gingerbread" make a backup then wipe all and then restore.

Everything seems to restore ok, but It stays at "htc magic".
[myTouch 3G, Magic Android Development] Sleeepy2:
It worked for me, just took forever for first boot.

Help, I feel naked. My PC doesn't detect my phone at all any more, and my phone doesn't detect the usb any more.

Phone is plugged into the same USB I have been using for ever (the actual official HTC one) and yes I have tried others. My phone is charging however there is no adb debug (yes it is turned on). I don't even have the option to mount the sd card, it's like my phone doesn't know that it is connected to USB only to a charger. It's like this in both recovery and fastboot (no fastboot usb).

Just ignore me, issue with my PC, wouldn't recognize any USB device. Reboot and I am good to go.

Sorry for any confusion, move along, nothing to see here.
[myTouch 3G, Magic Android Development] c0mrade2:
Hi!

I'm on dietGB and when i boot in recovery mode, i get this message:

E:can't open /cache/recovery/log
E:can't open /cache/recovery/log
E:can't open /cache/recovery/last_log
E:can't open /cache/recovery/last_log

But i can do all without problems... any explanation?:o

EDIT: Problem solved just wiping cache :D sorry
[Thunderbolt Q&A, Help & Troubleshooting] colecolecole:
I noticed after using the Thunderbolt that I could only hear off and on from the Left ear - the Right was fine. I thought it was the headphones so I went & purchased new ones and after that plugged my phone in using my aux port in my Jeep and the same problem. Its only playing from the Right side speakers*-- so with (2) pairs of headphones & the car I am thinking its the phone?

Any one else had this problem?

*

my thunder bolt is rooted if that helps :)

Sent from The TBolt using App
[Thunderbolt Q&A, Help & Troubleshooting] chriskader:
I noticed with mine I had to push the headphones down kinda hard to get left and right audio. Probably not good for the jack though

No, thats not a storm. Its just my Thunderbolt layin down this post.
[Thunderbolt Q&A, Help & Troubleshooting] inzandity:
I have noticed the same thing...with that, and the sleep button, I am not impressed with the build quality of these devices.
[Thunderbolt Q&A, Help & Troubleshooting] PWEB18:
Same with me...I get worried everytime I plug something in
[Thunderbolt Q&A, Help & Troubleshooting] Natronics:
Sounds like the headphone jack shorted out. I had the same issue with my og droid. I'd unroot it and get a replacement.
[Thunderbolt Q&A, Help & Troubleshooting] eraursls1984:
I have to push mine in hard also or I only get sound from one side. Also on phone calls the other person can't hear me if the head phones are plugged in
[Thunderbolt Q&A, Help & Troubleshooting] Natronics:
Does the pair of headphones have a Mic? If they don't then that makes sense on why they can't hear you. I'm rockin headphones now and don't have to shove them in the jack.
[Nook Color Q&A, Help & Troubleshooting] bustabob454:
ok so I have returned 3 nook colors for the whole ghost touch/random selecting of things....Anyways I noticed on CM 7.0.2 currently the best ROM for the Nook Color out there that the lcd density is at 161 in the build.prop file I like things bigger so I set it at 230 or so and I have been messing with diffrent settings. It seems to me that at the LCD Density Setting of 161 or so that the stock CM 7.0.2 comes with does virtually no/minimal ghost/random touch compared to say a setting of 230 or so.I have tryed stock roms n all the rest and it seems they all have the same problems with this matter. I guess my real question is does CM 7.0.2 have a setting of 161 for a reason? And if it does is there a way to fix to this issue and get a better size say of 200+ on the lcd density settings?
[Nook Color Q&A, Help & Troubleshooting] tsukisan:
I don't have the full story on why 161 but I know part of it is that alot of apps won't render properly with a setting of 160 so to answer the lesser question 161 is intentional.
[Nook Color Q&A, Help & Troubleshooting] bustabob454:
Ya thats what I was just reading but Im curious about the fact it seems at least to me being though 3 nook colors that the problem is more software related somehow some way rather than hardware if anybody has any thing else that would be cool....thanks! And btw another forum I was reading earlier said something about the software how it members where you touch and if u exchange for a new nook color like I did of course it will be better at the start but eventually will be the same old issue
[Nook Color Q&A, Help & Troubleshooting] Nburnes:
You may just need to re-calibrate your screen. I haven't had issues with ghost touches other then when trying to use it while connected to a charger.

https://market.android.com/details?id=com.assid.android.nookrecalibrate&feature=search_result
[Nook Color Q&A, Help & Troubleshooting] bustabob454:
Ya Im fairly use to the adb method of recalibrating the screen and also the app on the market that seems to help for a couple of mins. And so does flashing or restoring the rom and the usual screen off/on trick and the reboot I have been round the block with this thing once or twice
[Nook Color Q&A, Help & Troubleshooting] khaytsus:
Not the same old? So you're using the NC while plugged in? Or a really dirty screen, or wet, or..?
[Nook Color Q&A, Help & Troubleshooting] joenathane:
What this man says! The nook color screen is very sensitive, your screen doesn't have to even be very dirty, it can register old fingerprints as touches, any time you get ghost touches, just turn your screen off and clean it...
[Nook Color Q&A, Help & Troubleshooting] Slack3r:
I noticed there was a calibration APK in the stock 1.2 rom, however it won't install in CM7 and I couldn't find how to run it on the stock rom.
[Nook Color Q&A, Help & Troubleshooting] Jiggity Janx:
I have been using a density setting of 220 on the NC for weeks (and my DroidX for almost a year) without noticing any ghost touches. I recommend the same as above... if you get ghost touches, turn off the screen and clean any smudges.
[Nook Color Q&A, Help & Troubleshooting] mindcandy:
most ghost touches i experience are due to thin layer of condensation on screen, usually first thing in morning when the screen is cold but my hands are warm
[Nook Color Q&A, Help & Troubleshooting] indagroove:
My original NC had the ghost touch issue, and it was driving me nuts, so I exchanged it for a new one last week. The new one works great. I haven't cleaned the screen at all since getting it a week ago, so it's pretty dirty now, and still no issue with ghost touches. My feeling is that there is a hardware issue with many NCs.
[Nook Color Q&A, Help & Troubleshooting] joenathane:
I dont think its a hardware issue at all, every time i've had the ghost touch issue, i was able to fix it by cleaning the screen. It doesn't matter that your screen is just dirty, what matters is what its dirty with, since the screen is capacitive, it would have to be dirty with something conductive...
[Nook Color Q&A, Help & Troubleshooting] indagroove:
Well my original one started acting funky after just a day or two, I kinda thought that it was software related because I was running CM7 nightlys at the time, but later realized that the issue persisted even with stock. I did find that I could reduce the issue by cleaning the screen, but it didn't help completely, and would only help for a very short time. Since exchanging for a new nookcolor, the difference is night day. I am completely convinced that it is in fact hardware related, based on my experience with two different units.
[Nook Color Q&A, Help & Troubleshooting] robot8:
As explained by the man himself;

Regarding ghost touch issues, while there may be some units that have this problem due to hardware, IMHO most of them are due to the sensitive screen and dust/dirt/oil/condensation. Just the other day I was plagued with ghost touches because it was unusually humid in the room I was in. As has been posted by many, easily fixed with a simple good clean.
[Nook Color Q&A, Help & Troubleshooting] Phoenix84118:
Had my nook for over a month now, and just noticed this problem this weekend. I had to clean the screen real well (didn't even look that dirty) and the problem went away. FWIW I have a screen protector on it (added it a couple weeks ago).
[Nook Color Q&A, Help & Troubleshooting] john10101:
I have never seen any ghosting issues. Im running cm7 with a default density of 161 i got my nook at the beginning of the year. ive pretty much run every version of cm7 since it was released.

I had it a month or 2 before i got a screen protector. (official b&n, antiglare)

I did have to clean my screen really well prior to applying the protector. i dont think ive cleaned it since.
[Nook Color Q&A, Help & Troubleshooting] Ronin3178:
I have a Zagg InvisiShield, installed a few days after I got my Nook back in March, no ghost touch issues that I have noticed.
[Nook Color Q&A, Help & Troubleshooting] waterbound:
The ghost touches have 'nothing' to do with hardware, roms or applications used. Its entirely due to something on your screen such as grease, oil or something similar like the previous posters said. When or if it happens, turn off and clean your screen. That's it. All tablets can produce weird touching behaviour 'especially ' if you use something like a screen protector.
[Nook Color Q&A, Help & Troubleshooting] KnowledgeBroker:
I beg to differ, ONE poster said something about it happening more when they have it plugged in.. I have playing a game that drains it pretty quickly, so if I can play on the charger I do.. but the problem is constant, even when my screen is PERFECTLY clean. The problem has all but went away entirely when I leave it unplugged, even with screen dirtyness. And came back within a few minutes of it being plugged in AND fully charged. I think it happened once WHILE it was charging, but THAT may have been because I let the screen be dirty while charging.

So yea, I have a feeling that there IS some hardware reason for this. Or even just as possible, something in the way the software reacts once it is fully charged. Either way, I have tested this for weeks and it has held absolutely true.

So thanks to the poster that mentioned it being plugged in, fixed my problem entirely :)
[Nook Color Q&A, Help & Troubleshooting] dalingrin:
There is a hardware issue causing this but I think it is the cable/charger that is the problem. My Nook charger causes this issue but if I use a standard usb cable to charge I don't have touch screen problems. Some users have gotten replacement cables and no longer have the issue.
[Nook Color Q&A, Help & Troubleshooting] anapospastos:
I 've some weird issues with the screen only when trying to connect my hard disk using a hub. I think the current voltage causes it. The bottom part of the screen is hardly unusable. I am neither able to type the command to mount it on the filesystem. If I disconnect the hard disk (without disabling usb otg) it 's getting normal again.
[Nook Color Q&A, Help & Troubleshooting] Imbroglio:
I thought I was the only one having strange issues with the touch screen.

It seems to occur mostly when:

1) It is charging

2) It is angled up about 30 degrees

3) The NC is not being held

4) The finger touching the screen is parallel to the text

When viewing web pages I get unintentional zoom outs, select text to be copied, and clicks on links nowhere near my finger. Sometimes my finger is an inch away from even touching the screen and something gets clicked.

Could it be that the (cheap) power cord and/or charger are leaking some type of electromagnetic interference causing the screen sensor to go haywire?

When it isn't charging things go back to normal.
[Nexus S Android Development] bajansurfer:
Hi all,

Here's a nandroid backup of Stock 2.3.4 (GRJ22) rooted from my GT-I9020T. Just extract the zip and place the folder that's inside the zip into the /sdcard/clockworkmod/backup folder on your phone. Then reboot your phone into recovery and restore the backup that says "Stock_2.3.4_rooted"

I've only tested this on my phone but hopefully it should work for you. You may want to install Busybox after.

NOTE: the zip that you download contains another folder within it so when you extract it, make sure you use the folder inside and not the actual extracted folder.

DOWNLOAD:

http://www.mediafire.com/?a8cia8hxn3h7kcr

MIRROR:

http://dl.dropbox.com/u/17007111/Stock_2.3.4_rooted.zip

Thanks to ChainsDD for superuser access and Google for Android :)
[Nexus S Android Development] iamxeph:
Finally, thanks a lot.

FYI, restoring boot.img and system.img is just okay.
[Nexus S Android Development] PLEEZEFRAGME:
thx, someone tested this with ther european SLCD I9023 version?

If not, i am downloading atm. I´ll give you some feedback later, much later DL only with 56KB/S ?!?
[Nexus S Android Development] wutang01:
With Nexus S ROMs, do they differentiate between i9020T and i9020A? I have a i9020A.
[Nexus S Android Development] pairushletts:
I can't download from mediafile it said can't access from server can someone make mirror to the other web.

thank you. :)
[Nexus S Android Development] PLEEZEFRAGME:
ok, tested it, works with SLCD version from germany I9023
[Nexus S Android Development] nabiladeeb:
anyone tried it on i9020A ??
[Nexus S Android Development] spippo:
ok in the i9020t ;)
[Nexus S Android Development] lnjryan:
Will this update the radio also?
[Nexus S Android Development] reddv1:
No, but this will http://xdaforums.com/showthread.php?t=1060192
[Nexus S Android Development] bajansurfer:
Uploading to my dropbox public folder now, may take a while though as i live in Barbados and the internet here SUCKS compared to other places. 1Mb download and 256k upload :mad: so it's probably gonna take about an hour. Will post link when done.
[Nexus S Android Development] iamxeph:
Use this just for emergency: http://xeph.iptime.org/Stock_2.3.4_rooted.zip
[Nexus S Android Development] bajansurfer:
Thanks man, upload should be done soon.
[Nexus S Android Development] bajansurfer:
dropbox mirror is up

http://dl.dropbox.com/u/17007111/Stock_2.3.4_rooted.zip
[Nexus S Android Development] spippo:
with this backup you could restore the original recovery and block the bootloader? mother is recognized by google for future updates?

thanks
[Nexus S Android Development] AllGamer:
working good on the i9020T
[Nexus S Android Development] pairushletts:
Hi When I hear what you talk about I don't understand even model or radio but I just interest to update for use gmail video so I update mine from the file of this post everything work fine and my Nexus 2.3.4 already.

but the other file I don't know what is that and how to do. I am beginner.

thank you for the guy who sharing this. and will be thankful if can someone tell me what should I do next or what should i be careful. Thank you.

here is my screen
[Nexus S Android Development] bajansurfer:
What other file do you mean? The other link in the original post is just a mirror. They both download the same file. You either choose one or the other. Glad it's working for you!
[Nexus S Android Development] twerk:
How do i tell which model Nexus S i have. Under baseband version it says I9020XXJK8.

Is this I9020a or T or whatever.. thanks!
[Nexus S Android Development] rgl12miami:
Open the back cover, You will find the model written on the case

under the battery. ;)
[Nexus S Android Development] kponti:
Having a weird problem where some apps force close a lot and the Google sync keeps turning itself off all the time. I have to keep turn it on to get my Google gmail, calender, and contacts to sync

Any reason for this?
[Nexus S Android Development] bajansurfer:
Haven't experienced this issue myself, have you tried fixing permissions with ROM Manager or within clockworkmod recovery?
[EVO 4G General] jdh10475:
Just read about Airpush on Phandroid. So Airpush will allow developers to put adds in your notification bar. So airpush made their YT video private but I found it on their website. We all need to ensure that this BS does not make it onto our phones.

Link to Phandroid article

http://phandroid.com/2011/04/30/air...tification-pane-and-why-i-think-its-horrible/

Link to Airpush website to see video demo

http://www.airpush.com/
[EVO 4G General] flight01:
Yeah this could possibly suck. But it might not be as bad as some people might think if its used right.

If app devs from market use this instead of in app advertisments it will de-clutter apps and might make them more usable. Just take angrybirds, the freaking ads get in the way of playing or seeing things sometimes, But if they used airpush the ads would not be onscreen when playing but in the notification tray. So depending on what apps and the implementation it might not be so bad. As long as the ads go away or can be cleared and dont come back after the app is closed might be ok.

Just please god, this should not be used by carriers or google to target ads for specific people by search patterns and gps locals and such. If so i would leave android. But i dont think google would do that or let it happen ;)

Edit: NVM read a little more and it looks like the ads can be pushed without the user even having opened the app. Wow scary. The dev can even set the ads to push if on a set number of days the app has not been open. Wow everyone needs to get together and run this company out of business
[EVO 4G General] xHausx:
this will never work, the backlash would be brutal. If you ever see something in the market that does this just rate it one star and report it as malware
[EVO 4G General] JoshuaD80:
i feel like the concept is viable, and as long as the user can opt out, like the video says, then i feel like it might be a good alternative to in app advertising. HOWEVER, it should ONLY push ads when i'm using the application, and it should only use my location if i specifically allow it to at that moment.

there are just so many implications to this that it's mind boggling though.