yashsingh1/xdaforums huggingface dataset:
[Transformer TF300T Q&A, Help & Troubleshooting] mrquidz:
Hi XDA!

This is very exciting moment for me and I hope i'm welcome into this new family.

Here i want to share some experience as a newbie. I just bought my TF300T (blue) yesterday and it came with ICS 4.0.3.

It was smooth, zero lag and amazing when it was out of the box. Then i went back home and downloaded some apps and meanwhile upgraded it to Jellybean.

After everything was finished, the tab boot as usual but now the feeling was different. There was obvious stuttering and lag in any apps even at the homescreen.

I was sad and frustated on updating to jellybean. But then on the next morning, i did 'factory data reset', and everything is ok! The smoothness returned and much better than ICS. i was glad i did it and now i can't be happier than before.

I'm not yet root my transformers as to preserve warranty. The transformer is the best.tablet.ever!

St from my ASUS Transformer Pad TF300T using xda app-developers app
[Transformer TF300T Q&A, Help & Troubleshooting] vap_66:
Well, it seems that you're not nice after all :P. Joking aside, I can understand OP's excitement, but yes, there are several threads related to new users/JB upgrade. Also, rooting for JB without an unlocked bootloader is not possible for the moment.

Trimis de pe Motorola Defy
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Melodycd:
I read a lot of reviews on Amazon saying there is a touch screen problems. You have to click on item on the screen several times to make it respond to your finger. My order is on its way, so may be i want to return it if this issue is present on all KFHD. Does any one else here having the same issues?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] deaglecat:
Sorry can't answer your specific question but this is the sort of thing that can be fixed in a software update. Not sure how frequently Amazon will update the KFHD but if it became a significant issue (i.e. started generating lots of returns) then I bet they would fix it.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] noxas:
That problem sounds more to do with the laggy-ness of the KFHD rather than the screen itself. Once they do a few software updates and make it work a bit smoother it'll be sorted. If not then if it gets rooted and a custom rom installed, Id guarrantee it'll not do that anymore.

It's just the same as when you have a slow computer and you click something, sometimes it doesnt respond. Im not saying the KFHD is slow by any means, but the way amazon has skinned android so much makes it a little less responsive.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] revoltech:
The Kindle has all the android quirkiness touch screen issues. For example, when I wake the device from sleep to the lock screen and rotate the screen at the same time, I would have to touch the screen again to register my finger being on the lock swipe area. So, you should have no issues with the touch screen if you are used to the android operating system.
[Galaxy 3 Q&A, Help & Troubleshooting] ilievski.ace:
[GUIDE] Disable CPU Rendering

Thanks
[Motorola Droid Bionic] knitpurlgurl:
I've held off rooting my Bionic & putting an ICS Rom on it in favor of waiting for the OTA ICS update, but we're coming to the end of Q3 & I'm starting to wonder when that will happen. Anyone know if ICS is in soak testing for Bionic yet?
[Motorola Droid Bionic] mtbrgeek:
Not yet... soon.... the forums will blow up when it happens i assure you.
[Motorola Droid Bionic] ronaldheld:
Not holding my breath for it happening anytime soon. Maybe before the end of the year?
[Motorola Droid Bionic] MrRedPants:
Ironically you don't need to root to try ics. You install leak from stock recovery. I stay with 232 so I can Fxz back to 902 or 905. Really has minimal risk since can still get ota if on 905
[Galaxy S II Q&A, Help & Troubleshooting] Chaos Water2:
Does anyone know where I can find Android 4.0.4 stock firmware for my Samsung Galaxy S II on the Three network.
[Galaxy S II Q&A, Help & Troubleshooting] Jokesy:
ICS 4.0.4 firmware is not yet released for 3, Vodafone, and O2 in the UK.

The best bet is to flash 4.0.4 for unbranded UK firmware here: www.sammobile.com/firmware/?page=3&model=GT-I9100&pcode=XEU&os=1&type=1#firmware

Or simply stay with your present firmware

Swyped from my Samsung Galaxy SII
[Galaxy S II Q&A, Help & Troubleshooting] Chaos Water2:
Excellent answer!!, just what I was looking for, thanks pal :)
[T-Mobile myTouch 4G Slide] JohnnyP.akaJP:
So today I spent around 6 hours installing ICS. Out of all the phones, I found this the most confusing.

Also I had some problems with my SD card using FAT32 system. I recommend FAT. And I dont recommend 1gb SD card like me.

I was running Gingerbread 2.3, HBOOT 4.15.00003, S-ON. and locked bootloader.

Step 0. Find out what you have.

Power down phone. Hold volume down and power button until you see a small flash. Then let go.

On the top of the screen you should see HBOOT x.xx.xxxxx. Locked or Unlocked. S-ON or S-OFF.

If you have S-Off then this isnt the thread for you.

If you dont have HBOOT 4.15.00003 then this isnt he thread for you.

If you have a UNLOCKED bootloader, skip step 1.

Step 1. Unlock bootloader

I used the All in one tool. Watched the video, Follow it until installing clockworkmod recovery.

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

(I am not sure if it worked for me the first time..I installed it like 4 times.)

To go to recovery. When ur phone is off. Hold power+volume down until flash. Then let go. use ur volume keys to go up and down. The touchpad to select. Back button to go back. Anyways go down to "recovery". select it and it should say clockworkmod on the top

Also if you havent done an NANDdroid backup. Do it. Go to backup and restore. Select backup and wait...

Step 1.5 Root

Follow the steps here.

http://wiki.rootzwiki.com/HTC_myTouch_4G_Slide#Installing_Superuser_and_su

Step 2. Find desired ROM. I personally used

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

But ya know. Whatever ya want. ( I downloaded this while watching unlock bootloader video to save time.)

Don't forget Gapps if u need em!http://wiki.cyanogenmod.com/wiki/Latest_Version

Download version 9. All the way bottom.

Step 3. Setting up Fastboot

You need "fastboot". So go here

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

and scroll down till you see the download link for fastboot.exe

Download, Extract fastboot.

Then Extract your ROM, There should be a BOOT.img. Put that "BOOT.img" inside your recently extracted fastboot folder.

Run Fastboot.exe as Admin. (If you get a error for missing "AdbWinApi.dll" go on google and download the file. Then stick the .dll file inside the fastboot folder.

Step 4. Installing ROM

Follow steps from the picture and downwards

Then go here. http://xdaforums.com/showthread.php?t=1508556

Before Flashing the ROM I did this. (credits to muzzzmaggg on youtube. Original link http://www.youtube.com/watch?v=g0mb8AZnN9k)

- wipe data/factory reset

- wipe cache partition

- go to mounts and storage:

1.format /cache

2.format /data

3.format /system

- go to advanced:

1. wipe dalvik cache

2. wipe battery stats

Then install Gapps. Reboot. Win.

All credit to where it belongs. Im just noob who got lost and dont want others spending like 6 hours lols.
[T-Mobile myTouch 4G Slide] blackknightavalon:
So...you followed this guide?

Sent from Spaceball One.
[T-Mobile myTouch 4G Slide] Coug76:
That's weird because the MT4GS doesn't have that hboot number as far as I have ever seen. Are you certain that you had that number for the hboot? Can you confirm that you have the myTouch 4G Slide made by HTC?

Apparently you have the phone if that ROM worked...

Hastily spouted for your befuddlement
[T-Mobile myTouch 4G Slide] WeekendsR2Short:
:laugh:You guys are so cRAzY! LOL:laugh:
[T-Mobile myTouch 4G Slide] karri0n:
If you're using Hassoon's toolkit(and I see that you were), installing fastboot separately is unnecessary. In fact, no guide or instructions at all are required. Just click the little boxes in order and read what it says inside the app. His thread says "noob proof" for a reason.
[Samsung Galaxy Nexus] cmstlist:
I reflashed stock JB kernel the other day and found my phone to be running very smoothly. But I can't stand the colours on my purply screen, so back to Trinity (latest stable release).

The problem is, I'm getting a lot of lag and jerkiness on Trinity. Google Now takes forever to load, responsiveness takes a hit, and it generally feels like that whole "Project Butter" has turned into cold chunks of margarine.

I did buy the Trinity app to change settings. Is there anything I should be doing with Trinity that would give me stock-like smoothness and performance? I have a feeling there is some default setting in Trinity that is supposed to be helpful for some users but for me it's just killing the experience.

Or alternately, would I get better results with Franco?
[Samsung Galaxy Nexus] jordanprudent:
I had similar issues. Not flowing very well , reboots and crashes. Also even though I bought the trinity app changing the clock speeds made the phone very very unresponsive. Tried many times to install it but no luck. Swapped back to Franco / glados (tried air kernel which was nice for battery but a bit laggy)

Franco also has trinity settings you can play with

J
[Samsung Galaxy Nexus] kyokeun1234:
Me personally had a better experience than Franco. But all the phone are different and some might like trinity and some might like Franco. Seems like yours like Franco more

Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
[Samsung Galaxy Nexus] Guiding.God:
Personally I've had ridiculously good results with Trinity - with 384 GPU, not 512 (1536-384-Stable35). Absolute butter even when I have very resource heavy, multiple, tasks running - and havn't had a forced reboot, freeze or anything of the sort even once. Interactive/SIO, min 307, max 1190. Everything else on default (except screen colours/gamma which I changed to my liking).

That said, if the 384 GPU is also not working for you I suppose you can give Franco or the other kernels a try, every phone set probably responds a little differently to each kernel.
[Samsung Galaxy Nexus] KelevrA_8:
What trinity kernel are you using? I am on trinity 384 Alpha 56 and it is butter smooth... even get great deep sleep with it.
[Samsung Galaxy Nexus] simms22:
try using supersu instead of superuser. also, update your busybox. a lot of people have issues with root apps obtaining su slowly with superuser on jelly bean, which leads to lag.
[Samsung Galaxy Nexus] nevrlow:
I have good flow with trinity kernels. No lag or unresponsivness

*Who needs a gs3 when you have a NEXUS*
[Samsung Galaxy Nexus] cmstlist:
Already doing both, thanks for the input.

I'm using 1344/307 and I also previously tried 1536/384. My phone seems to have some overheating issues so I don't want to crank it too hard... Just want to get close to stock performance.

I'll try interactive / sio. Are those essentially what the stock kernel uses?
[Samsung Galaxy Nexus] simms22:
i like ondemand/deadline. overheating.. whats your cpu temperature? most think that their devices are overheating when it falls in the normal range. tkt comes with widgets(in the app drawer widget menu), put the no background cpu temp widget on your homescreen and youll also get a cpu temperature reading in your status bar. at 100C the thermal throttle will kick in to lower your cpu speed and cool down your device. the safety shutdown temperature is 110C, your cpu will automatically shut down at that point. 110C is only reachable if you turn off the thermal throttle in the tkt app and you are benching your phone at a high oc. otherwise, i wouldnt worry about overheating.
[Samsung Galaxy Nexus] cmstlist:
The other thing is I get lockups every day or three. Today I rebooted the phone and plugged in the charger while it was rebooting. The moment the screen went off the phone was locked up. Power button would not respond. Unplugging/plugging the charger did not light up the screen. Had to do a battery pull.

In fact this happened again a second time in a row. Is there a reason the phone is locking up immediately after boot if I have the charger in? I'm trying it again a third time with the charger out, letting the screen auto-sleep before I touch the phone. Okay apparently it has nothing to do with the charger.

EVERY time I start the phone up now, if I don't unlock the screen myself before it auto-sleeps, the phone locks up and auto-reboots again. WTF??
[Samsung Galaxy Nexus] simms22:
are you undervolting at all? which yrinity kernel are you using? did you happen to use franco kernel before using trinity? try using a different charger too, ive had similar issues with a certain charger before too, until i started using a different charger.
[Samsung Galaxy Nexus] cmstlist:
Despite the fact that I disabled "Set On Boot" in Trinity Kernel Toolbox, it does seem I'm still set to interactive/sio on boot. And check out the logcat I captured over USB when I was doing a reboot and it locked up:

http://pastebin.com/sSe9eFXT

In particular to trim out just the TKT lines and the last few lines before lockup:

D/TKTBootHelper( 1853): TKT: Boot Completed
D/TKTBootHelper( 1853): TKT: Set file permissions.
V/LockPatternKeyguardView( 299): Set visibility on com.android.internal.policy.
impl.LockPatternKeyguardView$4@41f3cf58 to 8388608
V/LockPatternKeyguardView( 299): Set visibility on com.android.internal.policy.
impl.LockPatternKeyguardView$4@41f3cf58 to 8388608
D/TKTBootHelper( 1853): Current Version: 3.0.38-04149-g1d1c555-dirt00:23:38|
D/TKTBootHelper( 1853): Previous Version: 3.0.38-04149-g1d1c555-dirt00:23:38|
D/TKTBootHelper( 1853): TKT: Versions match, let's restore settings.
E/vpnapi ( 1672): Function: Connect File: AndroidIPCSocket.cpp Line: 172 failed
to connect fd=38: Connection refused
E/vpnapi ( 1672): Function: Run File: LocaleChangeMonitor.cpp Line: 140 Invoked
Function: AndroidIPCSocket::Connect Return Code: -26476533 (0xFE6C000B) Descrip
tion: ANDROIDIPCSOCKET_ERROR_CONNECT_FAILED

So it would seem that right after TKT says "let's restore settings" it locks up, if the screen is off, when set to interactive/sio. Huh?
[Samsung Galaxy Nexus] cmstlist:
See my post immediately after yours.

No undervolting at least that I know of. I tried cranking max screen off frequency up in case that was the cause, and tried going back to default CPU settings. Still does the same upon reboot.

But I can confirm that if I uninstall TKT completely and boot with Trinity Kernel, there is no screen-off lockup. Whatever settings were being restored by TKT were causing the phone to freeze if the screen was off. I'll leave it at that for now and give it another go when it's not so lovely and sunny outside.
[Samsung Galaxy Nexus] simms22:
delete the data for the tkt app(main phone settings, apps). dont use set on boot, its usually not a good idea. my screen off is set to 307. if you are overclocking, you have to disable smart reflex mpu or you will freeze and reboot if not other issues. turning off smart reflex is very important if raising the cpu speed. otherwise the device will try to automatically set the voltage too low for the cpu speed and itll cause freezes/reboots.
[Samsung Galaxy Nexus] cmstlist:
I didn't overclock and I didn't undervolt. What is smart reflex?

Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
[Samsung Galaxy Nexus] simms22:
does your rom have its own cpu settings? maybe theres something enabled in there?

---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------

smart reflex is a built into stock, it controls your voltages. the thing about it is that it doesnt know overclock or undervolting, so if you overclock or undervolt, it restores voltages for stock cpu speeds. which causes freezes if youre trying to overclock by setting the voltages too low.
[Samsung Galaxy Nexus] cmstlist:
Stock yakju Jellybean flashed straight from Google image files, with the exception of Trinity.
[Samsung Galaxy Nexus] simms22:
did you try clearing the tkt data, or uninstalling it and reinstalling it? honestly, this is the first time ive seen this behavior. do you have any other cpu control apps installed?
[Samsung Galaxy Nexus] morfic:
Yes, set on boot is for critical settings only, like frequency policy and voltages.

All trivial settings are always restored as they were set.

What ROM are you on? I jumped into the middle of this page and missed it.

Side note, if it's settings being restored, clear the app data using the option in the menu.
[Samsung Galaxy Nexus] cmstlist:
No I do not. I will try reinstalling now since I uninstalled it completely.

Again, pure stock flashed straight from Google, except for Trinity.
[Samsung Galaxy Nexus] cmstlist:
Fresh install of TKT. Default settings that show up are: 307/1190, set on boot OFF, ondemand/deadline, screen off max 307. Voltages 580 1000 1070 1150 1240, set on boot OFF.

Tunables: Vibration 1450, contrast -24, content adaptive enabled, Spice Melange, USB fast charge disabled, battery, enabled, online, safer, and Smart Reflex enabled all three.

Plug in the USB, and adb reboot. Immediately after, adb logcat and wait for it to connect during the boot process.

Okay, so far so good... there was no lockup this time. I wonder what the lousy setting was that messed it up last time. I even set it back to interactive/sio and no lockup this time either.

BUT the interactive/sio setting remained in place after a reboot even though I disabled Set On Boot. Is this a bug?
[Samsung Galaxy Nexus] morfic:
can you get me a /proc/last_kmsg after the reboot?
[Samsung Galaxy Nexus] morfic:
That is indeed a feature, setting governors and schedulers is trivial and anything trivial always restores.

the stuff that could cause issues like a frequency too high to be handled or a voltage too low to be handled will require SoB to be set, other wise the voltages will only prefill the sliders, without being set, for a convenient setting of voltages with a single button press without prior setting them all individually.

Also if you flash a new kernel it will wipe your settings (you saw the version comparison in the log, if they are different, it will start up with out applying possibly incompatible settings (especially when switching between incompatible kernels))
[Samsung Galaxy Nexus] cmstlist:
Your input is greatly appreciated. For now the boot lockups have stopped, but I will be sure to follow up here if they start again.
[Samsung Galaxy Nexus] simms22:
you should post in the main trinity kernel thread(gsm). that way it could possibly help others with the same issue, and we would be able to get you help faster since we would see it faster :)
[Samsung Galaxy Nexus] cmstlist:
Yeah the problem is, 1) If I post in a much bigger longer thread it's easy for my follow-ups to get lost in the flurry of other conversations, 2) I don't want my control panel to indicate there are thread updates if they're not about my problem :)
[Samsung Galaxy Nexus] morfic:
Well, we are subscribed to this one, we can always refer to this thread when we think we hear (ok, "see") a similar issue.

It's just when you start a thread in here, i won't know about it and can't help unless simms22 runs across it.

Also, just in case, if you do have a follow up, email me a direct link, just in case i don't get a notification from this thread.

Or post a link in the Trinity thread, it'll get noticed and we can take care of it.

I can react to emails easier at work, so if you do collect a last_kmsg (attach it as a .txt ;)), email it to me rather than just attaching it or linking to it in here.

Thanks,

Daniel
[Samsung Galaxy Nexus] simms22:
1. the trinity thread isnt like all the other xda threads, you wont get lost in the thread. there are reasons that our thread has a great reputation. ill make sure. and if morfic nor i get to it, the thread is full of helpful people. anyways, chances are that i would get there first ;)

2. i dont check thread updates or get notified. i hate being notified. but, it is my home, and i rarely miss a post.

anyways, the thread is a learning experience for many, no topic is out of bounds. as i like to say, its our island paradise within the xda sea, where people should feel free to ask, even if its already been answered many times. please, feel free to come join us there.
[Samsung Galaxy Nexus] maverick_hunter:
Not only that, but you can completely derail the thread for a while by talking about things like music, and OP is ok with it! :highfive:

Seriously though, the Trinity thread is probably one of the, if not the, friendliest threads on XDA. Lots of helpful people.
[Samsung Galaxy Nexus] haxor:
Help me guys i am using JB stock rom and franco kernel now just have a look of screen shot will find sort of lines on a IMAGE its a screen shot of video ! What it cause and how can i get rid off from this problem
[Samsung Galaxy Nexus] cmstlist:
Just had a strange one. I got out of the shower and my battery was pretty low but not in the red zone, as I hadn't plugged it in all day. I woke the phone to see if I had any messages, and when I didn't, I put the phone to sleep again. Then a few seconds later it rebooted to the Google screen and lingered there for far too long (at least 45 seconds, maybe more?). I got scared and pulled the battery. Decided that if any recovery would have to happen, I'd put my spare charged battery in so I don't have to worry about charge.

Started up the phone again, and it lingered on the Google screen longer than usual but did successfully boot.

I tried going in with adb to a root shell and typing cat /proc/last_kmsg > /sdcard/last_kmsg.txt

but I just got: sh: cat: /proc/last_kmsg: No such file or directory

So I guess there is no last kmsg.
[Samsung Galaxy Nexus] morfic:
every so often a fsck will freak people out

you can't have a last_kmsg of a battery pull

check your dmesg for signs of the fsck in the current kernel messages

EDIT: That is a prime example of what to share in Trinity thread and get info there from many ;)
[Samsung Galaxy Nexus] cmstlist:
Ok but shouldn't there have been a last_kmsg from the random reboot?