Related
Sorry Guys,
As there doesn't seem to be a whole lot of interest in this project and as no one stepped forward to assist, I'm afraid I'm going to have to abandon this project.
Thanks for following.
___________________________________
OK Guys,
I've run into a bit of a brick wall and need some input from other developers. One of the required APKs from the Q needs a class not included along with my CM9 or Samsung stock roms. The class appears to be called "android.os.UpdateLock". So how do I go about ripping the class out of the Nexus Q rom and injecting it into CM9? Any help would be very appreciated!$!
--------------------------------------------------------------------
Hello All,
The Project
I'm looking to embark on a project to rip out the cloud function from the Q and install it on any android device. I want the cloud streaming of "Google" music and movies without the $300 expense.
The Progress
As of today I have the Nexus Q Deodexed, ripped out several apk files including the Nexus Q "Launcher" HubBroker.apk. I've merged the apks along with the fonts and lib folders of /system and my Galaxy Tab now boots up and runs like a Q. Primary issue outstanding is, the Nexus Q app won't detect the "galaxy Q" through bluetooth. I assume that some functions of the Q are sitting either within the bluetooth libs or that the Nexus Q has a specific bluetooth address that the app needs to see before detection.
My next attempt will be to try taking apart the Nexus Q apk and either changing its bluetooth search criteria or removing it completely. Second to that if anyone out there has a Q and has it setup on their phone, I could use the /data/data folder to extract more information about how it works. Or even better if someone knows what config file is generated on the actual nexus Q when it's set up for that first time.
You can already do that on most android devices. The Q just takes it to the big screen conveniently.
The function of being able to control the Google queue of device A from device B, C, D etc does not exist. Or at least I'm not aware of an app that does that.
I believe that I've tracked down the apk that does it on the nexus but I need to deodex the apps and can't seem to find a tool that works. Anyone out there deodex this rom yet?
JoeJonnyBoy75 said:
Hello All,
The Project
I'm looking to embark on a project to rip out the cloud function from the Q and install it on any android device. I want the cloud streaming of "Google" music and movies without the $300 expense.
The Progress
As of today I have the Nexus Q Deodexed, ripped out several apk files including the Nexus Q "Launcher" HubBroker.apk. I've merged the apks along with the fonts and lib folders of /system and my Galaxy Tab now boots up and runs like a Q. Primary issue outstanding is, the Nexus Q app won't detect the "galaxy Q" through bluetooth. I assume that some functions of the Q are sitting either within the bluetooth libs or that the Nexus Q has a specific bluetooth address that the app needs to see before detection.
My next attempt will be to try taking apart the Nexus Q apk and either changing its bluetooth search criteria or removing it completely. Second to that if anyone out there has a Q and has it setup on their phone, I could use the /data/data folder to extract more information about how it works. Or even better if someone knows what config file is generated on the actual nexus Q when it's set up for that first time.
Click to expand...
Click to collapse
This is a pretty nice project and there is nothing like this happening in Android now, besides the nexus Q. I'd like to see a future port of it to Google TV devices
auad said:
I'd like to see a future port of it to Google TV devices
Click to expand...
Click to collapse
Would love to have this functionality in an APK for me Google TV. Don't see why it wouldn't work, well other then no bluetooth on the Revue....
Still very interested in this thread regardless of GTV. I will be following your progress. Thanks!
.
I'm looking for this as well.
I have 3 spare HTC EVO's, and they all have HDMI out. I would like to be able to just plug them into the TV and use my other phones to control them / play music / etc. Maybe even throw XBMC on them with the ability to control from another phone..
They're slower, and less memory..but it may be doable.
Did anyone dig into this? I'd like this for the latest port of Android for a Raspberry Pi and willing to do some of the (noob)stuff myself.
That would be awesome to use any HDMI equipped phone along with the Nexus Q functionalities. I'm really interested.
I guess the problem with the missing API is that the Nexus Q runs android JB and he tried with a cm9.
Vettekult said:
I guess the problem with the missing API is that the Nexus Q runs android JB and he tried with a cm9.
Click to expand...
Click to collapse
Not true, Q runs ICS...
Let me know...
what I can do to help. If you give me a run down on what you would like me to try as far as pulling files from the q or my connected devices just shoot me a PM and i'll give it a shot. I too would love to add this functionality to my spare devices laying around.
I've been interested in this since day one as well. IT is what has me almost ready to fork out the money on more then one occasion. I have a party coming up and it would be fun to have my N7 as the Jukebox.
The Class issue, I'm not sure about. Here is some info that might get it started.: http://www.itcsolutions.eu/2011/08/...te-a-new-activity-class-with-manifest-editor/
AND:
http://stackoverflow.com/questions/5012004/adding-a-new-class-to-android-project
It looks like it is something created with the app. Since you cut/pasted the apk into system it may not have been installed. But I'm thinking that it is something else. Some where in the android system lib's it is probably installed. Since this was a device dedicated to this purpose, they were able to install it into the system and the app calls it. I'm slowly learning to write apps (very slowly) so I am not sure beyond this, or even about this for that matter.
I do have a question. It looks like you pulled some system apps and put them in your galaxy tablet. I think a better test would be to basically replace all the /system contents of say a N7 (galaxy tab may work) with those from the Q. Then once it works, cut down the files until it stops. Then with a list of what is needed to make it work we could get down to the nitty gritty.
My guess is some more knowledgeable devs, like those who got Google Now working, would have a better idea.
I'd love to see a third party app do the jukebox function, I think a issue is license certificate (DRM) for the multiple users. I don't understand how the user is associated/authenticated for the music. One Question is if a user Ques up music then leaves does it cause that music to not be able to be played or will it still play once it's been que'd? My guess is the app just organizes the music/user who is next then when it's their turn it streams from their device in real time... but I'm really not sure about this.
joeavery2 said:
I've been interested in this since day one as well. IT is what has me almost ready to fork out the money on more then one occasion. I have a party coming up and it would be fun to have my N7 as the Jukebox.
The Class issue, I'm not sure about. Here is some info that might get it started.: http://www.itcsolutions.eu/2011/08/...te-a-new-activity-class-with-manifest-editor/
AND:
http://stackoverflow.com/questions/5012004/adding-a-new-class-to-android-project
It looks like it is something created with the app. Since you cut/pasted the apk into system it may not have been installed. But I'm thinking that it is something else. Some where in the android system lib's it is probably installed. Since this was a device dedicated to this purpose, they were able to install it into the system and the app calls it. I'm slowly learning to write apps (very slowly) so I am not sure beyond this, or even about this for that matter.
I do have a question. It looks like you pulled some system apps and put them in your galaxy tablet. I think a better test would be to basically replace all the /system contents of say a N7 (galaxy tab may work) with those from the Q. Then once it works, cut down the files until it stops. Then with a list of what is needed to make it work we could get down to the nitty gritty.
My guess is some more knowledgeable devs, like those who got Google Now working, would have a better idea.
I'd love to see a third party app do the jukebox function, I think a issue is license certificate (DRM) for the multiple users. I don't understand how the user is associated/authenticated for the music. One Question is if a user Ques up music then leaves does it cause that music to not be able to be played or will it still play once it's been que'd? My guess is the app just organizes the music/user who is next then when it's their turn it streams from their device in real time... but I'm really not sure about this.
Click to expand...
Click to collapse
Ok so here is some more detailed info for those of you still following the project.
HubBroker.apk is the app that is for all intents and purposes the "launcher" for the nexus Q. It will install on the Galaxy Tab and Nexus 7. It takes over your "home" and replaces it with a picture of the Nexus Q and a welcome sign. This app looks to be only the launcher as it doesn't do anything if you tap on it. Also having the app running doesn't allow the Nexus Q app (from your phone) to find the device.
So I assume that that the Q is controlled via bluetooth to get it setup and running. Including configuring the Wifi, network settings, etc. Oddly enough the app does send a request to android system to turn on the bluetooth and changes the bluetooth device name to Nexus Q.... The ... part is a odd string of characters that I assume is used in case you happen to have multiple Nexus Q's.
Now as just having the app doesn't seem to work (Phone finding the Q). I've replaced all the bluetooth libs with the ones from the Q. Still nothing. I've migrated all the other APK files and then I get FCs all over, and still no connection. I haven't tried replacing the whole system yet, but I assume the hardware differences would be to great. The only other piece of the puzzle I have yet to attempt it merging the kernels or at least the init parts of the kernel relating to bluetooth.
If you have any questions though let me know. I've been up and down this thing.
Why don't we just flash the img on an old phone and see if that works?
zAo_ said:
Why don't we just flash the img on an old phone and see if that works?
Click to expand...
Click to collapse
For that to work we'd need to get a device with similar hardware (CPU, Chipset, etc.) Not only that but it would need to have the same MTD setup unless I'm mistaken.
Actually I'm going to give that a try with the nexus 7. I'll let you know what happens, won't be till tonight though.
JoeJonnyBoy75 said:
For that to work we'd need to get a device with similar hardware (CPU, Chipset, etc.) Not only that but it would need to have the same MTD setup unless I'm mistaken.
Actually I'm going to give that a try with the nexus 7. I'll let you know what happens, won't be till tonight though.
Click to expand...
Click to collapse
Cool, Thanks.
Sent from my Galaxy Nexus using xda premium
JoeJonnyBoy75 said:
For that to work we'd need to get a device with similar hardware (CPU, Chipset, etc.) Not only that but it would need to have the same MTD setup unless I'm mistaken.
Actually I'm going to give that a try with the nexus 7. I'll let you know what happens, won't be till tonight though.
Click to expand...
Click to collapse
Galaxy nexus has very similar hardware. Someone should try porting it.
Sent from my Nexus 7 using xda premium
If someone still interested in the project, i'm very interested in it, i have a galaxy nexus (almost same hardware) so we can give it a try, im also a android developer, so if it need to build some apk for it to work, i could give a shot.
Anyway, if there is someone interested just post here and we do all we can to make that work.
edit: Only one problem, as I'm out of USA, i need the q apk to test if it will connect or not. I cant download from play store.
I'm sure there will be so many people interested in it. I just think that not to many of them enter this category on forum
I also need the nexus q image so I can flash it. I tried searching it but didnt find
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.
EDIT: Please direct any development questions, queries, etc. to the new thread in the Development Forum, concerning all development-y things.
http://forum.xda-developers.com/grand-prime/development/unofficial-cyanogenmod-12-1-g530w-t3424761
============================================================
I've recently started working on a custom ROM for the Samsung Grand Prime G530W [gprimeltevl/gprimeltecan], and so far I have built a somewhat working ROM (without any radio/wireless capability or audio for now).
If there is interest in this project (which I think there is; the lack of any kind of love shown for the G530W is annoying), I'll continue hacking away at it until I (hopefully) have a working ROM.
I'm new to Android ROM building in general, and there have been several bumps along the way, so any help would be appreciated.
Thanks.
I will be uploading images daily to my Drive storage, in folders named by date (if the date today is not there, then the image had not been built or uploaded yet), and will be compressing the system.tar images with either gzip or xz to reduce the image size.
I will also be updating this area with issues and fixes as necessary.
What I have managed to get working so far (23/07/2016)
Limited mobile connectivity [ sending/receiving texts ].
- Calls can be received or made but there is no audio (speaker or microphone).
- Mobile data is not working.
- Currently the system does not show the mobile connection as active, but texts can still be sent and received.
Bluetooth is working
Audio is working (microphone, speaker)
Multimedia playback working
GPS is working
Wifi is working
Screen brightness controls working
Sensors are working (magnetic, rotation/gyro,proximity)
App installation is now working
Camera is kinda working - only back camera works, and the image is distorted.
Issues
Radio [ modem ] is not working properly
NFC is not working
MTP is not working
Cameras are not working
Here is a link to the system.tar, boot.tar and recovery.tar flashable by ODIN or fastboot (when unpacked).
https://drive.google.com/open?id=0B-bYwctD_MoDaWJGcUQ4eWtzRTQ
Project GitHub Repositories:
https://github.com/vince2678/android_device_samsung_gprimeltecan
https://github.com/vince2678/android_vendor_samsung_gprimeltecan
If there are any other issues I missed, let me know.
Great effort
vince2678 said:
I managed to compile and get an image working for the G530W.
What I have managed to get working so far
Bluetooth is working
Audio is working (microphone, speaker)
Multimedia playback working
GPS is working
Sensors are working (magnetic, rotation/gyro,proximity)
Issues
Device fails to unlock and heats up [only once, so far]
Wifi is not working
Radio [ modem ] is not working
User interface crashes periodically
Screen brightness controls not working
MTP is not working
Cameras are not working
Here is a link to the system.tar, boot.tar and recovery.tar flashable by ODIN or fastboot (when unpacked).
https://drive.google.com/folderview?id=0B-bYwctD_MoDVzd0eS1aaDV6RW8&usp=sharing
I'll be working at it to get at least the Wifi working, if there are any other issues I missed, let me know.
Click to expand...
Click to collapse
Good work so far!
I recently purchased a g530w and I would love to boot the stock ROM.
However, I am still busy researching and reading up on this device before I attempt to flash anything. Actually, I did create an update zip file to remove Skype and tried applying it while not rooted but it failed because it was not properly signed.
Anyway, I will watch your progress with keen interest!
Zippy Dufus said:
Good work so far!
I recently purchased a g530w and I would love to boot the stock ROM.
However, I am still busy researching and reading up on this device before I attempt to flash anything. Actually, I did create an update zip file to remove Skype and tried applying it while not rooted but it failed because it was not properly signed.
Anyway, I will watch your progress with keen interest!
Click to expand...
Click to collapse
Sounds interesting. Did you try rooting your phone and using Link2SSD to remove the app(s)? It works pretty well, and you don't have to go through the whole effort of packing and unpacking the ROM.
vince2678 said:
Sounds interesting. Did you try rooting your phone and using Link2SSD to remove the app(s)? It works pretty well, and you don't have to go through the whole effort of packing and unpacking the ROM.
Click to expand...
Click to collapse
Here's my plan for my new phone:
Reading and research (in progress)
Setting up Odin on a virtual machine (I am a Linux user) and testing a restore of the stock ROM. Do you have a good link to such a ROM? I briefly looked at http://www.sammobile.com/firmwares/ and this site looks a little sketchy to me.
Root the device. I believe the method described in this G530T thread has worked for our G530W.
Debloat the crapware. Surprisingly, there is not all that much on the device - mostly some Micro$oft crap, Skype, and an old, old version of Chrome which I cannot uninstall. As root, I'll just go in and delete the unwanted stuff from /system/app using a terminal emulator.
Once it get this far, I can probably live with stock Lollipop. Question, if you are learning how to port a ROM, have you considered starting with Marshmallow? I'm keen to move up.
Build the ROM myself and then attempt to build it with my Linaro toolchain which I built from scratch myself.
Questions, with what you know so far, will the G530H ROM in this thread work on our phone? Is this what you started from? What differences between the 2 devices what preclude it from working on ours - different hardware? software - i.e. different bootloader?, etc?
Zippy Dufus said:
Here's my plan for my new phone:
Reading and research (in progress)
Setting up Odin on a virtual machine (I am a Linux user) and testing a restore of the stock ROM. Do you have a good link to such a ROM? I briefly looked at http://www.sammobile.com/firmwares/ and this site looks a little sketchy to me.
Root the device. I believe the method described in this G530T thread has worked for our G530W.
Debloat the crapware. Surprisingly, there is not all that much on the device - mostly some Micro$oft crap, Skype, and an old, old version of Chrome which I cannot uninstall. As root, I'll just go in and delete the unwanted stuff from /system/app using a terminal emulator.
Once it get this far, I can probably live with stock Lollipop. Question, if you are learning how to port a ROM, have you considered starting with Marshmallow? I'm keen to move up.
Build the ROM myself and then attempt to build it with my Linaro toolchain which I built from scratch myself.
Questions, with what you know so far, will the G530H ROM in this thread work on our phone? Is this what you started from? What differences between the 2 devices what preclude it from working on ours - different hardware? software - i.e. different bootloader?, etc?
Click to expand...
Click to collapse
Hey Zippy,
That sounds like a good idea.
That website does seem kinda sketchy, and their downloads take millenia, but it's the only option available and their images actually work (just make sure to get the correct one).
Setting up a virtual machine is a good idea, because heimdall doesn't work with this device and I'm not keen on bricking my device trying to force it.
Rebooting between builds to test firmwares because of a lack of a good recovery was becoming a pain. (CyanogenMod Recovery is still missing critical features but it's better than stock).
You can use CF-Auto-Root to root the device (so simple) at:
https://download.chainfire.eu/774/C...uto-Root-gprimeltecan-gprimeltevl-smg530w.zip
Yup, debloating is good, i wanted to do so at first but I wanted to be done away with KNOX and have an su binary which worked flawlessly for good so I decided to start from scratch.
I've considered starting from M, but that will be a task for later. It is troublesome to start from a fimware above what your device is at when you're porting, because the vendor libraries and binaries you copy might not work in the newer version of Android because of linking errors.
You can copy the binaries fine but obscure errors due to missing references will pop up in the logs which will stop the modules from loading or binaries from running.
I'm having these issues with a build ID that is just a few apart from the one used on the stock ROM - LMY49J on the cm build versus LMY47X on the stock).
My Git repos are above - you can get yourself a cm12.1 source tree, pull my device_ and vendor_ trees, pull proprietary files using the scripts in the vendor tree, build from source and then flash the resultant images to your device.
The G530H ROM might, in theory flash without issue and actually boot, but whether it will be usable is another thing.
The thing that differs between the devices, as far as I'm aware, is mostly the baseband, some other device hardware (e.g the G530W has 1.5GB RAM instead of 1GB as most G530 devices), and the device bootloader. As such, the kernels and modules used might differ slightly in terms of modules compiled in, even though they're built from the same kernel source.
And yes, indeed, I started from a G530 device and vendor tree, though whether it was that one, or perhaps one for the G530FZ, I don't remember (though I think it's the G530FZ, it's the device closest to the G530W).
Finally something for this variant, I've been waiting for ages. Huge thumbs up dude, from a thankful Canadian. I don't use this phone as my daily driver so I'll be flashing this without delay. Mind if I trouble you for the order of operations? I've never used Odin to flash a custom ROM before.
Some more questions ...
Hi again @vince2678, I have more questions:
Do you have a local_manifest.xml that drives your build? ... I have a single-purpose Fedora24 virtual machine which I use to build android ROMs.
Does your build actually produce a CM12.1 zip installation package? ... And do you simply harvest the system.img, etc afterwards to put into a flashable this tar file?
What is the command line that do you use to create the flashable tar files? ... I'm just curious.
What version of the firmware does your device have? ... Mine has G530WVLU1AOFB. Apparently, this is the Tanzanian version! WTF? I purchased my phone from a Costco in Oakville, Ontario, Canada. It was purported to be unlocked for all Canadian carriers. My carrier is Virgin Mobile (owned by Bell) and it works fine. But, my understanding is that device actually locks to your SIM card upon first use so you can't use it for other SIM cards, but I haven't proven this yet. BTW, I got over half of the stock ROM DL'ed from SamMobile before it stopped due to a "network error". Yeah right! I'll try again later.
Have you (or are you) cherry-picking patches from the G530H CM12.1 ROM? ... android_device_samsung_fortuna3g I suggest DL'ing their key files and comparing them to yours. They appear to be in the final exhilarating phase of perfecting their ROM.
So you have totally removed the KNOX software without in deleterious consequences? ... I thought that I read in an XDA thread where somebody did this and then had issues such as connecting to WIFI, etc. It appeared that there may be a dependency in the BIOS.
Did you trip the KNOX e-fuse hence void the warranty? ... Not that I care about the warranty, I only worry about bricking the device.
Unlike @Pbotelho, this is my daily driver so I will be proceeding slowly and cautiously and look forward to his experience flashing it.
Pbotelho said:
Finally something for this variant, I've been waiting for ages. Huge thumbs up dude, from a thankful Canadian. I don't use this phone as my daily driver so I'll be flashing this without delay. Mind if I trouble you for the order of operations? I've never used Odin to flash a custom ROM before.
Click to expand...
Click to collapse
Hi Pbotelho, thanks man. You will have to enable Developer Mode on your phone and unlock the bootloader from the settings. I don't remember what exactly in the settings that option is, but it should be in the Debugging area for sure.
Once done, reboot into Download Mode [Press Power+Volume Down+Home].
Once you've done that, grab the boot.tar, system.tar.xz and recovery.tar from the links above. Extract the system.tar.xz with 7zip or `xz -d system.tar.xz` if under Linux to get a system.tar file, and flash the recovery, boot, and system, one after the other, in whatever order, by booting into download mode as soon as it is done flashing a file.
You will need to wipe your cache and data partitions, which can be done by rebooting into recovery [Power+Volume Up+Home].
The button options are built into the hardware so they can be used at any point after the phone is on.
When all that is done, you can report any problems here [or on the github page] and post logcats and I'll look at them if there's any issue I've missed.
Zippy Dufus said:
Hi again @vince2678, I have more questions:
Do you have a local_manifest.xml that drives your build? ... I have a single-purpose Fedora24 virtual machine which I use to build android ROMs.
Does your build actually produce a CM12.1 zip installation package? ... And do you simply harvest the system.img, etc afterwards to put into a flashable this tar file?
What is the command line that do you use to create the flashable tar files? ... I'm just curious.
What version of the firmware does your device have? ... Mine has G530WVLU1AOFB. Apparently, this is the Tanzanian version! WTF? I purchased my phone from a Costco in Oakville, Ontario, Canada. It was purported to be unlocked for all Canadian carriers. My carrier is Virgin Mobile (owned by Bell) and it works fine. But, my understanding is that device actually locks to your SIM card upon first use so you can't use it for other SIM cards, but I haven't proven this yet. BTW, I got over half of the stock ROM DL'ed from SamMobile before it stopped due to a "network error". Yeah right! I'll try again later.
Have you (or are you) cherry-picking patches from the G530H CM12.1 ROM? ... android_device_samsung_fortuna3g I suggest DL'ing their key files and comparing them to yours. They appear to be in the final exhilarating phase of perfecting their ROM.
So you have totally removed the KNOX software without in deleterious consequences? ... I thought that I read in an XDA thread where somebody did this and then had issues such as connecting to WIFI, etc. It appeared that there may be a dependency in the BIOS.
Did you trip the KNOX e-fuse hence void the warranty? ... Not that I care about the warranty, I only worry about bricking the device.
Unlike @Pbotelho, this is my daily driver so I will be proceeding slowly and cautiously and look forward to his experience flashing it.
Click to expand...
Click to collapse
Hi Zippy,
I do not have a local_manifest, if you want you can just manually pull the device and vendor trees into your build area, or you can make one yourself if you wish.
I will probably make one though, because the build has dependencies on some qcom sources.
I just use 'make -j8' to build everything, though you can use 'make otapackage' to build a flashable zip [You'll need the CMR recovery from here though, the images can't be flashed by stock recovery]
For creating flashable tar files, you can just use `tar`. You don't need to make .md5 verifiable archives, those are just to ensure a download wasn't corrupted [I provide md5sums for checking].
The system.img in the output directory will have to be renamed to 'system.img.ext4' and then archived, as so:
Code:
cd out/target/product/gprimeltecan
ln system.img system.img.ext4
tar cf system.tar system.img.ext4
tar cf boot.tar boot.img
tar cf recovery.tar recovery.img
Then you can move the files wherever and flash them with Odin.
Yes the gprimeltevl/gprimeltecan baseband is indeed G530WVLU1AOFB, though this should work with all G530WXXXXXXXs (not sure how many different ones are out there].
I'm not sure about the SIM locking thing, I cannot confirm this, someone might have to try to check.
I did consider sourcing from that repository, though ultimately i ended up using another one [I don't remember the name]. I might take a look at their source to see what I can do about mine though.
I did trip KNOX, though that was back when I was still trying to root my phone with CF-Root, so I'm not sure if flashing this will trip KNOX. And yes, KNOX is completely gone from this device, with no problems from the phone.
vince2678 said:
Hi Pbotelho, thanks man. You will have to enable Developer Mode on your phone and unlock the bootloader from the settings. I don't remember what exactly in the settings that option is, but it should be in the Debugging area for sure.
Once done, reboot into Download Mode [Press Power+Volume Down+Home].
Once you've done that, grab the boot.tar, system.tar.xz and recovery.tar from the links above. Extract the system.tar.xz with 7zip or `xz -d system.tar.xz` if under Linux to get a system.tar file, and flash the recovery, boot, and system, one after the other, in whatever order, by booting into download mode as soon as it is done flashing a file.
You will need to wipe your cache and data partitions, which can be done by rebooting into recovery [Power+Volume Up+Home].
The button options are built into the hardware so they can be used at any point after the phone is on.
When all that is done, you can report any problems here [or on the github page] and post logcats and I'll look at them if there's any issue I've missed.
Click to expand...
Click to collapse
I got impatient with it so I took a gamble and inferred with some background knowledge. Got it up and running several hours ago. Performance wise, it seems dead on perfect. There's no lag, no force closing of apps. Everything runs as snappy as it should. Its fast as f***. Now I even installed xposed framework and added in a few modules, one of those being the Android N-ify project, and it works really well with it, so kudos on this area. I'll be sure to uninstall xposed when it comes to error reporting and logcats.
The only issues I'm seeing besides the ones you've already outlined are graphical in nature. I'm not home at the moment but I'll upload some logcats when I get the chance.
1) What I'm seeing is a blackout out lock screen. I have a theme installed and used it to apply a custom lock wallpaper to test this out. The wallpaper only shows once you've accessed the Pattern input by swiping up. Haven't tried it with a pin. If you're only using swipe, it'll stay black until unlocked.
2) When unlocked and swiping down to access the notifications panel and quick settings, the same blackout effect is present. This is present only while you're looking at your notifications or tiles, and returns to normal when swiped back up.
3) The first half of this part is only noticed when using the material glass theme. When swiping down to access the notification panel without notifications, the "no notifications" text will be present as it should be, however, when swiped down again to access the quicksettings tiles, the "no notifications" text isn't cleared away. It sits behind the brightness slider. This isn't noticeable on the stock theme because its opaque, while material glass features transparency as their main selling card. If using the battery saver, the text from this persistent notification will appear instead.
Edit: Upon further analysis, it seems that the notification content is linked to the bottom of the header instead of the bottom of the quicksettings tiles, and that's why it works this way. When expanding or shrinking the header, the notification also moves directly with it.
Second half: whether on the stock theme or not, the "no notifications" text will continue to stick and be viewable on the lockscreen, retaining its position that is viewed in the notification panel. It sits directly above the clock. The persistent battery saver notification works the same way. I'm no expert, but I believe that since the notification panel and lockscreen both go to black, that this might be linked in some way.
4) Sometimes when using the stock theme and toggling options in the quick settings tiles, it'll glitch out and turn into what I can only describe as a zombie menu. The pixels of the status bar are replaced by that proportionate area of the quick settings menu, and when swiping down to use the menu, access is disabled (it can't be touched) and it closes itself when attempted. Only way I've been able to fix it was to toggle the theme to material glass and all was restored, still subject to the above three points.
Edit: 5) when using kernel adiutor to try to adjust the CPU frequencies, the only option that comes up for both minimum and maximum is 0MHz. The button seems to work as well, bringing the clock max speed down to 0 for a split second before it reverts to a a maximum of 200MHz. Adjusting the governor after the fact won't restore the maximum, seems only a reboot will get it done. I'm slightly amazed to be honest as before on Touchwiz, it was impossible to get it to hold onto a lower maximum. It would jump all over the place as it pleased.
Edit: 6) The recents hardware button is disabled. Touching it, holding it, nor double tapping brings up a function. It also isn't present in settings when trying to map the button functions. Its the only one that's missing. Power, home, back, and volume are all there.
That's all I got for the moment, I tried to be as descriptive as possible as I won't be able to get the logcats up for awhile. Let me know if you have any questions about what I've said here.
And also, are you taking feature requests?
Pbotelho said:
I got impatient with it so I took a gamble and inferred with some background knowledge. Got it up and running several hours ago. Performance wise, it seems dead on perfect. There's no lag, no force closing of apps. Everything runs as snappy as it should. Its fast as f***. Now I even installed xposed framework and added in a few modules, one of those being the Android N-ify project, and it works really well with it, so kudos on this area. I'll be sure to uninstall xposed when it comes to error reporting and logcats.
The only issues I'm seeing besides the ones you've already outlined are graphical in nature. I'm not home at the moment but I'll upload some logcats when I get the chance.
1) What I'm seeing is a blackout out lock screen. I have a theme installed and used it to apply a custom lock wallpaper to test this out. The wallpaper only shows once you've accessed the Pattern input by swiping up. Haven't tried it with a pin. If you're only using swipe, it'll stay black until unlocked.
2) When unlocked and swiping down to access the notifications panel and quick settings, the same blackout effect is present. This is present only while you're looking at your notifications or tiles, and returns to normal when swiped back up.
3) The first half of this part is only noticed when using the material glass theme. When swiping down to access the notification panel without notifications, the "no notifications" text will be present as it should be, however, when swiped down again to access the quicksettings tiles, the "no notifications" text isn't cleared away. It sits behind the brightness slider. This isn't noticeable on the stock theme because its opaque, while material glass features transparency as their main selling card. If using the battery saver, the text from this persistent notification will appear instead.
Click to expand...
Click to collapse
Hi Pbotelho,
I'll try to answer everything as completely as I can.
The blackout lock screen thing seems to be an issue with Trebuchet. I found that using a different lock screen app solves this issue.
As for the blackout on the notification area, I'm not sure what exactly is causing this, though I think this may be a problem with the cm-12.1 source and not necessarily the device port itself.
Second half: whether on the stock theme or not, the "no notifications" text will continue to stick and be viewable on the lockscreen, retaining its position that is viewed in the notification panel. It sits directly above the clock. The persistent battery saver notification works the same way. I'm no expert, but I believe that since the notification panel and lockscreen both go to black, that this might be linked in some way.
Click to expand...
Click to collapse
This seems to be an issue with Trebuchet again, and using a different lock application fixes this.
Sometimes when using the stock theme and toggling options in the quick settings tiles, it'll glitch out and turn into what I can only describe as a zombie menu. The pixels of the status bar are replaced by that proportionate area of the quick settings menu, and when swiping down to use the menu, access is disabled (it can't be touched) and it closes itself when attempted. Only way I've been able to fix it was to toggle the theme to material glass and all was restored, still subject to the above three points.
Click to expand...
Click to collapse
I'm aware of this one, for now you can fix this by disabling Brightness Control in the settings ( Settings->Status Bar->Brightness Control).
This again might be an issue with the cm-12.1 source, though it'll need some checking to confirm.
Edit: when using kernel adiutor to try to adjust the CPU frequencies, the only option that comes up for both minimum and maximum is 0MHz. The button seems to work as well, bringing the clock max speed down to 0 for a split second before it reverts to a a maximum of 200MHz. Adjusting the governor after the fact won't restore the maximum, seems only a reboot will get it done. I'm slightly amazed to be honest as before on Touchwiz, it was impossible to get it to hold onto a lower maximum. It would jump all over the place as it pleased.
Click to expand...
Click to collapse
I'm using Kernel Adiutor and frequency setting is fine. Did you try using a tunable governor like interactive? That may be the issue.
Edit: 6) The recents hardware button is disabled. Touching it, holding it, nor double tapping brings up a function. It also isn't present in settings when trying to map the button functions. Its the only one that's missing. Power, home, back, and volume are all there.
Click to expand...
Click to collapse
I'm aware of this, you can blame this on my bad arithmetic skills . I had set the wrong bit field mask for the button settings in the device frameworks.
I'll be pushing a fix addressing this shortly.
And also, are you taking feature requests?
Click to expand...
Click to collapse
That depends on what the features are, if they're reasonable and within my capabilities, then yeah .
PS: I would appreciate any help I can get, and if you have any coding skills and time to compile builds, you can help me polish up the device port.
Thanks!
vince2678 said:
Hi Pbotelho,
I'll try to answer everything as completely as I can.
The blackout lock screen thing seems to be an issue with Trebuchet. I found that using a different lock screen app solves this issue.
As for the blackout on the notification area, I'm not sure what exactly is causing this, though I think this may be a problem with the cm-12.1 source and not necessarily the device port itself.
This seems to be an issue with Trebuchet again, and using a different lock application fixes this.
I'm aware of this one, for now you can fix this by disabling Brightness Control in the settings ( Settings->Status Bar->Brightness Control).
This again might be an issue with the cm-12.1 source, though it'll need some checking to confirm.
I'm using Kernel Adiutor and frequency setting is fine. Did you try using a tunable governor like interactive? That may be the issue.
I'm aware of this, you can blame this on my bad arithmetic skills . I had set the wrong bit field mask for the button settings in the device frameworks.
I'll be pushing a fix addressing this shortly.
That depends on what the features are, if they're reasonable and within my capabilities, then yeah .
PS: I would appreciate any help I can get, and if you have any coding skills and time to compile builds, you can help me polish up the device port.
Thanks!
Click to expand...
Click to collapse
1) Aww man I love using Trebuchet, I like to keep my install as small as possible so I'm not one for installing additional apps. I'm a resource junkie though, so its just a matter of personal preference.
2) Again, I'm not an expert, but I suspect it might be the device port. Previously, I've had an unofficial version of CM12.1 installed on a Galaxy Tab 3 as well as a CM12.1 based Pac-rom installed on a Galaxy S4. I'm not sure if this is something those developers corrected on their own or not when building their ROMs, so it could be the source. That's the best of my knowledge on the topic.
3) Will do for the brightness slider, but again, it isn't something I experienced on the other devices with CM12.1 and the sister project.
4) Yeah I played around with the governors and tried all of them. They all list 0MHz as the only option. Maybe its a CPU hotplug issue? I didn't try playing around with those so I'll have to get back to you on that one.
5) Look forward to the update I have a question regarding it though. I'm really familiar with updating custom ROMs through recovery using the zip file format, but this is the first time I'm using Odin to do the job. Will flashing an update with Odin this way cause a factory reset? Or will it update as expected?
6) A couple more graphical hiccups I remembered. The blackout also happens when going to About Phone>Status. In About Phone, the device field says unknown (doesn't bother me, I just don't know if its significant or not), the illumination for the hardware buttons isn't working (I usually keep them off to save battery anyways, but someone out there probably uses it). And finally, when switching recents by holding the home button, only the title bars of the individual apps are viewable. The content of the windows themselves is completely transparent so it looks like a series of floating title bars.
(Apologies if some of these features are already included, I didn't get the opportunity to check, I just think they're awesome)
Feature requests:
1) When phone is off and charging, percentage is displayed inside battery symbol.
2) CPU and GPU undervolting built into the kernel. These custom ROMs are much better than the stock ROM in terms of functionality, but the battery life on the stock Samsung experience is no joke.
3) If possible, more steps for CPU frequency adjustments, every 100MHz or so. I remember the stock ROM had limited options. My S4 is the example I'm going to use here, it has a step for every 108MHz.
4) USB fast charging, aka setting USB to "charge only".
5) Wakelock Blocker. Its built into the latest Resurrection Remix for the S4, not sure if that could be of viable use to you. It'll certainly help out with battery improvements.
6) Boot Manager. Decide which apps get to start at boot. Its built into Marshmallow and an xposed module also exists for this purpose, so really low priority on this one, for me at least.
7) This one is a doozy. Absolutely the one I care most about, but most likely asking for too much. USB tethering. Already exists, I know, but not the way I hope it to. I have an old WRT54G router with DD-WRT installed. My goal is basically this: Phone's network connection>USB Tether>Micro-USB-LAN adapter>WAN port of router. In this sense, the phone would be acting as the modem in a regular home network. I know its possible to do this if the router has a USB port, but mine doesn't, and I also know its possible if you have an intermediate device that bridges the connections for you. Like a laptop, PC, or raspberry pi. Cost efficiency as a student is what I'm working towards though, so this one is a wishlist request.
Ps. The only coding skills I have are from high school's Visual Basic and HTML, truly beginner stuff, and that was about 10 years ago. I'm running Ubuntu on a core i5-2500k with 16GB of RAM and about a terabyte of space though, so compiling is definitely a possibility with some instructions.
Pbotelho said:
5) Look forward to the update I have a question regarding it though. I'm really familiar with updating custom ROMs through recovery using the zip file format, but this is the first time I'm using Odin to do the job. Will flashing an update with Odin this way cause a factory reset? Or will it update as expected?
Click to expand...
Click to collapse
Nope, this should be pretty much the same as flashing a zip from recovery. If you modified the system partition though (like by flashing GApps for example) your changes will be lost.
Pbotelho said:
6) A couple more graphical hiccups I remembered. The blackout also happens when going to About Phone>Status. In About Phone, the device field says unknown (doesn't bother me, I just don't know if its significant or not), the illumination for the hardware buttons isn't working (I usually keep them off to save battery anyways, but someone out there probably uses it). And finally, when switching recents by holding the home button, only the title bars of the individual apps are viewable. The content of the windows themselves is completely transparent so it looks like a series of floating title bars.
Click to expand...
Click to collapse
I fixed this in the device tree, once I've built a new image this should be corrected.
Pbotelho said:
(Apologies if some of these features are already included, I didn't get the opportunity to check, I just think they're awesome)
Feature requests:
1) When phone is off and charging, percentage is displayed inside battery symbol.
Click to expand...
Click to collapse
I'll be looking into this one.
Pbotelho said:
2) CPU and GPU undervolting built into the kernel. These custom ROMs are much better than the stock ROM in terms of functionality, but the battery life on the stock Samsung experience is no joke.
Click to expand...
Click to collapse
I'm still using the stock kernel in my builds, once the builds are stable I'll start compiling the kernel from source and I'll see if I can do something about this.
Pbotelho said:
3) If possible, more steps for CPU frequency adjustments, every 100MHz or so. I remember the stock ROM had limited options. My S4 is the example I'm going to use here, it has a step for every 108MHz.
Click to expand...
Click to collapse
According to the configurations, this is already how it is.
PS: I changed the governor under Kernel Adiutor to performance from interactive and switched back, and became unable to change the frequencies (like you were experiencing). I'll need to play around more with this to see why.
Pbotelho said:
4) USB fast charging, aka setting USB to "charge only".
Click to expand...
Click to collapse
This is already available under the Settings->Storage->USB Computer Connection menu
Pbotelho said:
5) Wakelock Blocker. Its built into the latest Resurrection Remix for the S4, not sure if that could be of viable use to you. It'll certainly help out with battery improvements.
6) Boot Manager. Decide which apps get to start at boot. Its built into Marshmallow and an xposed module also exists for this purpose, so really low priority on this one, for me at least.
Click to expand...
Click to collapse
Not sure I could do this, I'll check.
Pbotelho said:
7) This one is a doozy. Absolutely the one I care most about, but most likely asking for too much. USB tethering. Already exists, I know, but not the way I hope it to. I have an old WRT54G router with DD-WRT installed. My goal is basically this: Phone's network connection>USB Tether>Micro-USB-LAN adapter>WAN port of router. In this sense, the phone would be acting as the modem in a regular home network. I know its possible to do this if the router has a USB port, but mine doesn't, and I also know its possible if you have an intermediate device that bridges the connections for you. Like a laptop, PC, or raspberry pi. Cost efficiency as a student is what I'm working towards though, so this one is a wishlist request.
Click to expand...
Click to collapse
I don't quite understand what you mean by this, how does it differ from the normal USB tethering?
Pbotelho said:
Ps. The only coding skills I have are from high school's Visual Basic and HTML, truly beginner stuff, and that was about 10 years ago. I'm running Ubuntu on a core i5-2500k with 16GB of RAM and about a terabyte of space though, so compiling is definitely a possibility with some instructions.
Click to expand...
Click to collapse
If you can't code, that's fine, you could set up a build environment on your computer for creating images from the source.
vince2678 said:
Nope, this should be pretty much the same as flashing a zip from recovery. If you modified the system partition though (like by flashing GApps for example) your changes will be lost.
I fixed this in the device tree, once I've built a new image this should be corrected.
I'll be looking into this one.
I'm still using the stock kernel in my builds, once the builds are stable I'll start compiling the kernel from source and I'll see if I can do something about this.
According to the configurations, this is already how it is.
PS: I changed the governor under Kernel Adiutor to performance from interactive and switched back, and became unable to change the frequencies (like you were experiencing). I'll need to play around more with this to see why.
This is already available under the Settings->Storage->USB Computer Connection menu
Not sure I could do this, I'll check.
I don't quite understand what you mean by this, how does it differ from the normal USB tethering?
If you can't code, that's fine, you could set up a build environment on your computer for creating images from the source.
Click to expand...
Click to collapse
Sounds awesome, I'll flash it as soon as possible and continue testing it for you.
I uploaded a logcat to the other thread in development. The performance governor is set up as the default for me so I'm set up with that situation from the get go.
It technically isn't different from regular USB tethering, but it seems that no one has done it successfully before. There are adapters that you can use to provide a wired Ethernet connection to an android device over micro USB, but no one has been able to do it the other way around. Google results don't turn up any answers.
And I'm willing to learn how to code, but I fear that I may slow you down with this project as I get past the learning curve. That being said, I can definitely set up a build environment and compile it from source for you. That'll be a learning experience on its own. Just point me towards a noob guide and I'll get it done.
Pbotelho said:
Sounds awesome, I'll flash it as soon as possible and continue testing it for you.
I uploaded a logcat to the other thread in development. The performance governor is set up as the default for me so I'm set up with that situation from the get go.
It technically isn't different from regular USB tethering, but it seems that no one has done it successfully before. There are adapters that you can use to provide a wired Ethernet connection to an android device over micro USB, but no one has been able to do it the other way around. Google results don't turn up any answers.
And I'm willing to learn how to code, but I fear that I may slow you down with this project as I get past the learning curve. That being said, I can definitely set up a build environment and compile it from source for you. That'll be a learning experience on its own. Just point me towards a noob guide and I'll get it done.
Click to expand...
Click to collapse
The USB tethering thing sounds interesting, though I would need to have one of the adapters to test that, and time at hand as well.
As for the build environment, the best source of information is the CM wiki. You can look at these links below on how to get started:
https://wiki.cyanogenmod.org/w/Development#Learning_To_Build_CM
https://wiki.cyanogenmod.org/w/Doc:_Building_Basics
https://docs.omnirom.org/Setting_Up_A_Compile_Environment
https://wiki.cyanogenmod.org/w/Build_for_captivatemtd
http://jira.omnirom.org/browse/OMNI-1263
http://forum.xda-developers.com/showthread.php?t=2329228
The guides above are just outlines to detail the general build process - you will need to do things slightly differently from the steps above to get the proper source and device trees.
The attached local_manifest can be used with repo when obtaining the cm-12.1 source.
Remember you'll be getting the cm-12.1 source - not anything else.
vince2678 said:
The attached local_manifest can be used with repo when obtaining the cm-12.1 source.
Remember you'll be getting the cm-12.1 source - not anything else.
Click to expand...
Click to collapse
So if I add in your device tree and provide a toolchain, I should be good to go? (I think so.)
Thanks!!
EDIT: Not so fast! I'll have to find a kernel as well.
Pbotelho said:
Edit: 5) when using kernel adiutor to try to adjust the CPU frequencies, the only option that comes up for both minimum and maximum is 0MHz. The button seems to work as well, bringing the clock max speed down to 0 for a split second before it reverts to a a maximum of 200MHz. Adjusting the governor after the fact won't restore the maximum, seems only a reboot will get it done. I'm slightly amazed to be honest as before on Touchwiz, it was impossible to get it to hold onto a lower maximum. It would jump all over the place as it pleased.
Click to expand...
Click to collapse
I've test Kernel Adiutor and I too got the O MHz only window for both as the only option. Though Now I wonder if it is because I used the latest beta Kernel Adiutor, I'll further check with the normal stable version. Pretty sure it'll fix it if it worked normally for Vinc. --- Update; As strange as it might look while re opening kernel adi to take a screenshot, the list of normal MHz values is there and working properly.. Strange.. Magic? Huh technology, you're so unpredictable.
Zippy Dufus said:
So if I add in your device tree and provide a toolchain, I should be good to go? (I think so.)
Thanks!!
EDIT: Not so fast! I'll have to find a kernel as well.
Click to expand...
Click to collapse
Hi Zippy,
The kernel source was included there as well (it's just a dummy source so that the build can get the necessary source files for libraries which need them). The build still uses the default prebuilt kernel though.
vince2678 said:
Hi Zippy,
The kernel source was included there as well (it's just a dummy source so that the build can get the necessary source files for libraries which need them). The build still uses the default prebuilt kernel though.
Click to expand...
Click to collapse
As an experiment, why don't you try downloading the G530H ROM, unzip, take the boot.img, and flash it over top of your stock kernel? See if it boots and how it performs.
Meanwhile, I plan to hack at putting together complete manifest, possibly with the G530H kernel and my Linaro 4.9 toolchain and see if I can build a complete ROM.
Have you extracted the firmware?
However, I don't want to flash anything until I see your ROM's modem working because it is my daily driver. But I'm keen though!!
I've managed to download the stock ROM from SamMobile but I'm now thinking of going straight to your ROM once it is a bit more complete and stable.
Hello, everyone!
So as we all know, any developments to do with the Yoga Book seem to be very slow.
Considering a decent number of us have experimented with the Yoga Book, I thought it'd be a good idea to make a centralised place for methods that have worked for people, so we can all have a go and hopefully obtain similar results.
So the idea would hopefully end up being something along the lines of my Megathread (which is now in General).
I guess this is where I get the ball rolling...
Most Promising Leads for Installing Android (1/12/17)
I have tried to install Bliss OS, but with not much luck. Once you get passed the GRUB screen it says there was an emergency error of some kind and reboots the device.
https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
I found that his updated installer (v25.0004) doesn't work at all, but the latest version from the original developer worked fine, linked below:
https://forum.xda-developers.com/android/software/winapp-android-x86-installer-uefi-t3222483
I followed the following methods, all which resulted in a failed attempt, but the one with the most success was the first one:
- Easy install for Bliss-x86 UEFI/ESP
- For Bliss-x86 USB based installs
- Custom install for Bliss-x86 UEFI/ESP
My next attempt will be with Phoenix OS.
OLD INFO (as of 1/12/17)
Edit: I managed to replicate my situation twice. So I now have a method. Will post more info soon.
Okay... so if you want to get into Remix OS (knowing it's only temporary), here's how to replicate what I did. But make sure you have the following tools:
- USB keyboard & microUSB to USB adaptor (for the keyboard)
- Remix OS (I'm using the 64-bit version)
- A bit of time
What I did:
- Install Remix OS (doesn't matter what size you choose; 8, 16 or 32) on your C: Drive (main Local Disk) with the bundled installer
- Reboot when it finishes (via the dialog box, don't reboot any other way... it won't work properly)
- Give it about 10-15 minutes on the first boot. It'll be "stuck" at this Android-looking thing (mine's all glitched up and stuff)
- When it's done it'll show a black screen, and the Pencil icon to switch the Halo Keyboard on/off will stop turning on&off, it'll instead just stay on 100% of the time
- Reboot again, again choosing to boot into Remix OS
- As soon as you choose Remix OS, you NEED to hold the escape (ESC) key!!! If you don't do this, you'll have to start from scratch
- If you did it right, it'll come up with a couple lines of code, and then after a couple second it'll say "ANDROID" underneath the code, and everything will load up
- Everything should be in portrait-mode, but you should have no graphical glitches now, and should see the setup screen
- The touch-screen still shouldn't work here, you need to use the keyboard to navigate through the setup. If the Wi-Fi bit isn't connecting properly, do that later (just skip that step, up the top right). I left Google Play Services enabled, it doesn't matter, it won't ask for your information unless you open a Google App.
- When you finish the installation, everything should work (except the Halo Keyboard of course)
- To make Remix OS take up the whole screen instead of just the middle... go to the Settings App -> Remix OS Settings (whatever the top one is) -> Always show landscape thingo, toggling this off will make it use the whole screen instead of that little square in the middle.
This is far as I've gotten. I've tried getting USB Debugging to work, but it doesn't want to work. Bluetooth doesn't work for me, nor does changing the brightness. I wouldn't lock the tablet either, sometimes that doesn't work. Also don't try use the Google Play Store, because when you finish entering your information, it'll likely crash and you'll have to start over again. Rebooting will reset everything.
OLD INFO (as of 30/03/17)
I've had some random luck (as told in my recent post, I'll quote it here) with Remix OS.
I had a minor breakthrough last night. I don't know how I managed it though.
So Remix OS has an installer application you can run from within Windows. I used that, then rebooted into Remix OS. The first boot was met with just lots of graphical errors, but when I rebooted again into Remix OS, it booted perfectly. Android was running smoothly, everything worked (the touch screen, Wi-Fi, etc. - but not the Halo Keyboard). However, when I rebooted again, it stopped working. I was not able to successfully replicate that again - even with many re-installations of Remix OS.
I'll continue to mess with it, but if anyone has Windows and wants to attempt getting Android on it, this may be a viable method they can try. But of course, it's not perfect so don't do anything you don't know how to do just yet.
Click to expand...
Click to collapse
Somehow I managed to get it working, but only temporarily.
If I'm able to replicate this situation again, I may be able to install the Stock ROM alongside Windows 10. However, I don't have all the time in the world, so this may take a long while.
General Yoga Book Information:
To my knowledge, there are two versions of the Yoga Book, each with two sub-versions for the OS:
1.) YB1-X9aF - this is the Wi-Fi version
2.) YB1-X9aL - this is the LTE/4G version
Where the "a" between the 9 and the F/L is either a zero or a one, depending on the installed OS (Android: 0, Windows 10: 1)
The SIM card is a Nano-SIM with 3G capability.
Other than that, all Yoga Book devices share the following specifications:
- 10.1 inch IPS display, of resolution 1920x1200
- Intel Atom x5-Z8550 processor, which:
----+ Has an architecture of x86_64 (ie. 64-bit)
----+ Core base clock of 1.44 gigahertz
----+ Core boost clock of 2.4 gigahertz
----+ 4 cores and 4 threads
- Battery capacity of 8500 milliampere hours
- On-board storage of 64 gigabytes of solid-state storage (SSD)
- 4 gigabytes of random-access memory (RAM)
- A microSD card slot capable of up to 128 gigabytes of storage
- Two camera's, one above the display and one on the keyboard
- Wi-Fi (802.11 ac) and Bluetooth (v4)
- 3.5 millimetre headphone jack
- Micro-USB 2.0 OTG port
- Micro-HDMI port
Any information I put about my experience will be with the YB1-X91F version (aka Windows 10 Wi-Fi)
Dual OS or Switching the pre-installed one:
I have attempted getting Android on my Yoga Book, and completely deleting everything Windows. This has obviously not gone very well for me.
Version's I've tried:
- Android x86 6.0-r1
- Android x86_64 6.0-r1
- Android x86 6.0 20160129
- Android Nougat x86 20160902
- Android 4.2.2-r1 "ia3-core mesa-userdebug"
- Remix OS (32 & 64-bit)
The one I personally have had the most success with (by that I mean I've gotten it to display the Android set-up screen with no touch-input) is the 32-bit version of 6.0-r1 (so the first one on my list above).
Other OS's that I've tried/succeeded in running:
- GParted Live 0.28.1-2 i686 (although, the whole screen is in portrait mode)
- Ubuntu 16.10 Desktop (amd64 - so it obviously didn't work)
- Windows 10 with AMIDuOS on-top (honestly wasn't that great)
Currently testing:
- Windows 10 with BlueStacks on-top
TLDR:
If you're on the Windows 10 version of the Yoga Book, I cannot recommend attempting to install Android on it (even with a dual-boot) at this current time. This will probably change if x86 Android update their ROM/Image, though.
I'm currently testing the practicality of putting BlueStacks on-top of Windows 10, which is a player that allows you to run Android apps. The only thing I'm keeping an eye on is battery life (since it'll be doing background tasks for Windows AND Android). However, you will at least have full functionality - especially with the Halo Keyboard.
Ehh... BlueStacks isn't that great after all. Personally I'd stick with Windows apps if you need something like that.
I will add more info and links later on, I just wanted to get this out before hitting the hay. Australia's time difference sucks.
AmiDuOS works for me but the keyboard language cannot be changed somehow.
nan0s7 said:
Hello, everyone!
So as we all know, any developments to do with the Yoga Book seem to be very slow.
Considering a decent number of us have experimented with the Yoga Book, I thought it'd be a good idea to make a centralised place for methods that have worked for people, so we can all have a go and hopefully obtain similar results.
So the idea would hopefully end up being something along the lines of my Megathread (which is now in General).
I guess this is where I get the ball rolling...
General Yoga Book Information:
To my knowledge, there are two versions of the Yoga Book, each with two sub-versions for the OS:
1.) YB1-X9aF - this is the Wi-Fi version
2.) YB1-X9aL - this is the LTE/4G version
Where the "a" between the 9 and the F/L is either a zero or a one, depending on the installed OS (Android: 0, Windows 10: 1)
Any information I put about my experience will be with the YB1-X91F version (aka Windows 10 Wi-Fi)
Dual OS or Switching the pre-installed one:
I have attempted getting Android on my Yoga Book, and completely deleting everything Windows. This has obviously not gone very well for me.
Version's I've tried:
- Android x86 6.0-r1
- Android x86_64 6.0-r1
- Android x86 6.0 20160129
- Android Nougat x86 20160902
- Android 4.2.2-r1 "ia3-core mesa-userdebug"
- Remix OS (32 & 64-bit)
The one I personally have had the most success with (by that I mean I've gotten it to display the Android set-up screen with no touch-input) is the 32-bit version of 6.0-r1 (so the first one on my list above).
Other OS's that I've tried/succeeded in running:
- GParted Live 0.28.1-2 i686 (although, the whole screen is in portrait mode)
- Ubuntu 16.10 Desktop (amd64 - so it obviously didn't work)
Currently testing:
- Windows 10 with AMIDuOS on-top
TLDR:
If you're on the Windows 10 version of the Yoga Book, I cannot recommend attempting to install Android on it (even with a dual-boot) at this current time. This will probably change if x86 Android update their ROM/Image, though.
I'm currently testing the practicality of putting AMIDuOS on-top of Windows 10, which will be like having an app that just runs Android. The only thing I'm keeping an eye on is battery life (since it'll be doing background tasks for Windows AND Android). However, you will at least have full functionality - especially with the Halo Keyboard.
I will add more info and links later on, I just wanted to get this out before hitting the hay. Australia's time difference sucks.
Click to expand...
Click to collapse
deepsync said:
AmiDuOS works for me but the keyboard language cannot be changed somehow.
Click to expand...
Click to collapse
Have you tried different keyboard apps?
Well on screen keyboard works fine. I just can't change the key mappings of the Halo keyboard to my German keyboard. English may work as that seems to be the default.
deepsync said:
Well on screen keyboard works fine. I just can't change the key mappings of the Halo keyboard to my German keyboard. English may work as that seems to be the default.
Click to expand...
Click to collapse
Hmm you're right. I've tried switching to a Polish keyboard in AMIDuOS, and it doesn't work at all. Although I didn't try switching the keyboard language in Windows, and then using AMIDuOS. I'm kind of optimistic that that method may work, so possibly give that a try if you haven't yet?
Are you gonna try again if you can get your hands on Lenovo's stock Yoga Book ROM?
sawyerbenjamin said:
Are you gonna try again if you can get your hands on Lenovo's stock Yoga Book ROM?
Click to expand...
Click to collapse
I do actually have a copy of the stock ROM, but not in a format I can put on the Yoga Book without the Android bootloader installed. The versions of Android I tested were ones that include the files for the bootloader and such, but they didn't want to work properly.
If something new comes up, or I get another idea, I will for sure try again. I prefer to use Android over Windows, any day.
I had a minor breakthrough last night. I don't know how I managed it though.
So Remix OS has an installer application you can run from within Windows. I used that, then rebooted into Remix OS. The first boot was met with just lots of graphical errors, but when I rebooted again into Remix OS, it booted perfectly. Android was running smoothly, everything worked (the touch screen, Wi-Fi, etc. - but not the Halo Keyboard). However, when I rebooted again, it stopped working. I was not able to successfully replicate that again - even with many re-installations of Remix OS.
I'll continue to mess with it, but if anyone has Windows and wants to attempt getting Android on it, this may be a viable method they can try. But of course, it's not perfect so don't do anything you don't know how to do just yet.
nan0s7 said:
However, when I rebooted again, it stopped working. I was not able to successfully replicate that again - even with many re-installations of Remix OS.
Click to expand...
Click to collapse
Why so much headache? If you are having the Windows Version how often do you really miss Android? What Apps are not present under Windows? I am absolutely not a gamer, that's probably why I don't really have the need for Android... Anyhow, why installing Remix OS and risking to mess up with the Bootloader? I tried NOX Player and KO Player. The last one works very smooth on an Atom Processor. KO Player even let you go Fullscreen. Everything works out off the box as it's just a layer, Halo Keyboard, Pen, just all works and pretty decent. Many low equipped Android Tablets perform slower...
jamespmi said:
Why so much headache? If you are having the Windows Version how often do you really miss Android? What Apps are not present under Windows? I am absolutely not a gamer, that's probably why I don't really have the need for Android... Anyhow, why installing Remix OS and risking to mess up with the Bootloader? I tried NOX Player and KO Player. The last one works very smooth on an Atom Processor. KO Player even let you go Fullscreen. Everything works out off the box as it's just a layer, Halo Keyboard, Pen, just all works and pretty decent. Many low equipped Android Tablets perform slower...
Click to expand...
Click to collapse
I've got Windows machines all around me. Which is... tolerable. But it's more that I just enjoy having Android on my device, and I do really enjoy messing with tech. I've gotten so close to getting Android on my tablet, it's just a project to really satisfy my time with. Plus, with Android I have more control over everything
nan0s7 said:
I've gotten so close to getting Android on my tablet, it's just a project to really satisfy my time with. Plus, with Android I have more control over everything
Click to expand...
Click to collapse
As a techie achievement I totally understand. But I doubt you will get all the drivers working properly. Halo Keyboard, Wacom & AnyPen for example. But good luck... On the other hand I have to insist: Windows gives you more control over everything... lol...
jamespmi said:
As a techie achievement I totally understand. But I doubt you will get all the drivers working properly. Halo Keyboard, Wacom & AnyPen for example. But good luck... On the other hand I have to insist: Windows gives you more control over everything... lol...
Click to expand...
Click to collapse
Once I get some sort of Android on it, that will allow me to flash a ROM that has all the drivers in it. And it depends what you define control as...
nan0s7 said:
Once I get some sort of Android on it, that will allow me to flash a ROM that has all the drivers in it. And it depends what you define control as...
Click to expand...
Click to collapse
Hey dude,
It looks like this thread hasn't had a great deal of attention lately, which is kinda sad. I figured it would be a really tricky endeavour anyway.
Anywho, just letting you know that if you do ever figure this out, there's one chick in Australia whom will owe you her eternal thanks.
Seriously, I tried to Remix, I tried to x86, but all it got me was a trip to Harvey Norman and a 2-5 week waiting period to get my book back. If you get a flashable Android ROM for this thing you will be my favourite person in the whole world ever. :laugh:
Melliejoy said:
Hey dude,
It looks like this thread hasn't had a great deal of attention lately, which is kinda sad. I figured it would be a really tricky endeavour anyway.
Anywho, just letting you know that if you do ever figure this out, there's one chick in Australia whom will owe you her eternal thanks.
Seriously, I tried to Remix, I tried to x86, but all it got me was a trip to Harvey Norman and a 2-5 week waiting period to get my book back. If you get a flashable Android ROM for this thing you will be my favourite person in the whole world ever. :laugh:
Click to expand...
Click to collapse
Haha damn sounds like a.... fun time
But yeah, there hasn't been much progress. I mean you could always run an emulator on-top of Windows if you NEED an Android tablet.
nan0s7 said:
Haha damn sounds like a.... fun time
But yeah, there hasn't been much progress. I mean you could always run an emulator on-top of Windows if you NEED an Android tablet.
Click to expand...
Click to collapse
I didn't NEED Android until I discovered Freeview FV, so I could watch Highway Patrol without taking the TV from my hubby. Between that and the few apps I use for D&D, I'm sort of regretting going with the Windows version.
I can't really do anything until I get it back, anyway. The furthest I got was successfully installing Remix, but it wouldn't accept any external input when trying to select it from the boot menu. I guess I could use an emu, but it's not as good as the real thing.
Melliejoy said:
I didn't NEED Android until I discovered Freeview FV, so I could watch Highway Patrol without taking the TV from my hubby. Between that and the few apps I use for D&D, I'm sort of regretting going with the Windows version.
I can't really do anything until I get it back, anyway. The furthest I got was successfully installing Remix, but it wouldn't accept any external input when trying to select it from the boot menu. I guess I could use an emu, but it's not as good as the real thing.
Click to expand...
Click to collapse
Yeah I wish I had gotten the Android version, but I got mine for a reduced price... so I can't complain too much ;P
Yeah... none of the emus are perfect anyway. I'm hoping that a new version of x86 Android or Remix OS will allow me to get ADB to work, so I can then flash Android. But I'm not holding my breath for that.
Any recent experimenting with Remix? Im about to download it and see what I can gather. Too bad there's about zero android devs on this thing. Im sure a custom Kernel under RemixOS would be fix most of its problems.
sawyerbenjamin said:
Any recent experimenting with Remix? Im about to download it and see what I can gather. Too bad there's about zero android devs on this thing. Im sure a custom Kernel under RemixOS would be fix most of its problems.
Click to expand...
Click to collapse
Nah I haven't done anything recently. But if you're having trouble getting things booted use my method (assuming it still works now) and I guess see what you can do
nan0s7 said:
I do actually have a copy of the stock ROM, but not in a format I can put on the Yoga Book without the Android bootloader installed. The versions of Android I tested were ones that include the files for the bootloader and such, but they didn't want to work properly.
If something new comes up, or I get another idea, I will for sure try again. I prefer to use Android over Windows, any day.
Click to expand...
Click to collapse
Is your stock ROM for YB1-X90F or YB1-X90L?
ljbha007 said:
Is your stock ROM for YB1-X90F or YB1-X90L?
Click to expand...
Click to collapse
I have both. Got them from easy-firmware (had to pay for the X90F version).
They're not "ROMS" so much as they are just a way to replace Android with this particular version. So it comes with all the .img files for each partition you'd normally see (system, boot, etc.) and some scripts to use with the Intel flasher program thingo.
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.