yashsingh1/xdaforums huggingface dataset:
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] ahmedsalem89:
Look first, ana m3rfsh elmoshkla dy sara7a 3shan mafteesh :D

second, 5lek fel android bgd msh hatrg3 lel WinMo tany

and I've been testing lots of Android Versions/Builds today. just let me know when u want to try and I'll tell u which ROM to Choose. :)
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] Roushdii:
ok dear thanks alot

bs brdo you should tell me how to flash android lma a2olk :D:D
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] ahmedsalem89:
7ader :D 2olly enta bas w mlksh d3wa :D :D
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] Roushdii:
tell me b2a ya ahmed ezay w emshy m3aya 5atwa b 5atwa a5ook mobtade2 :D
[Galaxy S I9000 General] qiu:
Just updated through Kies the official way (no registry patch or anything)

I haven't experienced any lag in the past one hour of use. And it feels definitely faster and more lightweight than JPO+voodoo5.01.

Did Samsung change the file system in JPY? Anyway, I am very happy with this firmware:D

Oh, Merry Christmas, everyone!
[Galaxy S I9000 General] tragusman:
Still rfs. Had jpy for week or so no lagfix still runs smooth.
[Galaxy S I9000 General] ayongkot:
is this faster than jpx? i have uprgraded from jpo. i however downloaded jpy and jpx but i am satisfied so far with jpx.
[Galaxy S I9000 General] emmarbee:
+1. I'm much happy with JPX. Is it worth to upgrade to JPY or wait for a gingerbread firmware (hope they don't release furthermore firmwares in froyo :) )
[Galaxy S I9000 General] nazrazr:
what pcode is your phone? XEU?
[Galaxy S I9000 General] Stefanauss:
I really don't know why many people implies that stopping development of Froyo ROMs altogether, will guarantee a better or earlier Gingerbread build.

It makes no sense. ;)

If there is a bug (and we've seen plenty of them in this 6 months) in Samsung version of Android Framework, or in Samsung's add-ons, drivers and own binaries, the chances that still will be in Gingerbread are very very high.

And tracking down, hunting, debugging and solving a bug is much easier on a relatively stable environment that in a entirely new (or much newer) build like the 1st Gingerbread Firmware.

Gingerbread will benefit from almost every bug found and solved in Samsung's Froyos.
[Galaxy S I9000 General] dragec88:
I updatet before few days via KIES (reg-hack) to XXJPY and its still working very fast! only problem is the internet browser. its slower then on the XXJPX firmware.
[Galaxy S I9000 General] kunjar:
Updated to JPY a few days ago using the kies patch. Phone seems faster and snappier than before.

Noticed apps which are already installed are arranged alphabetically...apps installed after update will be added at the end.

Got 1210 on quadrant with this stock firmware. Tested the GPS yesterday going from nottingham to birmingham using copilot 8.2. Still sucks. Lost GPS fix 6-7 times on a 55min journey.

Shortest losses were around 4-5 mins and the longest outage was around 15-20 mins.

Browser still shows squares when pinching to zoom.

Overall its a better experience than before but i need a solid fully functional GPS. May just have to keep returning the phone to orange UK until they get fed up and offer a different handset (make/model) as a replacement.

Shame though, i like this phone :(
[G Tablet General] pqrs:
I just plugged my tab into my pc... and of course... nothing! I went to viewsonics site to see if they had drivers and nothing? How can i make my pc see this thing? I have had the worst luck with this tablet... nothing has worked for me! I really want to like it, but its difficult when everything fails to work.

please help me, otherwise i think ive reached the limit of what i can take. I may take it back...
[G Tablet General] rothnic:
when you plug it in, you will see a notification on the tablet, click it and select mount usb
[G Tablet General] pqrs:
Doh! Facepalm.... ill try that!

thank you!
[G Tablet General] pqrs:
That worked, you da man!

Merry christmas!
[Nexus One Accessories] DJBludLust:
I recently bought and finally received my brand new seidio battery for my nexus one. As soon as i tried to charge it however, I had issues. At first, the charge LED flashed orange and then green as if there was no battery in it at all. then after a while it finally started "charging" as indicated by the orange light. I left it overnight and most of today, more than 12 hours, and it still says it is charging. Even WORSE is that my phone won't even boot at this point, even though it has been "charging" for more than 12 hours. I have tried both a usb and wall charger, but the wall charger for 99.9% of the charge. Anyone heard of anything like this happening? I have searched for a while and found bubcus. Not even an FAQ from seidio or something.
[Nexus One Accessories] cmarti:
That sounds like a shorted battery, probably blew a fuse in the Nexus motherboard.

That sucks and Seido does not cover damages caused by their products to the phones.

Bummer.
[Nexus One Accessories] DJBludLust:
Well my phone still works just fine with the standard battery. It just won't boot with the extended one. guess I just have a lemon. Just wanted to confirm before I sent it back
[Nexus One Accessories] Gahh Its Lee:
Tell them they sent a faulty product and try to get a refund. Good luck
[Nexus One Accessories] DJBludLust:
Exactly what I will do. Are they usually diffucult to deal with when it comes to returns? Or do they actually act like they want to help?
[Nexus One Accessories] Lamar720:
They are kind of hard to deal with verses Mugen
[G2 and Desire Z Q&A, Help & Troubleshooting] mr.pnutt:
So what's the big deal about Gingerbread?

G1 Chromatic Dream(Android 2.2 Froyo)
[G2 and Desire Z Q&A, Help & Troubleshooting] ibemad1:
[YOUTUBE]Jx3pdWBlZ34[/YOUTUBE]

http://android-developers.blogspot.com/2010/12/android-23-platform-and-updated-sdk.html
[G2 and Desire Z Q&A, Help & Troubleshooting] opensourcefan:
It's got that unique flavor with just the right amount of sweetness all in a crunchy package.
[G2 and Desire Z Q&A, Help & Troubleshooting] Sleef:
Any new version of the Android OS is going to come with some new features and a boost in performance.

Running the buggy GB build that's out right now, I can say that the copy/paste is VASTLY improved. I'll have to wait for a stable release to say much more but I know that near field communications is supposed to be native to GB and overall performance should be better.
[G2 and Desire Z Q&A, Help & Troubleshooting] KiNG OMaR:
Well tis simply da bestest!
[G2 and Desire Z Q&A, Help & Troubleshooting] scottmog:
wow nice video.... cant wait for it now... @@
[G2 and Desire Z Q&A, Help & Troubleshooting] blackknightavalon:
It has the 3G and it has the wifis.
[G2 and Desire Z Q&A, Help & Troubleshooting] sino8r:
Too bad the UI is tacky... well except the black bar. Looks like HTC Hero took a sh*t on 2.3 and smeared it all in with all those black & green highlights.
[G2 and Desire Z Q&A, Help & Troubleshooting] AbsolutZeroGI:
+1

:p

That video is awesome.
[G Tablet Android Development] mzimand:
I had this issue with 3.0 but I reinstalled the ROM and did a data, cash and delvik wipe and have not had the issue since.

The first install I did not do a wipe and ran into the lag issue. But ever since I did the reinstall with the wipe I have not had any slow downs at all.

EDIT: Disregard the above, the lag came back.
[G Tablet Android Development] Neoprimal:
First thing I want to say is that I'm not a dev.

However I've been playing with the lag issue for a while since I updated as soon as the update showed on my Tablet and it showed pretty quickly for me. I didn't think this issue was related to the calendar problem that roth mentioned because I experienced it before I even installed GApps to my tablet.

I suspected some power saving issue from the beginning and what I've also noticed is no matter how long it sleeps, it doesn't happen at a certain battery level....in my case I went from 100% to ~45% and had no slowdown, even after sleeping.

So if you're at anything above 60% for example and sleep or don't use the tablet for even the hour or more, when you get back to it - it's just as fast as you left it.

In my experience, this happens when the Tablet is at roughly 30% - maybe a bit more, maybe less depending on your battery calibration and readings.

In order to really test this - wait until your tablet is at 20-30% and then leave it alone or make it sleep and try it to see if it slows down. If it does not, then maybe you're on to something with wiping the data/cache/dalvik. If you indeed show no signs of slowdown, I will try wiping as well in order to confirm so pls let me know when you can. Thanks.
[G Tablet Android Development] rothnic:
The reason I think this might not be kernel related is that I ran Vegan for a couple weeks straight without issues. Each time I install a new ROM I can recreate the issue when it has a clean data partition. If I restore my old data partition I well cease to see the lag on wake. I have tested and tested this, and each time it is related to the data partition.

It really is a shot it the dark looking at anything, but my bet is on some type of thread that is being called either on wakeup or before sleep that stalls out. Many apps use that time to sync, or read from disk.
[G Tablet Android Development] anlog:
Here is what I found tonight after some testing:

1.) Once the processor drops to the 216000 freq it's pretty much stuck there till you reboot. Couldn't find a way to snap it out of it.

2.) On a clean boot my cpuinfo_cur_freq file fluctuates between 246406 and 286484, but there is no slowness. Everything is blazing fast. Weird...

3.) After booting, setting cpu0's scaling_min_freq file to 1000000 does, in fact, change the speed listed in cpuinfo_cur_freq for both cpus.

4.) Overclock Widget doesn't set the governor profile "performance". It only sets the min and max speed. I think this may be part of the problem.

5.) Running "tegrastats -max" from a term is supposed to disable CPU frequency changes and enable max speed.

As a test I set the freq and governor, and also ran tegrastats. We'll see how the tab does in the morning.
[G Tablet Android Development] rcgabriel:
I'm glad somebody else is observing the same thing about "sticking" at 216MHz - it's hard to imagine that isn't related to the slowdown. It would also roughly explain the magnitude of shift in the Quadrant scores observed during the slowdown. Your clean boot behavior and mine are different because I've been running Overclock Widget. Also, if the cpu_info_curfreq is fluctuating that implies the governor is changing the frequency.

Good find on the tegrastats command, I wasn't aware of that one. I'm fairly hopeful you won't see the slowdown after running that.

Another thing - I'm starting to pick through the kernel source diffs a bit (I can't even get the kernel to build, as it seems to be angry that my Linux boxes are all 64 bit). I decided to peek through dmesg and see if it gave us any clues.

Lots of good info on the suspend/resume cycling in dmesg. Going to see if I can get this sucker to lag out again and then look at dmesg output to see if there are any clues.
[G Tablet Android Development] rushless:
I got the lag with 3.0 and never went into sleep mode. Seems the lag issue is random to any rom with the newest kernel.
[G Tablet Android Development] anlog:
UPDATE:

1.) Just wanted to clarify that even though the CPU speed was fluctuating in the 200,000's after a clean boot, it felt like it was running at 1ghz speed. Not sure what that's all about, but it seems that anything other than 216,000 = fast.

2.) I don't believe Overclock Widget is designed for multiple processors. While setting the parameter of one CPU usually scales the other, I've seen a couple of bugs with Overclock Widget where the parameters of one CPU were changed but not the other. I think a script running at boot to set the parameters and run tegrastats would be better

3.) The "performance" governor has to be manually set for both cpus.

4.) I'm not 100% certain tegrastats actually does anything with our build. I don't get an error when running it, but I do know that it definitely doesn't take the unit out of "slow" mode. Hopefully it keeps it from dropping if run at boot time.

5.) After leaving the unit sleeping and charging last night, this morning I am still at 1ghz. So far so good!
[G Tablet Android Development] clemsyn:
I built this kernel yesterday just before we left for vacation. It worked fine when I mixed it with vegan4 but had issues with making the market fix work. Tried a few times but I can't get full market functionality. It seems to fix the lag when turning it on but I forgot my tablet for further testing. If anyone is interested, just unzip and put this boot.img under vegan's zip file to replace the boot.img.

Please let me know how it goes. BTW, clockwork installation is a must.
[G Tablet Android Development] clemsyn:
I made a few changes in the CPU power management which IMO would help with how CPU is adjusted and also a few in yaffs: )
[G Tablet Android Development] anlog:
Still no slowdown. Come out of sleep about 20 times now. I might reflash beta 4 later to test. My power button doesn't work with beta 4, though.
[G Tablet Android Development] thebadfrog:
anlog,

You need testers for a slow down workaround? I am volunteering. Running update 3389 with tegra performance pack right now
[G Tablet Android Development] anlog:
Testers needed....

Please test the following commands on your tablet and see if the slowdown problem still occurs...

1.) Download and install android terminal emulator (free) from the Market.

2.) Uninstall ALL overclock and cpu scaling utilities such as Overclock Widget, etc.

3.) Power cycle your tablet to reset the CPU to full speed.

4.) Open a terminal and run the following commands:

4a.) su

4b.) tegrastats -max

4c.) echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

4d.) echo performance > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

4e.) echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

4f.) echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

4g.) echo 1000000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq

4h.) echo 1000000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq

4i.) tegrastats -max (yes, run it again)

5.) After the commands in step 4 have been completed, run the following terminal commands to verify that the CPU clock has been changed:

5a.) cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq (should be 1000000)

5b.) cat /sys/devices/system/cpu/cpu1/cpufreq/cpuinfo_cur_freq (should be 1000000)

After the above steps have been completed, use your tab regularly over next 24 hours. Don't ever power it off. Just keep it in sleep mode, use it any way you like, plug it in to power when needed. Just don't power it off. If you power it off, the settings above will be wiped out.

Once we confirm that this is working for multiple people, we should be able to add it as a startup script to any build.
[G Tablet Android Development] thebadfrog:
Thanks....pecking at screen right now
[G Tablet Android Development] butkol:
Giving it a try right now. I have definitely seen the slowdown on TNT Lite 3.1.1
[G Tablet Android Development] thebadfrog:
Either I've gone brain dead or something is wrong with the script because I get an error "cannot create performance: directory nonexistant"

EDIT: echo "performance" > /sys....needed quotes to work for me
[G Tablet Android Development] rob_z11:
I am going to test it out, and will report.
[G Tablet Android Development] anlog:
All,

If you notice the slowdown coming back after running the commands above, repeat steps 5a and 5b (after running su) to see what the cpu speed is. If it drops to 216000, you know the slowdown is back. If it is still 1000000, then something else might be slowing the system down (try closing apps, etc).

Here are the steps:

1.) su

2.) cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq (will probably be 216000 if slowdown is back)

3.) cat /sys/devices/system/cpu/cpu1/cpufreq/cpuinfo_cur_freq (will probably be 216000 if slowdown is back)

-EDIT-

Depending on the build you are running, you may notice that your sound stops working (as mine just did). This is not related to the CPU tweaks. I've had this problem happen randomly on several builds. Unfortuately, the only way to fix it is to restart the tab, so I guess I'm not going to have sound for awhile. I'm planning on keeping this thing going until I get a slowdown (still none yet) or one week (whichever happens first). I'm cool with rebooting once a week.
[G Tablet Android Development] mdwalker@yahoo.com:
patch 1.1.1 up

And I guess we do. I downloaded 1.1 the other day and ow it gives me 1.1.1.

NOPE. Files are identical.
[G Tablet Android Development] lamlam01:
I am running TnT Lite 3.1.2 & would like to test this patch. So can I apply kernel patch by just renaming the TnTLite3.1_kernel_patched_V0.1.zip file to update.zip and apply it using clockworkmod or do I need to extract the boot.img and then open up the 3.1 TnT ROM update.zip file and replace the boot.img with this new one? I wanted to make sure. Thanks!
[G Tablet Android Development] vsc:
No need to rename with CWM. Just select the ZIP in CWM and apply.
[G Tablet Android Development] rob_z11:
Vsc,

Where is your kernel for vegan beta4 sir?
[G Tablet Android Development] jkpatel79:
Vsc, I tried this out, and it seems to be responding better with all the functionality in tact after the market fix. It hasn't reached the 216000 speed yet. I'll let you know if things change tomorrow morning.
[G Tablet Android Development] rob_z11:
Can someone please attach vsc's Kernel?
[G Tablet Android Development] lamlam01:
If you are on Vegan ROM, it's post #112:

http://xdaforums.com/showpost.php?p=10138407&postcount=112
[G Tablet Android Development] rob_z11:
I went through bunch of post, but I can't seem to find one for beta4/vegan.
[G Tablet Android Development] japhule:
I can confirm that vsc's patch for tnt works for me. Thx!
[G Tablet Android Development] rcgabriel:
Cool, I suspected there was a simple explanation for the different results our kernels were having - sometimes when you're building, cleaning, patching and rebuilding it's very easy to mix patch sets up or snag the wrong zImage. :)

I think it's now safe to say that the major lag-on-wake issue has been identified and fixed.
[G Tablet Android Development] rcgabriel:
File is called vegan-b4-kernel-patch.zip, it's in my post on page 12 of this thread. Just drop onto SD card and apply as update.zip in Clockwork Mod. vsc's kernel and my kernel now should have the identical patchsets applies to them.

Just know that these patched kernels all still have the SDcard mount-related issues until we sort that issue out - so some apps like Angry Birds may be unhappy until you unmount sd card and reinstall them.
[G Tablet Android Development] rcgabriel:
That is a fine question. It may be something to do with Vegan ROM in some sense. But it's still a difference between the current stock kernel release and the Viewsonic source release, since Vegan ROM works fine (with respect to the sdcard and mounting stuff) with the current stock kernel.
[G Tablet Android Development] rcgabriel:
@clemsyn, here are my 4 merged files from that patch if you want to diff with yours.
[G Tablet Android Development] stanglx:
I am completely confused who has the build that is supposedly the "fix". I also recommended we bring some organization to this chaos. I love all the good work but it is very hard to follow and eventually will only benefit a very few due to the chaotic discussion. (some saying my version fixed the problem then in the next breath some saying it didnt fix anything, some asking which file, all not knowing what actually changed in the kernel, etc.)

Can someone give us a synopsis of what has transpired, what is the proposed fix and what was changed to fix the issue (please provide the source so we can diff those modules)?
[G Tablet Android Development] rcgabriel:
Thread summary

Stanglx - this was always a development thread, where we were working to pick through git commit logs and dmesg outputs. We spent most of this thread identifying possible solutions and testing them, so that's why it's a bit confusing if you haven't been following it all along.

There are several builds in this thread that will fix the lag issue, by vsc and by me.

Now that those disclaimers are out of the way, these are the posts with the working update.zip flashers for TNT Lite 3.1.x and Vegan beta 4:

My update.zip file for Vegan beta 4 (file is called veganb4-kernel-patch-2.zip):

http://xdaforums.com/showpost.php?p=10138407&postcount=112

vsc's latest update.zip for TNT Lite 3.1.x (uses his kernel build with the TNT Lite boot.img - he has one additional patch integrated, but I think both kernels are functionally equivalent):

http://xdaforums.com/showpost.php?p=10170515&postcount=206

There is also my update.zip for TNT Lite 3.1.x which uses the same kernel, but the rest of the boot.img is from TNT Lite (this is **not** tested well, so I recommend vsc's update.zip above instead):

http://xdaforums.com/showpost.php?p=10146906&postcount=153

As far as I know, all of these can be flashed from Clockwork Mod and will resolve the lag issue because they include the critical patch. I have extensively tested the first of these boot images, with Vegan beta 4 and am currently running it.

EDIT: vsc figured out the app install/SD Card issue. There is a new Vegan b4 update.zip now that resolves the SD Card issue, which I have tested - it no longer breaks Angry Birds and other app installs. I have also updated my tntlite update.zip to use the new kernel. And vsc has now integrated this config file patch into his build and I have updated that link to point to his latest post and updater.

For the curious, a synopsis:

Under certain conditions (LP1 suspend?), when the Tegra 2 was in a suspend state and a driver returned an error on wake-up, there is a step in the resume process where the voltage was supposed to be reset to the CPU, and that step was getting skipped. When the voltage was stuck low, the CPU would get stuck at minimum frequency, 216MHz and couldn't be pushed back to 1GHz or any other setting by the governor. There was a patch from NVidia that fixed this behavior, from a newer branch of the Tegra 2 source code than what Viewsonic used. We integrated this patch and found that indeed, it resolved the problem.
[G Tablet Android Development] roebeet:
@rcgabriel -- thanks for the excellent summary. I've actually linked it from my TnT Lite first post, as a good way for the uninitiated (myself included) to understand what their options are, currently.
[G Tablet Android Development] bmasephol:
You guys are really smart. Thanks for the effort!
[G Tablet Android Development] Butch1326:
rcgabriel,

Roebeet read my mind (or I read his... from his latest post on the 3.1.2 TnT Lite thread) as I was preparing to type up a question about the tegra-10.8.2 base where the tegra lag patch was applied.

Is this the tegra version that Roebeet and the other devs have been overlaying the tegra performance pack on? Is the performance pack part of the tegra release tree (I just haven't had time to research this yet), and if so, let's say that the performance pack was included in the tegra-10.9.x, then using good source code management practices, wouldn't the lag patch already been included in a later release (ie. the performance pack). If the performance pack is separate, then can we (or should we) overlay the performance pack on top of the patched kernel?

Also, your summary is very informative. Thank you!!! Can you (or vsc) summarize the differences (if any) between your kernel builds for TnT Lite 3.1. Thanks!!!
[G Tablet Android Development] stanglx:
Thanks... I saw that code and also suspected this would resolve the issue... I am still getting my Ubuntu image loaded up to do some compiling...but the wife keeps getting in the way..

I'm curious did you cherry pick this update or did you build from a newer kernel build that includes this fix?