yashsingh1/xdaforums huggingface dataset:
[Folio 100 Android Development] spicyalan:
Weird... Is the size correct ? (maybe something happened in the download)

EDIT: I have added a new download source... Hosting at goo.im is stll not working :(

EDIT2: found a trick to work around the 1.6Ghz SOD (see 1st post), might give a clue for other SOD's?

According to kernel code, the CPU is set to max speed when resuming (max speed during board initialization might be a bad idea). I think this should be throttled (e.g. 600Mhz) until the screen is on. This can be simulated with overclock widget and its "screen off clockspeed profile".

Again something to test for someone with SOD's
[Folio 100 Android Development] miazza:
I'm right now testing v4 at 1600. It looks stable. Nice job.;)

Edit: when the tablet goes to sleep with the blinking led I cannot wake it up. I need to maintain wakelock at 5.

Sent from Folio 100 using tapatalk
[Folio 100 Android Development] m32:
how did u flash/run new kernel - i'v used flashboot boot xxx.img, but it dies in cm-splash :( - I'v cm-10.1
[Folio 100 Android Development] miazza:
I simply followed the commands at first post.
[Folio 100 Android Development] spicyalan:
On which frequenties? I only have it on 1.6, but it could be interesting if you also have it on other frequencies
[Folio 100 Android Development] miazza:
At 1 Ghz with wakelock at 4 no SOD after standby. At 3 I have SOD.

Sent from Folio 100 using tapatalk
[Folio 100 Android Development] spicyalan:
What do you mean with "wakelock at 4"? Are you using an external program?

I'm also doing soms cleanup in the frequency tables, because it is a mess:

- undefined clocks when going into suspend

- 216 MHz is defined in the frequency tabel, but had no multiplier definitions, nor voltages in dvfs.

- suspend/resume governor switch weirdness (e.g. the config CONFIG_TEGRA_CONVSERVATIVE_GOV_ON_EARLYSUPSEND suggests that its developer was heavily dyslectic, or drunk :) )
[Folio 100 Android Development] spicyalan:
isn't it fastboot flash linux xxx.img. ?
[Folio 100 Android Development] miazza:
Yes, I use an external program "wakelock".

It gives you several wakes levels and as soon as I disable the wi-fi the SOD happens...

The program is likely overriding the system governator and , according to me, you are going in the right direction.

Good job to try frequency table clenup :) ...
[Folio 100 Android Development] spicyalan:
What happens if you disable wifi manually and put the tablet to sleep? (without wakelock program).
[Folio 100 Android Development] grenho:
Hi there. First of all thank you spicyalan, for trying to make our Folios somewhat usable.

I just wanted to report that I still am experiencing SOD with both V4 and V4b. Currently my settings are:

Rom: Jelly Bean / CM10.1 (4.2.2) Beta 1

CPU freq. - 1400MHz

screen off CPU freq - 1000MHz

That doesn't happen with V3. Sure, I still have to double click the power button to wake up the device, but still, was usable after standby.

I hope this information helps you finding and solving the problem
[Folio 100 Android Development] miazza:
If wi-fi is disabled manually I get SOD. :( This is quite strange...

Sent from Folio 100 using tapatalk
[Folio 100 Android Development] spicyalan:
As I was suspecting... Wifi and wakelocks also keep the CPU out of sleep.

Anyone up for another test? (especially who has the SOD at stock speed, preferrably on a kernel with LP0 or LP2 or DerArtem's kernel)

Install overclock widget ( https://play.google.com/store/apps/details?id=org.freecoder.widgets.overclock )

Place the widget on the screen and change the settings (don't forget to save and enable). You don't have to overclock.

Try several "Screen off Freq Settings", both wil low maximums an high minimums (e.g. 312-608,608-1000,...) and suspend the device.

This will not be the speed that the Folio will sleep at, This is the speed set before screen goes off. The processor will still go into deep sleep a few seconds later.

If any specific speed (or range) would work consistantly, that would be a help.

(as said.. mine sleeps fine on any frequency between 608 and 1400Mhz, lower then 608: wakeups, higher than 1.4: SOD)
[Folio 100 Android Development] uc370:
fastboot error

I always get the same error..

Device correctly conected.

Fastboot erase linux.. Error something like no such directory

Fastboot filas linux oc.img.. Error.. Sending 2660 till tomorrow

My tablet freezes (no SOD i use wakelock) with the B1 built and I'm trying to install A1 with V4.. Could you post a B2 with V4 kernel?!!
[Folio 100 Android Development] miazza:
I have tried different frequencise but everytime I go is sleep with blimking led I get sod. The blinking becomes fix a nothing else.

Sent from Folio 100 using tapatalk
[Folio 100 Android Development] spicyalan:
I don't know if my 1.6Ghz SOD is caused by the same problem as your SOD at stock speed...

I have added a new kernel with some cleanups. I don't think it will solve the SOD's, but still useful to try.
[Folio 100 Android Development] spicyalan:
uploading one now (with V5 kernel. I don't think LP2 sleep will solve the SOD)
[Folio 100 Android Development] grenho:
Even with the new V5 I'm still getting SOD.

spicyalan you should post a list of requirements to all testers to help you debug this problem. That way all would use the same apps to set freqs., wakelocks and whatnot
[Folio 100 Android Development] *Sami:
As far as I recall some have posted their logs, when SOD happened earlier [on A2 thread]. Secondly, while it might not be that much of importance - with 4.1 sometimes after resuming - audio did not work correctly - unless there was paused media playback in the background.

Anyhow, I think that TEGRA LINUX DRIVER PACKAGE documentation can be helpful lecture. (ʃ⌣́,⌣́ƪ)
[Folio 100 Android Development] miro_mad:
This boot.img file work for me (NO SODs). The file is from this ROM - update-cm-9.0.0-RC0-2012.03.04-betelgeuse-KANG-signed
[Folio 100 Android Development] spicyalan:
But this one won't work with cm10.1.

The newer kernel also works for me without SOD on cm 10.1 (and a few others), but not for everyone.
[Folio 100 Android Development] spicyalan:
I have checked these logs.

There aren't any hardware differences in dmesg (same tegra revision, same everything)

I don't know how much to trust these logs (is it really the last thing in dmesg... or not?), but it seems there is a difference in my 1.6Ghz SOD and the generic SOD which is not reproduceable on every device.

- The 1.6Ghz SOD fails at resume (goes to sleep fine sometimes, blocks on resume or during hidden resume in sleep). This SOD has an easy work-around by setting the max speed to 1000Mhz before early suspend and return to normal after late resume. This SOD blocks the whole device (no restart to read kmsg, but can be scanned with nohup cat). I can add this code in the kernel, so we don't need external programs for this.

The last thing in the log (be careful.. could not be the last thing...)

<4>[ 2444.027608] tegra_pwm tegra_pwm.0: pwm_disable called on disabled PWM

- The generic SOD

Last line in the log (reported by 2 people):

[ 177.344799] PM: Syncing filesystems ... done.
[ 177.346637] Tegra cpufreq suspend: setting frequency to 216000 kHz
[ 177.359322] Freezing user space processes ... (elapsed 0.02 seconds) done.
[ 177.385999] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[B][ 177.406212] Suspending console(s) (use no_console_suspend to debug)[/B]

While mine, without SOD, goes on:

<6>[ 395.256234] PM: Syncing filesystems ... done.
<6>[ 395.262871] Tegra cpufreq suspend: setting frequency to 608000 kHz
<4>[ 395.273642] Freezing user space processes ... (elapsed 0.02 seconds) done.
<4>[ 395.294806] Freezing remaining freezable tasks ... (elapsed 0.03 seconds) done.
[B]<4>[ 395.334828] Suspending console(s) (use no_console_suspend to debug)[/B]
<6>[ 395.344902] vi vi: suspend status: 0
<6>[ 395.344925] isp isp: suspend status: 0
<6>[ 395.344949] gr2d gr2d: suspend status: 0
<6>[ 395.344969] dsi dsi: suspend status: 0
<6>[ 395.346324] gr3d gr3d01: suspend status: 0
<6>[ 395.346351] mpe mpe01: suspend status: 0
<6>[ 395.347649] tegra_avp_suspend()+
<1>[ 395.347689] WLAN PWR set to DISABLED~

I will check those deeper, but during the holidays my time to work on this is limited

Other forums and tegra2 devices also try to solve SOD's. There are many patches, but none that really nails it.

Some report that they got rid of it after wiping reinstalling their ROM.

everyone that wants to help with the SOD investigation, please visit this post:

post

Also.. Is there someone with the SOD brave enough to

completely

wipe, format and reinstall a CM10.1 ROM + gapps and try if the SOD is still present? (without yet restoring backups or installing apps).
[Folio 100 Android Development] spicyalan:
I have placed a new version online:

This one includes a workaround for the 1.6Ghz SOD. Basically, it sets the max speed to 1000Mhz when screen goes off, and restores previous max speed when screen goes on.

It does not include a fix for the generic SOD that some have (still waiting for input...)

I have also been experimenting wih the carvouts. I have managed to get an Extra 3Mb from the framebuffer and 8Mb from the GPU (mem up to 371Mb).

Altough it doesn't show a regression in graphic benchmarks, I do feel that it is less smooth (e.g. Chrome browser.... tough, it could be wrong), so I have rolled back these changes.

Other tegra2 devices with 1Gb of mem (e.g. Sony tablet S at 1Ghz) are much smoother, but use up to 256Mb of GPU mem (a luxury the folio can't affort)
[Folio 100 Android Development] raptor92:
When I try yo flash it, it says: access denied (Too many links)

Donnow what to do!

Inviato dal mio GT-I9001 utilizzando Tapatalk
[Folio 100 Android Development] spicyalan:
is this with fastboot? Windows (did you reboot ;) )?

An alternative method would be to install the ROM+Gapps zips again through the recovery (no need for a wipe if you upgrade from Derartems CM10.1).

I have a kernel (and ROM) ready to upload, but again no big changes. I have added the "deadline" scheduler, which seems to help a bit in the "lag during write to SD". The Dalvik patch I included last time also helps the Folio (but this needs installation of the ROM, as it is not in the kernel).
[Folio 100 Android Development] raptor92:
I tried everything...reinstall recovery and re-partition, wipe and reinstall rom, reboot and reinstall fastboot drivers....

Don't know who to do!! :(
[Folio 100 Android Development] spicyalan:
But if you installed the ROM, you don't need to use fastboot (kernel is included already in the ROM)
[Folio 100 Android Development] raptor92:
What version?

Inviato dal mio GT-I9001 utilizzando Tapatalk
[Folio 100 Android Development] spicyalan:
The B1.20121220 should normally include the same kernel as in V6.

If you still need to flash, wait until this evening. I will upload a version with an extra I/O scheduler.
[Folio 100 Android Development] raptor92:
Thank you a lot! :D
[Folio 100 Android Development] spicyalan:
I have uploaded a new kernel (V7), and a new ROM (20140107, that includes this kernel). The rom is in the other thread.
[Folio 100 Android Development] *Sami:
As to not only lurk (thank You for your earlier reply) - again it's really heart warming to see that someone cares, so much for this tablet and other Users.

Nevertheless, I have slight concern over Your development choice - I do not believe that overlocking is a good idea, especially GPU. Those machines in general have low operating temperature (about 24 °C, 75 °F), which I believe is something to go after rather than pursue minor performance gains.

On SOD - from logs included in Your previous reply it seems that devices influenced by generic SOD have 3 times lower CPU frequency when going to sleep. 「(°ヘ°) Maybe then re-arrange whole sequence and force CPU spike on that action?
[Folio 100 Android Development] spicyalan:
I'll check the logs again... Maybe this is a good find (I didn't notice that...)

Overclocking is an option with these roms. If you don't change anything, it will still run at 1Ghz stock speed. There are also a few additions which aren't related to clock speed (low mem Dalvik Patch, reclaiming HDMI framebuffer memory, added I/O scheduler).

Anyway, normal operating temperatures of a tegra 2 can be between 40C and 60C, with a staggering maximum of 105C.

Don't forget that the Folio 100 has an excellent thermal reserve (big heavy case to conduct heat), while some phones without any thermal headroom run the same chip at 1.2Ghz.

Battery life might be negatively impacted. As I state, overclock is at own risk (but could breath new live in an old device).
[Folio 100 Android Development] *Sami:
Sorry, I have incorrectly recalled that You have increased GPU base frequency as well. However, have You considered adding additional governors instead of overlocking?

Build.prop could use some few tweaks as well - more aggressive ones (e.g.: omitting verification). I suppose that audio could also be checked, because if I remember correctly it supports 24-bit output, while it is set to 16-bit by default.

I was thinking of case temperature (also battery), which is possibly one of biggest pros of this tablet (as some skyrocket to even 40 degrees).

I still think that performance should be primarily achieved by optimization not by forcing hardware.
[Folio 100 Android Development] spicyalan:
I think we should do both. If you have suggestions for build.prop, please post.

Audio is quite messy in the code, but it does work perfectly.

As for the gpu overclock, you are right. I did change some parameters for max speed (and it is not possible to switch it at run time), but the same maximum parameter also exist in later (1.2ghz) tegra boards.

The interactive governor is the best one there is for speed. Others usually optimize for battery life (or both). I did include an io scheduler that can help in the stuttering when writing to flash.
[Folio 100 Android Development] spicyalan:
It seems I already do this. In a previous fix, I have filled in a missing suspend index in the frequency table, so it will always go to 456Mhz during the last step before cpu shutdown (before, it was a random speed). On resume, it will not go higher than 1000mhz (overclock will only start after screen has been activated).

I already did a test in the past with someone to try several speed settings (different mins/max), but none seems to fix it.
[Folio 100 Android Development] m32:
[ 177.344799] PM: Syncing filesystems ... done.
[ 177.346637] Tegra cpufreq suspend: setting frequency to 216000 kHz

in this moment my connection to folio by adb goes down :(

i'v used cat /proc/kmsg to see what is going on

:( doesnt help, i'v viped all, reformated all partitions - data and emulated0 both are 12GB in size

adding in board-betelgeuse-panel.c (betelgeuse_panel_early_suspend)

tegra_pm_irq_set_wake(tegra_wake_to_irq(24), 1);

in log its notices as wake24 - irq=...

does just nothing :( - in early suspend can wake by power button, but later ... adb connection is lost and can't reconnect

for me it looks like exception in kernel - null pointer assignment und device hangs with more> prompt with disabled all devices
[Folio 100 Android Development] spicyalan:
It is normal that this is the last message (cpu switches off).

I have found a patch that fixed an sod on the tf101. I didn't have time to check if this was already included in the folio kernel (the i2c part)

https://github.com/timduru/tf101-katkernel/commit/fecf2134edb6c047cb4e4ceafd0599d0e59d9dee
[Folio 100 Android Development] uc370:
Ive got no sod at all..

I use the 7/01 rom at 1400/618 interactive and deadline.. plus seeder on boot and lagfix regularly.. getting 10200 on untutu.(only)

Still got wakelock and advanced wifi unlock running

Thx again spcyalan!! This rom is perfect for me!! Keep going..
[Folio 100 Android Development] m32:
Nice but tablet wont boot up :-S - blinking red goes to stale white. After adding wake24 Pv2? Just before last message tablet wakes - after three or more presses but it hangs before fully running adb. Most commic part is screen - fully repainted but tps int responsible :( - at all
[Folio 100 Android Development] spicyalan:
Interesting. It seems to be unable to read the memory card (mmcblk0... so the build in one).

Now... or there is there a difference between the memory card in my folio and yours, or there is something triggering this behaviour.

As I suspected, the issue is at resume time (but folio resumes multiple times during a long suspend, sometimes even just after suspend)
[Folio 100 Android Development] spicyalan:
My kernel messages are the same, except for the MMC errors (I have none)

kmsg shows thep people with the wake bug has the same MMC in the boot.log as mine (so hardware is the same)

I have found similar errors where reported (on boot):

http://comments.gmane.org/gmane.linux.kernel.mmc/20572
[Folio 100 Android Development] spicyalan:
Anyone want to try this one?

I have added a patch in the MMC system (it is a long shot, but worth a try).

It does not have negative effects on a folio with a good sleep.

boot.img
[Folio 100 Android Development] doragasu:
I have flashed V8 kernel and I am still suffering SODs, but it took my by surprise that now touchscreen works WAY BETTER. Before, corners didn't work well (touching corners was really tricky) and sometimes touchscreen stopped working for a while. I thought it was a hardware problem, but since I flashed this kernel, corners work flawlessly and responsiveness is great!!!! Another big THANKS!!!
[Folio 100 Android Development] spicyalan:
If you overclock, the tablet can respond a bit quicker.... But what you are decribing is the "unresponsive touchscreen problem", which is quite common on Folio's

I had the same problem on my tablet (within 3 months of use), but got it repaired under warranty. I think some older threads also talk about it.

You can usually (temporarily) fix it by pressing in the lower middle of the screen, or by putting a thick folder paper behind the battery. Possibly this is some kind of loose cable.
[Folio 100 Android Development] doragasu:
I have read about this problem, and tried the tricks you describe, but believe it or not, the new kernel is what has fixed it. I had this problem for a very long time and since yesterday it is completely gone.
[Folio 100 Android Development] m32:
doesnt help :( - still have sod
[Folio 100 Android Development] Miraculix666:
Maybe could we get some hints from other Kernel developers, in may case the LG-P990 had SOD for a long time. but since a while (atm with KOWALSKI-Kernel) it is gone. as far as I know it is the same SOC build in.
[Android Q&A, Help & Troubleshooting] Raice.f4h:
I searched for a cheap phone because I have a happit breaking them. I ordered the Simdo D98T.

When I received the Simdo It came in a nice box. But I was supprised there wasn't any playstore. Only Chinese Markets and Apps. But I can't read a word Chinese so I would love to have the normal Play Store. After a few days searching I got across a Rusian forum. With the help of Google Translate, I figured out how to place CWM and also gapps on the Simdo D98T.

You need SP Flash tool (like every other Chinese phone. Ik used version 13.08. If there is somebody who needs it I can provide a link.

After that you need this files from the Russian guy:

https://docs.google.com/file/d/0B8K6WlfE3JM9Ri1PMDZyTGtlZU0/edit

Open SP Flash tool and load the scatter file that you just downloaded. After the scatter is loaded disable the preloader, it might save your phone.

In case (like mine) the other files are empty, fill the recovery with the CWM image and the boot with the bootimg.

Remove the battery from the phone and connect the USB cable. Be sure you have the drivers installed.

Press the DOWNLOAD button in the flashtool. After inserting the battery it needs a few seconds to install. When a green circle is displayed, you have succesfully installed CWM. Now you can download the matching GAPPS (4.2) and place it on the SD Card of your phone.

Boot to CWM and install GAPPS, No need to delete your data it just works out of the box.

I hope somebody is happy with this small explaination. Sorry for my bad English sometimes. But I hope I helped a few people out. Have fun with Goolge Play and CWM :D
[Android Q&A, Help & Troubleshooting] manolito1998:
Hello,

Thanks for the info.

But, may I ask you something?. Could you please make a backup of the rom and upload it?

I bought it, and this is the second time that pandawill sent it to me broken. Each time I send it to Pandawill costs me 25€, so I would like to try to fix by myself, because the only solution that they give me is send it back to be fixed.

Thanks in advance.
[Android Q&A, Help & Troubleshooting] Raice.f4h:
I bought a couple of phones but got scammed. So to not get a bad name around here I gave my phones away. A new phone from an other seller is on it's way to me. When I receive it I will upload it!
[General Questions and Answers] kkbs4u:
My karbonn A8 reboot automatically when I reboot my device manually after reboot 2 time device working fine what is the problem with my device
[General Questions and Answers] Mrinal Roy:
may be some apps...or your charger probem!
[General Questions and Answers] Mrinal Roy:
Or format ur phone! let see if it happens then?
[General Questions and Answers] kkbs4u:
I was also format my device but problem is same I want to install other custom rom on my device can u tell me where can I download custom ROM for my karbonn A8
[Asus Transformer TF700] ishamm:
i have the latest twrp and cromi-x, but when i reboot holding the volume buttons, i get RCK, Android and WIPE DATA as options, no fastboot. Presumably ive gone wrong somewhere, but i cant figure out where.. any help would be great! :)
[Asus Transformer TF700] _that:
Read the text in the upper left corner. The 10.6.1.14.x bootloaders enable fastboot automatically in the bootloader menu.
[Asus Transformer TF700] ishamm:
Thanks,

that is what i was thinking/hoping, but adb devices shows up with nothing. is this (another) windows 8.1 issue perhaps?
[Asus Transformer TF700] berndblb:
In fastboot you would use: "fastboot devices"

If that returns nothing, you will have to find the correct drivers for your PC. In Win 8 you have to turn off Windows driver signature verification or some such... Search for it - there are a couple of threads that help you to get Win 8 work with fastboot.