[ROM] [4.2.2] [ No-name CM10.1 nightlies ] [ Standard & Linaro ] [TF101 / TF101G]

Search This thread

josteink

Senior Member
Feb 8, 2011
2,243
1,808
Oslo
Hi, josteink

I just installed Your latest stable build. Everything is working fine right now, but it's to early to say anything ;). Quick question though, your rom doesn't support Exfat on micro sd. Is it because of rom or kernel ?. I guess it kernel related but want to be sure.

Latest builds has extra support. Just use those :)

Sent from my Galaxy Nexus using Tapatalk 4 Beta
 
  • Like
Reactions: zboq

zboq

Senior Member
Jan 8, 2010
419
67
Tarnów
On it, thanks. It does say in the op that exfat is supported by the 23.06.2013 build and that got me confused a little couse that's the one I installed ;)

Edit: Nope, it still doesn't work. I installed latest build, latest kat kernel and have a 64GB sandisk card. When I plug it into tablet, I get the message saying that card is empty.
 
Last edited:

josteink

Senior Member
Feb 8, 2011
2,243
1,808
Oslo
On it, thanks. It does say in the op that exfat is supported by the 23.06.2013 build and that got me confused a little couse that's the one I installed ;)

Edit: Nope, it still doesn't work. I installed latest build, latest kat kernel and have a 64GB sandisk card. When I plug it into tablet, I get the message saying that card is empty.

Dont install katkernel seperately. It's already baked in. Installing it seperately replaces the stuff and modules we have which ensures that we do have exfat support.
 

Chinaboy5216

Senior Member
Aug 27, 2008
1,928
2,127
59
Foshan, China
Hi Josteink,

I see that Samsung is on the verge of releasing android 4.3, any idea when CM would move towards it and what the extras (if any) would be for our beloved tf101?

Sent from my Transformer using xda premium
 

josteink

Senior Member
Feb 8, 2011
2,243
1,808
Oslo
Hi Josteink,

I see that Samsung is on the verge of releasing android 4.3, any idea when CM would move towards it and what the extras (if any) would be for our beloved tf101?

Sent from my Transformer using xda premium

From what I've read, 4.3 is still "jellybean" and there doesn't seem to be an earth-shattering amount of changes.

That said:

- CM wont touch this until there is a AOSP source drop. So far there hasn't been any.
- From source-drop to a CM-release based on that source can take anything from weeks to months
- Once the CM-team has something about based on 4.3, chances are there will be no official support for the TF101, just like it was with 4.2.
- If we're lucky, the changes between 4.2 and 4.3 wont be that major and we will be able to keep on maintaining a compatible device-tree so that we keep up to date.

This is all speculation and DON'T consider this me making any promises about anything :)
 

josteink

Senior Member
Feb 8, 2011
2,243
1,808
Oslo
Ok, so how can i go back to your kernel ?. I already installed latest build without installing the kernel afterwards.

If you installed the latest build, you should be all set. Have you tried unmounting and remounting the Micro SD-card after boot?

Worst case scenario, you can't make it work no matter how, I'll give this a try myself. I personally commited code to make this thing supported, and it would be a shame if it doesn't work out of the box ;)
 

josteink

Senior Member
Feb 8, 2011
2,243
1,808
Oslo
Maybe a stupid question but what is the whole story with the NEON thing? I have no idea what it is...

Long story short... GPUs (graphic chipsets) are immensly better at performing parallell operations than CPUs (general processors) are.

You can use these GPUs not only to render 3d graphics and stuff like that, but also to do calculations. Basically algorhitms which processes lots of data and can do it in parallell can /in theory) run much faster on a GPU than a CPU.

This requires ordinary program-instructions to be translated from normal code to GPU code. For that to be generally possible, a GPU must have a so called NEON-capable instruction set. Tegra2 does not have all the instructions required to be NEON-capcable.

This means that some program/system-components written to exploit the computational capacity of a NEON-capable GPU will not work and at worst crash on a Tegra2 device. This can be anything from the Google swipe-gesture keyboard to voice-recognition, to stuff like merging pictures in a photosphere or whatever.

CM's point is that Android is increasingly moving in that direction, and they don't see any reason to hold CM back just to support the two or three devices on the market with a Tegra2 chipset (TF101, Xoom and possibly the Galaxy tab).

We'll see how it all turns out.
 
Last edited:

zboq

Senior Member
Jan 8, 2010
419
67
Tarnów
If you installed the latest build, you should be all set. Have you tried unmounting and remounting the Micro SD-card after boot?

Worst case scenario, you can't make it work no matter how, I'll give this a try myself. I personally commited code to make this thing supported, and it would be a shame if it doesn't work out of the box ;)
Ok then. I have reformatted the card to fat32 for now to restore my apps but will change to exfat later and report back.
 

josteink

Senior Member
Feb 8, 2011
2,243
1,808
Oslo
Ok then. I have reformatted the card to fat32 for now to restore my apps but will change to exfat later and report back.

Sorry about my pedantry. Getting "SD card is blank or has unsupported filesystem".

Will look into why it doesn't work.

Edit: manually mounting via a shell works...

shell@android:/ # mount -t texfat /dev/block/mmcblk1p1 /storage/sdcard1/
shell@android:/ # ls /storage/sdcard1/
test.txt

Can probably be fstab/voldtab related.

Edit 2: Bingo. This thread says vold only supports vfat/ms-dos thingies:
http://xdaforums.com/showthread.php?t=1371621

This thread however has a work-around. Which makes perfect sense.
http://xdaforums.com/showthread.php?t=2149739

I'll see if I can create a flashable ZIP which can be used to add that to the ROM. Later though ;)

Edit 3: That solution has issues too... Ah well.
 
Last edited:
  • Like
Reactions: cdurex

Chinaboy5216

Senior Member
Aug 27, 2008
1,928
2,127
59
Foshan, China
Long story short... GPUs (graphic chipsets) are immensly better at performing parallell operations than CPUs (general processors) are.

You can use these GPUs not only to render 3d graphics and stuff like that, but also to do calculations. Basically algorhitms which processes lots of data and can do it in parallell can /in theory) run much faster on a GPU than a CPU.

This requires ordinary program-instructions to be translated from normal code to GPU code. For that to be generally possible, a GPU must have a so called NEON-capable instruction set. Tegra2 does not have all the instructions required to be NEON-capcable.

This means that some program/system-components written to exploit the computational capacity of a NEON-capable GPU will not work and at worst crash on a Tegra2 device. This can be anything from the Google swipe-gesture keyboard to voice-recognition, to stuff like merging pictures in a photosphere or whatever.

CM's point is that Android is increasingly moving in that direction, and they don't see any reason to hold CM back just to support the two or three devices on the market with a Tegra2 chipset (TF101, Xoom and possibly the Galaxy tab).

We'll see how it all turns out.

Thx for this explanation, in short it will mean our 101 will be abandoned by CM although it is still one of the most powerful tablets on the market. I keep comparing with newer tablets but find no advantage in them. TF101 rocks!!!!
I'll keep my fingers crossed on further development and bypasses for the neon thing. I love my 101 too much to abandon it.

Thanks Josteink

Sent from my Transformer using xda premium
 
  • Like
Reactions: fgsouza

zboq

Senior Member
Jan 8, 2010
419
67
Tarnów
Sorry about my pedantry. Getting "SD card is blank or has unsupported filesystem".

Will look into why it doesn't work.

Edit: manually mounting via a shell works...



Can probably be fstab/voldtab related.

Edit 2: Bingo. This thread says vold only supports vfat/ms-dos thingies:
http://xdaforums.com/showthread.php?t=1371621

This thread however has a work-around. Which makes perfect sense.
http://xdaforums.com/showthread.php?t=2149739

I'll see if I can create a flashable ZIP which can be used to add that to the ROM. Later though ;)

Edit 3: That solution has issues too... Ah well.
Just for you to know, previously I had ARHD 3.6 with RaymanFX elite kernel and exfat worked great there. Maybe You could look how he got it working ?
 

Magissia

Senior Member
May 9, 2012
1,151
270
127.0.0.1
Just tried here. Works fine.

Now to test exfat...

Your Ext4 MicroSD is mounted and ready to use right after booting ?
Any specific manipulation ? Here i just inserted the MicroSD card and let the system do everything.
At each boot/reboot i have to wwait about three minutes before the MicroSD card become avaliable for use (mounted)

If i try to force mount it using Kat apps before the ~3mins i get an error
I'm using a 32gb microSD if it's important.

Regards
 

josteink

Senior Member
Feb 8, 2011
2,243
1,808
Oslo
Your Ext4 MicroSD is mounted and ready to use right after booting ?
Any specific manipulation ? Here i just inserted the MicroSD card and let the system do everything.
At each boot/reboot i have to wwait about three minutes before the MicroSD card become avaliable for use (mounted)

If i try to force mount it using Kat apps before the ~3mins i get an error
I'm using a 32gb microSD if it's important.

Regards

What I did what this:

1. normal linaro no-name install. no extra kernel. no kat-app.
2. on a normal linux mahine, format a 8gb micro-sd card as ext4. copy a simple text-file over for verification.
3. insert microsd-card into tablet. see that it works. by doing a "ls /storage/sdcard1/" in terminal.
4. reboot.
5. reverify in a terminal with "ls /storage/sdcard1/"

Maybe it's the fact that I dont have a lot of media and stuff which needs to be scanned on the sdcard? I don't know, but it works here, and I dont need any additional apps or stuff to mess with the process.
 

josteink

Senior Member
Feb 8, 2011
2,243
1,808
Oslo
Thx for this explanation, in short it will mean our 101 will be abandoned by CM although it is still one of the most powerful tablets on the market. I keep comparing with newer tablets but find no advantage in them. TF101 rocks!!!!
I'll keep my fingers crossed on further development and bypasses for the neon thing. I love my 101 too much to abandon it.

Thanks Josteink

Sent from my Transformer using xda premium

Not sure I'd call it "the most powerful tablet on the market". It's been out for a while. It was an early model to probe the market.

It was revolutionary at the time of launch, but since then several models have superceeded it and everyone agrees Tegra2 is pretty much junk. Definitely so compared to what's available on the market today.

Like I said though: We may be able to get CM-builds running for the TF101 even though CM officially abandons it (like they already have).

Last official CM build for the TF101 was CM10. We still managed to get CM10.1 running. Maybe we'll get CM10.2 running as well :)
 

Chinaboy5216

Senior Member
Aug 27, 2008
1,928
2,127
59
Foshan, China
Not sure I'd call it "the most powerful tablet on the market". It's been out for a while. It was an early model to probe the market.

It was revolutionary at the time of launch, but since then several models have superceeded it and everyone agrees Tegra2 is pretty much junk. Definitely so compared to what's available on the market today.

Like I said though: We may be able to get CM-builds running for the TF101 even though CM officially abandons it (like they already have).

Last official CM build for the TF101 was CM10. We still managed to get CM10.1 running. Maybe we'll get CM10.2 running as well :)

Maybe not the most powerful anymore but still a great tablet!!!!!!!!! I hope it will never be forgotten.

Sent from my Transformer using xda premium
 
  • Like
Reactions: philseven

Top Liked Posts

  • There are no posts matching your filters.
  • 98
    No-name CM10.1 nightlies

    Welcome to the No-name CM10.1 nightlies ROM.


    Features:
    - No fuzz, stable CM10.1-based ROM for the TF101.
    - Timduru's wonderful KAT kernel built in
    - Can play 720p MKVs over wifi using Dice Player (and similar) if OCed to 1.4GHz (see details on OCing below)
    - Support for battery-dock indicator
    - Up to date, nightly builds, with change-logs.
    - Linaro builds available too.
    - Works with PPP widget from the Play Store.
    - Native support for USB and SD-card dock storage.
    - TabletUI mod available.
    - Experimental TF101G support.

    We'll do our best to keep it working, stable and fix issues as reported, but whoever feels like contributing should feel free.
    Pull requests welcome.

    No-name parts with extra features can optionally be installed from market.
    If you feel like donating, you can install Straitjacket which is my paid app with some extra features. Plus it might give you a warm fuzzy feeling for being a good guy.



    Installation:

    If coming from any non-4.2.x/CM10.1-based ROM, a factory reset is very much recommended.

    (0. Backup your existing ROM)
    1. Decide if you feel experimental. Linaro or normal build?
    2. Download latest nightly to device.
    3. Download special TF101 gapps linked below. (Choose only one)
    4. Boot into recovery. Use TWRP, not CWM, as CWM doesn't support 4.2 ROMs properly.
    5. Flash ROM. (This also wipes /system and any mods you already have.)
    7. Flash special TF101 Gapps.
    8. Optionally flash trackpad and/or tabletUI mod. (For tabletUI-mod: Do read below!)
    9. Ensure you wipe /cache and dalvik-cache.
    10. Reboot.

    Basically, the normal procedure for any ROM.


    Updating:

    Updating from a previous build does not require a factory reset and will in no way delete any user-data or apps.

    Be sure to flash ROM and to reflash gapps otherwise you will lose your current Google-account.

    (0. Backup your existing ROM)
    1. Download latest nightly to device.
    2. Boot into recovery.
    3. Flash ROM. (This also wipes /system and any mods you already have.)
    4. Flash special TF101 Gapps.
    5. Optionally flash trackpad and/or tabletUI mod.
    6. Ensure you wipe /cache and dalvik-cache.
    7. Reboot.


    Downloads

    TF101 (Wifi only) ROM available here:
    - nexfiles
    - dlumberg's mirror

    Experimental TF101G ROM available here:
    - nexfiles

    NOTE: These require TWRP for TF101G to be flashed. a_sh_ has you covered.

    Optional trackpad mods::
    - nexfiles
    - dlumberg's mirror
    - changes pointer-mode, but wont inverse scrolling direction of trackpad.

    Gapps available here:
    - Special TF101 gapps by dlumberg & josteink.
    - dlumberg's mirror


    Thanks to:

    - The Cyanogenmod team, for all the goodies they keep on delivering, across devices.
    - RaymanFX, for a CM-compatible device-tree for the TF101.
    - Timduru, for KatKernel which keeps this thing stable and functional.
    - Auto-patcher, for tabletUI mod.
    - ShevT and a_sh_, for TF101G support.


    Linaro?

    So you are asking "What's Linaro anyway?". Good questions. To learn more, you can head to the Linaro. Since that is a big, big page with lots of technical stuff, I'll be nice and provide a brief explanation:

    - Linaro makes an alternative toolchain which offers extra optimization-options not found in the "normal" Android build-chain. These optimizations should make the resulting build/ROM faster.
    - But these optimizations are not entirely proven yet, and there is some debate about compatibility-related side-effects.
    - These means that the resulting build may be less stable and/or less compatible with Android-software than builds produced using the normal build chain.

    Is Linaro for you? It works for me. If you feel very conservative, it's probably best to avoid it.

    If you still can't decide, you can check out this thread which dlumberg was nice enough to bring up. :)


    TabletUI mod

    In the ROM's download folder, for some releases you will find matching tabletUI mods availble for download.

    Do note that these mods are created from the ROM itself and must be exactly matched.

    That means that if your tabletUI mod is dated 20130428 and tagged "linaro", the only ROM that mod was created for was the 20130428 linaro build and no other build what so ever.
    A mod made for the linaro build isn't supported when applied to the standard build and vica verse. A mod made for one date should never be used on a build created on any other date.

    These mods are highly specific and needs to be treated that way. If you are mixing things and having any sorts of issues, there's nothing I can or will do about that. You have been warned.


    On over-clocking

    Don't use SetCPU or other third party tools. They are not needed, as the ROM has built in OC-controls. Using such tools may cause a conflict and in worst case possibly RRs and SODs.

    To unlock the OC controls, go to System settings, About tablet, scroll down to build number, and tap that repeatedly until the system responds with "You are now a developer".

    Exit and re-enter settings. You should now have a section called "Performance". Here you can enter a submenu called "CPU". Using this is the supported and recommended way to do over-cloking.


    Issues?

    Check the Github issue-tracker. They may be reported already. If not, feel free to report them.
    https://github.com/josteink/device_asus_tf101/issues?state=open

    Some issues are reported and closed, but have known workarounds:
    https://github.com/josteink/device_asus_tf101/issues?labels=workaround+available&page=1&state=closed

    If not there, you can also check or ask in the thread. Most issues will probably benefit from public discussion.

    Please do not PM me for technical support. You wont get it.


    Sources:

    Android is open-source. This is an open-source project.

    Cyanogenmod:
    https://github.com/CyanogenMod/

    TF101 device-tree:
    https://github.com/josteink/device_asus_tf101

    Kat-kernel:
    https://github.com/timduru/tf101-katkernel

    Experimental TF101G device-tree with modifications by ShevT:
    https://github.com/ShevT/device_asus_tf101g

    Experimental Kat-kernel with config for TF101G:
    https://github.com/josteink/tf101-katkernel

    Build-setup:
    https://github.com/josteink/android_multi-build
    https://github.com/josteink/simba

    Auto-patcher:
    https://github.com/mateor/auto-patcher


    Current contributors:
    - dlumberg
    - davebuk
    - ShevT
    - a_sh_
    - TheMrcool212
    - Jostein Kjønigsen (josteink)


    Other questions:

    - "These are the same builds you posted in RaymanFX's thread, right?"
    - Yes they are.

    - "Bleeding edge... Does this include cherry-picks?"
    - No. Only regular CM updates which has passed gerrit code review, just like the official nightlies. We're bleeding edge. Not extra bleeding edge.

    - "What makes this different from RaymanFX's 0.8 Work In Progress ROM?"
    - This ROM is based of his work, but he hasn't updated his sources in a long while. With the kernel being replaced by a non-Rayman kernel and him not really updating it anymore, I felt it would be wrong to keep posting it in his thread. As we keep making changes, I expect less and less of his original work will remain.

    Thus I felt it was time to give. Not to mention, now people have easy to locate downloads and up to date instructions in the first post.
    12
    Change log:

    This log (mostly) reflects changes specifically to this ROM, and does not (usually) include changes upstream from Cyanogenmod.

    2013-02-21: Initial release as own ROM, using forked KAT kernel.
    2013-02.24: GPS and battery-dock fixes.
    2013-02-25: Kernel renaming.
    2013-02-27: Fix touchpad-toggle on battery-dock. Thanks to whirleyes!
    2013-03-08: Fix issue with front-facing camera.
    2013-03-12: Fix issue with missing audio after deep sleep on some devices.
    2013-03-20: Added very basic trackpad mods.
    2013-03-21: Fix for bluetooth audio devices. Thanks Boomgawd!
    2013-03-22: Fix for non-working Google Backup.
    2013-03-24: Fix Google talk video chat (thanks to J-Pod)
    2013-03-29: Fix for 720p video-recording.
    2013-04-05: Kernel changed to actual KAT kernel nightlies as well.
    2013-04-14: Fix for Photosphere crashes merged upstream in CM. (Photosphere yet to be included in gapps)
    2013-05-12: Experimental builds for TF101G added.
    2013-05-20: TWRP for TF101G added.
    2013-05-21: TF101G build borken.
    2013-05-24: Broken TF101G builds fixed.
    2013-05-28: Added automatic building of tabletUI-mods for all 4.2 builds.
    2013-06-19: Updated Linaro toolchain.
    2013-06-23: Added support for exfat and better support for SD-card and USB devices in the settings.
    10
    Tablet UI thanks to Auto Patcher http://xdaforums.com/showthread.php?t=1719408
    Caldair is going to commit the change to the repo so that auto-patcher will have native support for tf101 going forward. Big thanks to him

    Flash from recovery over your existing rom.

    TabletUI
    http://zenithosis.com/update-cm-tf101-20130320-tabletUI.zip

    Restore phablet UI
    http://zenithosis.com/restore-cm-tf101-20130320.zip

    There is no settings panel yet.
    10
    [ROM] [4.2.2] No-name CM10.1 nightlies - Standard & Linaro

    If you don't mind could you explain something for me then...I have

    Using Total Commander as my file explore, I go to the "home/root" screen this is what I see

    SD-Card Total Commander shows the path as /storage/emulated/0
    and
    SD-Card (2) Total Commander shows the path as /storage/sdcard1 (when I initially downloaded my ROMS and stuff, I put them on the physical SD card...this is where they are appearing.

    If I go into /storage these are the folders I see

    emulated
    sdcard0
    sdcard1
    sdcard2
    usbdisk0
    usbdisk1

    Is it just me or does this seem unnecessarily messy? I'm not sure if this is a DEV issue or not, but thanks for your help! It seems to be a stable 4.2.2 ROM thus far.

    Ok, so here is a rundown:
    sdcard1 is the microSD
    sdcard2 is the dock SD
    usbdisk0&1 are the two USB ports.

    sdcard0 is the internal storage for the current user (also /sdcard/)

    /storage/emulated/0/ is the primary user (only SuperUser). This is mounted as /sdcard/ and /storage/sdcard0/ when logged in.

    If you add users, the second user has data stored at /storage/emulated/10/. When they are logged on, this folder is mounted at /sdcard/ and also /storage/sdcard0/

    Additional users will be added in the following order in the /storage/emulated/ directory:
    1st user - 0
    2nd user - 10
    3rd user - 11
    4th user - 12
    5th user - 13
    9
    Just to let you know: Ubuntu upgrade completed. Most things seems to have survived quite well, including the TF101 android build-setup.

    Also: I've gotten word from ShevT about the changes involved, so I'm now working on getting the TF101G builds back up.

    All in all, should (hopefully) be smooth sailing ahead now (unless I just jinxed it) :D