Dirty Unicorns Android 9, PIE by Flintman for HP TouchpadClick HERE for How to Flash the ROM
________________________________________________________________
Work in progress, not workingBluethooth
Camera
Home button________________________________________________________________
Disclaimer: I am not a developer, just a regular user like YOU.
That have found a way to improve the Tablet and would like others to benefit by sharing the information.
I am not the creator of the ROM or Recovery mentioned.
All credits goes to the developer@flintman and the Dirty Unicorns Team.
________________________________________________________________
Nice Find Thanks!
Touchie Pad said:
Nice Find Thanks!
Click to expand...
Click to collapse
You are welcome!
The following does not work, installing only the ROM.
Camera
Bluetooth
Youtube plays very well
Very smooth
Microphone works.
Wifi works perfectly.
The only problem is that the internal storage is not accessible.
It can not even save screenshots, no access. ( it is fix on the 3-28-2019 version )
I dirty flashed the 13.x over 12.5x and did not do the open gapps, so I will have to sideload them I guess at some point since I cannot get to internal storage like you said.
It boots up, but lots of stuff does not work (like bluetooth). At least the March 2019 security updates are in place!
Thanks
I can't believe we now have Pie on the old work horse. Thank you so much. I wiped everything but internal storage and did a clean install with open pico gapps. I had previously installed the DU swap in the boot directory and booting with it goes to a boot loop. I went back to 8.1 and deleted the DU swap in the boot directory and did another clean install of 9. It came right up and the few apps I have installed work. I tried installing YouTube but the play store says this version is not compatible. It won't even show it as an option. There is no access to storage from either the files app or ES File Explorer. I even tried USB with Windows and android shades out the file transfer option. All my other Pie devices give you an option in setting to set up the SD as either removeable or internal memory. I am wondering if we need to reformat internal memory to get access. I hate to kill it since I have all my install files there as well as TP Toolbox. Any suggestions welcome.
This is the first version of Pie and it boots and works, but the permissions are set for root as the user and it does not allow access to the internal storage. ( is all fixed on version 3-28-2019 )
Flintman is working on it and fixing that issue. Keep in mind it takes time and dedication to do this.
I installed the full version of Google Open gapps that comes with youtube and it works perfectly fine. Pie will be optimize as soon as the access permission is fix.
The Tablet soon will be working better than ever and all updated to the latest software available!
HP_TOUCHPAD said:
This is the first version of Pie and it boots and works, but the permissions are set for root as the user and it does not allow access to the internal storage.
Flintman is working on it and fixing that issue. Keep in mind it takes time and dedication to do this.
I installed the full version of Google Open gapps that comes with youtube and it works perfectly fine. Pie will be optimize as soon as the access permission is fix.
The Tablet soon will be working better than ever and all updated to the latest software available!
Click to expand...
Click to collapse
First
First, A big thank you to Flintman! I went ahead and flashed with mini gapps as the smallest package containing YouTube and it works fine. I will wait for the storage until it is fixed. The only other question I have is on partition sizes. I left them at the recommended sizes for the DU swap. I may be wasting memory but all appears to be working. I have TP Toolbox resident just in case. Thanks again. Also I assume we should not use the SKZ kernel since this looks later.
johnbelloh said:
First
First, A big thank you to Flintman! I went ahead and flashed with mini gapps as the smallest package containing YouTube and it works fine. I will wait for the storage until it is fixed. The only other question I have is on partition sizes.
The partition sizes applied using the following:
HP TOUCHPAD Optimize for Android with Swap Partition and SKZ Kernel_ Flash Files_
Will work with Pie, Q and any future release of Android.
The /system partition is set to 1.8G, which can accommodate a Super variant of the google open gapps.
I left them at the recommended sizes for the DU swap. I may be wasting memory but all appears to be working.
Is storage space not Memory or RAM. It will be about 500MB to 600MB extra of storage space not Memory, it does not affect performance.
I have TP Toolbox resident just in case. Thanks again. Also I assume we should not use the SKZ kernel since this looks later.
Click to expand...
Click to collapse
There is no SKZ kernel for Pie at the moment and it will not work with Pie 9 as it only works with 8.1.
The stock Kernel of Pie 9 is not optimize yet to use the swap partition, as soon as Pie is fix it will be available and the system will improve performance and stability as more RAM (Memory) will be available in Android. (Update Pie is completely optimize more than any other ROM
https://download.dirtyunicorns.com/?device=tenderloin du_tenderloin-v13.0-20190328-1316-RC.zip
28 de marzo de 2019
293.42M
---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------
du_tenderloin-v13.0-20190328-1316-RC.zip
28 de marzo de 2019 excelent room for TouchPad
larrywilson said:
https://download.dirtyunicorns.com/?device=tenderloin du_tenderloin-v13.0-20190328-1316-RC.zip
28 de marzo de 2019
293.42M
---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------
du_tenderloin-v13.0-20190328-1316-RC.zip
28 de marzo de 2019 excelent room for TouchPad
Click to expand...
Click to collapse
Thanks for the update ! The direct link now is updated to 03-28-2019 built.
Very impressive. Every app I have installed works including storage. I have 6 touchpads including a brand new 4G model. Is the plan to add swap to the ROM or will it be a separate install? If I can be of any assistance testing just ask. Thank you to all involved.
johnbelloh said:
Very impressive. Every app I have installed works including storage. I have 6 touchpads including a brand new 4G model. Is the plan to add swap to the ROM or will it be a separate install? If I can be of any assistance testing just ask. Thank you to all involved.
Click to expand...
Click to collapse
Android Pie is optimize and is swap enable from the core, all settings are set to be use with the swap partition.
Flintman did a marvelous job incorporating all the changes and making Pie available for the HP Touchpad with more improvement on its way that it could be the best ROM ever. I will update this guide soon.
It is worth it if i'm on 8.1 with swap ? I saw that yesterday we have got a update..
Steelskinz said:
It is worth it if i'm on 8.1 with swap ? I saw that yesterday we have got a update..
Click to expand...
Click to collapse
If you are using 8.1 now and enjoying your setup, then my recommendation is to keep using it that way until Pie which is 100% stable now with more features than 8.1, gets Bluetooth working and any other minor issues resolved. As of now Pie is working as Oreo. Pie is using the swap partition and fully optimized as 8.1 and 7.1.2. The only thing to do is to flash it just like any other ROM.
Hi all,
I keep popping back from time to time, and each time just keeps getting better and better... We're now up to Android 9 Pie ?? WOW !!! Fantastic work guys to all involved...
Couple of questions if you don't mind...
1) I'm currently on Android 8.1 Oreo, not sure which build or when.. without picking it up yet. Is it likely this will already be using SWAP partition, or do I still have to go ahead with it?
2) If I don't have a SWAP partition, and go ahead and create one... If I want to use an older DM rom at a later date. Do I have to remove SWAP, or will it just ignore the partition on older builds?
3) So we can use WebOS and Android 9 side by side, sharing the SWAP ??
4) Is there anyway to make the Boot partition larger than 32mb, or is that set in stone?? - and where can I find the uImage file for ToolBox, so I can have that as one of my selectable boot options.
Thanks, Lister
Lister Of Smeg said:
Hi all,
I keep popping back from time to time, and each time just keeps getting better and better... We're now up to Android 9 Pie ?? WOW !!! Fantastic work guys to all involved...
Yes Flintman still providing support and now has created the best ROM.
Couple of questions if you don't mind...
1) I'm currently on Android 8.1 Oreo, not sure which build or when.. without picking it up yet. Is it likely this will already be using SWAP partition, or do I still have to go ahead with it?
The swap partition must be created as in this guide:
HP TOUCHPAD Optimize for Android with Swap Partition and SKZ Kernel_ Flash Files_
2) If I don't have a SWAP partition, and go ahead and create one... If I want to use an older DM rom at a later date. Do I have to remove SWAP, or will it just ignore the partition on older builds?
WebOS came with a swap partition and all the ROMS were install side by side with WebOS but never implemented the use of SWAP, Android 9 is the first ROM to completely take advantage of swap thanks to Flintman for applying all the changes. And all future version of Android for the HP Touchpad will have support for the swap partition.
3) So we can use WebOS and Android 9 side by side, sharing the SWAP ??
Yes the partition that is created is the original from WebOS dev/store/swap.
In WebOS is a 400 MB
The new partition is 500 MB, it can be change to any size if the user wants to.
If you want to use any new ROM, 7.1.2 ,8.1 and 9 the /system partition must be 1400 MB, it can be resize using the ToolBox.
4) Is there anyway to make the Boot partition larger than 32mb, or is that set in stone?? - and where can I find the uImage file for ToolBox, so I can have that as one of my selectable boot options.
The /boot partition is a fix 32MB can not be change and there is no need for it to be larger.
Download the ToolBox from Here
Unzip the file rename TPToolbox-2015-01-08-v42.bin to uImage.ToolBox
Using TWRP Recovery mount /boot and using the TWRP File Manager copy uImage.ToolBox to /boot.
Using TWRP any boot uImage can be move from /boot to the SDCARD and then can be copy back.
There is no need for /boot to be larger as the boot files can easily be copy to it when need it to be use.
Think of it as a CD or USB disk that you insert into the PC to boot from, is the same concept. If you need to use the ToolBox make some space by removing a boot uImage and then copy the ToolBox in /boot.
Thanks, Lister
Click to expand...
Click to collapse
You are welcome!
Hi @HP_TOUCHPAD,
First of all, thank you for the very prompt and DETAILED reply, this is perfect and contains EXACTLY what I need to know. And apologies for the delay getting back to you, my brothers son has been in hospital last couple of days... So been a bit back and forth.
Thank you for your post, very clearly laid out and full of useful information. I shall follow that guide and re-create a swap partition. Had a quick look last night, and looks like Flintman has re-compiled all his old roms to support SWAP partition too. So should make them smoother still..
Thanks once again...
Lister
HP_TOUCHPAD said:
You are welcome!
Click to expand...
Click to collapse
Hi @HP_TOUCHPAD,
I've just picked up my Touchpad, and I appear to be running a build of Oreo 8.1.0, the Dirty Unicorns 12.5.xx.
However, in TWRP.... I only appear to have around 296k free, and not enough to store the Toolbox uImage (around 10mb) in there?? Any idea's what I can free up??
The largest files I can see are:
uImage.Android 5.4mb (boots my Android install)
uImage.moboot 63.KiB (boot manager)
uImage.TWRP 8.7mb (boots TWRP)
uImage.webOS 3.2mb (boots WebOS)
uImage-2.6.35-palm-tenderlion 3.2mb (no idea??)
System.map-2.6.35-palm-tenderlion 1.4mb (no idea??)
There are many other files and folders in the \boot partition. But not sure what, or if... I can free up any of those files/folders??
Thanks, Lister
Lister Of Smeg said:
Hi @HP_TOUCHPAD,
Thank you for your post, very clearly laid out and full of useful information. I shall follow that guide and re-create a swap partition.
Had a quick look last night, and looks like Flintman has re-compiled all his old roms to support SWAP partition too. So should make them smoother still..
The ROMS Kernels available from my guide for Evervolv 7.1.2 and DU 8.1 are my changes to make use of swap with optimization.
Flintman integrated all the changes posted on my guide to the Kernel, Ramdisk and also to the ROM of Pie (9).
Android Pie (9) is the first ROM to completely take advantage of the swap partition thanks to Flintman for improving and making the extra changes.
Thanks once again...
Lister
Click to expand...
Click to collapse
You are welcome.
Lister Of Smeg said:
Hi @HP_TOUCHPAD,
I've just picked up my Touchpad, and I appear to be running a build of Oreo 8.1.0, the Dirty Unicorns 12.5.xx.
However, in TWRP.... I only appear to have around 296k free, and not enough to store the Toolbox uImage (around 10mb) in there?? Any idea's what I can free up??
The largest files I can see are:
uImage.Android 5.4mb (boots my Android install)
uImage.moboot 63.KiB (boot manager)
uImage.TWRP 8.7mb (boots TWRP)
uImage.webOS 3.2mb (boots WebOS)
uImage-2.6.35-palm-tenderlion 3.2mb (no idea??)
System.map-2.6.35-palm-tenderlion 1.4mb (no idea??)
There are many other files and folders in the \boot partition. But not sure what, or if... I can free up any of those files/folders??
Thanks, Lister
Click to expand...
Click to collapse
The /boot partition is 32MB, It shows that WebOS is also installed. Before moving any files from /boot make sure to do a backup just in case if the wrong file gets removed. The ToolBox does not need to be in the /boot directory to be use . It can be loaded into the memory by placing the Tablet into Recovery Mode and from the PC with the novacom drivers install load it.
novacom boot mem:// <uImage.ToolBox
The ToolBox will be loaded into memory and use for anything need it, there is no need to keep it in the /boot.
The most important file to be in /boot uImage.moboot 63.KiB (boot manager)
Related
Hi again everyone,
I've prepped an IMG file that you can dualboot Phiremod v6.1 and HC v4 2nd Edition off one SDcard.
1-The image file is 3.7gb. So you will need a 4gb SDcard or larger.
2-Both roms share the same SDcard partition. So on a 4gb card, the available space is limited to 1.8gb.
3-If you use an 8gb SDcard. To get use of the remaining storage on your SDcard. Just burn the image and then use EASUS Partition Manager to extend the SDcard partition. (Which is the 7th partition on the card)
4-I've udpated the Phiremod v6.1 with:
-The latest OC Kernel by Dalingrin 041811C
-Alsa update for smoother video playback
-Honeycomb Softkey Icons by XDA user Bawb3
I've done this mainly just for fun and to see if it would work and thought I'd share it with everyone if you wanna give it a go. Thanks to all the devs for all their hard work in getting these great ROMs for our Nook Color.
Credits:
The CM7 Team
Dalingrin
Deeper-Blue
Samuelhalff
Divine_Madcat
Phiredrop
j4mm3r
Rookie1
Bawb3
Download:
ph-hc-dualboot-sd.img.zip
MD5: 36b474afb9436bc2e887aeecec8b5c7e
Click to expand...
Click to collapse
Follow directions from Nookdevs.com to burn the image to your SDcard.
Burning a bootable SD card
Once you burn the image to your SDcard. Power off your nook and place the SDcard in your nook.
-To boot into Phiremod Nook v6.1 just power on your nook with the sdcard in and leave it alone.
-To boot into HCv4 2nd Edition, hold the HOME button while powering on. Continue holding the HOME button until you see the "Android..._" screen.
Take it or leave it, just hope you enjoy it.
---------------------------------------------------------------------------------------------------
Edit 5/23: Updated Img with Phiremod 6.2 and Madcat's Honeycomb Hybrid-RC1
Reason for creating a new image and not just a flashable update is because the HC Hybrid /system was too large to fit on the original Dualboot img. So I prepped a new one for that reason as well as making the image smaller so it will definitely fit on a 4gb uSDcard.
What's included in this new image:
1- A 3.4gb Img file that should fit on any 4gb uSDcard or larger
2- J4mm3r's u-boot menu! (Read here for more info on how to use it)
3- Latest Phiremod 6.2 with Dalingrins 4/13a OC and Alsa update
4- Latest Divine_Madcat's Honeycomb Hybrid RC1
5- Honeycomb Hybrid RC1 has my sdcard mount workaround. I also included a file manager.
6- Read here for more info on the sdcard mount workaround.
7- Follow the steps above to burn the image to your uSDcard
8- Enjoy!
Keep in mind that the Honeycomb Hybrid RC1 is a work in progress so there are known issues. I suggest you read the OP in this thread here to see what's working and what isn't.
Download:
ph-hc-dualboot-sd-v0.2.img.zip
MD5: 9cda109f5fb8397d5bbd1912714b6a57
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------
Update 5/31-Phiremod Nook 6.3 Dualboot SD Flashable Update:
This will only format /system. Data stays intact.
1-If you're still using the original Dualboot-SD img. Follow directions below from 5/5 update on how to install latest Phiremod to your Dualboot-SDrom.
2-If you're using latest Dualboot-SD v0.2 with j4mm3r's boot menu. Choose to boot into SD-->Recovery and flash from there.
phiremod-nook-6.3-Dualboot-SD-Update.zip
MD5: 445482d78263e8596063ea104a46fb7d
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------
Update 6/22-Phiremod Nook v7-Test Dualboot SD Package Update:
This will format /system and /data of your Phiremod rom. So please backup all your apps!
Well I went ahead and made it easier for everyone. So I packaged the whole Phiremod v7-Test as a CWM-SD Flashable zip. This will install phiremod-nook-v7-test, gapps, and will install the launcher-pro backup to the sdcard partition for you.
-All you have to do is download the 'phiremod-nook-v7-TEST-SD-CWM-package.zip' file, no need to extract anything
-Boot into CWM-SD and flash the package zip file
-Reboot when done
-It will prompt with 2 different options on startup, choose "Setup Wizard"
-For some reason it won't get past that, even when touching the Android guy, to get around this touch all 4 corners of the nook screen starting with:
1. top left hand corner
2. top right hand corner
3. bottom right hand corner (just above the 'change language' button)
4. bottom left hand corner (just above the 'emergency' button)
-That should get you to the main screen.
-Connect to a wireless network
-Market will not populate correctly, so go into the app drawer and choose 'Talk'
-That should give you an option to add a google account
-Once completed go back to the main screen and goto options--> preferences --> and restore the launcher pro backup
-You should now see Market on the home screen
-Don't forget to thank the devs!
-Personal thank you to "bdeville" for testing the .zips for me before I borked any more installations!
phiremod-nook-7-Test-Dualboot-SD-Package.zip
MD5: b814eb7681ea57669764e449b77ef4c1[/QUOTE]
---------------------------------------------------------------------------------------------------
Edit 5/5: Update Phiremod to 6.2 and Honeycomb to Madcat's Honeycomb_RC1
1- I forgot to mention that with your dualboot rom SDcard. It also contains a Modded CWM that will allow you to flash updated roms from "my" thread only!
2- Place the .zips you downloaded from this thread onto your /sdcard (7th) partition.
3- To boot into the Modded CWM. When powering on your nook. Hold the "volume+/volume-" together while booting up, until it loads up CWM
4- Now select "choose zip from sdcard"
5- Choose the .zip file and confirm "yes"
6- Sit back and let it do its thing
7- You can either flash another rom or go back to the CWM main menu and choose "Reboot system now"
8- Enjoy your updated roms!
Downloads:
Phiremod 6.2 Dualboot SD Update: (This will keep your /data partition intact)
phiremod6.2-SD_Dualboot-Update.zip
MD5: f6350cb0393576d5e53fe5ce3315aec1
Click to expand...
Click to collapse
Divine_Madcat's Honeycomb RC1v2(Working su, market, sound) Dualboot SD Updated: (This will format both /system and /data)
update-HC-rc2-Dualboot-SD-a.zip [Updated 8pm EST. / Tested and working by me]
MD5: a4231f7e141c1e875ad07cef2e97d912
If you get a keyboard failure error on first boot. Just do a quick reboot and it should go away. Downloads from market seems very slow off an SDcard install. Might just depend on what Class it is. And remember. This is a WIP. Don't forget to thank Madcat for his work on this!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
If I've helped in some way, please say thanks in one way or another!
Thanks,
Racks
Nice. Will try
Sent from my SGH-T959 using XDA App
AAAAAAAAAaaaaaaaaaahhhhhhhhh
Just when I think: "Enough of this craziness, let's just sit down and enjoy my nifty little device," along comes YET ANOTHER rom to flash!
If I do this one, though, I get back one, maybe two of my 8 GB cards. So, win/win.
Excellent work, Racks!
glg
glgehman said:
Just when I think: "Enough of this craziness, let's just sit down and enjoy my nifty little device," along comes YET ANOTHER rom to flash!
If I do this one, though, I get back one, maybe two of my 8 GB cards. So, win/win.
Excellent work, Racks!
glg
Click to expand...
Click to collapse
Please let me know if it works out for you or not. Just so I can make any needed changes if necessary.
Thanks,
Racks
Worked great for me. Had my flashing 4gb and it booted right up into HC. Great work. Didn't realize how good HC looked on here, but I'm sticking to Phiremod for now.
racks11479 said:
2-Both roms share the same SDcard partition. So on a 4gb card, the available space is limited to 1.8gb.
3-If you use an 8gb SDcard. To get use of the remaining storage on your SDcard. Just burn the image and then use EASUS Partition Manager to extend the SDcard partition. (Which is the 7th partition on the card)
Thanks,
Racks
Click to expand...
Click to collapse
Howdy,
Any way to implement this "mod" into your image???
[ZIP][CM7] Nook Color SDcard and emmc swap!
Thanks very much Racks, it works really well. Finally get a chance to try Phiremod and honeycomb without using 2 SD cards!! I only have one, the poor guy that I am
I too loaded the image to a 4 gig card and it seems to work fine so far. Thanks for your efforts!
Thanks man.... It worked for me as well!
oops maybe I spoke too soon, the phiremod works ok, but, the honeycomb loader never gets by the screen with the android_ on it. I will reflash later without epanding the partition on the SD card to see does that make a difference.
(yeah I used an 8GB card and used easus to expand the 7th partition.)
Glad to see that this image was useful to some!
Thanks everyone for the thanks,
Racks
racks11479 said:
Please let me know if it works out for you or not. Just so I can make any needed changes if necessary.
Thanks,
Racks
Click to expand...
Click to collapse
Didn't actually get to try it last night. Bandwidth trouble.
Downloaded, unzipped, flashed to a 8gb Sandisk card. Left it as burned.
Installed in Nook: Booted to Phiremod AOK. Rebooted into Honeycomb AOK*.
Shut down and put sdcard back in my PC to resize the sdcard partition. Hmmm.
Both EASUS and MiniTool show the card as 8GB unallocated (ie: no partition information available!!).
Put it back in nook and reboot. Comes up to phiremod AOK. Weird.
OK, second time around putting SDcard in PC, I got correct mount and could edit partitions.
glg
* - Honeycomb lock screen says "Running on internal eMMC" which we know is not true.
** - I love that you changed the POST message. Those of us in Pennsylvania see the stock message as Touch the Future of Redding (the city). Um.. Not without latex gloves, I think.
glgehman said:
Didn't actually get to try it last night. Bandwidth trouble.
Downloaded, unzipped, flashed to a 8gb Sandisk card. Left it as burned.
Installed in Nook: Booted to Phiremod AOK. Rebooted into Honeycomb AOK*.
Shut down and put sdcard back in my PC to resize the sdcard partition. Hmmm.
Both EASUS and MiniTool show the card as 8GB unallocated (ie: no partition information available!!).
Put it back in nook and reboot. Comes up to phiremod AOK. Weird.
OK, second time around putting SDcard in PC, I got correct mount and could edit partitions.
glg
* - Honeycomb lock screen says "Running on internal eMMC" which we know is not true.
** - I love that you changed the POST message. Those of us in Pennsylvania see the stock message as Touch the Future of Redding (the city). Um.. Not without latex gloves, I think.
Click to expand...
Click to collapse
Lol. I really appreciate you sharing your experience with everyone.
And regarding honeycomb mentioning it's running off emmc. That's because I took the complete zip from samuelhalffs thread without modification and prepped it for the SD install.
Thanks,
Racks
How would i benefit if i already have phiremod v6 installed emmc?
First ever post: Great Job!!
Have been a lurker in the site for the longest time. Been actively watching the developments in the HD2, NookColor and GTab forums.
Kudos to all the developers and modders who've made Android dream a reality.
And, a special thanks to you, who made it a double treat for people like me.
Only trouble, with this dual ROM (which I've to tell you, my friend, has blown my mind away), that I've not been able to overcome yet is, getting my XP Pro or Win 7 Pro to recognize my 7th partition (SDCard). Nothing I've done so far has helped.
Tried both ADB and NookColorUMS. I sure am doing something wrong. Any help is much appreciated.
Once again, THANK YOU!
pisces73 said:
Have been a lurker in the site for the longest time. Been actively watching the developments in the HD2, NookColor and GTab forums.
Kudos to all the developers and modders who've made Android dream a reality.
And, a special thanks to you, who made it a double treat for people like me.
Only trouble, with this dual ROM (which I've to tell you, my friend, has blown my mind away), that I've not been able to overcome yet is, getting my XP Pro or Win 7 Pro to recognize my 7th partition (SDCard). Nothing I've done so far has helped.
Tried both ADB and NookColorUMS. I sure am doing something wrong. Any help is much appreciated.
Once again, THANK YOU!
Click to expand...
Click to collapse
Thanks for the kind words. Just remember to thank the guys who developed the roms. To mount the 7th partition try running the following command in adb shell:
#echo /dev/block/mmcblk1p7 > /sys/devices/platform/usb_mass_storage/lun0/file
This should mount the 7th partition. Let me know if it works.
Thanks,
Racks
I was looking to dual boot Phiremod and Stock on EMMC after seeing how awesome Phiremod is, but the place that I found supplying ROMs for dual-boot EMMC doesn't have Phiremod. Do you know where I could find it/do it (total n00b)
Source mentioned- http://forum.xda-developers.com/showthread.php?t=959461
Market script
Excellent work OP (and obviously all the devs that made the roms etc.). One quick question though, I first flashed this image on a transcend class 6 8gb card and, due to the low random write speeds, I experienced random sluggishness and force closes. I will be resolving this issue tomorrow, but another issue has arisen. When I first ran the market a script ran that asked which gapps i wanted installed. After it directed me to install the first two gapps the market force closed. Before I had realized that it was my SD card that was causing the force closes I tried reflashing the SD card with this image again but when I opened the market again after reflashing the script didn't run.
My question is this: When I flash the new SD card will the market script run again? And if not, how would I go about have the market script run again?
Thanks in Advance,
Deusx
I just love it, i just love it racks. Now i'm tryinna get used to the honeycomb. How do i change wallpaper?
Blaggah said:
I just love it, i just love it racks. Now i'm tryinna get used to the honeycomb. How do i change wallpaper?
Click to expand...
Click to collapse
Lol. Glad it's working out for you. Make sure you thank the roms devs as well.
Just long press the home screen and it will bring up options todo so in honeycomb.
[ROM] CM7 8GB &16GB Compatible Beta for the Nook Tablet.., Updated 7th July to Beta
***** DISCLAIMER ******
Please note this software is still classed as experimental and you use this at your own risk. We have done some in house testing and all has worked fine but we cannot guarantee the exact same results for everyone. We accept no responsibility for any damage or loss of information with your Nook Tablet. You use this software at your own risk. By choosing to download and install this software on your device you accept that you are willing to risk your own device and that any damage and or total loss is your own responsibility.
FOR PROGRESS AND UPDATES CONTINUE TO READ THIS THREAD. FOR KNOWN BUGS AND ISSUES PLEASE SEE THIS THREAD
Below you will find Internal release of our Nook tablet CM7. This has been rebuilt from the most recent CM7 stable source. I'll update the 2nd posts with release information asap.
Please feel free to base your rom on ours, I believe it is now tested well enough and is sufficiently stable to use.
The Source for the CM7 android device folder, the kernel and meghd00ts Improved recovery can be found here Here
For information on what you can and can't do and reasons for this please visit HERE
INTERNAL VERSION 8GB & 16GB COMPATIBLE
Download HERE MD5 95043b08484aa218ccf93b5ef4785825
For the internal version you need have access to CWM either internally installed as your recovery or from an SD card. I'm not going to reinvent the wheel telling people how to do that. Just have a look through the development thread and you'll se numerous threads showing you how to do this.
This version has the ability to reboot to recovery added to the reboot option in the power menu. It does not however come with a recovery image, this was already released by lavero.burgos and can be downloaded from http://forum.xda-developers.com/showthread.php?t=1640958
PLEASE BACK EVERYTHING UP BEFORE YOUR BEGIN!!!!
Once you have CWM on screen with the downloaded update zip archive on your sd card, Follow these simple steps
1. Goto install zip from sdcard
2. Choose zip from sdcard ( if CWM hasn't recognized your SD card you need to eject it and re insert it once or twice, sometimes you need to go to mounts and unmount SD, pop it out and back in then select mount sd)
3. choose the CM7-TEAM-B-BETA1-signed.zip
4. scroll down and select Yes - Install CM7-TEAM-B-BETA1-signed.zip
5. sit back for a couple of minutes while the installation is carried out
That’s CM7 installed, next you need to prepare the rest of the device
1. press your power button once
2. ***OPTIONAL*** scroll down and select wipe data / factory reset, this is optional but if you are coming from a different OS it is recommended, if you don't it can sometimes causes force closes and various other issues.
3. you're ready to roll! scroll up and select reboot system, initial boot can take a while and does pause for a short while on the black screen between flash page and CM7 Animation, enjoy CM7 For Nook Tablet!
if you were already running a version of CM7 it is possible you may be able to skip the wipe data bit and just select wipe cache instead but it's best if you can wipe data and know that you have a clean install without any bugs remaining from a previous install. By all means try just clear cache and see how you go, if you seems to have lots of bugs we recommend doing a clear data and trying again.
SD VERSION IMAGE ***UPDATE NOT YET AVAILABLE this is the Alpha final version***
Download HERE
I've done the SD version a little different this time, it's as a 4gb SD image (the last partition is used as SDcard in CM7 so you can resize this partition to fill up your whole card if your card is bigger than 4gb). The image can be burn using windows Image writer or dd command in linux / OSX
The window software is available HERE.
To write the image on linux / osx do the following
WITHOUT your sd in the machine go to a terminal window and type
Code:
mount
Notice the drives that are showing they will be something like dev/sda. Now insert your SD and give it a moment to recognise it. Once again terminal type
Code:
mount
and you should have an extra device such as /dev/sdc showing which is your sdcard (it may say dev/sdc1 or something but you aren't interested in the number)
Once you have the SD device id use following code exchanging sdc for your device id
Code:
dd if=/location/of/SDfile.img of=/dev/sdc
Then sit back and wait, it will appear to be doing nothing and will take a long time but once done the command will complete and you have a nice new SD version of CM7 to run
Power off the nook, insert the sd and then power it on to enjoy your new CM7. If it done'st boot try completely powering of and ten connect power cable and wait for it to turn on and hopefully boot form SD. The first boot WILL take a few minutes. Consecutive boots will be faster
We've been asked a number of times for a donation link so I set one up you can click HERE. Or if you prefer to donate directly to myself or Goncezila by clicking on the donate buttons under our names. We thank you in advance for your generosity
***** DISCLAIMER ******
Please note this software is still classed as experimental and you use this at your own risk. We have done some in house testing and all has worked fine but we cannot guarantee the exact same results for everyone. We accept no responsibility for any damage or loss on information with you Nook Tablet. You use this software at your own risk.
First boot can take a little while. once in you will be requested to enter your Google account details, because your wifi is not yet connected you will be better of skipping these steps, you will be asked again as soon as you try to open Google Market anyway.
Tap the menu button and select settings (not adwsettings) go to wifi and setup your wifi connection, if for some reason wifi networks do not show, just toggle wifi off and on and it will sort it's self out
Feedback thread HERE so please make sure you post any questions and / or feedback in there and keep this thread for development only. Thank you!
Thanks and mentions
All those that support the new release, I'm sure you all know who you are
Quid246 - for his skills in photoshop to make our new splash screen (Alpha release)
Bauwks - Without him we would not be here. He blew the top off the bootloader and his thanks bar is no where near what it should be. Also a thank you for him agreeing to allow us to change his box image on the bootloader when we asked. Please find some of his posts and hit Thanks!
Loglud - again for helping us out with our research
AdamOutler - His guide was used to help us with kernel issues and build our SDcard version
succulent for pointing out that although we had commented out a file in the build, it was was still possible it was effecting up our new build. Also thanks to succulent for creating a build script that automatically added the 2nd boot onto the boot.img during source build. Thank Succulent! You’re a star, it just wasn't happening when I tried to do it
The Cyanogen Mod team for the initial build of Cyanogen mod that we ported over
Generally every other member of XDA - For being so supportive and throwing out ideas and experience!
Know issues, Hints and Tips
keyboard numbers layout when you hold a letter doesn't initially work, to fix just change keyboard language to your local setting e.g. US english
PROGRESS UPDATES
7th July 2012
Released beta update built on latest Stable CM7 source
Made some changes which will hopefully help with wifi issues
added some stability fixes
Added reboot to recovery in the reboot menu
Other minor issues tweaked to improve general overall performance and response
MARCH 20th{/I]
build.prop update zip added to support thread to cure mounting on USB issues
MARCH 9th
CM7 Final Alpha released
A complete relbuild of CM7 for the Nook Tablet. The new version is based on Gingerbread 2.3.7 CM7.2
All software updated to latest CM7.2 version and all files rebuilt to match
Full hardware video decoding for h264 encoded videos
Hardware acceleration for gfx
Wifi issues fixed so now connection should work without crashing
GAPPS removed as per Google requests and GAPPS download link added to OP
Many general system bugs fixed
Much much more that ill post here when home from vacation
MARCH 7th 2012
SD version of CM7 re-released
MARCH 5th 2012
Sorry for the lack of updates recently, Gonc and I have been really busy but we're happy to say a new build has been getting tested personally by us and has now been passed on to the testing team.
Bit more about it is HERE
FEB 19th 2012
2nd public release of CM7 for Nook Tablet.
Changes since original version are:
Format bricking issue fixed
Boot count issue where it resets your device to standard after 8 boots fixed
Market should now install any software you can get on there without the SD / USB issue
Browser should now happily play videos from mobile youtube
Graphics driver update allows playing of YouTube videos a720p without issue
Previous issues updating BusyBox should now be cured
Many games and applications that crashed on intro video will now work flawlessly
Internal media partition now fully accessible
internal media and sdcard now show when connected to USB on computer
more things which I'll add here when I remember them!
Feb 12th 2012
The new build which is alpha 8 is now ready and testing will begin in the next day or two.
Thanks to all members of the team for volunteering and to xIndirect for setting up the application forms online that everyone filled out to become members and the bug report forms he's also set up.
Goncezilla and I haven't really discussed a length of time for testing but generally Testing will continue until we believe that the remaining bugs do not cause severe problems for the end user. Once we are at that stage the donators will then get their copies which will allow us to gradually increase the testing coverage before finally being released as a beta to all member of XDA.
Myself and Goncezilla would like to take this opportunity to thank everyone for their support and understanding while we build you a version of CM7 for your Nook Tablets that we can be proud of
Feb 10th 2012
Following bugs have been fixed
SD format and bricking issue,
Market app install problem
Various software crashing when it tried to play video (even browser in mobile youtube)
Internal Media partition not mounting
Media partition not connecting to USB host when plugged in
Further information on updates and release are available HERE
Difference
Sorry for this question. What are the differences between internal and external? Does internal completely wipe and remove all Nook software, and external only boots CM7 with the card in and boots Nook style without?
For those on Windows machines (like me!), the free Mini Partition Wizard Home Edition can be used to create the SD card partitions. In this case just make the first partition Primary and Active; that will allow it to be seen as a bootable partition.
joeras said:
Sorry for this question. What are the differences between internal and external? Does internal completely wipe and remove all Nook software, and external only boots CM7 with the card in and boots Nook style without?
Click to expand...
Click to collapse
For Internal you need to have CWM running (either from SDcard or internally) and it WILL wipe your stock setup.
External runs purely from the SDCard and will not mess with your internal data.
Remember that Celtic and I are the only ones who have tested this as of yet so there may be unfound bugs! This is Beta after all
Please report all bugs here, do not PM us. We will try to validate and then correct them.
Enjoy everyone!
tonyp22 said:
For those on Windows machines (like me!), the free Mini Partition Wizard Home Edition can be used to create the SD card partitions. In this case just make the first partition Primary and Active; that will allow it to be seen as a bootable partition.
Click to expand...
Click to collapse
Yes sure just shrink the partitions a little to fit
We'll be adding a small modification to allow SDCard simulation when booting form card which will require adding a 4th partition later to act as the SDCard
Just thought to release as was to get it to everyone
I take it there is a way to go back to stock 1.4.0 just in case?
Unit is rebooting into cm7 as we speak. Looking great, speed is awesome. Great job guys.
arclite00 said:
I take it there is a way to go back to stock 1.4.0 just in case?
Click to expand...
Click to collapse
Yes you can flash a stock image the same way
did internal version. Downloaded to PC, unpacked, copied directly to directory via usb mount, restored. The restore went fast, and the initial boot-up was faster than my G2's backup restores...lol Connected to wifi, signed in, and up and running.. Fantastic!!! kudos!! and i used the "Thank You" button so i'm not thanking you in this reply...<snicker> Over all, everything done in less than 5 minutes. Now to tweak/customize/play with.
For those of us who don't know/have ubuntu, can you point to a good resource/post for creating the SD card under Windows 7 to run the SD card version of CM7?
Thanks!
If I don't see a clockworkmod folder I assume it installed wrong or I create the folder?
offlimitz said:
If I don't see a clockworkmod folder I assume it installed wrong or I create the folder?
Click to expand...
Click to collapse
I'm pretty sure Clockworkmod makes it as standard, as long as you have clockworkmod installed you should be able to just create the folders and drop your files in, do a backup from CWM and the folder should appear anyway
Thanks man. downloading sd release now. this doesn't affect the stock NT rom, right? the SD release ofc.
Celtic,
You may want to mention that the user may need to eject/reinsert the SD card for CWM recovery to recognize it.
Thanks for the good work!
darthvince said:
Celtic,
You may want to mention that the user may need to eject/reinsert the SD card for CWM recovery to recognize it.
Thanks for the good work!
Click to expand...
Click to collapse
I'll post that in first thread now.
Know-Fear said:
Unit is rebooting into cm7 as we speak. Looking great, speed is awesome. Great job guys.
Click to expand...
Click to collapse
After it's first boot it's a lot quicker than stock
In fact I think even the SD version is faster than stock, stock really is poor!
Just an FYI to everyone. We mounted the internal B&N partition (the 11 GB that used to locked out) to /data/media and the 1GB you used to have access to to /mnt/media.
Both fully rw!
Holy **** people!! 200 downloads already and only 20 of clicks of thanks on the first thread :s
I think my server bandwidth is going to get a hammering, I best check it's ok!
Sorry for the basic question, but when we go to CWM -> Advanced restore -> NTCM7, do we want to restore boot? system? data? cache? sd-ext? all?
Thanks!
RemixOS_Jason said:
Release notes
Remix OS for PC version: 3.0.102
Release date: August 2, 2016
Fixed more Wi-Fi issues related to Broadcom wireless chipsets
[*]Support hard disk partition mount allows you to access other files and folders
Support for future updates via OTA
Added feature where recent apps will be shown on the top line of apps in the App Drawer
Added “App Store” to Remix OS
Click to expand...
Click to collapse
I updated my Remix OS hdd installation today and recognized that all external (read: non Remix OS) partitions got automounted. I now lots of people asked for easy access to their windows partitions from within Remix OS, but I would prefer to keep things seperated.
Is it possible to disable the "access to other files and folders" in general or at least to stop automounting those partitions?
Thanks in advance
Martin
auto-mount is even tried for non-ntfs partitions
I am running Remix OS 3.0.102 in a dual boot system together with Ubuntu. While signing on the auto-mount function says already that there are two "corrupted" ext4 partitions beside one NTFS drive. After signing on the NTFS drive has been mounted automatically, while the Remix-OS partition "Android-x86" and the Ubuntu partition are called "corrupted" - probably because they are formatted with ext4.
I think, showing partitions which can't be opened in Remix OS doesn't make sense, especially if they are shown together with a dangerous offer "Touch to fix". There should be a way telling Remix OS which partitions are interesting and which should be mounted automatically.
https://postimage.org/
filius.martis said:
I updated my Remix OS hdd installation today and recognized that all external (read: non Remix OS) partitions got automounted. I now lots of people asked for easy access to their windows partitions from within Remix OS, but I would prefer to keep things seperated.
Is it possible to disable the "access to other files and folders" in general or at least to stop automounting those partitions?
Thanks in advance
Martin
Click to expand...
Click to collapse
@filius.martis @remixtester - Got it. I'll flag this question with our PM and I'll let you guys know. Thanks!
I have same problem, my drive got corrupted, dev should fix this asap.
arts821 said:
I have same problem, my drive got corrupted, dev should fix this asap.
Click to expand...
Click to collapse
Did you mean using latest remix version, the windows and another partition get error or corrupt omg
FYI so everyone in this thread is updated, we have developed the option to turn off the mount partition feature. It is being tested right now and it will be rolled into a future update, likely with a week or two.
Thanks!
RemixOS_Jason said:
FYI so everyone in this thread is updated, we have developed the option to turn off the mount partition feature. It is being tested right now and it will be rolled into a future update, likely with a week or two.
Thanks!
Click to expand...
Click to collapse
Will a test version be available for testers?
Sent from my on Z00A using XDA Labs
@RemixOS_Jason
...is the Gaming ToolKit being looked into to attempt improvemtnts for future releases?
<<<New World Order (NWO)>>>
Selection of the partitions possible which should be mounted?
RemixOS_Jason said:
FYI so everyone in this thread is updated, we have developed the option to turn off the mount partition feature. It is being tested right now and it will be rolled into a future update, likely with a week or two.
Thanks!
Click to expand...
Click to collapse
You are writing of "option to turn off the mount partition feature". What I would prefer is an option to select the partitions which you want to mount (and which not). Another option should be: manual mount / automatic mount of the partitions which you want to mount.
remixtester said:
You are writing of "option to turn off the mount partition feature". What I would prefer is an option to select the partitions which you want to mount (and which not). Another option should be: manual mount / automatic mount of the partitions which you want to mount.
Click to expand...
Click to collapse
That's what we have at the moment; Yes they are auto-mounted but they can be ejected via that Storage & USB screen. Maybe add a lock button on that screen so it isn't remounted on reboot.
If the corrupted message is due to the system trying to treat all partitions as fat/ntfs/exfat then that should be fixed [I'd run e2fsck on those partitions just to make sure they aren't actually corrupt].
And to answer the OP [this question has been asked and answered before]; you disable the service MediaScannerService from the Media Storage system app.
[email protected] said:
@RemixOS_Jason
...is the Gaming ToolKit being looked into to attempt improvemtnts for future releases?
<<<New World Order (NWO)>>>
Click to expand...
Click to collapse
@[email protected] - Yes, in fact there's an improvement program for the Gaming Toolkit going on now. After using it in your preferred games, we'd love to get your feedback through this form: https://goo.gl/forms/IaRM5aedoznFAr2C3
Thanks!
RemixOS_Jason said:
@[email protected] - Yes, in fact there's an improvement program for the Gaming Toolkit going on now. After using it in your preferred games, we'd love to get your feedback through this form: https://goo.gl/forms/IaRM5aedoznFAr2C3
Thanks!
Click to expand...
Click to collapse
good day....i have just updated to v3.0.201, and i have few requests concerning changelogs posted on your site: http://support.jide.com/hc/en-us/categories/202520967-Remix-OS-for-PC
1)...is it possible that if there are any changes/modificatios are made to the Gaming Tool Kit can be included in the changelos together with the system changes that are well detailed as you do?
2)...i assume this is a stable release as i see it on your site, and thank you for using the latest Android-x86 RC2, the system has significantly improved, more stable, fluid , but the ads on the start menu still cripples system RAM(this is for funding purposes, the advertisements, so no need/wont complain any further)
3)....for futur releases, can u please or is there a way that Proxy SET-UP can be done for Ethernet connections?...include this somehow if within your future plans!
4)I tried the GameKITtool, IMO its still same as in the previous v3.0.104, nothing "seems' to have being changed, also nothing bas broken, still works marvellously, but lacks the previously made requests for 100% game controll compatibility!
5)overall system perfomance and stability is greatest,and thank you for including previously requested features into the sytem/update!
6..........for linux users that installed RemixOS, and thus obviously never installed using the Jide Installer, either wont be able to get OTA?
based on this? "OTA support disabled if software was NOT installed by official Jide installer"
<<<New World Order (NWO)>>>
HP Touchpad Universal Optimize Swap Settings for All Android ROMs
MAX 1GB RAM - MAX 1836 Frequency
Click HERE for detail Memory and Frequency information for each ROM
Click HERE to dual boot all listed Android ROMs and LuneOS
Click HERE for PowerOFF - Prevents Battery Drain
Upated: November 12, 2020: Added HP TOUCHPAD DEBRICK Linux Live CD
Upated: November 12, 2019: Added PowerOFF
Upated: November 07, 2019: Rom_Reducer to Evervolv, Kitkat by Milaq and LuneOS
Upated: October 09, 2019: HpTp_MaXtreme (Max Extreme Kernel Settings for All ROMs)
Upated: October 01, 2019: Added ROM: LineageOS 11 Kitkat by Milaq build October 01, 2019
Upated: September 28, 2019: All_Files for Lollipop got updated to fix WiFi
Upated: September 25, 2019: Added ROM LineageOS 14.1, HpTp_MAX_Settings, 1GB Swap
Upated: September 2, 2019: Fix Evervolv 7.1.2 Frequencies, Created: Universal Authority, Added: Evervolv Pie, Posted: Universal Settings
Upated: August 24, 2019: HP Touchpad Novacom Repair Android
Upated: August 2, 2019: New Improved Settings: HpTp_Universal_Optimized_Swap
Added ROM_Reducer; Removed support for Lineage 11
Upated: July 12, 2019: Flash ToolBox v42 by jcsullins to /boot
Upated: July 8, 2019: /System Partition is 2.2 GB:/ Improved Settings to All ROMs
________________________________________________________________
HP TOUCHPAD DEBRICK Linux Live CD
Built in with all the tools to properly run TP Debrick v005 by jcsullins and also novacom drivers.
Click HERE for the Guide
Click HERE to Download ISO File
________________________________________________________________
HP Touchpad Novacom Repair Android
Built in Novacom Driver, Repair non bootable Tablet, Flash ToolBox, Modify Ramdisk and more !
Click HERE for the Guide
Click HERE to Download ISO File
________________________________________________________________
Back up any data before making any changes to the Tablet, follow this guide:
Click here on how to backup ROM to PC and restore
Important, do not restore the /boot partition
________________________________________________________________
For WebOS users
WebOS has the swap partition and it can be share with Android.
There is no need to Flash the file Automatic_Wipe_All_and_Create_Android_with_Swap.
But to use Android PIE, Oreo and Nougat the Android /system partition must be 1400 MB.
There are two options to resize the Android /system partition.
Inside webOS using Tailor:
Click here for Tailor
Using the ToolBox:
Click here to download the ToolBox
After the Android /system partition have been resize Flash any listed ROM.
________________________________________________________________
The Automatic_Wipe_All_and_Create_Android_with _Swap can be flash using any Recovery.
It is best to use TWRP Recovery Version 3.1 or 3.2
Click here to download TWRP Recovery 3.1 by Flintman
Click here to download TWRP Recovery 3.2 by Flintman
________________________________________________________________
Easy Automatic process to Wipe All and Create Android partitions with Swap 1GB or 500MB
Click Here to Download Automatic_Wipe_All_and_Create_Android_with _Swap, choose 1GB or 500MB
This file MUST BE FLASH to create the swap partition to be use by the listed ROMs
A complete Data RESET of all the internal storage.
All partitions are deleted, is a total fresh start as if the Tablet came from factory with only Android install.
The Android partitions are created and formatted ready for use:
/system 2.2 GB ( Allows to install any ROM plus the maximum size of Open Gapps Variant Super )
/cache 200 MB ( Standard size )
/media 1GB or 500MB ( USB Media in Android, use it to save the ROM, Gapps and Universal Settings to Flash )
HpTp_MAX provides more RAM available and Android can use over 750 MB of swap space.
/swap 1GB or 500MB ( It allows Android to store temporally Data from RAM to allocate more Memory for Apps. )
/data depends on the model 16, 32 or 64 GB ( The free space available for Android Apps and user Data )
/boot 32 MB ( Is a fixed sized ) Moboot will be created and also TWRP Recovey 3.2.
The Tablet will boot as always, with Recovery in the Moboot Menu ready to Flash any ROM.
________________________________________________________________
Flash all listed ROMs in the order to download:
1. First the ROM ( Only the specific ROM by the built date will work )
2. HpTp MAX Universal Optimize Swap Settings ( Enables swap partition and provide the best settings for Android )
All_Files (name of the ROM) zip contains everything. Uncompress on PC first then flash the selected frequency.
2_A Optional -- HpTp_MaXtreme (Max Extreme Kernel for All ROMs)
Click HERE to Download HpTp_MaXtreme for All ROMs
If you do not know the maximum CPU speed of your Tablet flash 1674 first to set up.
All Kernels are the same, the speed is preset to avoid installing any Kernel App in Android.
Do not install any Apps in Android to make the Tablet work faster, it will be the opposite.
It will use more RAM and cause reboots, there is nothing to change.
This is a laptop with a touch screen keyboard not a phone.
3. Optional -- ROM Reducer Click HERE for ROM Reducer
4. Flash the Open Gapps according to the ROM version, is best to install Pico and build the system as need it.
5. Optional -- All listed ROMs have /system Read and Write enabled, Click HERE for Root access using SuperSu v2.82
6. Optional -- Universal Authority Click HERE for Universal Auhority
7. Important: Read the section on this guide -- Flash the ToolBox 2015-01-08-v42 by jcsullins into /boot
Flash the files in the listed order in TWRP all at one time.
The Tablet will boot into the Welcome setup screen as a brand new Device.
________________________________________________________________
Root access with SuperSu v2.82 for all the ROMs
5. Click Here to Download SR5-SuperSU-v2.82
________________________________________________________________
Evervolv v9 Android PIE by Elginsk8r
1. Click Here to Download the ROM
2. Click Here to Download HpTp_MAX, select All Files for this ROM
4. Click Here to download Google Open Apps
Select Platform ARM, Android 9 and the Variant you want, Pico is recommended
Click Here for detail information about the Pie ROM
________________________________________________________________
Dirty Unicorns v13 Android PIE by Flintman
1. Click Here to Download the ROM
2. Click Here to Download HpTp_MAX, select All Files for this ROM
4. Click Here to download Google Open Apps
Select Platform ARM, Android 9 and the Variant you want, Pico is recommended
Click Here for detail information about the Pie ROM
________________________________________________________________
Dirty Unicorns v8.1 Android Oreo by Flintman
1. Click Here to Download the ROM
2. Click Here to Download HpTp_MAX, select All Files for this ROM
4. Click Here to download Google Open Apps
Select Platform ARM, Android 8.1 and the Variant you want, Pico is recommended
Click Here for detail information about the Oreo ROM
________________________________________________________________
Evervolv 7.1.2 Android Nougat
1. Click Here to Download the ROM
2. Click Here to Download HpTp_MAX, select All Files for this ROM
4. Click Here to download Google Open Apps
Select Platform ARM, Android 7.1 and the Variant you want, Pico is recommended
Click Here for detail information about the Nougat ROM
________________________________________________________________
LineageOS 14.1 Android Nougat 7.1.2 by invisiblek
1. Click Here to Download the ROM
2. Click Here to Download HpTp_MAX, select All Files for this ROM
4. Click Here to download Google Open Apps
Select Platform ARM, Android 7.1 and the Variant you want, Pico is recommended
________________________________________________________________
CyanogenMod 12.1 Android Lollipop by Jcsullins
1. Click Here to Download the ROM
2. Click Here to Download HpTp_MAX, select All Files for this ROM
4. Click Here to download Google Open Apps
Select Platform ARM, Android 5.1 and only Pico
Click Here for detail information about the Lollipop ROM
________________________________________________________________
CyanogenMod 11 Android KitKat by Jcsullins
1. Click Here to Download the ROM
2. Click Here to Download HpTp_MAX, select All Files for this ROM
4. Click Here to download Google Open Apps
Select Platform ARM, Android 4.4 and only Pico
Click Here for detail information about the Kitkat ROM
________________________________________________________________
LineageOS 11 Android KitKat by Milaq November, 01 of 2019 Build
1. Click Here to Download the ROM
2. Click Here to Download HpTp_MAX, select All Files for this ROM
4. Click Here to download Google Open Apps
Select Platform ARM, Android 4.4 and only Pico
Click Here for detail information about the Kitkat ROM
________________________________________________________________
ROM Reducer
Click HERE for the Guide
2.Click HERE to Download, ROM Reducer is included in the All Files for each ROM.
________________________________________________________________
Universal Authority
Click HERE for the Guide
6. Click HERE for the Flash Files
________________________________________________________________
Flash the ToolBox 2015-01-08-v42 by jcsullins into /boot
________________________________________________________________
After successfully flashing any of the listed ROM the ToolBox can be flash into boot to maintain the battery.
Do NOT use the ToolBox to Resize or Repair Android Volumes.
If done it will corrupt all the Volumes ( Partitions ) and a PC with the Novacom driver must be use.
The ToolBox does not display the /swap partition, it was not created for that purpose.
Only after flashing all files from this guide the /boot partition has just enough space for the ToolBox.
7. Click Here to download all the files to flash the ToolBox to boot/
Flash_TPToolBox_v42_to_Boot.zip ( delete any splash *.tga images files and copy ToolBox into /boot )
Remove_TPToolBox_v42_from_Boot.zip ( delete the ToolBox from /boot )
If more than one ROM got flash and the ToolBox was not successfully copied to /boot then use this file:
Clean_Boot_Remove_All_ROM_Files.zip
It will create a back up of the boot files and clean /boot preserving the basic files, MoBoot and TWRP.
Then the Flash_TPToolBox_v42_to_Boot.zip can be flash.
Plus the Universal Optimize Swap Settings for the ROM installed in the Tablet.
The Universal Optimize Swap Settings copies the boot uImage for the ROM into /boot.
Keep all the downloaded files in the Micro SD card (USB Media) /external_sd ( it goes by all those names )
Any of the listed files can be flash any time and a PC is not required to maintain the battery of the Tablet.
Special Thanks to Jcsullins "The God Father of the HP Touchpad" for all the unique and great software that made it
possible to transition easily from WebOS to Android.
Click Here for my guide on How to unpack and repack the ToolBox
________________________________________________________________
/boot Partition Detail Information
________________________________________________________________
Code:
The boot partition was created with the basics to get everything working and provide
enough storage to accommodate:
TWRP/Recovery 3.2, each of the listed ROMs from Kitkat to Pie and the ToolBox.
The size of /boot is 32MB, is a fix size and can not be expanded.
Boot partition details after Automatic_Wipe_All:
Directories: size file name
bin 647.5k busybox
etc 16.1k lvm.conf
lib
lost+found
usr 1.2M lvm.static
Files: size
android.default.recovery 9 bytes
uImage 13 bytes (link to uImage.moboot )
uImage.moboot 63.8 K
uImage.Recovery 10.6 M
Total:
/dev/block/mmcblk0p13 size used available Use %
32.0M 14.1M 17.9M 44% /boot
A clean /boot has 17.9M of free space
Free Space After Pie ROM
/dev/block/mmcblk0p13
32.0M 20.8M 11.2M 65% /boot
The ToolBox is 11.2M
After flashing the ToolBox
/dev/block/mmcblk0p13
32.0M 31.6M 395.0K 99% /boot
There is only 395.0k available.
________________________________________________________________
HpTp Universal Optimize Swap Settings
________________________________________________________________
The following settings are applied to all listed ROMs and makes the Tablet work as a Laptop, not a phone.
All Developers have done a great job building the ROMs, if the same settings are apply then all performs very similar.
The hardware does not change and the basic requirements must be apply to all Android version.
There is nothing to add, but removed all the modules and only use the swap option.
The following features must be disable and can not be use:
Disable KSM, Low Memory Killer, CPU Boost, mpdecision
Changes in the Ramdisk:
The changes can be permanently modified using:
Click HERE to modify the Ramdisk
Not Permanent, Inside Android:
Click HERE to modify inside Android
File in the Ramdisk:fstab.tenderloin
Code:
/dev/store/swap none swap defaults swapprio=0, 0 0
File in the Ramdisk:init.rc
TCP Buffer increase to 6MB
Code:
on boot
# Define TCP buffer sizes for various networks
# ReadMin, ReadInitial, ReadMax, WriteMin, WriteInitial, WriteMax,
setprop net.tcp.buffersize.default 4194304,5242880,6291456,4194304,5242880,6291456
setprop net.tcp.buffersize.wifi 4194304,5242880,6291456,4194304,5242880,6291456
# Assign TCP buffer thresholds to be ceiling value of technology maximums
# Increased technology maximums should be reflected here.
write /proc/sys/net/core/rmem_max 6291456
write /proc/sys/net/core/wmem_max 6291456
extra_free_kbytes 20480
Code:
# system server cannot write to /proc/sys files,
# and chown/chmod does not work for /proc/sys/ entries.
# So proxy writes through init.
on property:sys.sysctl.extra_free_kbytes=*
write /proc/sys/vm/extra_free_kbytes 20480
# write /proc/sys/vm/extra_free_kbytes ${sys.sysctl.extra_free_kbytes}
File in the Ramdisk:Init.tenderloin.rc
Code:
on fs
# Enable swap partition
swapon_all /fstab.tenderloin
on property:sys.boot_completed=1
# Swap Partition Settings
write /proc/sys/vm/block_dump 0
write /proc/sys/vm/dirty_background_bytes 0
write /proc/sys/vm/dirty_background_ratio 10
write /proc/sys/vm/dirty_bytes 0
write /proc/sys/vm/dirty_expire_centisecs 600
write /proc/sys/vm/dirty_ratio 20
write /proc/sys/vm/dirty_writeback_centisecs 600
write /proc/sys/vm/drop_caches 3
# change in ramdisk init.rc write /proc/sys/vm/extra_free_kbytes 20480
write /proc/sys/vm/highmem_is_dirtyable 0
write /proc/sys/vm/laptop_mode 0
write /proc/sys/vm/legacy_va_layout 0
# write /proc/sys/vm/lowmem_reserve_ratio 32 32
write /proc/sys/vm/max_map_count 65530
write /proc/sys/vm/min_free_kbytes 40960
write /proc/sys/vm/min_free_order_shift 4
write /proc/sys/vm/mmap_min_addr 32768
write /proc/sys/vm/mmap_rnd_bits 16
write /proc/sys/vm/nr_pdflush_threads 0
write /proc/sys/vm/oom_dump_tasks 0
write /proc/sys/vm/oom_kill_allocating_task 1
write /proc/sys/vm/overcommit_memory 1
write /proc/sys/vm/overcommit_ratio 50
write /proc/sys/vm/page-cluster 8
write /proc/sys/vm/panic_on_oom 0
write /proc/sys/vm/percpu_pagelist_fraction 0
write /proc/sys/vm/scan_unevictable_pages 0
write /proc/sys/vm/stat_interval 1
write /proc/sys/vm/swappiness 100
write /proc/sys/vm/vfs_cache_pressure 100
# Increase readahead buffers on MMC devices
write /sys/block/mmcblk0/bdi/read_ahead_kb 0
# CPU Scaling
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 384000
write /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq 384000
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 1674000
write /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq 1674000
# Configure Performance
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor performance
write /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor performance
# Entropy
write /proc/sys/kernel/random/write_wakeup_threshold 2048
write /proc/sys/kernel/random/read_wakeup_threshold 1195
# I/O
write /sys/block/mmcblk0/queue/rq_affinity "0"
write /sys/block/mmcblk0/queue/scheduler "bfq"
________________________________________________________________
Disclaimer: I am not a developer, just a regular user like YOU that have found a way to improve the Tablet and would like others to benefit by sharing the information.
I am not the creator of any ROM, Recovery or App mentioned or used. All credits goes to the developers than have worked and provided the best ROMs there is for our Tablet and there are way too many to mentioned, but everyone know who they are! Thanks a lot to all of YOU (Developers for the HP Touchpad)!
Special Thanks:
@flintman for all his work creating TWRP Recovery and the many customs ROMs with the latest PIE.
@elginsk8r for developing and maintaining Evervolv ROMs, currently PIE.
* The stock Kernel has been modified to provide more RAM and a higher frequency.
Does seem pretty responsive, even though i have been downloading apps etc, to get it set up. I downloaded the Gapps as well not sure if that was mentioned in your post, but it will be necessary if you go with a clean install. With the DU 11/16 kernel couldnt get the play store to work. went back to the 6/18 and it worked but no videos would play...... so updated again to 11/16 and now both seem to be working ok. I think that could have been a problem with the initial ROMS, its been awhile so i cant remember but there were a few bugs there to work out as well. I will keep checking it out...
Thanks very much....much simpler
@ Touchie Pad,
Thanks for trying it out!
It will only work as intended by downloading the "Skz Kernel Optimize and Swap Partition enable" links provided.
It will not work at all by only downloading the ROM. The Dirty Unicorn ROM Kernel does not provide support for the swap file or optimized Android.
The proper Installation is:
1. Flash DU ROM "du_tenderloin-v12.5.3-20181116-0140-RC.zip" ( It has to be that in specific)
2. Flash one of the SKZ Kernel speed provided ( Without it, no optimization or use of the swap partition will happen"
3. You can install any Google Open Gapps, I have installed all version , please provide a link to the one that does not work for you and I will try it out!
4. If you want Root access you must install SuperSu and the SKZ Kernel allows System read and write ( is a complete open system)
Let me know if those were the steps you followed otherwise I will try to explain my instructions better!
Did the swap partition with the 2017.11.03 Evervolv build with nano Gapps and my tablet confuses me because it is so quick and responsive. Thank you HP_TOUCHPAD, shumash and everyone involved in making this happen.
Gborg3 said:
Did the swap partition with the 2017.11.03 Evervolv build with nano Gapps and my tablet confuses me because it is so quick and responsive. Thank you HP_TOUCHPAD, shumash and everyone involved in making this happen.
Click to expand...
Click to collapse
It is FAST and you can do a lot on it, mostly is all about the settings apply in Kernel and Ramdisk that makes the magic and giving Android OS room to breath by placing in swap unnecessary services not need it at the moment, instead of killing it and been limited to only 1GB of RAM, it can expand allocating a lot of memory to the active application. Once you close the App Android will clean up the RAM and load it from the swap file and everything goes back to normal. Android is the perfect OS for swapping.
Can you share which Kernel speed worked for you?
HP_TOUCHPAD said:
It is FAST and you can do a lot on it, mostly is all about the settings apply in Kernel and Ramdisk that makes the magic and giving Android OS room to breath by placing in swap unnecessary services not need it at the moment, instead of killing it and been limited to only 1GB of RAM, it can expand allocating a lot of memory to the active application. Once you close the App Android will clean up the RAM and load it from the swap file and everything goes back to normal. Android is the perfect OS for swapping.
Can you share which Kernel speed worked for you?
Click to expand...
Click to collapse
1782000 is what I flashed of the swap enabled kernel. That speed has been working well for me so I stuck with it. I am still using a few options in the L Speed app also. Nothing that contradicts the changes you have made. Just a few extra boosts and streamlining. The battery seems to drain more slowly also. I have not reflashed the A6 battery firmware since enabling swap and I expected the higher speed to drain more but everything is working great. No problems, no worries.
Gborg3 said:
1782000 is what I flashed of the swap enabled kernel. That speed has been working well for me so I stuck with it. I am still using a few options in the L Speed app also. Nothing that contradicts the changes you have made. Just a few extra boosts and streamlining. The battery seems to drain more slowly also. I have not reflashed the A6 battery firmware since enabling swap and I expected the higher speed to drain more but everything is working great. No problems, no worries.
Click to expand...
Click to collapse
Contrary to believe a higher speed will not drain your battery. By using this settings the Tablet will have an extremely power efficiency. A higher speed only means if the CPU needs power to run an App is not going to be limited by the governor, but when idle does not consume much power. The modules on the Kernel have been remove so there is no kernel workers checking on how much memory to clean and all that extra task that is not need it. If your tablet will run at 1836 you will see the big difference, but if you are using any App to improve anything you are not going to see the full potential benefit. All those apps are only setting things up that are already set and working in the background slowing things down. None of them are need it, this is been run as a Tablet mode setting not a Phone.
HP_TOUCHPAD said:
@ Touchie Pad,
Thanks for trying it out!
It will only work as intended by downloading the "Skz Kernel Optimize and Swap Partition enable" links provided.
It will not work at all by only downloading the ROM. The Dirty Unicorn ROM Kernel does not provide support for the swap file or optimized Android.
The proper Installation is:
1. Flash DU ROM "du_tenderloin-v12.5.3-20181116-0140-RC.zip" ( It has to be that in specific)
2. Flash one of the SKZ Kernel speed provided ( Without it, no optimization or use of the swap partition will happen"
3. You can install any Google Open Gapps, I have installed all version , please provide a link to the one that does not work for you and I will try it out!
4. If you want Root access you must install SuperSu and the SKZ Kernel allows System read and write ( is a complete open system)
Let me know if those were the steps you followed otherwise I will try to explain my instructions better![/QUOTE
I did it in that order...used pico and micro, also had the problem with the AOSP keyboard stopping which i remember having when i first flashed the ROMS. I flashed the 183 kernel..... works fast but i did have a reboot on the second day and the screen was just dark, rebooted a couple times and then reflashed the rom, and optimize, and super su files ......and all is up and running again. I was seeing -220ma drain up until i reflashed it. I will give it some more time to sort it all out, and play around with it a bit. The video playing is 1,000,000,000 times better, i love it, thanks a lot
Click to expand...
Click to collapse
Touchie Pad said:
HP_TOUCHPAD said:
@ Touchie Pad,
Thanks for trying it out!
It will only work as intended by downloading the "Skz Kernel Optimize and Swap Partition enable" links provided.
It will not work at all by only downloading the ROM. The Dirty Unicorn ROM Kernel does not provide support for the swap file or optimized Android.
The proper Installation is:
1. Flash DU ROM "du_tenderloin-v12.5.3-20181116-0140-RC.zip" ( It has to be that in specific)
All the testing that I have done and prove to be stable is on that version, I can only recommend what I have tested.
2. Flash one of the SKZ Kernel speed provided ( Without it, no optimization or use of the swap partition will happen"
All the settings are on the Kernel and Ramdisk (the boot image) no settings are on any ROM. If that Kernel is not apply no performance will happen it will be worse.
3. You can install any Google Open Gapps, I have installed all version , please provide a link to the one that does not work for you and I will try it out!
4. If you want Root access you must install SuperSu and the SKZ Kernel allows System read and write ( is a complete open system)
Let me know if those were the steps you followed otherwise I will try to explain my instructions better![/QUOTE
I did it in that order...used pico and micro, also had the problem with the AOSP keyboard stopping
Yes you are correct the Keyboard stops working in most of the ROM that is why I recommend it to install the FULL Google open Apps because, it will replace the stock Keyboard with the one original from google.
The issues has been around for as long as I can remember. The only way around is to flash another keyboard after installing pico and micro or you can do it manually. I do not know if I am allow to distribute google keyboard as a separte flash-able zip file, that will resolve the issue and all open gapps will work.
which i
remember having when i first flashed the ROMS. I flashed the 183 kernel..... works fast but i did have a reboot on the second day and the screen was just dark, rebooted a couple times and then reflashed the rom, and optimize, and super su files ......and all is up and running again. I was seeing -220ma drain up until i reflashed it.
If your tablet reboots at 1836, it may not be able to sustain that speed and it will be better to go for 1782, you will still be able to do the same. The CPU does not work at that speed all the time, only if it needs to and the cap is at 1836, but if stays that high and your CPU can not handle it then it will reboot, but others can maintain it.
I will give it some more time to sort it all out, and play around with it a bit. The video playing is 1,000,000,000 times better, i love it, thanks a lot
Click to expand...
Click to collapse
You will be able to play videos in HD 720 using youtube app and also the web browser. I use Opera as is easy to change to desktop mode and play music with the screen off. It can play for days none stop and no reboots, you can watch movies back to back a HD 720 no issues and will never close down or reboots, that is why the use of the swap file as an extra space to allocate memory resources.
But the most important do not install any app to optimize anything, it will make it worse, all the Kernel modules have been removed, there is nothing an app can do, just work in the background and make things worse.
It is set up to run as your PC or Laptop not as your Phone, that is the difference!
Click to expand...
Click to collapse
@HP_TOUCHPAD I have flashed the 1836000 swap optimized kernel and left things as they are. Interactive BFQ the preferred setup for best performance? In the Toolbox I have set it just below performance with dynamic scaling as well. This TouchPad functions like a tesseract now. Speed of light? Bwahahaha, that is nothing compared to this.
I did it in that order...used pico and micro, also had the problem with the AOSP keyboard stopping which i remember having when i first flashed the ROMS. I flashed the 183 kernel..... works fast but i did have a reboot on the second day and the screen was just dark, rebooted a couple times and then reflashed the rom, and optimize, and super su files ......and all is up and running again. I was seeing -220ma drain up until i reflashed it. I will give it some more time to sort it all out, and play around with it a bit. The video playing is 1,000,000,000 times better, i love it, thanks a lot[/QUOTE]
I updated the guide and added the Keyboard Flash file to be use with Pico and Micro and the others. My advice, if you want the Tablet to run smooth fast and stable, flash all those files in that specific order and everything will work as a brand new device.
Gborg3 said:
@HP_TOUCHPAD I have flashed the 1836000 swap optimized kernel and left things as they are. Interactive BFQ the preferred setup for best performance? In the Toolbox I have set it just below performance with dynamic scaling as well. This TouchPad functions like a tesseract now. Speed of light? Bwahahaha, that is nothing compared to this.
Click to expand...
Click to collapse
I know that is very contradicting after been accustom to use apps to get better performance, but with this set up none can be use.
The Kernel modules have been removed, there is nothing an app can do, it may even make the system unstable and worse.
The best is to disable the ToolBox in Evervolv. Is best to completely disable any background tune performance app. There is only two Governors Interactive and performance.
Is set to interactive by default it scales perfectly, no app is need it for that to happen is control my a kernel module.
Keep the system lean and simple you will get the best performance and efficiency. There is nothing to do, just don't install bloatware that will use resources without you knowing and creating lag.
HP_TOUCHPAD said:
I know that is very contradicting after been accustom to use apps to get better performance, but with this set up none can be use.
The Kernel modules have been removed, there is nothing an app can do, it may even make the system unstable and worse.
The best is to disable the ToolBox in Evervolv. Is best to completely disable any background tune performance app. There is only two Governors Interactive and performance.
Is set to interactive by default it scales perfectly, no app is need it for that to happen is control my a kernel module.
Keep the system lean and simple you will get the best performance and efficiency. There is nothing to do, just don't install bloatware that will use resources without you knowing and creating lag.
Click to expand...
Click to collapse
I am following your advice and doing as you say. Lean, simple and set to run fast has Android N running as well as kitkat did. Thank you very much @HP_TOUCHPAD
hello everyone! how does this swap thing influence flash storage? Will it degrade much faster using this way?
[/COLOR]
HepCat86 said:
hello everyone! how does this swap thing influence flash storage? Will it degrade much faster using this way?
Click to expand...
Click to collapse
With this age device and a swap partition in the flash memory being used often, it will likely degrade somewhat faster. No guarantee or prediction of how much faster because all devices behave differently. Think along the line how different TouchPads can functionally use different max processor speeds. You can have a quick and functional TouchPad that will degrade faster or one that is usable for almost nothing.
Great tutorial dude. Thanks !
Waiting to reboot after flashing rom/gapps/keyboard/kernel/su right now..
HepCat86 said:
hello everyone! how does this swap thing influence flash storage? Will it degrade much faster using this way?
Click to expand...
Click to collapse
I updated the guide with a short statement. I want to make things very easy and quick to follow but the problem is that there are more Taboo to dismantle than the settings itself.
I will try to explain in in here:
A swap file is created by default in all modern Linux installation. There is nothing new about this and everyone that has ever owned a PC knows about it.
Swapping only takes place when the system requires more memory than is physically available.
Any time you would like to see how much memory Android is using type this in on PC using adb shell or in terminal in Android:
free -h
This is Dirty Unicorns with basic ROM installed:
Code:
[email protected]:~$ adb shell
[email protected]:/ # free -h
total used free shared buffers
Mem: 828M 574M 254M 0 5.4M
-/+ buffers/cache: 568M 260M
Swap: 504M 0 504M
Is the basic ROM nothing installed.
This is Dirty Unicorn installed with Micro gapps as the guide:
Code:
[email protected]:/ # free -h
total used free shared buffers
Mem: 828M 804M 24M 0 8.9M
-/+ buffers/cache: 795M 33M
Swap: 504M 16M 488M
There is 16MB used in swap, because the system is set up to 60% swapping.
Android is the King of swapping, it does it all the time. Is not a true multitasking OS, it places background Apps in hibernation, temporally storage. Then when active it pick ups where it was left, it gets awake. The swap file is the perfect place to place anything that the user is not using at the moment and then load it later. It is not going to be use to be running the OS, it will be extremely slow to run Android or any App directly from swap space. Is only use to free RAM to run Apps and make the system stable instead of killing services and process.
The swap will help all the components by making the CPU, RAM and storage work less. To keep Android alive with only 1 GB or RAM the CPU has a lot of overhead and the RAM is been constantly in use. For example zRAM, compress Memory for swapping. The CPU has to compress and uncompressed everything that is going into zRAM plus the RAM is constantly been used with read and writes, none stop.
Is the other way around with swap, what is not need it is place there, nothing else is working , all at rest!
Hopefully this explain a little is the basic!
Steelskinz said:
Great tutorial dude. Thanks !
Waiting to reboot after flashing rom/gapps/keyboard/kernel/su right now..
Click to expand...
Click to collapse
You are welcome, but the only way to find out if the tutorial is set up properly is if the user can achieved the results.
Otherwise something got lost in the translation, hopefully it worked for you with no issues.
Update:
The Keyboard zip files got updated today February 23, to completely removed the LatinIME directory and then recreated again and copy all files the files from google Open Gapps Keyboard.
Pico works great now, it will be best to install the minimum and add Apps as you need.
The computer I used somehow deleted most of what I backed up from my TouchPad. It kept the TWRP backup of /boot in existence. For anyone with ample use and data on theirs this could aggravating but it caused me to do a cleaner clean install. I did not remember which apps I had on mine so I now have less than 80 total apps on mine and after flashing the full wipe zip and the swap partition creation zip I restored my backup of /boot so I had a TouchPad Toolbox uImage available in moboot and a spectacularly quickly performing tablet. Minimizing excess like this made my TouchPad as quick and responsive as the new iPad one of my roommates recently got.
I have one suggestion and one question -
Setup instructions for swap will be more understandable if accompanied by full written step-by-step instructions.
What are your thoughts on the effects of setting the number of background processes maximum to one or two after boot?
Swap allows for more to be done without lagging but these are still 8 year old tablets so I am curious about the expert opinions. @HP_TOUCHPAD and @shumash
It would be helpful to hear both of your thoughts on this matter.
Gborg3 said:
The computer I used somehow deleted most of what I backed up from my TouchPad. It kept the TWRP backup of /boot in existence.
When you back up the tablet using TWRP, you have to select the partitions /System and /Data. Boot is not necessary at all and you do not want to back up or restore boot in this case as it will restore LVM old configuration files. That is the reason that this guides wipes and reformat /boot and places TWRP on it.
For anyone with ample use and data on theirs this could aggravating but it caused me to do a cleaner clean install.
A clean install is the best option to do, there are Apps that will back up only the Apps if you do not use the Play Store
I did not remember which apps I had on mine so I now have less than 80 total apps on mine and after flashing the full wipe zip and the swap partition creation zip I restored my backup of /boot so I had a TouchPad Toolbox uImage available in moboot and a spectacularly quickly performing tablet.
After you do apply the Full wipe zip flash file it is not a good idea at all to restore /boot, and there is no need.
Boot keeps the uImages of the ROM and LVM ( storage partition configuration and size ). It could keep the old partition layout, I have not tried that myself.
Minimizing excess like this made my TouchPad as quick and responsive as the new iPad one of my roommates recently got.
The less Apps you have or keep it to what you really needs, the faster the Tablet will be. This apply to any computer. The worse is to have bloatware, most run in the background or create process that keeps the CPU working most of the time.
I have one suggestion and one question -
Setup instructions for swap will be more understandable if accompanied by full written step-by-step instructions.
What area do you think that must be written better?
1. How to back up and restore.
2. Or the process to flash the Wipe_ALL zip flash file.
What are your thoughts on the effects of setting the number of background processes maximum to one or two after boot?
The background process limit that you can setup under Developers options is how many Apps Android will keep in pause (hibernation), when you open another app, it has nothing to do with process that are launch to collect data or updates. Those are terminal commands to apply to each specifically installed Apps to prevent it from activating its data collection. Keep in mind Android and many Apps are free, but in exchange off data mining.
Swap allows for more to be done without lagging but these are still 8 year old tablets so I am curious about the expert opinions. @HP_TOUCHPAD and @shumash
It would be helpful to hear both of your thoughts on this matter.
Click to expand...
Click to collapse
Can you provide the link to the experts options? """ Corrections , Gborg3 said opinions my brain captured options """" This is a great example when humans interact!
All the flash files on provided on this guide will apply all the settings that any expert can do by entering line y line in a terminal window.
The tablet is old but the basic of streaming HD video, using the Web, running Apps, all that can be done as with any other device. The most important is to have the most current ROM and the open gapps installed.
crDroid 6.2 ROM 15-01-2020
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA before!
Make sure you have a custom recovery installed (TWRP is the preferred recovery. [I'm not using Fox recovery, I'm not going to give you advice.])
Boot into recovery
Wipe data, cache partitions to clean install. Wipe dalvik, cache to update previous crDroid.
(If your /data partition secured, maybe need format /data if you want to use this ROM.)
Flash Rom in TWRP (sideload or copy any storage)
Flash OpenGapps (Optional) [I'm not using GAPPS, I'm not going to give you advice.]
Flash Magisk Root (Optional) [I'm not using Magisk, I'm not going to give you advice.]
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 1 minute.
DOWNLOAD SF
DOWNLOAD AD
All ROMs here: LINK
Known issues: don't know
*
Screenshots: LINK
OS source: LINK Many thanks to adi153!
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.18.140 (not my work)
ROM info: Q10 Lineage-17.1, system_root partition, Android quota removed (easier to go back to earlier 7.x-9.x ROMs).
If you have previously used Android 9.x or 10.x ROM which has a quota set on the data partition, you can remove the quota in TWRP, and not need format the data partition (this method tested, working was for me, but no guarantee for by all means)
commands:
Code:
tune2fs -O ^quota /dev/block/bootdevice/by-name/userdata
tune2fs -Q ^usrquota,^grpquota /dev/block/bootdevice/by-name/userdata
If you then use a ROM that configures quota (fstab.qcom), you can start over, if do not want quota. Or cleaning from fstab: "quota".
Created 24-12-2019 6.0 version
Last Updated 15-01-2020 6.2 (build3)
I am not aware that it contains malicious code in the ROM, I have never put it in. This is a ported ROM, all its elements come from the Internet.
You're welcome.
New build 15.01.2020, & many changes to the system. I'd like to get feedback on whether VOLTE is working? Thanks.
SYS update V1 out: 14-01-2020
Something wrong with the system updates, I moved it to the test directory.
Nice
Wow, a new rom... Thanks szanalmas, will give feedback after testing it
@szanalmas
Edit: Already tested your rom, so stable and smooth...
But found some small bug (doesn't really matter anyway but you may need know):
-At first boot/crdroid setup wizard, email exchange request permission but when i grant it permission manager crash (but back normal after that)
-When i change the hardware button function to screenshot... The Setting app will crash and back to main menu
Just that, still looking for other
Big thanks again for this nice rom
(Sorry for my bad english :v)
@szanalmas thanks ...for stable ROM.
---------- Post added at 04:18 AM ---------- Previous post was at 04:00 AM ----------
From long time i was waiting for stable ROM. Thanks for your hard work.
@szanalmas thanks for make stable ROM :good:
while there are no bugs,
if there are bugs
I'll tell you later
thanks man i like crdroid
rom stable smooth did not find any bug after 2 hours use
Fadly357 said:
But found some small bug (doesn't really matter anyway but you may need know):
-At first boot/crdroid setup wizard, email exchange request permission but when i grant it permission manager crash (but back normal after that)
-When i change the hardware button function to screenshot... The Setting app will crash and back to main menu
Click to expand...
Click to collapse
Thanks for the feedback!
I didn't know about the first bug, probably because I have always denied email permissions in the wizard. I have bad habits!
I knew about the second bug, some of the function settings on the buttons don't work.
Unfortunately, these bugs are in the official ROM, but I think they will be fixed over time.
And of course, the SD card camera and gallery permission bugs have remained, but the solution is to use internal storage for the time being.
szanalmas said:
Thanks for the feedback!
I didn't know about the first bug, probably because I have always denied email permissions in the wizard. I have bad habits!
I knew about the second bug, some of the function settings on the buttons don't work.
Unfortunately, these bugs are in the official ROM, but I think they will be fixed over time.
And of course, the SD card camera and gallery permission bugs have remained, but the solution is to use internal storage for the time being.
Click to expand...
Click to collapse
Okay, will tell you as soon as possible if i found other
could you teach me rom build? i wanna learn and help
@szanalmas
About your ported TWRP, can you install magisk? When i use your TWRP to install magisk, the magisk installation failed, says it can mount vendor which is same as cust, right?
viethoang18 said:
could you teach me rom build? i wanna learn and help
Click to expand...
Click to collapse
Sorry I can't give you guidance. I'm not building ROM, I'm just porting. If you really want to build ROM, I recommend the ViperOS developers, this was the only Official build for this phone (7.1.2). Building a ROM requires 3 things, the kernel, vendor, and AOSP. Since phone manufacturers largely do not make their source code public, their construction is tremendously laborious and time consuming.
If you want to port, it is highly recommended that you know Linux, which is quite a bit of time and energy. Actually, you need to learn the basics of linux for Android, but at least to the point where you can already interpret log error messages.
I don't know if you use linux, if you don't and you want to start with it, install linux, configure it well, and compile a linux kernel for ugglite, which starts with ROM 10. If you want to go hard, thoroughly, and deeper, do it all without installing a linux graphical interface. I don't really know how much time it takes to easily manage Linux. How to port Android 10 on windows I don't know, but I think it's not easy.
And on top of that, Android has some specific changes that are different from the Linux system, so you also have to get to know Android so.
And now we're just about to boot on Linux based Android, on the DalvikVM running applications is another world with lots of Java code.
For all this, there is no guide to doing this or that, you need to apply knowledge in a complex way.
I only do this on a hobby level.
Fadly357 said:
@szanalmas
About your ported TWRP, can you install magisk? When i use your TWRP to install magisk, the magisk installation failed, says it can mount vendor which is same as cust, right?
Click to expand...
Click to collapse
I once used the magisk in TWRP but not this ROM. It worked for some.
But I didn't write in my post on my TWRP either now.
(I don't use magisk now.)
Use Canary: LINK
Or whatever.
szanalmas said:
Sorry I can't give you guidance. I'm not building ROM, I'm just porting. If you really want to build ROM, I recommend the ViperOS developers, this was the only Official build for this phone (7.1.2). Building a ROM requires 3 things, the kernel, vendor, and AOSP. Since phone manufacturers largely do not make their source code public, their construction is tremendously laborious and time consuming.
If you want to port, it is highly recommended that you know Linux, which is quite a bit of time and energy. Actually, you need to learn the basics of linux for Android, but at least to the point where you can already interpret log error messages.
I don't know if you use linux, if you don't and you want to start with it, install linux, configure it well, and compile a linux kernel for ugglite, which starts with ROM 10. If you want to go hard, thoroughly, and deeper, do it all without installing a linux graphical interface. I don't really know how much time it takes to easily manage Linux. How to port Android 10 on windows I don't know, but I think it's not easy.
And on top of that, Android has some specific changes that are different from the Linux system, so you also have to get to know Android so.
And now we're just about to boot on Linux based Android, on the DalvikVM running applications is another world with lots of Java code.
For all this, there is no guide to doing this or that, you need to apply knowledge in a complex way.
I only do this on a hobby level.
Click to expand...
Click to collapse
can i use Unbutu wls on windows ?
@szanalmas I flashed this ROM.
ULTRA SMOOTH... NO SERIOUS BUG, SOMETIMES AUTO BRIGHTNESS RESPONSE SLOWLY. Suddenly high brightness automatically. Another issue with attached sd card asking for format.
"Issue with sandisk SD Card"
Its for daily use is ok.
bug, when enabling ambient display d2tw stopped not wroking after disable ambient dt2w work again
Thank you very much feedbacks and thanks to everyone! :good:
Call volume on speaker is very high by default
@szanalmas Call volume on speaker is very high by default. Please set lower level by default. I hope in new build it willbe resolve.
Thanks...
ahmedhelmy71 said:
bug, when enabling ambient display d2tw stopped not wroking after disable ambient dt2w work again
Click to expand...
Click to collapse
This is what LINK is all about, and I still hold that the double-tap feature cannot be used for two things at once. What's interesting is that I can't find the ambient display double-tap menu option, and there's a separate one in Havoc ambient settings.
This is also an Official bug unfortunately.
*
cpglbitm said:
@szanalmas I flashed this ROM.
ULTRA SMOOTH... NO SERIOUS BUG, SOMETIMES AUTO BRIGHTNESS RESPONSE SLOWLY. Suddenly high brightness automatically. Another issue with attached sd card asking for format.
"Issue with sandisk SD Card"
Its for daily use is ok.
Click to expand...
Click to collapse
The SD card problem is very-very interesting.
What filesystem is in sd card?
Could you send us a logcat digest right after the phone is started?
Code:
adb logcat | grep vold > sdcardproblem.txt
viethoang18 said:
can i use Unbutu wls on windows ?
Click to expand...
Click to collapse
I don't know. I haven't used Windows for years, sorry.