yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] googlephone:
I saw drmarble is working on kernel 3.0 on rootzwiki forum but seems like he encountered trouble and got stuck up. Really hope the developers with kernel knowledge can join their efforts (maybe great a dedicatory thread) and get a bootable kernel 3.0. Patiently waiting if it will ever happen.

Got tempted to buy the new nexus 7 last week but deceided to keep my 2 32GB touchpads since they served me well in the past 2 years. Thank the food job done by the developers.

Without kernel 3.0 we won't see official cm10 or future KLP.
[TouchPad Development] nevertells2:
Each to his own.:laugh:
[TouchPad Development] drmarble:
I am being misinterpreted here. I am working on a 3.0 kernel. I want one that works with ION and fence and the new cm10.1 graphic drivers. It is easy to use jcsullins' 3.08 kernel with the qcom/display-legacy directories. I want to use the normal cm10.1 tree. Then we can become official.

Various circunstances in real life have prevented me from spending time on it lately. I hope to get back on it. It's a fun problem. Like a really really big crossword puzzle. I will let people know when I have done something useful. I could upload some ugly, nonworking trees up to github but it would be embarrasing. Commit messages shouldn't just say, 'another try,' they should be informative. I want to try a more systematic and documented approach.

Look for results over on RootzWiki. Don't hold your breath. I promise to share my results if I ever have any. Just a I shared the way to get cm10.1 to build using the qcom/display-legacy directories.
[TouchPad Development] milaq:
testbuild available

for all those curious ppl who want to test out a build with the webOS-media/sdcard-partition shrinked to 512mb and an emulated sdcard on /data, here you go.

READ CAREFULLY AND FOLLOW THESE STEPS ONE BY ONE

(copy all three zips linked below to your sdcard before beginning with the procedure)

make room on your sdcard partition (not more than 500mb USED space, even better: erase it completely)

install lvm resize via recovery - it will shrink your webOS-media/sdcard partition to 512mb. IF ANYTHING GOES WRONG, DO NOT PROCEED. check if enough space is free and repeat this step.

immediately reboot to recovery (important - don't do anything else, really!)

install new recovery with datamedia support

reboot to recovery

install build with datamedia support (you need to select "install zip from external sdcard" now)

reboot and enjoy (reporting back appreciated)

from now on, your main sdcard will reside in /data/media (i.e. shares storage with /data) but is fully accessible like a normal sdcard in android (just like on modern devices). the shrinked sdcard partition is also accessible and mounted as a secondary "external sd".

don't worry: when hitting "factory reset" or "format /data" in the new recovery your (emulated) sdcard stays untouched. you will keep all data on your emulated sdcard.
[TouchPad Development] nikos5800:
will this work on jelly bean 4.1.2(jcsullins ROM)?
[TouchPad Development] GotsOJ:
No.
[TouchPad Development] rrrrrrredbelly:
I'm assuming other devs will be able to implement the data media support in their roms if they choose?
[TouchPad Development] rhidalgo1973:
Emulated sd card!!!!!

What's WebOS? lol...jk...but really, I bought my touchpad for the Android port not for WebOS, so emulated SD card sounds great, even if WebOS completely disappear from my touchpad I could care less...IMHO!!!;)

---------- Post added at 09:57 PM ---------- Previous post was at 09:48 PM ----------

It would be nice if someone can make a video of this procedure (hello Reverend Kyle)...;)
[TouchPad Development] Y314K:
This seems to be the best option until hopefully there is a Nand option for the TP...

Still had some ?'s...

How easy is to fully reverse this...

On a 16GB & 32GB if one chooses the 512MB WebOS Media size... How much space will it leave for Android as compare with the AcmeInstaller 3 we are using now...

How easy is it for Rom makers to add DataMedia to their roms ??? I myself am waiting for Shumash to add support to it to try it...

Thanks a lot for the option...
[TouchPad Development] shumash:
Adding support is not a big deal; it's just a separate build. The real issue is having to maintain two different builds, and the problems that each set of users may experience. I don't have two TP's that I can install different partition configurations on, nor do I want to waste a lot of time going back and forth formatting and re-formatting them just to test the different versions. AFAIC, the developers in this forum need to decide if an emulated sdcard is the way we will all go or not. The size of the WebOS data partition is immaterial, users can decide that. Whether we are going to uniformly use the datamedia method isn't. If we can develop a simple boot-up test to determine the partition layout, and mount it accordingly, that would be ideal. If not, you may lose some developers if they determine its too much of a hassle to manage.
[TouchPad Development] milaq:
remember sir, the jump to 4.3 is nigh.

this would be the ideal time to make such transition. the new vold doesnt like logical volumes very much. david has already fiddled around with it but it seems pretty troublesome.

thus, my current mr2 tree doesnt include sdcard partition mounting but only datamedia support.

as things stand right now from my side, 4.2 will stay as is and 4.3 will use the datamedia standard.
[TouchPad Development] shumash:
I agree that this is a good start time, but requiring anyone who wants to test out 4.3 to re-partition their TP to do so, and then restore it back to current standard when they decide to go back to CM9, CM10, or CM10.1 is going to be problematic unless we provide an easy way to do that or update their current build to use the datamedia support.
[TouchPad Development] rrrrrrredbelly:
What's the process to restore? Is it just restoring a backup in recovery?
[TouchPad Development] milaq:
well, in fact you can just install a datamedia build with your current partition layout but will only have ~1.5gb storage space available for both /data and /sdcard.

rem: the resize process is just to maximize the space for android. and just for testing you dont need to resize at all. if you're pleased with the funtionality you can then go ahead and resize your partitions and use a new recoveryimage.
[TouchPad Development] murkurie:
Do you happen to know if TWRP works with the data media build or is the new cwm required?

I have data media installed with cwm just wondering if I can switch back
[TouchPad Development] x000x:
this may be odd to ask, but why post this poll for the public? why not privately collect feedback from the devs and discuss etc and then you guys can all decide on whats best? i'm just a lowly user, and really don't understand any of the technical mumbo-jumbo be proposed :P i guess what i'm wondering about is why get us users involved. i'm sure we'll go along with whatever the devs feel is the best way to move forward :)
[TouchPad Development] shumash:
That sounds reasonable, but I'm going to have to familiarize myself with exactly how to do that. You're much more knowledgeable about the datamedia layout than I am.
[TouchPad Development] milaq:
https://github.com/milaq/android_de...mmit/deb408d57014dd31cbe04df74fcfd91815fb7375
[TouchPad Development] shumash:
PM coming
[TouchPad Development] Y314K:
Sounds great... I was gonna ask if it could be something that we could chose & add thru a rom installer like AROMA Installer... But I guess this should work perfectly too.. Making only one Rom needed for all current options for Android space...

I just hope the BT code is release this weekend to get both new options added at once...lol Not sure how long it will take JCSullins to cleaned-up and organized a proper release to the CM10.1 (based) ROM...

Thanks a lot for u'r openness to continue to improve an already awesome rom...

Was wondering if u had any info on the earlier posts...

Will TWRP need to be updated for compatibility with datamedia ???
[TouchPad Development] rob_z11:
I would like the idea of having 4.3 build using maximum available space. I have not care about WebOS since android started running on this.

I think it would be nice if everyone can get behind uniform approach starting with 4.3 build is the way to go in my opinion.
[TouchPad Development] Y314K:
Dev's are not always on the same page & getting DEV's to agree to something can sometimes be like herding cats... So it makes sense to get the current possible options out there.... No one is forcing anybody to add anything... At worst the Dev can say that's not something they wish to support & that is that... All end users should respect that, even when it doesn't make sense to us... It would be good for the Dev's to have a weekly Dev chat session to iron out any standards they need... But I don't think that will be an easy thing to setup & to keep up with constantly...

I do commend Shumash for trying to create TP Rom convention as much as possible... If u follow the RootWiki threads u will see that he constantly recommends or ask for options to simplify & establish common naming, cooking & other options... This is a lot easier on actual native Android devices... But it becomes more Wild West with non-Android devices like the TP... I think the TP = HD2 but even more complicated...
[TouchPad Development] x000x:
i guess that makes sense, but the way i see it is we the users should not really have a say what actually happens. we're just users, not developers and i'd rather leave those decisions to those who are actually working on it. i'm sure the people who voted on the poll were mostly users and not devs.. anyways, i've read those comments by Shumash too, and they seem like a good idea. but maybe easier said than done. :)
[TouchPad Development] Y314K:
Here, Here... The main prob with that is that there are 2-3 options with varying levels of difficulty on how to increase the space size for Android 4.3 on a device with a definite amount of memory... Milaq's option is ready to be implemented now... Although we will probably run into some bugs like with everything else... But the other options have ways to go or do not add as much space as possible while keeping a bootable & functioning WebOS... Eventually the best option but the one that would probably take the longest to implement is a NAND like flash like on the HD2.. But this option should be an awesome option to bridge us till that becomes possible... This option should not stop anybody from working on other options...

---------- Post added at 07:27 PM ---------- Previous post was at 07:02 PM ----------

I understand what u'r saying... At first I voted for emulated sdcard... Then some posted possible down falls of emulation... But with Milap's explanations on just how each user has completely control how much space is shared in just one part of the whole system without having to repartitioning anything on WebOS... It became clear how good of a multiple user option it was... Those that use WebOS can keep using it by giving it more space then 512MB... For us that don't deal with WebOS we can go the 512MB just in case we ever need to fix anything from WebOS... I do wish there was a chart of 16GB / 32GB TP's Android space vs 512MB/1GB/1.5GB etc. WebOS media space to have a better idea of much space it actually give us...
[TouchPad Development] gradular:
You would get about 27 gigs of space to use for files and apps for a 32 gig version. I guessing about 11-12 gigs for a 16gig version, but I don't have one. If someone with a 16gig could post the lvm stats I could tell you better. Also other options could easily be done to give more space to webos.
[TouchPad Development] Y314K:
I only own a 32GB too... If it's 27GB's after Android has been install... That is awesome.... It would = the same space one gets on a Nexus 7... And that is with WebOS install... Are u sure it's 27GB for files & apps aka actual usable space ???
[TouchPad Development] GotsOJ:
I can confirm. I've been using the build for a few days now and have had no problem installing and using apps on the 27 gb.
[TouchPad Development] shumash:
I'm not sure 1.5 gig is worth all the hassle.
[TouchPad Development] DrewYK:
Is there anyone who feels ready to test or make the switch who can post images (like the one shumash did above) but of both before and after so we can do a visual comparison? It might also provide insight for those of us who are less informed, like myself, to "see" what the impact of the change will be.
[TouchPad Development] milaq:
it's not about "additional" storage. it is about unifying the available space between /data and /sdcard
[TouchPad Development] shumash:
Finally! I get it! This allows /data apps the same limit as the /sdcard. No more running out of room for app storage, up to the combined size of the two, right?
[TouchPad Development] milaq:
you should use the new cwm as with the older one and the current version of twrp you will erase your emulated sd storage when doing a data wipe / factory reset.

with the newer cwm your emulated sd is protected and you can format /data w/o worrying about your sdcard.

yip
[TouchPad Development] DrewYK:
Best graphics ever! LOL

And it does help. :D
[TouchPad Development] Razor512:
I really like it the way it currently is. Hardware acceleration on android is not on the level of that of webOS at the moment. thus I am forced to use webOS for 1080p video (and low compression 10 bit 720p videos)

While I often stream using DLNA, if I have to go somewhere for a while I like loading up as much anime and other videos as possible, and 90% of them will only play smoothly in webOS

I can record a video showing just how staggering the difference in video playback is between webOS and android if needed. but as it is now, android sucks for HD video especially the formats commonly used for the HD content we get online today.

I have tried many video players and most will freeze if hardware acceleration is enabled and will often have to use software rendering which causes very laggy/ choppy video) while on webOS the same large HD video will play with very little CPU usage if you leave govnah running in the background to monitor usage.
[TouchPad Development] gradular:
I finally got around to doing this last night. But instead of using the media 512 zip, I used tailor in webos to shrink my sd card to 6 gigs for webos stuff and back ups and the rest went to data.
[TouchPad Development] milaq:
poll results

emulated: 53.28%

separate partition: 24.59%

i don't care: 22.13%

Voters: 122
[TouchPad Development] shumash:
Would you mind describing this in more detail, like where in milaq's instructions this fits, what it over-rides, and where to continue using his list?
[TouchPad Development] gradular:
Instead of following step 2 to resize the media partition to 512 and the data to basically the rest of the touchpad. I used Tailor to shrink media to 6144 and the rest to data. (Minus some space to system to get ready for 4.3. On my SGT2, the cm 10.2 roms plus the current equivalent to gapps is about 440 right now.)
[TouchPad Development] nikos5800:
edit:problem solved
[TouchPad Development] Y314K:
Is the only line that needs to be changed to mod the size of the WebOS media partition in the LVM-tenderloin-media_512M\update\update_script.sh file??? The changes just need to be in multiples of 32 right??? Or is it more complicated then that???

##########
##########
NEW_MEDIA_VOL_SIZE=[B][COLOR="Red"]512[/COLOR][/B]
EXTPART="cm-data"

edify_init

edify_ui_print

I might eventually go the Tailor route for more options & better modding/monitoring of the partitions... But just wanted to make sure this was all that was needed if one used the LVM-tenderloin-media_512M package...

Tailor seems to be a good option... But there are some hoops to jump thru to get it install in WebOS... Researching the best option for me to enable the Beta Feeds first...

The options seem to be...

webosquickinstall aka WOSQI or novaterm but I am leaning towards Xecutah/XServer/Xterm following the Enabling WebOS Internals new Testing Feeds for the HP TouchPad Tutorial...
[TouchPad Development] shumash:
TWRP and DataMedia

Based on this information (What is a data media device?), those of us using TWRP don't need to install a new recovery, or do they?
[TouchPad Development] Y314K:
Until TWRP adds DataMedia support u would need to switch to the new CWM to be able to do data wipe / factory resets... Hopefully TWRP is working on that... Not sure how to request DataMedia support on TWRP for TouchPad... Anybody know any of their team ???

Reading u'r link... I guess the ? for Milap is: Will the New CWM do anything different then what TWRP already does in order to correctly spare the data/media folder when doing a reset or a wipe on the DataMedia partition???

So the New CWM built omitted doing anything to the /data/media... Seems it's something TWRP already does..

Reads like the same thing to me.... Guess that's another thing that needs to be tested out..

Milap... Most of us including Shumash only own one TouchPad... And for u'r DataMedia solution to become something TP DEV's see as a no brainier to add to their roms.... I believe they would need something as wonderful as NativeSD support for the virtual DataMedia configuration... Is there any chance of adding NativeSD support for the virtual DataMedia to be able to run multiple Android installs ala HD2... Giving us the multiboot functionality that we would like...

Seems u'r already moving in that direction....

On a HD2 we can run anything on the NAND & we can use a physical SD card to run multiple NativeSD roms on it... And as long as the SD card is at least a Class 6... They are as smooth as butter... We can fit 3+ Android installs into a 8GB card.. So I think a TP with just 512MB left for WebOS & with the DataMedia mod should be able to handle that too... And we wouldn't have to worry about having to repartition anything since NativeSD already seems to use a type of DataMedia type of system under a different folder structure... That way we can run our most stable rom & then test some nightlies & maybe some future 4.3 alphas... We would be able to give each rom what ever EXT4 size it needed while being able to share our music & movies through the system, etc...

More info here.. [DEV] NativeSD Rom Boot Script for HD2

Specially the Q&A

NativeSD Rom+EXT4 for New Users with peechurs
[TouchPad Development] daedric:
Just disagree with this part, SD cards have too much latency compared even to the weak nand of the HD2. I tried that, everyone has tried that since the beggining of Android (data2sd, app2sd, link2sd you name it, the principle is the same, /data on a SD card). It's not "butter smooth", it's laggy has hell, just install a bunch of apps. (tried on a Lexar 32gb CL10).

Now, since our touchpad has 1 NAND with multiple partitions, speed shouldn't really be affected with either option.
[TouchPad Development] Y314K:
Guess I need to clog it up more to fully get the full feel of NativeSD... Can this be a TRIM prob, since time & added stuff seems to cause the prob... Unlike what u see on a freshly install Rom on it ???

Yeah... Some parts will be more complicated & something easier... Hope this options is added though.. Since we will always have a Tortoise vs Hare type of wait for the latest version of Android.... Tortoise = Last version running very stable & with everything working vs Hare = Newest flavor of Android CrashZilla...
[TouchPad Development] daedric:
The problem with SD cards (and SD card readers in general) is that they were made to access 1 file at great speeds, being it read or write. When you start to have to write multiple files, dalvik cache, shared preferences, game files etc etc, the speed of a CL10 card (theoretically max write at 6mb/s non sequential) grinds to 100 kb/s, 50kb/s and lower.

From Anandtech:

On other words, to access a sdcard we have to go trough the sdcard reader's chip limitation (being it speed or the designated interface), and the through the sdcard itself nand controller. On eMMC and NAND, those two are (usually, see the Transformer for a exception) eleminated. The SoC accesses the NAND at full speed.

See this on the HD2:

http://xdaforums.com/showthread.php?t=2045316

Even though HD2's NAND is 4mb/s max speed, it's random access speed is way better than a SD card.

Remember, just like SSD on desktops and laptops, it's not the max read/write that makes them fast, it's the almost inexistance of access time. Avoiding 6 ~14 ms on each access leads to a huge boost :)
[TouchPad Development] milaq:
aight, BTT now - this is tenderloin, not leo.
[TouchPad Development] Y314K:
Good info... Just hope it's doable on the TP... Specially since the speeds should be fast... Would just need to get over the virtual sd complications...

Right... But it's all Linux code... As Shumash wrote earlier.. He only has one TP & does not want to have to repartition his TP each time he might want mess with something different... I think u'r DataMedia + NativeSD would help get the other DEV's to adopt DataMedia... Just an idea...
[TouchPad Development] milaq:
you don't get it.

both technically and logically.

thread locked
[JAM, MDA Compact, S100 Software Upgrading] KT:
hello people

i jusr don't seem to find the new rom 1.11 from www.qtek.fi

checked out the ftp and the links given in other pages but NOTHING !!

PLEASE HELP

thanks
[LG Optimus 3D] melanrz:
Hi guys.

I have optimus 3d prototype after root a got battery issue always 0%

The last way for solve this problem is flash original bootloader.

Please guys upload original bootloader.

Or full dump from v08i rom.
[Android Apps and Games] flopower1996:
Dashclock Whatsapp Extension - German Translation

​

Hey, i've translated the wonderful whatsapp dashclock extension into german. The App is not made by me, so no credits to me.

The app is open-source and also my translations are avalible on Github!

Google Play Link for the original app: https://play.google.com/store/apps/details?id=com.mridang.whatsapp

My Github: https://github.com/flopower1996/dashclock-whatsapp

mridang's Github: https://github.com/mridang/dashclock-whatsapp

Translated app: see the attachment

Thank you very much mridang for that wonderful app! :)

Please hit the thanks button if i helped you. Thanks!
[Android Apps and Games] Dreiundachzig:
Thanks. Would you please add the ability to add this add on to stamina whitelist? Without this it hardly has any function.
[Android Apps and Games] flopower1996:
I've sent you a pm,