Related
Mupen64plus-AE
Hi I just wanted to give some attention to the new open source
n64 emulator for android Mupen64plus-AE which was developed by Paul Lamb.
Its currently in its beta testing phase and it would be awesome if other developers wanted to join in and contribute to the project.
Android market link:
https://market.android.com/developer?pub=Paul+Lamb
Heres a link to the latest build + source code:
http://www.paulscode.com/forum/index.php?board=11.0
[This is currently the only emulator for android with xperia touch pad support]
Here is an overview of the emulator:
Here is a comparison video of banjo-tooie running on n64oid and mupen64plus-ae:
Here is an extra video I made of the xperia play touch pads working with the emulator:
Common questions
The GUI is now finished so most of this information is now irrelevant
How do I map the gamepad buttons?
First, install and run the "SDL Scancode Finder" linked below. Press the keys you want to map, and write down the Scancodes that are displayed. Then after running Mupen64Plus AE at least once, close the app and edit the file [sdcard]/app-data/paulscode.android.mupen64plus/data/InputAutoCfg.ini. Under the [Keyboard] section, enter the scancodes that you wrote down earlier. For the analog stick, use the scancodes for the left and right buttons for "X Axis", and the scancodes for the up and down buttons for "Y Axis". Finally, save the file and restart the emulator.
SDL Scancode Finder:http://www.paulscode.com/source/AndroidSDLScancodeFinder/ScancodeFinder-debug.apk
Alternatively you use my control config and just paste is over the file. Just replace [sdcard]/app-data/paulscode.android.mupen64plus/data/InputAutoCfg.ini with the custom version of the InputAutoCfg.ini
Heres my config: http://dl.dropbox.com/u/13594612/paulscode/InputAutoCfg.ini (right click and save as)
How do I change games?
Delete or rename the file [sdcard]/app-data/paulscode.android.mupen64plus/roms/mario.n64. Place the ROM you wish to play into that directory, and call it "mario.n64" (it doesn't matter what format the ROM is in, just call it "mario.n64", and the emulator will load it instead of Mario64).
How do I remove the touch control overlay?
Go to [sdcard]/app-data/paulscode.android.mupen64plus/skins and delete everything in there except the folder called touchpads, the touch pads folder it what lets you use the xperia play touch pads.
Click to expand...
Click to collapse
*I take no credit in the creation of this emulator all credit goes to Paul and the people behind the original Mupen64plus source code. Im just a tester nothing more haha*
that'd be cool, but even cooler if N64oid got it
Nhialor said:
that'd be cool, but even cooler if N64oid got it
Click to expand...
Click to collapse
N64oid probably never will though. Adding touch pad support cuts of every android device
that has a firmware lower than 2.3 and thats alot of devices.
With Mupen64plus-ae multiple builds can be made so it doesn't effect other devices.
Thats why I feel so strongly that developers should help support this project,
it means that developers can add whatever they want and can create device specific features.
I would love to see this with touchpad support. Waht do you guess how long will it take?
IE-coRe said:
I would love to see this with touchpad support. Waht do you guess how long will it take?
Click to expand...
Click to collapse
Touch pad support is nearly done, my best guess it will either be finished by tomorrow or in a few days. Also just to clarify I am not the one making this emulator.
This the latest build for non qualcomm devices: http://www.paulscode.com/source/Mupen64Plus-AE/13SEP2011/Mupen64Plus-debug.apk
This is the latest build for qualcomm devices (like the xperia play: http://www.paulscode.com/source/Mupen64Plus-AE/13SEP2011/Mupen64Plus-debug-sortProblem.apk
The xperia play version has very bad graphics at the moment but paul is working on fixing that atm.
You mean Paul as in Paul O'Brien, Modaco's overlord and programmer extraordinaire?
Logseman said:
You mean Paul as in Paul O'Brien, Modaco's overlord and programmer extraordinaire?
Click to expand...
Click to collapse
No the full name of the Paul who is making the emulator is Paul Lamb
Rockin'
Sent from my R800x using xda premium
P.s. I can't wait for this to come to fruition. Finally! A viable way to play Duke Nukem
What are you talking about? Google made it so that multiple versions of the same apk can be uploaded to the market under the same heading, so adding it for our device would therefore NOT rule out other phones, as they could just download the regular version (our version wouldn't be able to be seen by them), also, as a computer science major, it'd be easy to not have this problem if he doesn't want to go down this road, he could do, for arguments sake, if build.prop=="R800i"|"R800x"{control-type="touchpad"}else{control-type="regular"}, or even just a tick box in the option menu...!
therefore avoiding the problem. Obviously it goes a lot deaper than that, but saying that adding support for us would rule out other devices is just not true. It's something else that's stopping him.
Nhialor said:
What are you talking about? Google made it so that multiple versions of the same apk can be uploaded to the market under the same heading, so adding it for our device would therefore NOT rule out other phones, as they could just download the regular version (our version wouldn't be able to be seen by them), also, as a computer science major, it'd be easy to not have this problem if he doesn't want to go down this road, he could do, for arguments sake, if build.prop=="R800i"|"R800x"{control-type="touchpad"}else{control-type="regular"}, or even just a tick box in the option menu...!
therefore avoiding the problem. Obviously it goes a lot deaper than that, but saying that adding support for us would rule out other devices is just not true. It's something else that's stopping him.
Click to expand...
Click to collapse
Well If you actually knew anything about n64oid you would know that its not even on the android market. Its distributed via slideme which does not support uploading of multiple apk's for a single app.
And ive talked to alot of emulator developers and for some reason (Im not entirely sure why) Including touch pad support cuts off support for older versions (lower than 2.3).
bubblegumballon said:
Well If you actually knew anything about n64oid you would know that its not even on the android market. Its distributed via slideme which does not support uploading of multiple apk's for a single app.
And ive talked to alot of emulator developers and for some reason (Im not entirely sure why) Including touch pad support cuts off support for older versions (lower than 2.3).
Click to expand...
Click to collapse
haha ,completly forgot about that, but still, u see my point about the proper implemantation?
EDIT: Wait, I remember something that either Yonghz or Shtruck said something like the classes needed for this are unaccesible for Froyo and before or something, so you may be right. Apologies
Nhialor said:
haha ,completly forgot about that, but still, u see my point about the proper implemantation?
EDIT: Wait, I remember something that either Yonghz or Shtruck said something like the classes needed for this are unaccesible for Froyo and before or something, so you may be right. Apologies
Click to expand...
Click to collapse
No problem and Im sure ive seen Shtruck say something along those lines on the fpsece forums
I would imagine they would be able to add backwards compatibility after adding touch pad support, but that would take extra time - which they may not be willing to give the time.
hairdewx said:
I would imagine they would be able to add backwards compatibility after adding touch pad support, but that would take extra time - which they may not be willing to give the time.
Click to expand...
Click to collapse
Im not sure what you mean by backwards compatibility but in the future arm6 devices will be supported as well.
Also touch pads are in the process of being added, in the newest build the touchpad overlay has been added to the screen and different layouts have been made for different screen sizes (phone, tablet, small screens etc).
bubblegumballon said:
Im not sure what you mean by backwards compatibility but in the future arm6 devices will be supported as well.
Also touch pads are in the process of being added, in the newest build the touchpad overlay has been added to the screen and different layouts have been made for different screen sizes (phone, tablet, small screens etc).
Click to expand...
Click to collapse
I meant having N64oid, FPSE, etc. detect the android version and run version specific code to add touch pad support while avoiding the compatibility issues.
I have done that before in software (I am a software engineer for a living) but it takes a long time to do and adds extra things to support. I certainly would not be motivated enough to do that either
hairdewx said:
I meant having N64oid, FPSE, etc. detect the android version and run version specific code to add touch pad support while avoiding the compatibility issues.
I have done that before in software (I am a software engineer for a living) but it takes a long time to do and adds extra things to support. I certainly would not be motivated enough to do that either
Click to expand...
Click to collapse
Im no emulation programmer but alot of emulator developers have said the same thing that implementing the touch pad controls limits it to 2.3+
Im sure if somebody was brainy enough to create an emulator then they would know how to support more versions if it were possible.
also I would like to point out that Mupen64plus-ae supports arm6, It was already implemented but I forgot to update my post.
bubblegumballon said:
Im no emulation programmer but alot of emulator developers have said the same thing that implementing the touch pad controls limits it to 2.3+
Im sure if somebody was brainy enough to create an emulator then they would know how to support more versions if it were possible.
also I would like to point out that Mupen64plus-ae supports arm6, It was already implemented but I forgot to update my post.
Click to expand...
Click to collapse
Touch pads limit it to 2.3+ because of some of the classes and available system calls it needs are only in 2.3+.
But that doesn't mean it's impossible to make one apk support all android versions, just very impractical implementation-wise and probably not worth it.
hairdewx said:
Touch pads limit it to 2.3+ because of some of the classes and available system calls it needs are only in 2.3+.
But that doesn't mean it's impossible to make one apk support all android versions, just very impractical implementation-wise and probably not worth it.
Click to expand...
Click to collapse
The project is open source so anybody (with the right knowledge) could just go and add touch pad support if they wanted.
Also I would like to point out touch screen controls have now been added but they are still not finished, there are still a few more things to be added like a moving analog stick and lots of optimisations so dont expect it to be perfect just yet.
Mupen64plus-ae now works properly on adreno GPU's (qualcomm chipsets)
It works great on my xperia play! keep in mind that its still not finished yet.
bubblegumballon said:
Mupen64plus-ae now works properly on adreno GPU's (qualcomm chipsets)
It works great on my xperia play! keep in mind that its still not finished yet.
Click to expand...
Click to collapse
did you use the first apk or the "qualcomm" apk?
because Im trying the second apk and its not letting me download the data from paulscode.com...
any help would be appreciated
Valcho said:
You know how Flipboard was exclusive only to the Galaxy S III? Sure, you can stand in line and wait for the official launch for the Android app, but since we are all buddies here...
It's simple, I just had a Galaxy S III lying around and I extracted the .apk using AirDroid. So, there you go.
Woot! My favorite site has covered me - http://blog.gsmarena.com/flipboard-...gs-cool-news-feeds-to-non-galaxy-s-iii-users/
About the S Voice, I no longer have the phone with me. But I'll try my best to get it again and extract everything you guys have asked for. Stay tuned.
edit : how to create account : http://forum.xda-developers.com/showpost.php?p=25871282&postcount=141
edit 2 : for working widget install app in internal storage (not on sdcard)
UPDATE: GET THE LATEST VERSION!
Click to expand...
Click to collapse
Thanks Valcho
Download:
Code:
http://forum.xda-developers.com/showthread.php?t=1644212
Works fine with Longhorn v2.7 Red rom.
I just don't get it
Thank you for the info about the android version of flipboard. I just don't get why people will choose this sort of software over a solid rss-feedreader.
The only advantage I could find is the eye-candy with that flip effect. But the downside is much more severe:
* works only in portrait, no landscape
* doesn't remember which articles I've read, and which are new to me
* can't import my opml-feedlist, I can't even use my own rss-feeds.
* need an account at their side to 'manage' my sources
* collects some data about my device (even the device-id)
* in german papers the picture and the text often don't match
* need a lot of space in /sdcard/Android
* prioritise articles high that doesn't interest me
It took me half a day to remove google-analytics, flurry, hockey and some other crap-library that counts every click I make in this spyware.
All in all I think this software is just another instagram. Some glorified little value software, only apple-users can be excited about.
Similar to my TWRP / Multirom thread, this is temporary until xda decides to add this device to the dev db list. A few comments and a known issues list will be all in this post. Please report any and all problems you find. This is still very early in the development process.
NOTES:
This will only install using my TWRP build here because I'm have to do some hacky things to support a unified build. I may eventually find a cleaner method.
This doesn't yet contain my attempt at controller pairing. The framework patches are there, but not the apk. It will be tested and included in later builds. Wifi doesn't work, so pairing wouldn't work anyways.
I had to use aosp libs to make this boot, which is different from my Portable and Tablet releases. The hdcp libs seems to be very different, so I have no idea if 4k works at all and I seriously doubt youtube and netflix drm will verify correctly.
You will have to wipe data to install this, make a backup first. Do note this is just /data, not the entire internal sd.
KNOWN ISSUES:
Wireless controller pairing not implemented
No audio over hdmi (so, no audio at all)
SOURCE:
device
kernel
vendor
CURRENT RELEASE:
cm-13.0-20160224-UNOFFICIAL-foster.zip
OLD RELEASES:
cm-12.1-20150819-UNOFFICIAL-foster.zip
cm-12.1-20150720-UNOFFICIAL-foster.zip
cm-12.1-20150709-UNOFFICIAL-foster.zip
missing default android keyboard?
installs fine boots into CM - displaying in 1080p on my monitor just fine.
missing android keyboard.
works fine with usb keyboard (logitech k400r)
amazon app store installs fine, recognizes all apps - minecraft PE crashes on start
touch pad / mouse freezes intermittently
netflix installs but does not play
great start, looking good.
I'm finding all kinds of interesting things working on this... Well, I got the stock libs 'working'. HDCP (or something in the graphics stack) locks up the system on boot when using a custom built kernel. From within CM or even from Nvidia's aosp tree. It will only boot with the kernel pulled out of an official boot image. I compared the ikconfig out of the official kernel with what I'm building in CM and they match. So, I'm kinda lost as to what black magic is at work here... Is something doing a crc check? Is there black box GPL violations in the stock kernel? I don't know. And I had a custom kernel booting stock when I was first trying multirom stuff. So that makes me *really* confused. For the moment, I've disabled kernel compiles in my device tree and I'm shipping a blob kernel. And I hate doing that.
Haven't looked at the missing keyboard yet.
Wifi is closer, but still not there. The wlan0 interface seems to init, but the p2p interface fails and brings it immediately back down. I'll do some more research into that over the weekend.
The screen flickers at times. Don't know why, but I think I saw some system props that affects the screen drawing on stock, once I find those again I should be able to fix that.
The OMX libs work now. Which means game streaming works. I tested a grid game already. Don't have Windows, so I can't test local streaming. And theoretically the aforementioned Netflix problem should be fixed by this as well.
I'm kicking off a build to run overnight (takes 4+ hours for a clean release build [on a AMD FX 9370, no less]), so I should have this stuff up first thing tomorrow morning (pending life (r)).
Edit: And... build failed. Starting over... So, looking at this afternoon now.
Edit 2: Well... I can make it boot when I tinker with it manually, but I'm not having much luck making a reproducible build from source. So... I'll have a release eventually, but with 4 hour rebuilds, I can't say when at this rate.
Steel01 said:
Similar to my TWRP / Multirom thread, this is temporary until xda decides to add this device to the dev db list. A few comments and a known issues list will be all in this post. Please report any and all problems you find. This is still very early in the development process.
NOTES:
This will only install using my TWRP build here because I'm have to do some hacky things to support a unified build. I may eventually find a cleaner method.
This doesn't yet contain my attempt at controller pairing. The framework patches are there, but not the apk. It will be tested and included in later builds. Wifi doesn't work, so pairing wouldn't work anyways.
I had to use aosp libs to make this boot, which is different from my Portable and Tablet releases. The hdcp libs seems to be very different, so I have no idea if 4k works at all and I seriously doubt youtube and netflix drm will verify correctly.
You will have to wipe data to install this, make a backup first. Do note this is just /data, not the entire internal sd.
KNOWN ISSUES:
Wifi doesn't enable. (ethernet works fine, though)
Keyboard not installed
SOURCE:
device
kernel
vendor
CURRENT RELEASE:
cm-12.1-20150709-UNOFFICIAL-foster.zip
Click to expand...
Click to collapse
screenshots ?
Glad to see ATV gettin some action ... ooooo hel I'm excited. I've been fastbooting your twrp img. for a few things and its working quite nicely on my pro model. BIG BIG thanks for that @Steel01 Does it look like there will be any issues reguarding which version console its running?
@aniel300: Screenshots? It's Cyanogenmod. The same Cyanogenmod as on any other device...
@ElwOOd_CbGp: Like mentioned in the OP, I do a hacky thing or two to support unified builds. It have the pro version myself, so that's what I test on. I'm pretty sure it will work with no extra problems on the 16 GB model, however.
Alright, I *think* I finally ironed my build problems (all related to using a prebuilt kernel... got to figure out a way to not have to do that), so theoretically I'll have a build out tomorrow. Probably won't be able to test much until the afternoon, so I doubt it'll be out bright and early.
yey! please keep going! AOSP + Kodi + Support for official remotes would be awesome!
Steel01 said:
@aniel300: Screenshots? It's Cyanogenmod. The same Cyanogenmod as on any other device...
@ElwOOd_CbGp: Like mentioned in the OP, I do a hacky thing or two to support unified builds. It have the pro version myself, so that's what I test on. I'm pretty sure it will work with no extra problems on the 16 GB model, however.
Alright, I *think* I finally ironed my build problems (all related to using a prebuilt kernel... got to figure out a way to not have to do that), so theoretically I'll have a build out tomorrow. Probably won't be able to test much until the afternoon, so I doubt it'll be out bright and early.
Click to expand...
Click to collapse
is it a hybrid rom ?
@[email protected]: Kodi is of great interest to me as well, so I'll work to make sure works well.
@aniel300: No, it's pure CM. I plan to make the TV stuff accessible, but it won't be there by default.
I finally got a bootable build, but it does show more problems. The launcher and some programs lag terribly. Not locking up, but slow enough to trigger ANRs. Netflix does still crash when loading a video, hopefully that won't be hard to fix once I can read the logs. The interface still flickers, but only the interface, not videos or games or such. I'll do some more testing this afternoon and unless an even worse problem shows up, I'll release.
New build is up. It appears the netflix bug affects others things too, like youtube. Appears to be audio related, but I don't have time right away to try and track down the root cause. So, consider this another bug hunting build and not truly usable.
I've fixed an audio problem, so sound and YouTube and all that works again. Netflix is still confusing me a bit, though. It appears to be a problem with the OMX libs, but not one seen on any other Shield device. Haven't spent too much time looking the last few days.
I'm in the process of restructuring the build setup on my dev machine. Like moving the build trees to a faster spinny disk and ccache to a ssd. That should get builds going a lot faster. 4 hours per build gets old real fast. And 45 minutes for a one package change. I plan to release a new build once I get that all sorted out.
what about you try to port android m tv developer preview instead or at least cm but with all the good stuff from android tv.
It seems Forge has unlockable bootloader they posted instructions also for home images so it's a start it should be easy to flash recovery if there was one. Sorry for going little off topic but this seems more active here
New build up. Seems the OMX libs are only partially working. Youtube works, but mxplayer and kodi fall back to their software decoders. Wireless appears to finally work, but logcat messages lead me to believe it's still not completely there. Oh, and the UI flickering is still there.
So, I loaded this build up and promptly installed HALauncher and Kodi. With the controller wired in, this seems to be a pretty usable setup. As things begin to stabalize, I'll probably start to recommend that launcher as a replacement for leanback. Now if only I can find a replacement for the leanback keyboard, I won't have to include any Google blobs... Suggestions are welcome for a free and preferably open source dpad enabled keyboard.
Really good progress tonight. Barring something patentably bad happening, I should be releasing a new build tomorrow. List of progress:
1. Interface flickering is way down. Don't know if it was something I did or if upstream CM tweaked stuff. Either way, it's bearable now. I only notice it on some transitions, whereas before it was all the time on builtin android interface stuff.
2. OMX libs work. Hardware accelerated video and movies, plus game streaming and grid works now.
3. Leanback IME (controller enabled keyboard) is part of the build. It's smaller than on stock, but still usable.
Some things still need work, though:
1. Netflix still fails to play a video. At least it doesn't crash to desktop anymore...
2. Wireless controller pairing fails. The app runs and it tries to set stuff up, but seems to hit the same problem the Portable does most times. I have got the Portable to pair once or twice, though, so some people might be more lucky than me and it'll actually work.
All in all, this looks like a very usable test build, if not a daily driver for some use cases.
Hi steel01
I am planning to buy this device, pro version, but its true that the SSD storage drive has some problems about performance and response, speed, looking all around for a good review about this and nothing found yet,unbelievable, I want to be sure the 16 GB or pro version.
Counting on you,like you doing on the shield tablet,interesting approach with CM,look forward, when I get it I will install the Zulu99 full android ROM first and them....cm
Good luck on this, thank for you hard work
I haven't had any lag problem with the Pro edition, but I also haven't done anything IO intensive. So, I'm not really a good yardstick for that. However, the pro edition does have the 16GB hardware, just needs some tweaking to be able to access it. Probably could do some boot image trickery to get /system on that device. Haven't looked at that yet since CM and multirom are higher priority in that order.
Other stuff came up today, so I didn't get to test the new build. As soon as I drag it back across the house to reflash it, I'll verify the build and upload. Maybe tomorrow afternoon.
I am just a thinker, its possible to use all the best feature of CM and put it in android tv or viceversa.
I dont own yet a android tv device, but is like no to manny peoples like it, may restrictions from google, its entirely new or old UI, developers needs to port their apps to android tv platform, maybe we like the custom launcher or just the regular launcher, well its until everybodys decision.
Multirom sound good, but i like the basic and fast, what about if we can have two launcher in the GUI or UI, can be possible, there is a really need an apps to be ported to android tv platform, why google put restriction, we can sideload to get what we want, i think this is confusing android OS is android.
I think the best thing to do its going back to the basic.
Well, I didn't get to testing today either. I think I'll run another build tonight and try to get to a test tomorrow night.
@duanim: That is my end goal for my device. The Shield TV running CM with a 10 foot launcher (that isn't leanback) and everything accessible from the controller. The current build isn't too bad for that, but not all the way there. CM and HALauncher works pretty well. But the controller still needs help wirelessly.
There's one major problem with running android and android tv simultaneously. It seems the play stores are different. You either get the TV apps or the normal apps, not both. If someone knows different or a way to work around this, I'd love to hear it.
Still can't get the dumb wireless controller libs to package the way I want. So the latest build is missing some, causing the app to continuously force close, making the build unusable. I'll split it like I didn't want to and should have a releasable build tomorrow.
Recently inherited a Nook Tablet 16GB with OS 1.4.3.
Did some searching and Phone Arena http://www.phonearena.com/phones/Barnes---Noble-NOOK-Tablet_id6548 lists it as Android (2.3).
Am not familiar with TI OMAP4 SoC.
Since Android is now at 6, I wonder what the latest OS can be used with it?
Appreciate comments and suggestions!
Thanks
Ken
Should add am wondering what is the latest Android OS I can use before the TI OMAP4 SoC becomes noticeably Slow.
Ken
KenithO said:
Should add am wondering what is the latest Android OS I can use before the TI OMAP4 SoC becomes noticeably Slow.
Ken
Click to expand...
Click to collapse
Slow compared to what? The original 2.3? That I can't speak to since I never did much with my original (ebay) tablet but turn it on and flash CM 10.2.1 (after having it repartitioned at my local B&N store). I ran CM 10.2.1 for a little over a year and was fairly happy with its performance but I have to add that it has been my only tablet experience (if you don't count my much-modified Nook Simple Touch!) and the rest of my experience is with desktop and laptop Windows machines.
I think if you intend to use the tablet for memory and graphics intensive gaming, you may be disappointed. Not sure since I'm not a gamer. I use mine for reading news, watching movies and/or streams, listening to audiobooks, doing crossword puzzles, email, some limited internet browsing, running Kodi, etc. I'm not sure I'd call the tablet response "sprightly", but I'm comfortable with the performance. I don't need to grab a cup of tea while something starts up
I'm not sure about CM 11 (that's roughly KitKat). I skipped over that one to investigate CM 12.1 (Lollipop) for just about a week now and have noticed some strain on the hardware resources and a change in response. But it's still settling in and things change a little from day to day so I'll give it a few more weeks before I decide whether to return to 10.2.1 or try 11.
So....it's largely what you'd expect. This is a piece of hardware that was designed as mainly a reader with a few bones thrown in to tantalize people into thinking they were getting a little something extra--which they were. But that was in the days of Android 2.3 and it really wasn't designed to be a super-duper multimedia tablet. That said, there are a lot of people who still use them and spend a lot of time developing CM for them.
As a 2.3 device it's pretty limited (except as a reader, if you like the backlight) so I'd say give at least CM 10 a try and see what you think. Just keep in mind its hardware origins.
Hi nmyshkin,
1st thanks for your comments! Will try to explain in more detail.
I would like to use my Nook Tablet as a audio/video player (No games) so like to install VLC media player or similar.
"Slow compared to what?" To my experience installing newer Windows OSes on same hardware. Have had best results using apps like nLite or with WinXP using Hiren's MiniXP to reduce all the Win Bloatware!
Since you are much more experienced concerning the Nook Tablet do you have a blog concerning your OS upgrade experience? Also what Audio/Video Player App(s) do you use?
Ken
KenithO said:
Hi nmyshkin,
1st thanks for your comments! Will try to explain in more detail.
I would like to use my Nook Tablet as a audio/video player (No games) so like to install VLC media player or similar.
"Slow compared to what?" To my experience installing newer Windows OSes on same hardware. Have had best results using apps like nLite or with WinXP using Hiren's MiniXP to reduce all the Win Bloatware!
Since you are much more experienced concerning the Nook Tablet do you have a blog concerning your OS upgrade experience? Also what Audio/Video Player App(s) do you use?
Ken
Click to expand...
Click to collapse
If you're interested in mainly audio/video then the NT should serve you well. I hear you about trying to put newer (read: hungrier) operating systems on older machines. The CM people have done a great job but every piece of hardware has its limits. For your purposes I would think that CM 10 would be fine, but you could certainly try 11 or (maybe) 12. The advantage to choosing a more up-to-date operating system is that more apps are available to you. The catch is that the PlayStore will often say an app is not compatible since it sees the device as a Nook Tablet and has no idea that you have upgraded the OS. So you sometimes have to be creative in obtaining apps and sideloading them. As for bloatware, the principal source is the GoogleApps! When I did my CM 10 flashing there was just the typical package but there are now mini, micro, nano, etc., versions which narrow down the list of GApps to bare essentials. I used the nano set on my CM 12.1 and don't miss anything.
I've attached a screenshot of my current Home running CM 12.1. I have a second screen which is just a few utilities (file manager, print, wi-fi transfer, etc.) but you can get an idea of what kind of stuff runs well on the tablet with a newer OS. I've not used VLC player on the NT but I imagine it would be fine. MX Player works well for me and it also serves as my music player. Since I grew up in an era when the album was king, I don't keep separate songs and use minimal tags. If you're a more tag-driven music listener then you'd want something else. CM 10 comes with a tag-friendly music player but if that didn't suit your needs, there are plenty of apps to try in the PlayStore.
Anything that MX Player can't handle (haven't found it yet) Kodi would be able to deal with. I guess you could use Kodi exclusively as a media player but the screen interface is a little trying for a small screen.
I'm "experienced" only to the extent that I've had a lot of help with problems In my view you can't do better than the instructions given by user digixmax. His installation instructions for CM 10 are here. For CM 11 or 12 they are here. If you read through both threads you'll find plenty of panic-stricken posts by yours truly
nmyshkin said:
...
The catch is that the PlayStore will often say an app is not compatible since it sees the device as a Nook Tablet and has no idea that you have upgraded the OS. So you sometimes have to be creative in obtaining apps and sideloading them.
...
Click to expand...
Click to collapse
FWIW I usually can download and install from an alternate source such as 1MobileMarket (http://market.1mobile.com) or Amazon appstore the very same app that Google Playstore deem incompatible with my Nook.
digixmax said:
FWIW I usually can download and install from an alternate source such as 1MobileMarket (http://market.1mobile.com) or Amazon appstore the very same app that Google Playstore deem incompatible with my Nook.
Click to expand...
Click to collapse
Yes, or you can try here: http://apps.evozi.com/apk-downloader/
Most common apps can be downloaded to your PC from there and then side loaded. Supposedly they will also fetch less common ones if you ask.
nmyshkin,
Thanks again for your detailed comments!
Also while I am new to Nook Tablet have been using Android cell phones for a while. My 1st Android phone was a Kyocera Hydro http://www.phonearena.com/phones/Kyocera-Hydro_id7096
Wanted to root it but after reading "!!WARNING!! there is currently no working recovery, beware of the changes you make to your phone, modify at your own risk" (am a believer in Murphies Law
https://en.wikipedia.org/wiki/Murphy's_law) decided not to take the chance.
Recently I got an and hoped to root it but found "Alcatel A460G Rooting Trouble - a lost cause" http://forum.xda-developers.com/general/help/alcatel-a460g-rooting-trouble-pointers-t3261024
so am waiting for someone to do this first.
While I have never Rooted an Android Device did learn early to side load, usually using http://apps.evozi.com/apk-downloader/
Have recently found mention of another Android app download site APKPure https://apkpure.com/ but do Not know how trustworthy it is?
The only thing I know about "CyanogenMod" is what I read at https://en.wikipedia.org/wiki/CyanogenMod
Since my Nook Tablet is still original will volunteer to use any test apps to determine its speed.
Also since it does not have a Camera do not understand the need to go above KitKat (4.4). If there is some other reason would be interested.
"When I did my CM 10 flashing there was just the typical package but there are now mini, micro, nano, etc., versions which narrow down the list of GApps to bare essentials. I used the nano set on my CM 12.1 and don't miss anything." Nano is for me! What about Pico? Also found Pico(Uni)?
Where do you normally download them? Is it http://www.androidrootz.com/2015/03/download-android-44x-kitkat-pa-gapps.html
Question: What do you gain by using CyanogenMod 12.1, based on Android 5.1?
Ken
Hi digixmax,
"I usually can download and install from an alternate source such as 1MobileMarket (http://market.1mobile.com) or Amazon appstore the very same app that Google Playstore deem incompatible with my Nook."
Thanks for the tip!
Do you know of any posts concerning the reliability of alternate sources?
Ken
KenithO said:
nmyshkin,
Thanks again for your detailed comments!
Also while I am new to Nook Tablet have been using Android cell phones for a while. My 1st Android phone was a Kyocera Hydro http://www.phonearena.com/phones/Kyocera-Hydro_id7096
Wanted to root it but after reading "!!WARNING!! there is currently no working recovery, beware of the changes you make to your phone, modify at your own risk" (am a believer in Murphies Law
https://en.wikipedia.org/wiki/Murphy's_law) decided not to take the chance.
Recently I got an and hoped to root it but found "Alcatel A460G Rooting Trouble - a lost cause" http://forum.xda-developers.com/general/help/alcatel-a460g-rooting-trouble-pointers-t3261024
so am waiting for someone to do this first.
While I have never Rooted an Android Device did learn early to side load, usually using http://apps.evozi.com/apk-downloader/
Have recently found mention of another Android app download site APKPure https://apkpure.com/ but do Not know how trustworthy it is?
The only thing I know about "CyanogenMod" is what I read at https://en.wikipedia.org/wiki/CyanogenMod
Since my Nook Tablet is still original will volunteer to use any test apps to determine its speed.
Also since it does not have a Camera do not understand the need to go above KitKat (4.4). If there is some other reason would be interested.
"When I did my CM 10 flashing there was just the typical package but there are now mini, micro, nano, etc., versions which narrow down the list of GApps to bare essentials. I used the nano set on my CM 12.1 and don't miss anything." Nano is for me! What about Pico? Also found Pico(Uni)?
Where do you normally download them? Is it http://www.androidrootz.com/2015/03/download-android-44x-kitkat-pa-gapps.html
Question: What do you gain by using CyanogenMod 12.1, based on Android 5.1?
Ken
Click to expand...
Click to collapse
Yes, it's best to do some homework on a device before purchase if you plan to root it or install alternate ROMS.
Sources for the various GApps packages can be found in the instruction thread I referred you to earlier.
Even CM 10 includes camera and Bluetooth fluff on the NT-- not functional, of course. Theoretically running a more up-to-date OS extends the useful life of the device. App development eventually leaves older devices in the dust, although not completely. I still have a generous complement of apps on my NST and that runs Eclair!
Anyway, the chief advantage of an OS like CM is that it is fluid, with people working to improve and enhance. Also, it overcomes some of the limitations imposed by B&N when they designed their "front end".
KenithO said:
...
Nano is for me! What about Pico? Also found Pico(Uni)?
Click to expand...
Click to collapse
Info on different package types:
http://forum.xda-developers.com/android/software/reborn-gapps-5-t3074660
Where do you normally download them?
Click to expand...
Click to collapse
http://opengapps.org/#
---------- Post added at 07:16 PM ---------- Previous post was at 07:14 PM ----------
KenithO said:
Do you know of any posts concerning the reliability of alternate sources?
Click to expand...
Click to collapse
Not off-hand.
digixmax,
Thanks for the links! Somehow I thought the various builds were CyanogenMod and searched for "CyanogenMod Pico" but found nothing.
Looked over "Info on different package types" http://forum.xda-developers.com/andr...pps-5-t3074660 and am interested in PICO MODULAR PACKAGE ANDROID 5.1 DOWNLOAD LINKS (~43MB).
Question: Is a Pico Modular package available for Android 4.4.4 KitKat? Am guessing No.
To restate I would like to use my Nook Tablet 16 Only as a Multimedia Player and for reading DOCs and PDFs.
Since I only side load apps is it possible to eliminate Google Play Store, Google Calendar Sync, and the following Play Store application and leave only the core Google system base?
[GAPPS][DAILY] Open GApps for Android 5.1,5.0,4.4; arm,arm64,x86,x86_64
http://forum.xda-developers.com/showthread.php?t=3098071
[GAPPS][DAILY] Open GApps for Android 5.1,5.0,4.4; arm,arm64,x86,x86_64
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Am trying to do my homework so have been searching for early articles about the Nook Tablet.
Found "How To Sideload (Almost) Any Android App On The Nook Tablet" by K. T. Bradford http://www.gottabemobile.com/2011/11/16/how-to-sideload-android-apps-nook-tablet/
Am wondering if this Nook originally had OS 1.4.0? Does anyone know how to find out? If yes is there an easy way to go back to it? That way I would get a baseline. If no I hope someone has found a workaround!
The 1st app I would like to install is a File Manager and would appreciate any recommendations.
Since OS 1.4.3 is listed as Android 2.3 checked Google Store for FMs that will run on this or older and found X-plore File Manager 3.78 (2.3), File Manager (File transfer) by Cheetah Mobile Tools (Varies with device?),
SD File Manager 1.0.9 by MobilDev (2.3), File Manager by 1.1 by IT STARS (2.3), File Manager 1.31 by xFrame Labs Tools (2.3)
Hi champ1919,
Thanks for the link! I have a lot of catching up to do concerning Open GApps!
Liked DL page http://opengapps.org/ for giving a quick overview of all the options!
Saw there is an X86 ver for 4.4 to 6.0 Nano. Am wondering if I can install these on a std 32bit PC?
Have been searching and found "Advanced Features and Options", "Removal of Stock applications", and "Universal Application Removals"
https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options These give you a lot of options!
Any good tutorials?
OK guys, I'm updating a 16GB Nook tablet, it has 1.4.3.
From what I've pieced together, I need to create a bootable TWRP sdcard and flash the root file then flash the TWRP 3.0.0-0(the acclaim works for the old Nook?) Then flash CM12 or CM13?
I'm starting from scratch and these guides are rather old so I'm trying to make sure I use the most up to date recovery and ROM available but with everything spread through different guides its a little confusing to decide which steps and files I need and which ones I don't considering I'm trying to go from stock to TWRP and CM12/CM13 in as few steps as possible.
Droidriven said:
OK guys, I'm updating a 16GB Nook tablet, it has 1.4.3.
From what I've pieced together, I need to create a bootable TWRP sdcard and flash the root file then flash the TWRP 3.0.0-0(the acclaim works for the old Nook?) Then flash CM12 or CM13?
I'm starting from scratch and these guides are rather old so I'm trying to make sure I use the most up to date recovery and ROM available but with everything spread through different guides its a little confusing to decide which steps and files I need and which ones I don't considering I'm trying to go from stock to TWRP and CM12/CM13 in as few steps as possible.
Click to expand...
Click to collapse
You can look at this thread for combinations of files that worked. I'm in there later in the mix and that's how I ended up with CM 12.1.
Looking at the SD card I prepared I can see everything I used except for the TWRP version because it was renamed. At this point I would just use one of the versions mentioned in the thread I just referenced for someone who succeeded at 12.1 (or if you want 13.0, there is a separate thread for that). Just know that TWRP gives error messages during the preparation process (at least my version did--mentioned in the thread) and these can be ignored.
The rest of the files I used with success:
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim.zip
flashable_CWM_6.0.4.8_chrmhoffmann.zip
open_gapps-arm-5.1-nano-20160109.zip
FWIW, the file size on the TWRP version I used shows as 7516 KB.
Hello Ken,
All CMs are somewhat slower that stock Android from BN. You will also loose the proper behavior of tablet when you connect cable to charger - stock OS wakes tablet from sleep when tablet gets connected to charger, CM does not, so you will have to wake it up first, otherwise tablet will not charge. Then, under every CM build RAM (under 'About Tablet') is stated 672 Mb, but under stock OS RAM is 1024Mb. Don't know is B&N trick us or not.
Next, if tablet left asleep for some prolonged period its time/date gets frozen, so when you wake it up it will show some wrong time/date and it does not auto-update on wake up, so you will have to manually update it by going to proper menu in Settings.
Tablet definitely lags compared to stock (in my opinion), especially when apps upgrade themselves and/or you turn on the WiFi - it's total hell. Also, apps like FB can take forever to install.
I tried CM12.1 but decided to get back to CM10.2.1. I also use alternative launcher, cause native one works in landscape mode and nothing made it to run in portrait.
Btw, in newer CMs you will loose access to some of the internal storage and to recover it - you will have to repartition your tablet.
Hope my info helps a bit.
PepeladZ said:
Hello Ken,
All CMs are somewhat slower that stock Android from BN. You will also loose the proper behavior of tablet when you connect cable to charger - stock OS wakes tablet from sleep when tablet gets connected to charger, CM does not, so you will have to wake it up first, otherwise tablet will not charge. Then, under every CM build RAM (under 'About Tablet') is stated 672 Mb, but under stock OS RAM is 1024Mb. Don't know is B&N trick us or not.
Next, if tablet left asleep for some prolonged period its time/date gets frozen, so when you wake it up it will show some wrong time/date and it does not auto-update on wake up, so you will have to manually update it by going to proper menu in Settings.
Tablet definitely lags compared to stock (in my opinion), especially when apps upgrade themselves and/or you turn on the WiFi - it's total hell. Also, apps like FB can take forever to install.
I tried CM12.1 but decided to get back to CM10.2.1. I also use alternative launcher, cause native one works in landscape mode and nothing made it to run in portrait.
Btw, in newer CMs you will loose access to some of the internal storage and to recover it - you will have to repartition your tablet.
Hope my info helps a bit.
Click to expand...
Click to collapse
This further reinforces my feeling that the CM flashings are somewhat idiosyncratic (at least on the Nook Tablet). I've run both 10.2.1 and 12.1 (current) on my tablet and never saw the clock update issue described. In 12.1 the AM/PM indicator had update issues, but I solved that by disabling the cLock widget and installing Chronus from the PlayStore.
Sluggish is as sluggish does, I guess. Running CM 12.1 is no more sluggish than my cheap KitKat LG smartphone I use as an mp3 player. I have to agree that sometimes the tablet just has a bad time of things. This happened a lot after my initial 12.1 installation and there were many odd things that needed fixing. I just kept at it until it is finally running as well as 10.2.1---even better since it now boots reliably every time, whereas with 10.2.1 there were many times when I would boot to a black (backlit) screen. So now I shut it down every night and boot up the next morning without any problem.
The moral seems to be that you just need to try. Keep a backup of the stock system in case you have "buyer's remorse". Don't give up right away. Reflash if things are just a mess, but if only a few things are wonky, work with the tablet for a week or so. It seems to get better after each reboot. Decide for yourself whether the reported sluggishness of the tablet is something that you notice for the apps you are using. A lot of it is about expectations.
nmyshkin said:
I've run both 10.2.1 and 12.1 (current) on my tablet and never saw the clock update issue described. In 12.1 the AM/PM indicator had update issues, but I solved that by disabling the cLock widget and installing Chronus from the PlayStore.
Click to expand...
Click to collapse
The thing is that I tried one of the latest 12.1 with the same results. I don't think the clock problem comes from cLock widget but is related to deep sleep mode or something like that.
nmyshkin said:
This happened a lot after my initial 12.1 installation and there were many odd things that needed fixing. I just kept at it until it is finally running as well as 10.2.1---even better since it now boots reliably every time, whereas with 10.2.1 there were many times when I would boot to a black (backlit) screen.
Click to expand...
Click to collapse
Well, I switched to CM since 10.x and followed along till 13.x came out. So I was on 12.1 for quite some time and tried fresh builds quite frequently, doing 'full reset' install. Btw, I've never had unreliable boots.
nmyshkin said:
So now I shut it down every night and boot up the next morning without any problem.
Click to expand...
Click to collapse
Yes, turning it off is the only way to keep clock right.
After looking at the Index thread, it seems as if Lollipop 5.1 is the latest version of Android that is safe for an HP Touchpad. Am I understanding this correctly?
Also, if I install that one, does it wipe out WebOS? I guess it doesn't matter if so because from what I'm reading, it's completely outdated and no longer supported. Also, I'm locked out and cannot remember the passcode anyway.
No version of Android is supported on the TouchPad, therefore there isn't a 'safe' version. You'd have most success updating to current (7.1.2+) firmwares. As a TouchPad modder, these versions are the fastest and most supported by Play Store. The initial process of installing 'moboot' for the first time can be daunting, so look into using which ever version of Android is used in jcullins' Toolbox tutorial. Once moboot and TWRP are installed, you can pretty much try whichever rom you want, as this device is near impossible to brick.
Good luck!
mrlaugh01 said:
No version of Android is supported on the TouchPad, therefore there isn't a 'safe' version. You'd have most success updating to current (7.1.2+) firmwares. As a TouchPad modder, these versions are the fastest and most supported by Play Store. The initial process of installing 'moboot' for the first time can be daunting, so look into using which ever version of Android is used in jcullins' Toolbox tutorial. Once moboot and TWRP are installed, you can pretty much try whichever rom you want, as this device is near impossible to brick.
Good luck!
Click to expand...
Click to collapse
Can you please link me to a/the tutorial for the version you suggested?
ashleyquicik said:
Can you please link me to a/the tutorial for the version you suggested?
Click to expand...
Click to collapse
Try the below link which points to the updated guide on how to install Android on the HP Touchpad.
If you are a newbie on this stuff, you would be a good test on how well this guide is written and if it needs any tweaks to help people follow it with accuracy.
I mean I tested it myself, but I am a "seasoned veteran" LOL, I installed KitKat from this guide and also Nougat the version that was recommend to you. Its all there.
https://forum.xda-developers.com/hp...-guide-alternative-method-to-install-t3575861
DoubleStuff said:
Try the below link which points to the updated guide on how to install Android on the HP Touchpad.
If you are a newbie on this stuff, you would be a good test on how well this guide is written and if it needs any tweaks to help people follow it with accuracy.
I mean I tested it myself, but I am a "seasoned veteran" LOL, I installed KitKat from this guide and also Nougat the version that was recommend to you. Its all there.
https://forum.xda-developers.com/hp...-guide-alternative-method-to-install-t3575861
Click to expand...
Click to collapse
1) So I got it to install (Evervolv Nougat) and my feedback on the tutorial is that it's a bit of information overload. Not sure how easy it would be to simply it though.
2) I could not find a link for Boost (what is that?) or the Keyboard fix. Can you assist (assuming they can be installed retroactively)? The keyboard, for instance, works in Chrome but does not appear on the home screen when tapping the Google Search Bar.
3) And maybe this should be #1...but this Nougat seems to slow things down considerably. I tried installing the game Run Race 3D for instance and it was unplayable. Would an older Android version speed things up or am I just dealing with old hardware that can't keep up?
ashleyquicik said:
1) So I got it to install (Evervolv Nougat) and my feedback on the tutorial is that it's a bit of information overload. Not sure how easy it would be to simply it though.
2) I could not find a link for Boost (what is that?) or the Keyboard fix. Can you assist (assuming they can be installed retroactively)? The keyboard, for instance, works in Chrome but does not appear on the home screen when tapping the Google Search Bar.
3) And maybe this should be #1...but this Nougat seems to slow things down considerably. I tried installing the game Run Race 3D for instance and it was unplayable. Would an older Android version speed things up or am I just dealing with old hardware that can't keep up?
Click to expand...
Click to collapse
Hello AshleyQ,
Well along with the step by step, I added a bit of instruction. For example you said, "I could not find a link for Boost (what is that?) or the Keyboard fix." So I will add a little more "overload" of instruction for what Boost Optimized settings are, in my OP at a later date.
But as per your performance. The reason its slow is because you did not load the following ZIP's in the exact sequence the instructions say. I realize its because you could not find the links for boost and keyboard. If you go to HP_TOUCHPAD's "Master List of ZIPs" in the OP of the guide, or I put it below for convenience, you will see the green list below for Nougat 7.1.2, and find the links you were missing earlier.
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
and once you click link, hit "page down" 3 times and it will get you to the "Master List of Zips"
Evervolv 7.1.2 Android Nougat
1.Click Here to Download the ROM
2.Click Here to Download the Boost Optimized settings with preset CPU Frequency
3.Click here to download Google Open Apps
Select Platform ARM, Android 7.1 and the Variant you want, Pico is recommended
4.Click Here to Download the Keyboard Fix
As per the Boost Settings always start with 1728, and after that is working good, you can try to flash a higher frequency for speed, and you don't have to re-flash everything just the Boost Zip ( like 1782, or 1836 ) file from TWRP recovery. If it freezes screen just go back and flash lower frequency.
So click each link in the OP, and download the said 4 ZIP files, and follow the Original Post again, with these 4 ZIP's ready to go!!! Do not do this retroactively, but start again from scratch.
And you will be able to play the "Run Race 3D" game!!
Look at this link below, a non-gamer like user HP_TOUCHPAD from Florida, played the game Hearthstone!!! I believe you will be able to play "Run Race 3D", but we would love to hear how your results go, and we will be here to help you get a smooth running touchpad that is 100% Android, with SWAP!!!
https://forum.xda-developers.com/hp-touchpad/general/how-to-play-hearthstone-blizzard-t3924170
@HP_TOUCHPAD
Using these downloads from your Master List of Zips, and running my install method.
AshleyQ the OP'er wants to play Run Race 3D game. Now I am not a gamer at all, but you tried with Hearthstone so I will try now, when I download Run Race 3D game I get the attached errors. But I can run YouTube fine, everything seems fine until I run that game ( Run Race 3D ). What are these errors telling you? I waited till SWAP was over 400 Mb, and I used various boost files, first 1782, 1836 and 1728, but with no luck.
I should point out that I had about 10 minutes where I was running the game with smoothness and doing the jumps and winning the races, but then HP Touchpad started to get sluggish with little mini freezes and it threw my timing of the jumps off and I started to lose, then the error came.
Evervolv 7.1.2 Android Nougat
1.Click Here to Download the ROM
2.Click Here to Download the Boost Optimized settings with preset CPU Frequency
3.Click here to download Google Open Apps
Select Platform ARM, Android 7.1 and the Variant you want, Pico is recommended
4.Click Here to Download the Keyboard Fix
p.s. the 2nd pic is kind of hard to read, I just wanted to show that I ran "running services" and it shows 558 MB of SWAP.
DoubleStuff said:
@HP_TOUCHPAD
Using these downloads from your Master List of Zips, and running my install method.
AshleyQ the OP'er wants to play Run Race 3D game. Now I am not a gamer at all, but you tried with Hearthstone so I will try now, when I download Run Race 3D game I get the attached errors. But I can run YouTube fine, everything seems fine until I run that game ( Run Race 3D ). What are these errors telling you? I waited till SWAP was over 400 Mb, and I used various boost files, first 1782, 1836 and 1728, but with no luck.
In the Developers options --.>> Running Services shows Device Memory been use but does not show the swap.
The FREE in gray color shows the available free RAM, but is not the size of the swap file, for example the system can report 485 MB Free RAM and only use 60 MB of swap.
The best way to see how much swap is been use is by connecting the Tablet to PC using usb, open a terminal window and using adb shell then type
free -h
I should point out that I had about 10 minutes where I was running the game with smoothness and doing the jumps and winning the races, but then HP Touchpad started to get sluggish with little mini freezes and it threw my timing of the jumps off and I started to lose, then the error came.
Keep in mind that the free version of this game have Ads, that is a service that is running in the background and when is time to display the ads is another process getting activated. Android is constantly launching background process it does not seem to care if the device is been use, it will take priority.
Evervolv 7.1.2 Android Nougat
1.Click Here to Download the ROM
2.Click Here to Download the Boost Optimized settings with preset CPU Frequency
3.Click here to download Google Open Apps
Select Platform ARM, Android 7.1 and the Variant you want, Pico is recommended
4.Click Here to Download the Keyboard Fix
p.s. the 2nd pic is kind of hard to read, I just wanted to show that I ran "running services" and it shows 558 MB of SWAP.
Click to expand...
Click to collapse
The reason that I mentioned to wait until it shows 400 MB of free RAM (is not swap) is that Android finishes launching all process and the system is finally "IDLE", it takes that long for Android to finally settle and the Tablet ready to be use..
I just installed the Game, it only took about 73 MB of swap space, but I am testing on DU 9 using completely different settings. I am not a gamer, but it looks very simple, graphics are minimal, it does shows a lot of ads and even launching the Play store to install more games. The issues that I am having is that there is no minimal specification for any App, it only shows the Android version and it will depend on the Device. It will help if an App shows the minimal RAM requirement to run, then the settings can be apply to provide that amount, but is all about guessing. I am not done testing my next settings, I will use this game as a tester.
I applied some settings and tried the game and I won! is very easy to play on the Tablet with a bigger screen but it could be a real challenge on smartphone.
Attached is the screenshot of my victory.
Is work in progress, but the game should play with no issues once I finish the settings.
So what do you guys recommend that I do? I just used Run Race 3d as an example of the sluggishness and really just want an Android version and setup that will give me the best overall (meaning fastest) performance...with games/browsing/etc.
HP_TOUCHPAD said:
I applied some settings and tried the game and I won! is very easy to play on the Tablet with a bigger screen but it could be a real challenge on smartphone.
Attached is the screenshot of my victory.
Is work in progress, but the game should play with no issues once I finish the settings.
Click to expand...
Click to collapse
Congratulations on the RR3D win! I won a few times myself and the man did a little dance on the screen, but then my HPTP got sluggish and I kept crashing into the walls because when I pressed the screen the man would not jump like I told it too. In fact my setup got to the point I could not even take a screenshot it was too sluggish.
But if @ashleyquicik is reading this, please be patient it seems like HP_TOUCHPAD is working on some Universal performance settings that will work for all ROMs, past present and future. In the meantime you could load JC Sullins KitKat 4.4 ROM you will find that link in the 2nd Master List of zips ( RolandD's ) on below install method. I find for YouTube and Podcast apps this current version of Nougat is fine, but once I start playing "Run Race 3D" it gets sluggish. Be sure to follow directions in flashing the ZIP's in order.
HP_TOUCHPAD is now using the Run Race 3D game as a testing app, so you can be sure sooner or later this game will be working, not to win at the game, but to win and beat the sluggishness!!
This is the classic case of MAN vs. MACHINE!!!
https://forum.xda-developers.com/hp...-guide-alternative-method-to-install-t3575861
DoubleStuff said:
Congratulations on the RR3D win! I won a few times myself and the man did a little dance on the screen, but then my HPTP got sluggish and I kept crashing into the walls because when I pressed the screen the man would not jump like I told it too. In fact my setup got to the point I could not even take a screenshot it was too sluggish.
After the first stage of the game was over and I selected to play again, then what seems to be an Advertisement came up, but it was only a black screen, then the image show trying to trick me on touching to install another game, there was no way of getting out of it, then the Play store got launch by itself and then I had to close both. There is a difference when you the user open many apps and place them on the background and when two apps are running at same time, is too much to ask for a 1GB RAM device.
But if @ashleyquicik is reading this, please be patient it seems like HP_TOUCHPAD is working on some Universal performance settings that will work for all ROMs, past present and future. In the meantime you could load JC Sullins KitKat 4.4 ROM you will find that link in the 2nd Master List of zips ( RolandD's ) on below install method. I find for YouTube and Podcast apps this current version of Nougat is fine, but once I start playing "Run Race 3D" it gets sluggish. Be sure to follow directions in flashing the ZIP's in order.
I will provide the settings but I do not want to send the wrong signal as it will allow for any apps, specially games to play. Android's apps are extremely buggy even on the stock devices, just search for an issue and you will find how many users are experiencing the problem and none are related to the HP TP, just regular devices.
HP_TOUCHPAD is now using the Run Race 3D game as a testing app, so you can be sure sooner or later this game will be working, not to win at the game, but to win and beat the sluggishness!!
As you have tested yourself the game will play, you won. It is a very basic game with low graphics., but it provides HUGE Ads and also any other apps that you have installed on the Tablet will impact performance. The sluggishness comes as background services that becomes active, that is why as soon as you connect the Tablet to WiFi, it will slow down, just check Running Services and you see them all, opening and closing plus the google apps updates, it will happen even if the CPU is at full capacity and low ram available, is the way Android works.
This is the classic case of MAN vs. MACHINE!!!
I will call it MAN vs Google!
Here is the explanation for that, I will try to keep it short.
https://forum.xda-developers.com/hp...-guide-alternative-method-to-install-t3575861
Click to expand...
Click to collapse
Android Apps are written in Java, Google does not want to pay license feeds as is offering the OS for free and making revenue on the data it collect from the devices for Ads placement, each device is a Digital Billboard that Google charge for displaying time to companies promoting their services or products.
If you have experience running a Virtual Machine on the Desktop, then it should be easy to understand the concept. Android apps are running inside an open source virtual machine " Dalvik" to run the java code and be display on the screen. To virtualize an OS on the desktop if the PC has 6 GB of RAM, and the guess OS requires a minimum of 4 GB to run, then it must be configure and there will only be 2GB left on the Host OS. Then the speed will degrade for low RAM resources and the HOST can not be use for nothing else. Once the Guess OS has done its job, it can be close down and the Host OS will function normally. But if the correct amount of RAM is not allocated to the Guess it will not boot, or shutdown. That is the same that happen in HP TP with Android, and those settings are apply manually in the build.prop by the manufacture. Everything in Android must be configure manually as the OS is too basic and primitive all settings are device specific according to screen resolution, size and amount of RAM ( Memory ).
Hopefully I explained it or compare it, easy to understand.
HP_TOUCHPAD said:
Android Apps are written in Java, Google does not want to pay license feeds as is offering the OS for free and making revenue on the data it collect from the devices for Ads placement, each device is a Digital Billboard that Google charge for displaying time to companies promoting their services or products.
If you have experience running a Virtual Machine on the Desktop, then it should be easy to understand the concept. Android apps are running inside an open source virtual machine " Dalvik" to run the java code and be display on the screen. To virtualize an OS on the desktop if the PC has 6 GB of RAM, and the guess OS requires a minimum of 4 GB to run, then it must be configure and there will only be 2GB left on the Host OS. Then the speed will degrade for low RAM resources and the HOST can not be use for nothing else. Once the Guess OS has done its job, it can be close down and the Host OS will function normally. But if the correct amount of RAM is not allocated to the Guess it will not boot, or shutdown. That is the same that happen in HP TP with Android, and those settings are apply manually in the build.prop by the manufacture. Everything in Android must be configure manually as the OS is too basic and primitive all settings are device specific according to screen resolution, size and amount of RAM ( Memory ).
Hopefully I explained it or compare it, easy to understand.
Click to expand...
Click to collapse
So having said that...and to sort of reiterate some of what I wrote in my last post, what is arguably the best ROM/procedure to have the best overall performance?
ashleyquicik said:
So having said that...and to sort of reiterate some of what I wrote in my last post, what is arguably the best ROM/procedure to have the best overall performance?
Click to expand...
Click to collapse
It all depends of the intended use from the user.
Does it needs to have a working:
Bluetooth ?
Reliable WiFi ?
Camera ?
Android compatibility with a special App ?
Android Versions are different and that sets the ROM apart, it will not be comparing Apples to Apples from different versions.
If you check my guide I have optimized 7.1.2, 8.1 and 9 to use swap and all those three versions works very similar.
One of the reason that I will be doing an Universal Setting and retro-fit older ROM, is to show that the Tablet will work similar with different ROMs.
I should probably make a version that is completely optimized only for games, that will required to delete unnecessary Android system process and RAM could be about 600 MB Free.
Does it needs to have a working:
Bluetooth ? Yes
Reliable WiFi ? YES
Camera ? Yes
Games really aren't necessary because I'm giving this tablet to someone that won't be gaming.
ashleyquicik said:
Does it needs to have a working:
Bluetooth ? Yes
Reliable WiFi ? YES
Camera ? Yes
Games really aren't necessary because I'm giving this tablet to someone that won't be gaming.
Click to expand...
Click to collapse
I started reading your thread from the beginning as I though that it was all about the 3d racer game.
You have a Tablet that would like to give to someone that has WebOS installed and also another Android version on it, which is 7.1.2 and you found it to be slow.
My recommendations for a newest ROM is the same as everyone on here recommended Evervolv 7.1.2 Android Nougat. You could use older ROMs but some basic apps may not work.
Previously @DoubleStuff provided the information on how to installed Evervolv 7.1.2 and also provided the link to my guide that with instructions.
If you flashed the Automatic_Wipe_All, then the Tablet is 100 % Android with swap and WebOS is gone, which will provide more storage space on the Tablet.
As per my guide the proper way to flash all the zip files provided is as follow:
Evervolv 7.1.2 Android Nougat
1.Click Here to Download the ROM
2.Click Here to Download the Boost Optimized settings with preset CPU Frequency
3.Click here to download Google Open Apps
Select Platform ARM, Android 7.1 and the Variant you want, Pico is recommended
4.Click Here to Download the Keyboard Fix
The Boost optimized settings link (2) will give you the option to download 5 different CPU frequency, start with 1728 after you set up the tablet then try a higher speed, the fastest is 1836, if the Tablet boot into Android after flashing 1836 and use some apps and does not freeze then keep using it, if it reboots or freeze then flash 1782 if still not stable keep flashing lower frequencies.
To have a properly working camera, install this app:
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en_US
If you have any issues just ask.
ashleyquicik said:
Does it needs to have a working:
Bluetooth ? Yes
Reliable WiFi ? YES
Camera ? Yes
Games really aren't necessary because I'm giving this tablet to someone that won't be gaming.
Click to expand...
Click to collapse
Well as I talked about in another thread where HP_TOUCHPAD wants to start retrofitting old ROM's with SWAP and Universal boost settings, there is a ROM that most agree is the "greatest ROM of all time", but its an old version of Android called KitKat 4.4.4 by JC Sullins and you can find the link here:
https://forum.xda-developers.com/showthread.php?t=2712680
Now one version later Lollipop 5.1 ( or 12.1 CM ) this same developer JC Sullins created a Lollipop ROM, that HP_TOUCHPAD is working on retrofitting: As @HP_TOUCHPAD said in a previous thread about this retrofit.
"...I Applied all optimization to CM 12.1, but testing. The only problem that I am experiencing is if I open about 8 to 9 apps and then press the square, next to home, it will reboot. I do not know if is the ROM or my settings.
But overall works great with swap. Will be posting new optimized settings, soon...." -HP_TOUCHPAD
And if I am not mistaken he may have finished it, but its not posted yet in his MASTER ZIP's list
What I recommend you do AshelyQ because its so easy and quick to install ROMs with our install methods, I would install KitKat above and test it for a day or two, then install another one maybe 7.1.2 and again test it, and maybe even another. And then you can pick the one you think meets you or your friends needs the best and stick with that ROM.
I am going to install HP_TOUCHPAD's retrofitted Lollipop ROM ( when HP_TOUCHPAD posts the settings ) and try to run "Run Race 3D" on it....I will report back with my findings.
HP_TOUCHPAD said:
<-SNIP->
To have a properly working camera, install this app:
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en_US
Click to expand...
Click to collapse
Hmm ... I still get critical camera errors, even with the Open Camera app, even after a couple of reboots.
Do Not Touch said:
Hmm ... I still get critical camera errors, even with the Open Camera app, even after a couple of reboots.
Click to expand...
Click to collapse
The stock camera App of 7.1.2 works, but colors and orientation shows incorrectly, but it works on Open Camera.
DoubleStuff said:
...snip....
I am going to install HP_TOUCHPAD's retrofitted Lollipop ROM ( when HP_TOUCHPAD posts the settings ) and try to run "Run Race 3D" on it....I will report back with my findings.
Click to expand...
Click to collapse
Well I have not tested JC Sullins Lollipop ROM with Universal settings yet, but I just installed JC Sullins 4.4 without swap or any special settings, just the ROM and the GApps, and I am happy to report the "Run Race 3d" game went well, I made it to the BONUS Level and earned 146 coins with lots pomp and circumstance, and was getting adds everytime I completed a race, but I waited 5 seconds then pressed the "X" and things went well. So now I am very curious how these old "great" Android versions will work with HP TOUCHPAD'S Universal settings.
3 days ago I was not a gamer, but I guess I am now!!! LOL The HP Touchpad even had enough memory to take a screen shot.