yashsingh1/xdaforums huggingface dataset:
[Asus  Eee Pad Transformer Prime] Hobbesian:
I believe motley is already doing so, judging by the wierd flickers, EOS is still using an older build without some of the teg patches, I have no idea on gummy or AOKP. Right now I'm running androwook with motley's .4 and I've not had ANY of the flickering or lockups I was having when gaming, even with EOS. I'm tempted to get really freaky and flash motley's 3.x kernel into an EOS build to see what kind of performance I'd get (for reference, EOS is generally pretty quick to start with).
[Asus  Eee Pad Transformer Prime] Diamondback:
Since we got some development going on here, I moved the thread to the dev subforum :)
[Asus  Eee Pad Transformer Prime] dagrim1:
Thanks Diamondback...

Hopefully this will speed up things some more (hah!) ;)
[Asus  Eee Pad Transformer Prime] Peter Galbavy:
While I have not yet found any git interface to nvidia's source tree there is a "ssnapshot" link next to every tag and each revision under the HEAD entries. This will generate you a nice, big, chunky tar.gz to play with. I am downloading one right now based on the last update (13 days ago at time of writing) to the L14T head.
[Asus  Eee Pad Transformer Prime] jazzy__b:
I managed to get the nvidia latest L4T tree and merged the updated mmc code into my CM9 tree. Unfortunately because of the amount of change in the code it ended up forcing me to pull in most of the arch/arm/mach-tegra tree plus various kernel header updates (I think they're building r15 against Linux 3). While I am approaching the end of the merge I don't have great hopes for this working when done as the change is massive (a text diff against upstream CM9 kernel code is 1.4MB size. I will see it through to the end and see how bad it looks. The good news is that this does mean that I have seen most of the code changes from CM9 current and L4T r15 and some of the other codebases out there (SGS2, One X) and I think I should have a good feel for trying targetted updates after this.
[Asus  Eee Pad Transformer Prime] Peter Galbavy:
Well, the good news for my playing is that the nvidia sources built without any gotchas. I doubt it would boot without some TF201 specific hacks, but at least the nvidia sources are complete:

-rwxrwxr-x 1 peter peter 97750040 Jun 13 09:26 vmlinux
[Asus  Eee Pad Transformer Prime] jazzy__b:
Which snapshot did you download?

I noticed a bunch of ASUS-specific codes in the CM9 kernel source that wasn't in the nvidia source I downloaded.

Sent from my Samsung Galaxy S II
[Asus  Eee Pad Transformer Prime] leppie:
.28 decreased I/O...

Before update: 120 sec for bench, now 142 sec.

I have not done a diff, but it looks like ASUS pretty much copied the design of the 'cardhu' development board (well base on it heavily). Unfortunately, details on this board is not publicly available. :(
[Asus  Eee Pad Transformer Prime] Peter Galbavy:
http://nv-tegra.nvidia.com/gitweb/?...it;h=e6d7d2f5e4028455655cbd7c35f086f71a4aba02

But again, all I've done is cross compile a kernel as per standard android build (using tegra3_android_defconfig) - this is nothing near attempting to boot from it...
[Asus  Eee Pad Transformer Prime] jazzy__b:
Just to let you know I'm still looking at this but real life got in the way this week plus I had a broadband outage this week which got in the way of research. Any news on whether .28 made a difference?
[Asus  Eee Pad Transformer Prime] Tempie007:
.28 does not improve sqlite or io performance. maybe .29 or.30 will
[Asus  Eee Pad Transformer Prime] jazzy__b:
I think I have identified a set of kernel changes from the Linux source tree that will improve MMC I/O speed and reliability. I'm currently cloning the Linux github mirror (very slow!) so I can cherry-pick the changes into a Motley kernel build.
[Asus  Eee Pad Transformer Prime] knives of ice:
Has anyone thus far ran into any problems running the patches found in the first post?
[Asus  Eee Pad Transformer Prime] Tempie007:
in the AOPK thread on 'that other forum' someone wrote about a corrupt application. but at this point its guessing to tell if this patch is truly the cause of it.

the device/application has to crash to result in data corruption ( or instant power off ), with Androwook and motley kernel ive only seen youtube crash so less chance for data-failure...

correct me if im wrong

i keep using this patch until there are other 'fixes' , or when i start using my device for 'serious' stuff
[Asus  Eee Pad Transformer Prime] Tempie007:
Ok i thought lets rollback the patch to see how it performs.....

After some hours i decided to re-apply.. tapatalk was lagging so much!

This patch really makes big difference in certain apaps\areas!
[Asus  Eee Pad Transformer Prime] leppie:
As soon as we get a full unlock, I will do so.

Currently I am still too worried about screwing up and bricking as the kernel flashing support is broken for the current unlock (or so I hear).
[Asus  Eee Pad Transformer Prime] CekMTL:
Working beautifully on my heavily modded and scripted Wookie/motley .28 system .... and I mean VERY HEAVILY MODDED ICS... this flies big time, and no problems so far, thank you THANK YOU!!!!!! :)

Enviado desde mi Transformer Prime TF201 usando Tapatalk 2
[Asus  Eee Pad Transformer Prime] demandarin:
I brought this back up to Asus attention again and linked them, again, to this thread & the mulibenchmark bad sqlite performance thread.
[Asus  Eee Pad Transformer Prime] jazzy__b:
I'm going to need some help with this from anyone who knows how to get a kernel booting on TFP. I am following some fairly simple steps but cannot get a compiled kernel to boot. I have tried the ASUS .21 source and Motley's 3.0.4 source. My build command is pretty simple, something like:

make -j4 ARCH=arm CROSS_COMPILE="/home/jazzyb/tf201/prebuilt/darwin-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-" zImage

I have also tried the arm-linux-androideabi-4.4.x tools.

I then use the a variant of AnyKernel that identifies itself as Jermaine151's TFP kernel updater. I am just dropping the zImage in place of the existing one, rezipping and flashing with TWRP. When I reboot after flash the tablet just stops at the initial ASUS screen. Reflashing motley's 3.0.4 packaged kernel brings everything back. Any suggestion to what I am doing wrong?
[Asus  Eee Pad Transformer Prime] tobi01001:
Don't know if its possible with the prime but in my HTC desire days (still got it) I used to not flash the kernel but to use fastboot to test it.

Should be something like "fastboot boot zImage".

With fastboot, the kernel is only booted temporarily and you should have your old system up and running after reboot.

Well it could happen, that you may miss some modules then....

Edit:

http://elinux.org/Android_Fastboot#To_boot_with_a_host-side_kernel_image_.28and_rootfs_image.29

You may then check with adb logcat whats going on during boot...

Sent from my Transformer Prime TF201
[Asus  Eee Pad Transformer Prime] jazzy__b:
I was just beginning to look at fastboot anyway but it seems not to be working on my TFP. I can see the device in 'System Information', calling itself Fastboot but, when I try to perform an action in fastboot it just says <waiting for device> and sits waiting indefinitely.
[Asus  Eee Pad Transformer Prime] st33med:
Did you give fastboot the vendor id? (0x0b04 if I remember correctly). For whatever reason, fastboot doesn't detect the device automatically and you have to tell it the vendor id.

Additionally, you can't fastboot a kernel. Really, if you want to do anything, fastboot a recovery like CWM or TWRP and flash a zip in there.

---------- Post added at 08:53 PM ---------- Previous post was at 08:51 PM ----------

Speeds can vary. I've had 136 on one test in .21. Take benchmarks with a grain of salt, people.
[Asus  Eee Pad Transformer Prime] saturn_de:
I can make a blob image, if you give me the source. Any github tree?

---------- Post added at 03:03 AM ---------- Previous post was at 02:55 AM ----------

Get BootTools and BlobTools. Extract the ramdisk with blobunpack and bootunpack.

Inject your bcm*.ko (wifi driver) in the cpio ramdisk, or maybe the old ones work.

# mkbootimg --kernel <your_zImage> --ramdisk <blob.LNX-ramdisk.cpio.gz> -o boot.img
# blobpack -s boot.img LNX boot.img
[Asus  Eee Pad Transformer Prime] Tempie007:
Found some other benchmark, Androbench. This has SQLite tests, raw speed tests and real world tests.

With this patch the SQLite bench gives really good scores as expected.

The area that really shows what's wrong with this device is the Random Write test.

Ok the prime does perform twice as bad than most devices in most areas but not as mind shocking as in this test....

And its no coincidence that random write performance is important for SQL ... do your math ....
[Asus  Eee Pad Transformer Prime] dagrim1:
Yeah, it's pretty sad...

Just ran the Androbench on my SGS3 and on the prime...

Sequential read: 43.5 vs 17

Sequential write: 7.4 vs 4.7

Random read: 9 vs 5.4

Random write: 0.23 vs 0.56

SQlite: these scores seemed way off ( factor 5 to 10 higher for the prime, sqlite patch messing something up here imo)

Browser: 1429 msec vs 132 msec

Market: 2561 msec vs 349 msec

Camera: 5894 msec vs 211 msec

Camcorder: 3940 msec vs 552 msec

*sigh*

If only other brands had this sleek dock design option.

Made me lookup comparisons with other tablets, here a comparison with the Acer Iconia A510:

http://www.androidpolice.com/2012/05/09/head-to-head-asus-transformer-prime-vs-acer-iconia-tab-a510/

Interesting pieces:

and
[Asus  Eee Pad Transformer Prime] Tempie007:
comparible results here on my sgs3

my desire HD is faster than prime too..

but back on topic :)

wondering on how the compiling goes!
[Asus  Eee Pad Transformer Prime] Tempie007:
take a look at this

http://xdaforums.com/showthread.php?p=27642426
[Asus  Eee Pad Transformer Prime] leppie:
Once you have that working, let me know, I think I'll start tinkering on it :)

My Git skills suck big time.

Also still need to find how how to package the kernel blob.
[Asus  Eee Pad Transformer Prime] jazzy__b:
Still struggling big time with getting a stable kernel build onto my tablet. Getting some help from motley on PM. It's either my build process or the TFP AnyKernel zip I'm using. I've done clean builds on 3 different machines now from motley's source (1 Mac, 2 Linux). I also extracted and repackaged motley's kernel into AnyKernel and that fails to boot but I may have extracted the blob incorrectly. Is there another source for the TFP AnyKernel; I downloaded the zip from a forum thread - is there a github somewhere for it?

On the assumption that I will get the packaging issues sorted out I'm going to start patching the changes across into a new build directory ready to test.
[Asus  Eee Pad Transformer Prime] jazzy__b:
The patches I want to incorporate from the linux tree target this exact area.
[Asus  Eee Pad Transformer Prime] jazzy__b:
Thanks I will look at this.

EDIT - sorry I forgot to say I'm building from motley's latest github source tree. A blob would be great as a starting point, or I may use your pointers to unpack and repack motley's blob.
[Asus  Eee Pad Transformer Prime] CekMTL:
Hey, I'm using this same approach (anykernel) without any issues... what is the problem? last_kmsg could help maybe?
[Asus  Eee Pad Transformer Prime] _motley:
Yeah, I have been trying to help him as well with the same types of suggestions. I am not 100% sure, but I think it is his built kernel (zImage) that is causing the issue. I recommend that folks always first unpack/repack with a known working zImage (mine or stock) to make sure your packaging and deployment method works.

Next, build from known working source without any changes (stock or mine) and then use the known working deployment method.

Finally, add your changes, compile and deploy using your known working deployment method.

If you have a 32GB prime, skip the blob unpack/repack steps for now, they just further complicate things. Hope you get it sorted out JB!

CekMTL, how were you grabbing the last_kmsg when the kernel wouldn't boot? Did you flash the working kernel and were still able to retrieve it or were you using adb somehow to do it from recovery or something?
[Asus  Eee Pad Transformer Prime] CekMTL:
Heeeeeeey Master _motley !!!!

Well.... I always try to keep it stupid and simple (kiss, simple=elegant), so in reality, I just "flash" a .zip that copies the last_kmsg from /proc to /sdcard.... heheheheh :D

I've attached the file I use here for all to use ;)

Boot into recovery, flash this first and then flash a known kernel that works, then reboot, and go grab the last_kmsg in /sdcard :cool:
[Asus  Eee Pad Transformer Prime] CekMTL:
Disable fsync() without patched libsqlite.so

BTW, completely forgot to post this info that I found a couple days ago...

You can enable/disable the "fsync()" functionality by doing the following:

1) Terminal as root

2) sqlite3

3) PRAGMA synchronous;

This will give you the current setting...

0=Disabled (so with patched lib, it will give 0, else 2).

To change you just have to issue:

PRAGMA synchronous=0;

and that's it!

For more technical info : http://www.sqlite.org/pragma.html#pragma_synchronous

Cheers!
[Asus  Eee Pad Transformer Prime] jazzy__b:
Works like a charm, I had no idea the last kmsg would persist across a reboot. I don't see a smoking gun in the output. There are a number of failures to initialise or read various things. I don't know if these are normal or point to something else going wrong. Perhaps it is a failure to load modules? Any ideas?

http://pastebin.com/Q4j6h090
[Asus  Eee Pad Transformer Prime] CekMTL:
Hey!

Hummm.... well.... I think you should wait longer before rebooting, to let it fill more infor in the kmsg... weird is that it all seems ok more or less, but there should be more info... it stops at around 7.5s ....

1) could you retest again and grab log but WITHOUT EXTERNAL SD CARD

2) does it reboot automatically in like 10s (bootloop) ?

3) To where do you get?

- Phase 1: Eee Pad nVidia logo

- Phase 2: Asus Animated logo

- Phase 3: Asus Animated logo and circular progress indicator (high brilliance screen)

- Phase 4: The same but the screen gets dimmer

- Phase 5: Graphical shell comes in.

Phase 1 is pure kernel domain, loading image, decompressing, booting, decompressing ro ramdisk, loading all modules and initializing all the preripherals, etc. From there it loads the partition table of primary boot (GPT), checks FS consistency, fsck if necessary (I think it does it almost always...), then switch to RW and continue with the rc scripts

Phase 2 start loading all the services and other system binaries, then initiate Zygote, Dalvik, and start the Android layer, and then keep on, etc...

Now this...

It does see these partitions:

This I don't remember seeing, will have to check with mine...
[Asus  Eee Pad Transformer Prime] jazzy__b:
Thanks for all this help guys I appreciate it.

Retried without the microSD. From bootup I get the eee pad nvidia logo for 42 seconds before a spontaneous reboot, then it's volume down and back into TWRP to get the last kmsg.

http://pastebin.com/a3uAvg1Y
[Asus  Eee Pad Transformer Prime] CekMTL:
From what you are saying, I understand that the system partition doesn't get mounted, and the .RC don't get executed...log should be longer...

The difference I see with mine is :

Did you by chance disable the SD option, scsi or other stuff?

WAIT, still investigating on my end...

I'm out of ideas for now... something must be missing.

I would recommend making a backup of your kernel .config and starting from scratch, first with modded sources (.c .h), and only motley's config (make ARCH=arm motley_cardhu_defconfig), compile and try to boot that, and if lucky, then little by little start modding kernel options, etc.
[Asus  Eee Pad Transformer Prime] jazzy__b:
jazzyb@and-dev:~/tf201/motley_TF201-Kernel$ git remote -v
github git://github.com/motley-git/TF201-Kernel.git (fetch)
github git://github.com/motley-git/TF201-Kernel.git (push)

jazzyb@and-dev:~/tf201/motley_TF201-Kernel$ git diff remotes/github/master

jazzyb@and-dev:~/tf201/motley_TF201-Kernel$ git status
# On branch master
nothing to commit (working directory clean)

jazzyb@and-dev:~/tf201/motley_TF201-Kernel$ diff .config arch/arm/configs/motley_cardhu_defconfig
1,5d0
< #
< # Automatically generated make config: don't edit
< # Linux/arm 2.6.39.4 Kernel Configuration
< # Wed Jun 20 10:31:27 2012
< #
43c38
< CONFIG_LOCALVERSION="-cardhu-motley-v3-jazzyb"
---
> CONFIG_LOCALVERSION="-cardhu-motley-v3"
330a326
> CONFIG_ASUS_GPS=y
338a335
> CONFIG_ASUS_OVERCLOCK_MODES=y
2636d2632
< CONFIG_ASUS_GPS=y
3067c3063
< # CONFIG_AVERAGE is not set
---
> # CONFIG_AVERAGE is not set
\ No newline at end of file

I didn't change the CONFIG_ASUS_OVERCLOCK_MODES setting, just running make menuconfig seems to do that. The only other change I made was to take some -O2s out of the Makefile but that was a recent change, my kernel was broken before that. EDIT - the -O2 changes were reverted just before I took this diff which is why it doesn't show.

FYI my build command is:

make -j2 ARCH=arm CROSS_COMPILE=~/tf201/android-ndk-r8/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-
[Asus  Eee Pad Transformer Prime] dagrim1:
Wish I could be of more help with all this...
[Asus  Eee Pad Transformer Prime] jazzy__b:
In anticipation of finding a fix for my build/packaging issues I have begun patching mmc kernel code. Unfortunately all I can do for now is prove that each one compiles and keep them as separate commits in git to allow separation for debugging if necessary. I will keep you all posted of any progress.
[Asus  Eee Pad Transformer Prime] saturn_de:
Can you make your changes public? Maybe I can get a kernel to boot...
[Asus  Eee Pad Transformer Prime] jazzy__b:
I will look into this but I feel a bit uncomfortable about pushing untested changes into a public git repo. In the meantime I wonder if anyone else would like to test my kernel update .zip just to prove it's not an issue with my tablet. I don't expect this to be the case but it's another variable to rule out.
[Asus  Eee Pad Transformer Prime] dagrim1:
Want to give it a try but running AOKP atm so I dunno if that'll work... will try it anyway, making a cwm backup first ;)
[Asus  Eee Pad Transformer Prime] jazzy__b:
This is a motley generic build so should work with AOKP - that's what I'm running. Just keep motley's .zip handy to flash back to, that's been working fine for me.
[Asus  Eee Pad Transformer Prime] CekMTL:
Just tested, and the same result as you.

[ 7.273688] scsi 0:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 0
[ 7.274464] sd 0:0:0:0: sda:wake_lock +
[ 7.276592] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 7.554264] tegra_watchdog_touch
[ 7.555055] nct1008_get_temp: ret temp=36C
[ 7.555408] Reg Status Reg 0x02 Value 0x80
[ 7.555865] Reg Configuration Reg 0x03 Value 0x04

No errors detected
[Asus  Eee Pad Transformer Prime] dagrim1:
No luck, getting into a bootloop where I see the Eee pad asus screen and then back to black again (etc)...
[Asus  Eee Pad Transformer Prime] jazzy__b:
If I understand correctly, motley's kernel is built for use with a ramdisk, which is built into the installation blob and I guess the recovery image. AnyKernel doesn't provide a ramdisk so where will things like /init come from? Would a missing /init be consistent with the logs I posted?
[Asus  Eee Pad Transformer Prime] Peter Galbavy:
AFAICR this is only valid for the "session" you are running for. As soon as you close the database file(s) / exit then the change is reverted. You would have to find the open database routinges in Android and insert the PRAGMA there. It's easier to change the compile time default.
[Asus  Eee Pad Transformer Prime] CekMTL:
Ok, thanks for the info, thought it was a global switch. :good:
[Asus  Eee Pad Transformer Prime] jazzy__b:
I'm continuing to merge mmc patches in from Linux ready for when I get my build to work. I seem to be getting more log output from the boot when I switch to a non-motley kernel. The bad news is that the output includes a kernel oops. I got my first with stock kernel on AOKP. I have pasted the output from my build of cm9 kernel run against the 22nd June nightly cm9 ROM. Hoping someone cane give me a pointer.

http://pastebin.com/77BagNgA
[Asus  Eee Pad Transformer Prime] jazzy__b:
For what it's worth, all of my recent builds have been clean git clones followed by make config then make. The above log was using the CM9 tegra3_android_defconfig.

Sent from my Samsung Galaxy S II
[Asus  Eee Pad Transformer Prime] st33med:
Thank you for trying to improve the transformer prime. It would help if you provided git source code so people can look at it. Don't worry about people compiling it as people are lazy and some don't know how to compile one. Hell I don't even know. :p
[Asus  Eee Pad Transformer Prime] CekMTL:
Hey!

Well.... :( checked log but don't have a clue... seems I need to learn more debugging skills to be helpful.

What I do with my kernel is incremental in very small steps .... I have compiled like about 200 times now... small change compile test see if everything ok, better? worse? the same? ... over and over again.

I also made myself a script that takes care of automating all these tasks, and also creates the zip file with the modules and all...
[Asus  Eee Pad Transformer Prime] jazzy__b:
Maybe I could take a look at your script to compare with what I'm doing? I had no idea that I could spend a week and still not have a working kernel build from untouched source code. So far I've tried 4 different source repositories, two different ROMs on my tablet, three different build machines (1 Mac, 2 Linux) and I'm just trying my third compiler toolchain. I'm sure it shouldn't be this difficult. I'm wondering if there's a real beginner's step I'm missing that seems so obvious to everyone else that noone's mentioned it.
[Asus  Eee Pad Transformer Prime] CekMTL:
Very VEEEERY simple script, nothing fancy or special...

#!/bin/sh

# Por ahora muy muy basico pero nos sirve para automatizar todo el ciclo de pruebas.

BASE_ANYKERNEL=~/android/MyTools;
DEST_MODULES=${BASE_ANYKERNEL}/AnyKernel/source/system/lib/modules;
DEST_KERNEL=${BASE_ANYKERNEL}/AnyKernel/source/kernel;
COMP_KERNEL=~/android/TF201-Kernel;
# Ejecutar desde donde esta el source del kernel en cuestion!

clear;

# Compilamos todo para luego empaquetar el archivo .zip para flashear.
#make -j7 ARCH=arm CROSS_COMPILE=/home/cek/android/arm-2011.03/bin/arm-none-eabi-
make -j7 ARCH=arm CROSS_COMPILE=/home/cek/android/toolchain-4.6.3/bin/arm-linux-androideabi-

# Copiar archivos necesarios
cp arch/arm/mach-tegra/baseband-xmm-power2.ko $DEST_MODULES;
cp crypto/tcrypt.ko $DEST_MODULES;
cp drivers/net/usb/raw_ip_net.ko $DEST_MODULES;
cp drivers/net/wireless/bcm4329/bcm4329.ko $DEST_MODULES;
cp drivers/net/wireless/bcmdhd/bcmdhd.ko $DEST_MODULES;
cp drivers/scsi/scsi_wait_scan.ko $DEST_MODULES;
cp drivers/usb/serial/baseband_usb_chr.ko $DEST_MODULES;
cp drivers/staging/android/logger.ko $DEST_MODULES;
cp arch/arm/boot/zImage $DEST_KERNEL;

# Crear el nuevo .zip
rm ~/android/MyTools/AnyKernel/out.zip;
cd ~/android/MyTools/AnyKernel/source/;
zip -r9T ~/android/MyTools/AnyKernel/out2.zip *;

# Copiamos el nuevo .zip al TF si está conectado.
sudo /home/cek/sdk/platform-tools/adb kill-server;
sudo /home/cek/sdk/platform-tools/adb start-server;
sudo /home/cek/sdk/platform-tools/adb push ~/android/MyTools/AnyKernel/out2.zip /sdcard/-ROM/TEST;
sudo /home/cek/sdk/platform-tools/adb shell sync;
sudo /home/cek/sdk/platform-tools/adb shell sync;
sudo /home/cek/sdk/platform-tools/adb reboot;

Are you saying that you can't even compile a bootable _motley kernel yet? ... maybe it's you compiling enviro?, toolchain? ... I've switched today to Gcc 4.6.3 to see how it goes...
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Eborg:
When internet access (either idle or during active use) is necessary, what is the better option for battery life?

Does Wi-Fi drain more battery, is it the other way around or is it the same?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] GR36:
Best option for bettery life is to leave wifi on when your in wifi area

Sent from my GT-N7000