yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] ingenue007:
I have this video issue too.
[TouchPad Development] N00Bextrordinaire:
Just wanted to throw my observations in here:

1. Beautiful work

2. Had issues trying to save email attachments, the system seemed to confuse file types

3. On-screen Home button worked after the first flashing of the rom, but not after flashing the second time.

4. Could not create backups in ClockWorkMod Recovery. It said there was an error mounting system (or something along those lines)

5. Best Wifi connection that I have experienced

6. Good battery life.

7. All of my games worked without a special mod.

I think that about sums it up. Also, I flashed the rom once, over an ICS rom, without wiping anything because I was in a hurry and it worked Great. All of the soft keys worked and all of my day-to-day apps worked fine. With the exception of Chrome, it did that flickering screen thing, and ICS Browser+ crashed every time I tried to open it.

All in all I think this is a great rom and I "tip my hat" to the Developers. Unfortunately, I decided I could not live without a dependable flash player so I had to revert back to an ICS rom. Keep up the great work and thank you for presenting this great rom to our community!
[TouchPad Development] nitrobg:
I agree, this ROM is quite beautiful and versatile, personally I loved the AOKP's functionality to reduce the status bar size and include widgets into it. I also loved the ability to change the DPI on per-app basis. Overall, it's a great idea, but it requires a lot more polishing because there are a lot of bugs that need a fix.

Right now it is an incredibly Frankensteinish build - everything is bunched together and most of the functions are conflicting with each other. If the developer manages to merge AOSP, AOKP and PA functionalities into one and fix the bugs caused by merging all three platforms, this will be the best ROM out there. This is why I migrated to the CM10 for the time being.

shumash should post the source into github and let the other devs help him in getting this to work.
[TouchPad Development] shumash:
For those who want to try it out, here's my github source:

https://github.com/shumashv1/Schizoid.git jellybean branch

It's a mess of commits bouncing back and forth trying to do just what you suggested ...
[TouchPad Development] nikos5800:
Are you going to update with jelly bean 4.2.1?
[TouchPad Development] tm21fourt3:
No matter what I do, I can't get flash to actually work good.

I followed the instructions in here with no luck.

The YouTube app works great, but any flash on the browser, dolphin, or Firefox is very glitchy, blinks when it comes on, or just doesn't work....

What do I do?

Thanks.
[TouchPad Development] nevertells2:
Flash in CM10 is no longer supported by Android. If you sideloaded the Flash .apk, most have found that it works somewhat in Dolphin Browser and not very will any any other browsers. I don't know this for a fact, but since support has been dropped, I suspect that the developers of all these apps are removing the code that supports Flash. Live with what you have or go back to CM9.
[TouchPad Development] deathgod99:
I getting a WiFi issue, works great in webOS but works sometimes when I boot into the rom, love this rom help.
[TouchPad Development] nevertells2:
Explain what you currently have and what you have done to get there in explicit detail.
[TouchPad Development] shumash:
07JAN13 Fully Compiled ROM Uploaded

For those who want nothing but the purely organic, no added ingredients version, I've uploaded a fully compiled signed ROM. Everything works, but the power draw in standby is poor. If anyone has a source fix for that, I would appreciate some help. I'm leaving the previous ported version available because there's no particular advantage to the compiled version other than the code is up-to-date.
[TouchPad Development] nevertells2:
You should check in with J.C. Sullins on IRC, he has been dealing very effectively with that.
[TouchPad Development] shumash:
SCHIZOID Build Instructions

SCHIZOID Build Instructions

This guide assumes you have completed the Set Up Android Build Environment, or already have a 64 bit Android build environment set up. i.e., you have:

- Installed Ubuntu 64 bit (I'm running 32-bit Ubuntu 11.10 & 12.04 virtual machines without problems)

- Installed the Android SDK

- Installed the Java SDK/JDK

USE THESE STEPS INSTEAD OF THE GUIDE CM10 STEPS!

1. CREATE THE BUILD REPOSITORY

Create directories and setup your local repository using my git repository:

Create the Directories

Type the following in a terminal window:

Download and make the "repo" binary executable...type the following In the terminal window:

Close the terminal window to insure these changes take effect.

2. INITIALIZE THE REPOSITORY

Open a new terminal window and type the following:

Now to sync the repository, type:

The default for SCHIZOID is -j16, but if you have trouble downloading, you can add -j4, or even -j1 -f to the above command.

Go eat dinner, maybe read a book... It's going to take a long time.

To build, make sure you're in your build directory, i.e. ~/android/skz, or whatever, then type in the terminal window

:

When that completes, type:

Type in the number corresponding to "skz_tenderloin-userdebug" (probably 7)

You should have a local_manifest.xml file in the .repo directory that was created automatically. If not, create an empty

file named "local_manifest.xml" and copy the following into it:

Save it, then repo sync and lunch again (don't worry about the warnings about putting the xml files in a directory called "local_manifests".

That's caused by a change in the repo command that doesn't work properly yet.

Then type:

Wait an incredibly long time, and you will find your skz_(stuff).zip waiting in the out/target/product/tenderloin directory, or you can just type "cd OUT$"
[TouchPad Development] zsiddiqi:
Hi Shumash,

Thanks for the documentation. I encountered some differences while trying to build as follows:

1. envsetup.sh when run complains about not being able to find Term.apk under vendor/cm/proprietary/Term.apk

2. The local manifest xml did not have "TheMuppets..." entry. Just had one single entry for CM.

I am going to let it "bacon" now and see how it goes.

Thanks again.
[TouchPad Development] shumash:
Don't. Add the Muppets entry to the local_manifests.xml. It's the TP proprietary files. The ROM won't work without it.
[TouchPad Development] menwoft:
I Can't download google, up other link pls
[TouchPad Development] zsiddiqi:
Hi Shumash,

Thanks for the tip. I added the line for "The Muppets.." and started build process which is still running.

Since the source code base is so big, is there documentation available on what patches were applied to which location and their source of origin. If you could share that would be great. ty
[TouchPad Development] zsiddiqi:
Build errors

I encountered the following error while building the sources using "bacon":
[TouchPad Development] shumash:
Fixed. The best thing to do is to repo sync in your build directory, then delete the vendor/cm/proprietary directory. Close the terminal window. Open a new terminal window and do the envsetup thing, lunch, and rebuild.

Expecting me to outline all the things I've done to make this work isn't going to happen. If you want to find out for yourself, go to my repository and review all the commits.

Alternate file link is in the OP

That's a continuing problem that I haven't yet resolved. For now, type the following in your build directory:

cp -i vendor/skz/overlay/common/packages/inputmethods/LatinIME/java/res/values/gesture-input.xml packages/inputmethods/LatinIME/java/res/values/gesture-input.xml
[TouchPad Development] yeahman45:
is there the bug that bricks you touchpad if you let it run out of battery like the Jcsullins rom? otherwise looks nice! gj
[TouchPad Development] shumash:
All CM10-based ROM's do that.
[TouchPad Development] yeahman45:
is there actually a way to unbrick it if ever it runs out of battery?
[TouchPad Development] Silencer96:
What in the world? So there's no way to charge it so it'll boot up? That sucks!

---------- Post added at 10:17 PM ---------- Previous post was at 10:11 PM ----------

Also, other than being based on CM10 and having project butter, what other benefits does this ROM have over the CM9 nightlies? I can't justify upgrading to a buggy ROM (it bricks your tablet if it runs out of juice, dafuk?) and bad battery life.
[TouchPad Development] shumash:
Let's get back on topic. Here's the answer:

http://rootzwiki.com/topic/36658-tpdebrick-v01/page__st__300#entry1065574

and here's the thread to be discussing it in:

http://xdaforums.com/showthread.php?t=2075274&highlight=dead+battery
[TouchPad Development] zsiddiqi:
Okay, so I have managed to build everything fine. But when I try to create the OTA Zip file, it is unsuccessful:

Thanks for your help.
[TouchPad Development] nevertells2:
Technically, all TouchPads are subject to this regardless of what is installed.

---------- Post added at 08:33 PM ---------- Previous post was at 08:32 PM ----------

http://rootzwiki.com/topic/36658-tpdebrick-v01/
[TouchPad Development] shumash:
Look at what I posted a few posts back and do this:
[TouchPad Development] shumash:
New version uploaded 09jan2013

I've uploaded a new ROM with a ROMControl app that allows setting of the CPU frequencies, i.e. the sliders work. There is still some work to do to make it fully functional, but I expect to revise the code further and write some startup scripts that will make everything work. Enjoy. (now if I can solve that pesky standby power problem....)
[TouchPad Development] thepwneddroid:
Is anyone experiencing System UI crashes when you first boot? Apps and everything works fine, except because of the System UI crash, I cannot get the status bar working. Any help, please?
[TouchPad Development] erick161:
Yup, same problem here. I did a fresh install as well, wiped it all.

Only way i see around this was booting into Cyanogen instead of AOKP at the moboot screen. No crash. Not sure what the difference is, but it has all PA and AOKP setting in it as well...
[TouchPad Development] sstar:
I haven't used this rom as it sounds too unstable for my everyday use but I don't think you should have the option to boot into Cyanogen and AOKP

What did you upgrade from as having an unused ulimage is going over fill your boot folder and cause problems . I believe the Max for the boot folder is just over 32mb as a matter of interest what is yours showing ?
[TouchPad Development] erick161:
26.33mb

I went from cm9 to cm10. I forget the ROMs name but it was unstable as hell on my TP. Stumbled onto this ROM and wiped everything again and flashed this one.
[TouchPad Development] sstar:
26.47mb on mine which is Oat's ,so nothing in it . Just thought that the fact that you have the option to boot into either Cyanogen or AOKP would mean you that you also have the corresponding ulimages and therefore an over full boot folder which can cause problems , oh well maybe this rom just works differently .
[TouchPad Development] zsiddiqi:
Same here, I flashed the latest version 0.91 yesterday after a full wipe and the first thing I see after it boots up is the System UI FC dialog box :(

I have tried clearing dalvik cache again but that doesn't help either, so, not soft buttons or status bar at the bottom.
[TouchPad Development] shumash:
This is a CM build. I don't mess with wiping /boot like -SGA- does. If anyone has a AOKP moboot option, they should either boot the CyanogenMod option manually, define the default boot image, or delete the uImage.AOKP in /boot (all of which is discussed at length in other threads. Search first)
[TouchPad Development] shumash:
I'm not sure what is causing that, which is why I haven't suggested doing a full wipe from a previous version, just dalvik and cache. If you can get to Settings->System->Navigation bar->Tablet UI soft buttons during the FC's and also set Force Tablet UI in ROM Control, then reboot, my recollection is it fixes itself.
[TouchPad Development] shumash:
It's not that unstable, but as someone described it in one of the posts, it's "Frankensteinish" which makes it a challenge to figure out how to get from point A to point B. ;)
[TouchPad Development] graffix31:
i actually havent had a single problem since flashing this rom. i did a clean install with acmeinstaller 3 before making the jump to any cm10 builds. i also had a aokp option in my moboot but if you search you tube there is a great video that shows a very easy way to remove any options you dont want anymore. i think i just searched remove aokp from moboot to find it. i havent installed the newest version because it is running so good for me. i will wait until we get a source build with everything working correctly. you can run into problems settig everything up to your liking because of all of the options but i dont have any issues with anything fc or not working correctly. love this rom. best thing until we get a clean 4.2 build working.

thanks for all your work on this.
[TouchPad Development] shumash:
New version 1.00 (!) uploaded 10Jan2013

New ROM with fully functional ROMControl. It wasn't as difficult as I thought to modify the ROMControl app or create the script.

EDIT: And with a simple fix from jcsullins, the power draw in standby is fixed. We stand at version 1.00.
[TouchPad Development] dannieboiz:
nevermind figured it out

---------- Post added at 11:04 PM ---------- Previous post was at 10:22 PM ----------

has anyone been able to play video with this? I tried MX player and have tested only AVI file and I get no video only audio
[TouchPad Development] lepa71:
"the power draw in standby is fixed" what is it now and what was it before?
[TouchPad Development] shumash:
90-100mA, now 28-38mA
[TouchPad Development] Moronig:
Great news! Downloading now...

Question: does this have Dorregaray's gyroscope patch already included?

Another question: if I do a clean install, how do I enable MTP mode? There is no option for that in Settings/Storage.
[TouchPad Development] Jedipottsy:
I'm having system ui crashes too, full wipe from cm10. Used acme3
[TouchPad Development] shumash:
1. No

2. Asked and answered elsewhere. My recommendation is that you don't do a full wipe. If you're coming from any CM10 build, just dalvik and cache.
[TouchPad Development] erick161:
Yes you do. Go into storage and the 3 little dots in the upper right corner.

make sure it isnt booting into AOKP. I has this issue from previous flashes leaving a leftover uImage in my boot screen. It needs to boot into cyanogenmod.

its not working. Drain is still there...if not worse. Went from 66% to 53% in 6 hours while I slept.
[TouchPad Development] shumash:
I stand by my post. It went down 13% in 6 hours, about 2.15%/hr, well within the typical range of deep sleep power consumption (1%-2%). There are all kinds of other things that you can do to minimize power consumption, but it is never going to be zero.
[TouchPad Development] sahhar1993:
does the status bar fixed?

Envoyé depuis mon cm_tenderloin avec Tapatalk
[TouchPad Development] FaberfoX:
After some initial glitches, I've got the rom running great, thanks!

Now, you're not fully up to date on PA, right? On my gnex, changing layouts doesn't require a reboot, and I remember that being added not long ago. Is that the reason, and if so, do you plan to update soon? Or is something from ROM control maybe conflicting with Hybrid?

I also noticed that after applying Tablet UI and rebooting, it's back at phablet (600 dpi instead of 720).

Anyway, great work, really enjoying the rom, thanks!
[TouchPad Development] f_padia:
Got a problem; battery dead and tablet won't recharge. Is this the problem with cm10 that I'm reading about? I'm using the original charger but a different cable, although this cable has been working fine up till now.

If it is the cm10 battery dying problem is there a way to fix?
[TouchPad Development] nevertells2:
And you don't want to install or include the gyro patch just yet. It needs a lot of tweaking.

---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------

Did you insure you had MTP checked in settings/storage/three dots upper right?
[TouchPad Development] erick161:
Happened to me last night. I just plugged it in. Let it charge for a few mins and booted into WebOS (I didn't have mtp checked). All was fine. Let it charge about 10% and switched back to this ROM and enabled mtp

If that's normal, then OK. This was the same drain I was experiencing on CM9. Thought it could get better, but I suppose not. I assumed when you said you fixed the drain...that you fixed the 1-2% an hour drain
[TouchPad Development] agent00f:
Problems all around even with full wipe: on startup, says System UI has stopped. No nav bar (no back button, clock, etc), even if I go enable it in AOKP controls.

Tried from the CM10 12/16 build, same thing.

WTF? Buggy.

also tried this: http://xdaforums.com/showthread.php?p=36536056&highlight=status#post36536056, and it loops at boot animation forever (I think it's the force-tablet-ui).

BTW, guys, it' called the navbar, not status bar, just so that others can find this with search.
[TouchPad Development] siralsmooth:
Two things I did that fixed the ui crash.

1. Set tablet mode on both cm and aokp settings panel

2. Changed the screen dpi to 140

After the reboot the ui crash stopped, although I'm fairly certain its the dpi that did the fix, as I've had that systemui crash with other dpi settings in the past. Hope this helps. Not going to nandroid and reflash just to confirm this though.

Also. Wakelock/current draw is DEFINITELY FIXED. My tablet dropped 5% battery over a 12hr period with several apps in the recents history.

Hope this helps. Rom is otherwise super smooth.
[TouchPad Development] rhidalgo1973:
[/IMG]

There is nothing wrong with the NavBar in this ROM.... Go to settings>ROM control>general UI>enable force tablet UI and reboot. After rebooting go to settings>system>navigation bar>click on tablet UI soft buttons and you will have the navbar on your screen...you just need to play with settings a little bit before posting discourage comments on the thread..thanks.:cowboy:
[TouchPad Development] agent00f:
Again, I did all of this from clean boot and was met with infinite boot animation at which point no further progress is possible. Judging by the numerous comments about the "status bar" issues on the prior pages and the author's own recommendation to install over an existing rom (which didn't work over CM10 btw), it's best if the emphasis was on making it work out of the box for the benefit of the ROM's reputation. As it is right now, it's only suitable for those who've already somehow got it working via some previous hodgepodge of tweaking.

Thanks for understanding.
[TouchPad Development] nitrobg:
Are you sure that it isn't app-related, something could be preventing the device from sleeping. Facebook app, weather widget perhaps?
[TouchPad Development] CrustyMcLovin:
Yeah I agree with you on that, it would be ideal of something as critical as the status bar was working from the start. I've followed the instructions on the OP and I still can't get it up and running. Between the System UI FC and occasional boot loops, I'm gonna have to move on to another ROM. Thank you for your efforts but this one isn't ready yet.
[TouchPad Development] Stryder5:
System UI forcecloses on first boot and subsequent reboots. Can't get status bar running. Did a clean install and everything too. Thanks for the effort, but I can't use a ROM without a status bar.
[TouchPad Development] Ruggerxpunk:
On the flip side of this, i have been running this ROM for a month rock solid stable with no issues and being able to overclock this beast to 1.7 is icing on the cake.
[TouchPad Development] rhidalgo1973:
I don't know where all these issues that ppl are claiming to have are coming from....maybe they are not doing it the right way....I used to have CM9 but since JB came to the TP I run ACMEUninstall, to start a fresh install of Jb, and then ACME3, to gain more space on the partition, and I've been jumping from SGA's, OaT's and this Rom without any issues at all....of course I always wipe caches 3X and Factory Reset before installing a new ROM, I don't like doing dirty installs cause that's where all the issues come from...and I only use CWM6 Recovery to install my roms...TWRP is not of my liking. With this Rom I experienced the System UI has stopped working in the first boot but I always let the rom settle for at least 30 minutes then I apply my settings and download my apps, reboot, wipe again caches and fix permissions and issues are gone....Becasue the NavBAr and Status Bar don't come install out of the box doesn't mean that they are not available on the settings, just play with settings and you'll find them...;)
[TouchPad Development] dvaderx:
Download link appears to not be working
[TouchPad Development] dapirate:
it worked for me on a PC but not on the TP
[TouchPad Development] shumash:
Having Problems?

For those of you having problems with the compiled ROM, I suggest you download the ported version which contains older code and is stable. Once you get a handle on how it works, you can try the compiled version.

Anytime you recompile with upstream code revisions, there is a chance that something will break and cause problems. You should view the compiled version as a "nightly". If you're happy with the ported version, stick with it. I'll try to fix problems created with the recompiled ROM when and if I can. If it doesn't bork my tablet, I won't be able to determine why it does yours. That's why we have this community here- to share experiences and help solve problems.
[TouchPad Development] theskymoves:
I can see here that a lot of people have been having problems getting this ROM to work properly for them.

I had problems too during the last release that I eventually fixed just by fiddling around with the settings long enough. Downloading the latest version to flash. Looking forward to the improvements.

Thanks!
[TouchPad Development] Stryder5:
For anyone who got the status bar working after a clean flash, can you please explain what settings you changed?
[TouchPad Development] tbob18:
Try this (should probably be in the OP):

Settings > System > Tablet UI soft buttons

Settings > Rom Control > General UI > Force Tablet UI (mentioned in the OP)

This is also good to change:

Settings > Rom Control > General UI > Show Menu UI Overflow (otherwise there is no way to enable MTP, open browser settings, wifi settings, etc)
[TouchPad Development] Stryder5:
Thanks. I was trying to use PA settings so didn't try that method.
[TouchPad Development] tbob18:
Actually, I can't seem to get PA settings to save at all. :confused:

I re-flashed a few times (clearing data/system of course), I am downloading a fresh file now.

Edit: Still no luck, I tried 777 on the paranoid config files but that did not change anything.
[TouchPad Development] pogi1100:
Flash player not working in the latest build but it was working on the previous one.
[TouchPad Development] thi3um:
i think i had miss some thing, impossible for me to have navbar...

I do that "To get softkey buttons in navbar, go to Settings->System->Navigation bar->Tablet UI soft buttons (check)

AOKP tablet UI setting overrides PA's. To set phablet or phone mode, first uncheck AOKP's setting:

Settings->ROM Control->General UI->Force Tablet UI (unchek if i understand, but by default it is uncheck )

then:

Settings->Paranoid Settings->Launch-> press Stock or Phone UI

reverse to set tablet UI (I press stock then it warm me that the tablet will reboot, it reboot )

nothing change i don't have navbar.

and if i do that:

Settings > System > Tablet UI soft buttons (chek)

Settings > Rom Control > General UI > Force Tablet UI (mentioned in the OP) (chek)

i get a bootloop at reboot

Yes, I have finally enable navbar and navbar button, I don't know how exactly but it work ( I think the order of the check parameters is primordial)

System /Tablet UI force button - > check

Rom Control / general UI / force Tablet UI - > check

Pa setting / launch / Tablet mode - > then reboot

Voilà, this Rom is awesome thanks...