Hi,
I currently own a Touch pad running Cyanogen Mod, Version 4.2.2 which I installed in 2013.
I'm confused about upgrading as their is many ROMS to choose from.
Can someone recommend me a stable rom with the latest version on android available for the touchpad, something that has everything working.
preve83 said:
Hi,
I currently own a Touch pad running Cyanogen Mod, Version 4.2.2 which I installed in 2013.
Click to expand...
Click to collapse
A lot changed since 2013.
preve83 said:
I'm confused about upgrading as their is many ROMS to choose from.
Click to expand...
Click to collapse
Does the Tablet has WebOS, or only Android?
New ROMS requires the system partition to be larger.
preve83 said:
Can someone recommend me a stable rom with the latest version on android available for the touchpad, something that has everything working.
Click to expand...
Click to collapse
A ROM that all works, Bluetooth, Stable Wifi and camera is:
Evervolv 7.1.2 Android Nougat
My recommendation is to set the system partition to allow the installation of newer ROMS. Then any Android version can be flash until 9.
The Automatic_Wipe_All_and_Create_Android_with _Swap
Can be flash and will take care of everything, follow this guide, it also provides all the links to all ROMS.
https://forum.xda-developers.com/t/...all-android-roms-with-swap-partition.3901773/
Any ROM can be flash ( install ), just wipe everything using TWRP 3.2 download zip files, copy to tablet and flash.
@HP_TOUCHPAD , Hello, I still can't believe we have support for the touch pad....
I flashed Evervolv 7.1.2 in my 1gb rab (black touchpad) and it didn't work quite well, it would often crash and every app would either become slow and unresponsive or simply crash..
The ram in my tp is just around some 830 mb and I noticed that the OS would use up as much as 220 to 250 mb. The touch pad was dead a long ago and I revived it back today, and I am planning to delete the Evervolv ROM and flash something else that wouldn't stuck or crash a lot, I only want to use it for Youtube and google searches(if not google app, maybe at least internet browsing using a browser).
What rom would you recommend that's not floppy and laggy and at the same time the one that can support Youtube and Internet browser ?
Now I know you said use the Evervolv 7.1.2, but I think I have either missed something while I was flashing or I downloaded an experimental rom, the Touchpad would literally become unresponsive to the touch(well ironically it's named "touchpad"), and a lot of times just drain the battery.
And, Yes I still have the web OS with the Evervolv9it was my first time flashing a rom so I let the Web OS stay as a fail safe, coz I was 15 when I first flashed a custom rom to the touchpad).
I just want to give it to my mom, so I want it to work smooth and stable(more importantly, I just want it to run youtube in a stable and smooth state)....
LN11211 said:
@HP_TOUCHPAD , Hello, I still can't believe we have support for the touch pad....
Click to expand...
Click to collapse
I can not believe that my original touchpad from the fire sale still has a battery capacity as NEW, that one I do not use much. But I have others that do specially as a music player, yes is louD ! Best device that I will ever have.
LN11211 said:
I flashed Evervolv 7.1.2 in my 1gb rab (black touchpad) and it didn't work quite well, it would often crash and every app would either become slow and unresponsive or simply crash..
Click to expand...
Click to collapse
Did you get the ROM from this guide?
https://forum.xda-developers.com/t/...all-android-roms-with-swap-partition.3901773/
You are using WebOS, there is no need to do the Automatic Wipe All.
A lot has changed since 2011, is 2021 now and all ROMs have more memory up to the full 1GB and the highest CPU frequency.
LN11211 said:
The ram in my tp is just around some 830 mb and I noticed that the OS would use up as much as 220 to 250 mb. The touch pad was dead a long ago and I revived it back today, and I am planning to delete the Evervolv ROM and flash something else that wouldn't stuck or crash a lot, I only want to use it for Youtube and google searches(if not google app, maybe at least internet browsing using a browser).
Click to expand...
Click to collapse
Dead long ago and it came back, it almost sound as the new Messiah that everyone has been waiting for !
It all depends on the kernel version, the MaXtreme 1836 is the fastest with more RAM.
There are other alternatives to youtube and the best browser to use is : https://www.bromite.org/
youtube alternatives apps.
LN11211 said:
What rom would you recommend that's not floppy and laggy and at the same time the one that can support Youtube and Internet browser ?
Click to expand...
Click to collapse
Evervolv 7.1.2, ( it all depends on the Kernel version that is use ) Do not use it with the original kernel, look at the guide of the different options.
LN11211 said:
Now I know you said use the Evervolv 7.1.2, but I think I have either missed something while I was flashing or I downloaded an experimental rom, the Touchpad would literally become unresponsive to the touch(well ironically it's named "touchpad"), and a lot of times just drain the battery.
Click to expand...
Click to collapse
If that battery was not in use for a long time, it may actually have less capacity left.
LN11211 said:
And, Yes I still have the web OS with the Evervolv9it was my first time flashing a rom so I let the Web OS stay as a fail safe, coz I was 15 when I first flashed a custom rom to the touchpad).
Click to expand...
Click to collapse
Flashing is now done with TWRP 3.2 and all ROMs can be flash easily, working 100% all the time.
LN11211 said:
I just want to give it to my mom, so I want it to work smooth and stable(more importantly, I just want it to run youtube in a stable and smooth state)....
Click to expand...
Click to collapse
The HP Touchpad works perfectly as a streaming device, either for music or video. But there are ways to set it up to get the most out of it that will allow it to perform. It can not be compare to an actual device in performance or user experience.
Is a device that can be fully customized to fit your specific needs. Flashing the ROM properly with the best kernel option is as important as the type of Apps. The Android options are too many and the user needs to experiment on it's own.
I also have a Touchpad with 4.2.2. that I installed on it and I'm wondering if there's any advantage of upgrading to another newer rom. The main issue here is this device is old and not very fast and so maybe its best to keep it on 4.2.2, unless someone can tell me that a newer rom would make this faster. New features in newer roms don't matter much if the speed becomes slower and if the OS takes more RAM etc. On top of that some people are reporting issues with the stability of a newer rom (change the kernel or not).
It doesn't look like its possible to have a stable rom that is newer and has more features and provides us a faster user interface.
So.... does any one know of any advantages of using a newer ROM on this device?
alan-31 said:
I also have a Touchpad with 4.2.2. that I installed on it and I'm wondering if there's any advantage of upgrading to another newer rom.
Click to expand...
Click to collapse
Android 4.2.2 is no longer supported by google. With a never ROM everything works, the ones that supports all the hardware is evervolv 7.1.2.
alan-31 said:
The main issue here is this device is old and not very fast and so maybe its best to keep it on 4.2.2, unless someone can tell me that a newer rom would make this faster.
Click to expand...
Click to collapse
Yes it is an old device, but what matters are the settings and how is been use.
With the settings from this guide: https://forum.xda-developers.com/t/...all-android-roms-with-swap-partition.3901773/
The cpu can be set in all the ROMs up to 1836 ( that is for each core ). All the ROM RAM is optimized to use almost the full 1GB, versus the original that can only use a little over 800 MB.
What makes the Tablet slow are the google services ( play store ).
The tablet can be use with no gapps and set up to use bromite, newpipe and many other googles alternatives.
alan-31 said:
New features in newer roms don't matter much if the speed becomes slower and if the OS takes more RAM etc.
Click to expand...
Click to collapse
The features are provided by the hardware which is the same for all the ROMs, WiFi, Bluetooth, sound and camera.
New Android version use more RAM only if the play store is use, and the speed can be set the same to all the ROM.
alan-31 said:
On top of that some people are reporting issues with the stability of a newer rom (change the kernel or not).
Click to expand...
Click to collapse
All ROM posted on the mentioned guide are 100 % stable if the kernels use are the one listed.
Stability issues are due to users installing optimizing Apps to make things faster, which takes more RAM and create problems.
alan-31 said:
It doesn't look like its possible to have a stable rom that is newer and has more features and provides us a faster user interface.
Click to expand...
Click to collapse
Yes all ROMs are stable, Wifi works better until 7.1.2, it works on 8 and 9 but may not reconnect, but al depends on the user router.
alan-31 said:
So.... does any one know of any advantages of using a newer ROM on this device?
Click to expand...
Click to collapse
A newer ROM provides support from google and all new apps can be use. This has always been the same with all PC operating system, a 10 year old OS is not supported any longer and even a basic web browser will not work.
The same will happen when google stops supporting Android PIE, no more apps will run one it not even a web browser.
That could probably happen 10 years from now or sooner, by then the tablet could only be use as a local media player, for music, video or pictures.
Example: https://www.bromite.org/ The best full browser to use on the tablet with no need of the play store.
But it can only be use on Android Lollipop 5.0 and above (SDK21)
HP_TOUCHPAD said:
Android 4.2.2 is no longer supported by google. With a never ROM everything works, the ones that supports all the hardware is evervolv 7.1.2.
Yes it is an old device, but what matters are the settings and how is been use.
With the settings from this guide: https://forum.xda-developers.com/t/...all-android-roms-with-swap-partition.3901773/
The cpu can be set in all the ROMs up to 1836 ( that is for each core ). All the ROM RAM is optimized to use almost the full 1GB, versus the original that can only use a little over 800 MB.
What makes the Tablet slow are the google services ( play store ).
The tablet can be use with no gapps and set up to use bromite, newpipe and many other googles alternatives.
The features are provided by the hardware which is the same for all the ROMs, WiFi, Bluetooth, sound and camera.
New Android version use more RAM only if the play store is use, and the speed can be set the same to all the ROM.
All ROM posted on the mentioned guide are 100 % stable if the kernels use are the one listed.
Stability issues are due to users installing optimizing Apps to make things faster, which takes more RAM and create problems.
Yes all ROMs are stable, Wifi works better until 7.1.2, it works on 8 and 9 but may not reconnect, but al depends on the user router.
A newer ROM provides support from google and all new apps can be use. This has always been the same with all PC operating system, a 10 year old OS is not supported any longer and even a basic web browser will not work.
The same will happen when google stops supporting Android PIE, no more apps will run one it not even a web browser.
That could probably happen 10 years from now or sooner, by then the tablet could only be use as a local media player, for music, video or pictures.
Example: https://www.bromite.org/ The best full browser to use on the tablet with no need of the play store.
But it can only be use on Android Lollipop 5.0 and above (SDK21)
Click to expand...
Click to collapse
Some of this is just wrong. Yes, 4.4 isn't supported. But that doesn't mean you can't use it. YouTube v14 will run fine, so will NewPipe. You can use Google Chrome 80-something, and that works perfectly fine for browsing the web, it's still new enough to render almost everything properly. Bromite of that same version should work as well on 4.4. You can also use Yalp Store instead of Aurora to use 4.4 without Gapps. If apps are unsupported, you could download old versions from apkmirror, they usually still work fine, even the internet based ones.
Sanras said:
Some of this is just wrong. Yes, 4.4 isn't supported. But that doesn't mean you can't use it.
Click to expand...
Click to collapse
What makes a device to be functional is the Operating System. That is the reason we are in the XDA Web Site forum and not HP or WebOS. The Tablet can be use even with WebOS and many still do because they do not want to upgrade.
You can use it any way you want it, but is not the optimal or best way to get the full functionality that it can offer.
Sanras said:
YouTube v14 will run fine, so will NewPipe. You can use Google Chrome 80-something, and that works perfectly fine for browsing the web, it's still new enough to render almost everything properly. Bromite of that same version should work as well on 4.4. You can also use Yalp Store instead of Aurora to use 4.4 without Gapps. If apps are unsupported, you could download old versions from apkmirror, they usually still work fine, even the internet based ones.
Click to expand...
Click to collapse
Why try to work with old software when new ones are available and works perfectly with the Tablet?
On the news today, January 4 of 2022:
https://www.blackberry.com/us/en/support/devices/end-of-life
BlackBerry 7.1 OS and earlier, BlackBerry 10 software, BlackBerry PlayBook OS 2.1 and earlier versions, will no longer be available after January 4, 2022. As of this date, devices running these legacy services and software through either carrier or Wi-Fi connections will no longer reliably function, including for data, phone calls, SMS and 9-1-1 functionality.
https://en.wikipedia.org/wiki/BlackBerry_10
On 14 May 2013 BlackBerry OS 10.1 was launched.
The HP Touchpad was released July 1, 2011 (WebOS), is two years older than the BlackBerry released in 2013.
The HP Touchpad is 100% functional, due to the great job of many developers that got Android on it.
HP_TOUCHPAD said:
What makes a device to be functional is the Operating System. That is the reason we are in the XDA Web Site forum and not HP or WebOS. The Tablet can be use even with WebOS and many still do because they do not want to upgrade.
You can use it any way you want it, but is not the optimal or best way to get the full functionality that it can offer.
Why try to work with old software when new ones are available and works perfectly with the Tablet?
On the news today, January 4 of 2022:
https://www.blackberry.com/us/en/support/devices/end-of-life
BlackBerry 7.1 OS and earlier, BlackBerry 10 software, BlackBerry PlayBook OS 2.1 and earlier versions, will no longer be available after January 4, 2022. As of this date, devices running these legacy services and software through either carrier or Wi-Fi connections will no longer reliably function, including for data, phone calls, SMS and 9-1-1 functionality.
https://en.wikipedia.org/wiki/BlackBerry_10
On 14 May 2013 BlackBerry OS 10.1 was launched.
The HP Touchpad was released July 1, 2011 (WebOS), is two years older than the BlackBerry released in 2013.
The HP Touchpad is 100% functional, due to the great job of many developers that got Android on it.
Click to expand...
Click to collapse
4.x Android is simply faster than Android 7.1. That's why you would bother with using old builds of software on an outdated OS. No matter how optimized it is, or how much you overclock it, 7.1 will always be a heavier OS than 4.4. I've seen it before, and on low end devices, that speed difference really matters.
Essentially newer OS means more reliable apps, but worse performance.
Older OS = better performance, worse apps.
It all depends on what you prefer. For me, so long as that old OS is useable enough, I prefer the outdated but fast OS over the fully useable slow one.
Let's take another example: Say you have one laptop to use in 2022. You've got a netbook with a 1.6Ghz Intel Atom n280, and 1GB of RAM.
You *could* technically run Windows 10 on here if you wanted to. The hardware technically supports it. But is it a good idea? No, not at all. It's gonna be extremely slow and annoying to use. I'd rather run Windows XP on such a device, use Firefox 52.9ESR and deal with some broken webpages than use Windows 10 and a modern browser. At least with XP you're gonna have a fast and snappy computer, even if you have to use some old apps to get things done.
(Of course, this is hypothetical. The true best choice in this situation would be a Linux install with a simple X11 window manager or Windows 7 without transparency effects)
Sanras said:
4.x Android is simply faster than Android 7.1. That's why you would bother with using old builds of software on an outdated OS. No matter how optimized it is, or how much you overclock it, 7.1 will always be a heavier OS than 4.4. I've seen it before, and on low end devices, that speed difference really matters.
Click to expand...
Click to collapse
No, Android 4.x uses an old kernel, Android 7.1 and newer are built with a newer kernel providing better support for the hardware and software.
Android is not the native operating system for the Tablet, earlier version of Android had issues than with the time was improve.
Sanras said:
Essentially newer OS means more reliable apps, but worse performance.
Older OS = better performance, worse apps.
Click to expand...
Click to collapse
It all depends on the settings and how is set up, but newer OS provides better support. Software is what makes the hardware to work.
Devices are not mechanical machines that works on the principal of physical parts, but works on code, software.
Sanras said:
It all depends on what you prefer. For me, so long as that old OS is useable enough, I prefer the outdated but fast OS over the fully useable slow one.
Click to expand...
Click to collapse
Check this guide and see that all ROMs have the same settings, optimized to use the full 1GB of RAM and CPU speed plus swap partition.
Any original ( stock ) Android ROM can not provide the same settings even if the user try.
https://forum.xda-developers.com/t/hp-touchpad-max-1gb-ram-max-1836-frequency-for-all-roms.3973149/
Sanras said:
Let's take another example: Say you have one laptop to use in 2022. You've got a netbook with a 1.6Ghz Intel Atom n280, and 1GB of RAM.
You *could* technically run Windows 10 on here if you wanted to. The hardware technically supports it. But is it a good idea? No, not at all. It's gonna be extremely slow and annoying to use. I'd rather run Windows XP on such a device, use Firefox 52.9ESR and deal with some broken webpages than use Windows 10 and a modern browser. At least with XP you're gonna have a fast and snappy computer, even if you have to use some old apps to get things done.
(Of course, this is hypothetical. The true best choice in this situation would be a Linux install with a simple X11 window manager or Windows 7 without transparency effects)
Click to expand...
Click to collapse
It all depends on how that laptop is setup and the drivers installed.
If the laptop is used with all the bloatware ( extra software ) and outdated display drivers, it can not be use.
A Windows 10 installation that has all the unnecessary software remove ( which is a lot ) will provide the basic to support the hardware of a 10 or 15 year old PC and performs very fast with even just 4GB of RAM. What makes the PC slow is all the extra Task ( background process ).
The same applies to any Linux OS now days. The installation automatically install a lot of extra software and services, it takes time to clean it up and make it efficient.
Same principal applies to Android, what makes the Tablet slow is the google apps and all the extras that are not need it. The Tablet is just a Linux laptop with a touch screen.
Look at this guide of ROM Reducer:
https://forum.xda-developers.com/t/hp-touchpad-rom-reducer-for-more-ram.3954026/
HP_TOUCHPAD said:
No, Android 4.x uses an old kernel, Android 7.1 and newer are built with a newer kernel providing better support for the hardware and software.
Android is not the native operating system for the Tablet, earlier version of Android had issues than with the time was improve.
It all depends on the settings and how is set up, but newer OS provides better support. Software is what makes the hardware to work.
Devices are not mechanical machines that works on the principal of physical parts, but works on code, software.
Check this guide and see that all ROMs have the same settings, optimized to use the full 1GB of RAM and CPU speed plus swap partition.
Any original ( stock ) Android ROM can not provide the same settings even if the user try.
https://forum.xda-developers.com/t/hp-touchpad-max-1gb-ram-max-1836-frequency-for-all-roms.3973149/
It all depends on how that laptop is setup and the drivers installed.
If the laptop is used with all the bloatware ( extra software ) and outdated display drivers, it can not be use.
A Windows 10 installation that has all the unnecessary software remove ( which is a lot ) will provide the basic to support the hardware of a 10 or 15 year old PC and performs very fast with even just 4GB of RAM. What makes the PC slow is all the extra Task ( background process ).
The same applies to any Linux OS now days. The installation automatically install a lot of extra software and services, it takes time to clean it up and make it efficient.
Same principal applies to Android, what makes the Tablet slow is the google apps and all the extras that are not need it. The Tablet is just a Linux laptop with a touch screen.
Look at this guide of ROM Reducer:
https://forum.xda-developers.com/t/hp-touchpad-rom-reducer-for-more-ram.3954026/
Click to expand...
Click to collapse
So you are saying the EV 7.1 build is as fast as CM11? (both same settings, no Gapps)? I really don't see how that can be the case. I have had A 7 on an old Galaxy Tab and Galaxy Nexus. On both devices, Android 4.4 (CM11) was quite a bit faster than the Android 7 builds (LOS 14.1). Ultimately, KitKat (2014) was made for the devices of its time, which were much less powerful than the devices of 2017, when Nougat launched. It makes sense that KitKat would thus run better on outdated hardware. Granted, those were native Android devices, but I think that should still apply to this touchpad, which is running an old Qualcomm CPU.
Anyway, once this boots, I'll test both JCSullins' CM11 and the EV 7 to see what is better. The only issue I really see with using 4.4 is the lack of Aurora Store, since that requires Lollipop at minimum. However, apkmirror should do fine for the few apps I need to install. YouTube Vanced 14.21.54 will work on KitKat as well.
Sanras said:
So you are saying the EV 7.1 build is as fast as CM11? (both same settings, no Gapps)? I really don't see how that can be the case. I have had A 7 on an old Galaxy Tab and Galaxy Nexus. On both devices, Android 4.4 (CM11) was quite a bit faster than the Android 7 builds (LOS 14.1). Ultimately, KitKat (2014) was made for the devices of its time, which were much less powerful than the devices of 2017, when Nougat launched. It makes sense that KitKat would thus run better on outdated hardware. Granted, those were native Android devices, but I think that should still apply to this touchpad, which is running an old Qualcomm CPU.
Anyway, once this boots, I'll test both JCSullins' CM11 and the EV 7 to see what is better. The only issue I really see with using 4.4 is the lack of Aurora Store, since that requires Lollipop at minimum. However, apkmirror should do fine for the few apps I need to install. YouTube Vanced 14.21.54 will work on KitKat as well.
Click to expand...
Click to collapse
Is all about the settings and how is set up by the user and that applies to all devices, PC, smartphone even cars or anything !
You can see it with your own eyes, take a look at my youtube channel.
https://www.youtube.com/channel/UCKoir6bzzPU-Uq9UjcRR3hw
On this guide all the optimize settings are applied to all the ROMs to make them work the same.
I know there is a lot to read, but is 10 years of development.
https://forum.xda-developers.com/t/...all-android-roms-with-swap-partition.3901773/
LN11211 said:
"@HP_TOUCHPAD , Hello, I still can't believe we have support for the touch pad....
The touch pad was dead a long ago and I revived it back today, "
Click to expand...
Click to collapse
How did you revive your TouchPad??? Mine will not power on - there are no lights when charging. I have even replaced the battery with no difference.
Any Help is truly appreciated!
deegge said:
How did you revive your TouchPad??? Mine will not power on - there are no lights when charging. I have even replaced the battery with no difference.
Any Help is truly appreciated!
Click to expand...
Click to collapse
Use original charger or equivalent.
Tablet must be in a warm environment of 80F. ( it won't take charge in the cold )
Check that the USB port is not damage, try the wireless charger if available.
Try to apply the de-brick process:
https://forum.xda-developers.com/t/hp-touchpad-debrick-linux-live-cd.4189245/
Related
I have done some (very basic) game development with Unity and would like to port my work to Android. I will use the tablet for other purposes, web browsing, etc and want it to run flash. I need the tablet to be stable, and all OEM features to work.
Unity has a robust online forum but not a lot of them are specifically using the gTab, most just use whatever device they already have, so I figured I'd ask here but I am asking there too.
I am planning to get a gTablet because I want a 10" capacitive multitouch tablet with a front facing camera, USB connectivity and the ability to use a keyboard/mouse and external SD cards, that doesn't break the bank. TFT screen = a reasonable way to save $100 or so.
I think that hardware acceleration is important, I would like the camera to work well (i.e. not grainy), and sound needs to work. Having only one core work is ok; Unity will only use one core, and a lot of people's Android devices still have only one core. I figure some day I'll use a ROM that uses 2 cores when they have the kinks worked out, and when most phones/tablets have/can use 2 cores.
Stability, and having a ROM that is good for testing apps/games that will run on other tablets, is more important than benchmark speeds and the latest 'non-phone UI'. I'd rather not flash and try every ROM, I'd rather spend that time swearing at my computer trying to get my game to work.
I'm thinking that a 2.2 ROM is best because 2.3 and 3.1 don't have hardware acceleration; so, my options seem to be: stock, stock 4393, TnT Lite, or Vegan. If I were to go stock, at a minimum I'd turn off TnT. Other options? Which is the best ROM for a stable, development tablet.
I am not a developer but I am not exactly unfamiliar with tech. I am trying to understand how different Android phones work with respect to their specs.
For example, I was looking at one with these specs:
OS Android 4.0 (Ice Cream Sandwich)
CPU 1.0GHz Dual Core
512 MB ROM
512 MB RAM
From what I've read, I understand ROM is more on the OS side and RAM is for multitasking. CPU speed is more on how smooth apps are launched or how the phones responds to commands. Did I understand these correctly?
I compared those above against what I have. (I've attached a screenshot of my phone's specs.) I do not understand the entry on the second screeshot re: memory. Is that RAM or ROM? Also with these specs, can I (if at all possible) install or upgrade to ICS?
Thanks in advance!
fpjones3 said:
I am not a developer but I am not exactly unfamiliar with tech. I am trying to understand how different Android phones work with respect to their specs.
For example, I was looking at one with these specs:
OS Android 4.0 (Ice Cream Sandwich)
CPU 1.0GHz Dual Core
512 MB ROM
512 MB RAM
From what I've read, I understand ROM is more on the OS side and RAM is for multitasking. CPU speed is more on how smooth apps are launched or how the phones responds to commands. Did I understand these correctly?
I compared those above against what I have. (I've attached a screenshot of my phone's specs.) I do not understand the entry on the second screeshot re: memory. Is that RAM or ROM? Also with these specs, can I (if at all possible) install or upgrade to ICS?
Thanks in advance!
Click to expand...
Click to collapse
Considering your device runs gingerbread, it is not possible to run ICS unless a developer has developed a custom ROM for your device. ROM pertains strictly to the OS itself as a whole, RAM is the devices total memory, as in what's available for the ROM to be stored and any non SD apps to be installed. Hopefully this helps you.
Sent from my LG-LS970 using xda app-developers app
RE: spec
ROM is not only for OS storage it is also for apps, music, other files etc., but your phone should probably have a mini SD card slot where you can expand this. This is analogous to a hard drive on your computer
Yes, RAM determines how much you can run at once, the Android OS uses up a portion of this. You are also correct about the CPU controls the processing of information so therefore controls 'speed'.
No you will not be able to upgrde to ICS (which isn't even the newest version of Android) because your phone is a dinosaur LOL as your manufacturer probably realises they wouldn't be able to. Also, I've never heard of your phone so it must be really a fly by night company (exaggeration) so there would probably not be a ROM (custom update built by people on this forum) for this device and I don;'t suggest that do so anywys are you are not a technical person and would probably mess it up (I know I did when I started 4 years ago). I would suggest that you buy the Nexus 5 when it comes out in October... I know I will.
Hit thanks if I've helped
fpjones3 said:
I am not a developer but I am not exactly unfamiliar with tech. I am trying to understand how different Android phones work with respect to their specs.
For example, I was looking at one with these specs:
OS Android 4.0 (Ice Cream Sandwich)
CPU 1.0GHz Dual Core
512 MB ROM
512 MB RAM
From what I've read, I understand ROM is more on the OS side and RAM is for multitasking. CPU speed is more on how smooth apps are launched or how the phones responds to commands. Did I understand these correctly?
I compared those above against what I have. (I've attached a screenshot of my phone's specs.) I do not understand the entry on the second screeshot re: memory. Is that RAM or ROM? Also with these specs, can I (if at all possible) install or upgrade to ICS?
Thanks in advance!
Click to expand...
Click to collapse
Thank you for the replies! Yeah I purchased a cheap-o phone, hence the brand, mainly because I want to play around with the OS.
Well now that I know I cannot upgrade the phone, a couple of follow-up questions:
I know you can only save apps on the SD if rooted. How will I know if it's rooted?
What benefits does rooting give to a living fossil such as my phone?
How does the specs I quoted on the first post sound? Is 512 ROM and 512 RAM good enough?
Is RAM upgradeable? (I doubt the answer is yes though. lol)
Lastly, are all android versions not upgradeable? (Sounds like a waste of hardware especially when 4.1, 4.2, and 4.3 were released shortly after the other. 4.4 is almost out even.)
Cheers!
A phone will not come rooted as standard you must do it yourself using a simple one click solution such as gingerbreak and others (make sure to find them on XDA only or you will get malware, just download it and install the APK by tapping on it in a file explorer). If you can return it you should do so, gingerbread is really easy to exploit, the Nexus 4 phone is only about $200 if you can find a used one and it has the latest android which is very good looking. Rooting does not require any extra hardware as it is like getting admin privileges on Windows or root perms on Ubuntu and other Linux. A good app is SD maid, it does A LOT. Yeah you guesses it RAM is not upgradeable on phones as everything is soldered and highly compact. Yes, Android is upgradeable (unlike certain other OSes cough cough Windows) but manufacturers seem to not follow that as they pull the plugs on such things, however with Nexus phones google provides the updates and they do it fast and for a long time which is why I suggest you cut your losses with this phone (return if possible) and get a nexus 4/5.
BTW, for next time when responding, you should respond to us by quoting what we say or we won't be able to read what you say.
AJM-hackers said:
A phone will not come rooted as standard you must do it yourself using a simple one click solution such as gingerbreak and others (make sure to find them on XDA only or you will get malware, just download it and install the APK by tapping on it in a file explorer). If you can return it you should do so, gingerbread is really easy to exploit, the Nexus 4 phone is only about $200 if you can find a used one and it has the latest android which is very good looking. Rooting does not require any extra hardware as it is like getting admin privileges on Windows or root perms on Ubuntu and other Linux. A good app is SD maid, it does A LOT. Yeah you guesses it RAM is not upgradeable on phones as everything is soldered and highly compact.
Click to expand...
Click to collapse
Hello there again! I can't return this anymore as I've had this for a good month or two now, but thanks for the tip.
I'll install the apk as soon as I get home but I recently replaced Avast with AVG and it says I'm running on high-privilege mode, I guess that's it right?
Yes, Android is upgradeable (unlike certain other OSes cough cough Windows) but manufacturers seem to not follow that as they pull the plugs on such things, however with Nexus phones google provides the updates and they do it fast and for a long time which is why I suggest you cut your losses with this phone (return if possible) and get a nexus 4/5.
Click to expand...
Click to collapse
How did the manufacturers pull the plug? I understand Android is open-source. So why can't I just get an installer for ICS or Jellybean and slap it over Gingerbread like I would upgrade a desktop from XP to Win8?
Thanks again!
fpjones3 said:
Hello there again! I can't return this anymore as I've had this for a good month or two now, but thanks for the tip.
I'll install the apk as soon as I get home but I recently replaced Avast with AVG and it says I'm running on high-privilege mode, I guess that's it right?
How did the manufacturers pull the plug? I understand Android is open-source. So why can't I just get an installer for ICS or Jellybean and slap it over Gingerbread like I would upgrade a desktop from XP to Win8?
Thanks again!
Click to expand...
Click to collapse
It's not as simple as pushing Google's version of the OS to your device, they need to modify it and create their own pseudo operating system tailored to the hardware of your device. DO NOT INSTALL A ROM FROM ANOTHER DEVICE OR TRY TO INSTALL AN INSTALLER, they are most likely fake and are out to get you. Send me a link of where you got the apk so I can see if it's okay
AJM-hackers said:
DO NOT INSTALL A ROM FROM ANOTHER DEVICE OR TRY TO INSTALL AN INSTALLER, they are most likely fake and are out to get you. Send me a link of where you got the apk so I can see if it's okay
Click to expand...
Click to collapse
I have yet to search for an alternate ROM. That is what you are asking for right?
Is there a basis for determining compatible ROMs, if any at all?
fpjones3 said:
I have yet to search for an alternate ROM. That is what you are asking for right?
Is there a basis for determining compatible ROMs, if any at all?
Click to expand...
Click to collapse
No your root apk but you already did it so its fine. And there probably wont be any Roms compatible for your device
AJM-hackers said:
No your root apk but you already did it so its fine. And there probably wont be any Roms compatible for your device
Click to expand...
Click to collapse
Thanks for all the replies AJM! (Just so we're on the same page, I have not done anything, much less attempt to root the phone.) Looks like I have lots of room to experiment and explore.
One last question: I found this in the forum:
[GUIDE] [how to] CREATE OWN ROM [FOR ANY ANDROID DEVICE] [FOR N00B] [EASIEST METHODS]
I'm totally fishing here so please excuse the probable misuse of terminologies or the nonsensical question(s):
1. Based on my initial post: is my device capable of running a higher version of Android? Preferably the latest of course.
2. Assuming #1 is a yes, is a custom ROM created around the android version (gingerbread, ICS, etc.) or, err, what? (Do I start with a blank slate or do I download something off the web?)
fpjones3 said:
Thanks for all the replies AJM! (Just so we're on the same page, I have not done anything, much less attempt to root the phone.) Looks like I have lots of room to experiment and explore.
One last question: I found this in the forum:
[GUIDE] [how to] CREATE OWN ROM [FOR ANY ANDROID DEVICE] [FOR N00B] [EASIEST METHODS]
I'm totally fishing here so please excuse the probable misuse of terminologies or the nonsensical question(s):
1. Based on my initial post: is my device capable of running a higher version of Android? Preferably the latest of course.
2. Assuming #1 is a yes, is a custom ROM created around the android version (gingerbread, ICS, etc.) or, err, what? (Do I start with a blank slate or do I download something off the web?)
Click to expand...
Click to collapse
I would not advise you to try to build a rom when you are COMPLETLY new to android and probably don't know about linux I assume and no it wont be able to run any other version other than 2.3.7( you're device is reminiscent of my first android phone, the xperia x10 which could only run 2.3.7, although later on a very skillful develop managed to get 4.0 on it but it wasn't exactly ideal).
AJM-hackers said:
I would not advise you to try to build a rom when you are COMPLETLY new to android and probably don't know about linux I assume and no it wont be able to run any other version other than 2.3.7( you're device is reminiscent of my first android phone, the xperia x10 which could only run 2.3.7, although later on a very skillful develop managed to get 4.0 on it but it wasn't exactly ideal).
Click to expand...
Click to collapse
At least I now know it is sort of possible.
Why was it not ideal though (your upgraded phone)?
Battery life and unreal lag. On a side note you can think of gingerbread as the xp or vista for android 4.4 is coming out soon that means you're going to be 5 versions behind.
Sent from my ME173X using xda app-developers app
AJM-hackers said:
Battery life and unreal lag. On a side note you can think of gingerbread as the xp or vista for android 4.4 is coming out soon that means you're going to be 5 versions behind.
Sent from my ME173X using xda app-developers app
Click to expand...
Click to collapse
Excuse the necromancy but I sort of renewed my interest in the topic.
I am now using a newer phone running 5.1 for around a year now, with slightly better specs. Not yet rooted so I don't void the warranty. I was wondering, what can I do with the dinosaur of a phone?
I still don't get why people think the memory has anything to do with 64 v 32. I have never heard a person ever say "oh you machine is laggy because you have a 64bit machine and not enough memory." until I found this sub-forum. The iPhone/iPad have had 1-2GB of RAM and not had any huge performance issues while being 64bit.
There are memory issues, that's it, nothing to do with it being 64-bit or not. 3GB MAY "fix" the issue, but that would really just mean the machine would go longer until it started to show symptoms. The nexus 5 and 6 had LOTS of memory issues on Android 5 and no one ever said "it's not enough memory" and not being 64bit hardware they couldn't blame that, because it worked fine on 4.X. We have no 4.X to compare with, so everyone just wants to blame 64 bit when really, it just needs more software fixes that Google isn't spending time on.
If anything having a 64bit CPU just means the CPU can work harder and faster, even if it was running 32bit software. I know that not many developers ahve latched on to the n9, but i would NOT be surprised if a few clever ones could figure out what is actually causing the memory leaks/aggressive paging. For example on my n6 it is using about 4-500MB less ram, just to to Android OS and Google App. There is nothign about being 64-bit that means the Kernel needs over 2x's the memory usage. Something is making it keep memory instead of releasing it. I am not smart enough to know what that "something" is, but I'm sure someone that develops and has an N9 is smart enough and can file a bug report for it that we can all upvote.
If there are any current open bug reports for memory usage on the n9 please link them to me, I will gladly upvote them. Lets just be clear there is no reason to suspect this is anything more than a software issue.
To Update:
Here is a bug report i found of the problem, if more people could Star it then it can get up the priority list.
https://code.google.com/p/android/issues/detail?id=175232
People like to blame the 64bit OS because the switch does make processes consume slightly more memory. If implemented poorly, a 64bit OS can eat up a lot more RAM. Windows XP 64, any Itanium based system and many early x64 Linux distributions come to mind.
Somehow Android OS on my N6 averages 220mb, while it's 800+ on the N9. Because the N9 is 64 bit, that change seems to be the obvious culprit. Clearly, the N9 didn't ship with enough RAM based on the OS memory use as somehow the N6 has 3gb for an 220MB OS footprint and the N9 has only 2mb, despite an OS that eats almost 4x the memory.
Switching to a 64bit OS should make the CPU, RAM, etc. all run 'faster', but if there's not enough RAM to hold running software, the experience will slow down as more processes need to be shuffled in and out of RAM. Look at what happens to a computer when it 'runs out of RAM'. The constant game of musical RAM chairs will more than erase any gains from switching to 64 bit.
In my mind, there is no question that SERIOUS problems exist with this device. The fact that this is one of the first 64bit Android devices is almost definitely a contributing factor, but the slightly reduced efficiency of how 64bit memory is allocated can in no way explain the problems with the devices. Something MUCH deeper is going on. Based on some research, here is what I've learned.
1: Some part of the OS is using an obscene amount of memory. Some of this is probably Google's fault because 64 bit Android just wasn't ready. I'm also pretty sure nVidia and HTC are more to blame for this issue than Google.
2: There's still not enough RAM. If the N6 has 3GB, there is no reason why the N9 shouldn't. Most tablet users run more memory-intensive
3: HTC built a bad device. I've had cellular issues with VZW & ATT which have been discussed in these forums and are obviously HTC's fault. I've also read about there being some hardware issues causing the ram to 'freeze' which required a replacement device.
4: nVidia's hardware sucks. More accurately, their x64 bit implementation of the hardware.
5: Graphics: I BELIEVE THIS IS THE GIANT ELEPHANT IN THE ROOM OF ISSUES. The nVidia Shield has similar hardware with a standard HD screen. The N9 has a different aspect ratio and a lot more pixels. The horrible application switching lag even with relatively low memory use (a process that is still taxing on the GPU) makes me think this is the main flaw of the device. This problem could also make the OS eat more memory to make up for the OS issues. A graphics issue would be everyone's fault. Google is to blame for insisting on this change when the other hardware just couldn't support it properly and choosing partners incapable of delivering the hardware to properly support the screen. nVidia and HTC to blame for not providing sufficient hardware and software support for the screen.
In reality, I think several factors combined to produce this issue. The components of the system were designed primarily for 32-bit implementations of Android. 64-bit support was baked into them, but it wasn't the focus of the components. The device itself was probably designed before 64-bit Android was even available to test properly. Because the pieces looked like they should fit together on paper, everyone just assumed they would. Unfortunately,for some components the fact that they could run in 64-bit mode, didn't mean they would run well.
x64 gets blamed because it is unknown. The average user has no idea what it means to have a 64 bit platform vs 32 bit. IMO x64 is unneeded unless you're mapping 4gb or more RAM and doing a lot of computations with large numbers.
There is most certainly a memory penalty since the os must run 64 bit code and likely have a vm of some sort to run all the existing 32 bit stuff. In windows this is obvious as you have program files and program files (x86) folders as well as windows\system32 and windows\syswow64 humorously the former is the 64 bit subsystem and the latter is the x86 subsystem. This is why you should plan ahead when architecting your applications and not name your folders poorly.
All that said, I have an htc m9 in addition to the nexus. The m9 is also 64 bit and has no issues. Not an apples to apples comparison since it is a Qualcomm processor with 3gb of ram and less pixels but it should indicate that 64 bit android is not the problem in and of itself.
Thanks guys. 64-bit apps should use at most 15-20% more RAM compared to their 32-bt counterparts, simply due to the fast that 64-bit assets are larger. The issue we have is that in cases like Android OS, using over 120% more memory than on a 32bit device. It also for some reason seems at times to feel like the GPU is taxed and it definitely should not be. So either the GPU drivers are buggy or the GPU memory is very limited. Luckily much of this is improved on 6.0, but there are still issues that need to be addressed in the OS itself.
Because saying "I do not know why my Nexus 9 performs poorly" is boring. Jumping to conclusions is much more exciting and dramatic.
knitler said:
Thanks guys. 64-bit apps should use at most 15-20% more RAM compared to their 32-bt counterparts, simply due to the fast that 64-bit assets are larger. The issue we have is that in cases like Android OS, using over 120% more memory than on a 32bit device. It also for some reason seems at times to feel like the GPU is taxed and it definitely should not be. So either the GPU drivers are buggy or the GPU memory is very limited. Luckily much of this is improved on 6.0, but there are still issues that need to be addressed in the OS itself.
Click to expand...
Click to collapse
I suspect you are right that there are driver issues. Sadly our only recourse is to wait on nvidia/htc/google to rectify the issue.
Don't know what it is but 6.0 is not what I expected. Jerky , slow loading and very unpleasant to use. Have never rooted or rommed. Don't think I should have to. Did a FDR, no improvement. Have to constantly clear app cache and system cache to make it tolerable. Hoping for some relief from Google
Android 6 on my stock nexus 9 has brought every task switch of any kind to a near unusable lag. 4 to a full 20 seconds is the norm now. In fact, just about every response to user action in every app has this problem now. I've got almost nothing except Google's apps, many of which I don't use, but still have something running.
The tablet is now a paper weight, almost. The delays make it unusable, as you can't tell whether an interface action didn't "take", or is just laggy.
I did this as an update. Should I just wipe and reinstall clean? If so, where do I get the necessary files and instructions?
Thanks for any insight.
Black Friday buy, feeling I'm going to return it, two days in and I can see the issues already
dislplin01 said:
Black Friday buy, feeling I'm going to return it, two days in and I can see the issues already
Click to expand...
Click to collapse
Welcome to the Lagsus 9 owners club [emoji6] Did it ship with latest android version, or did you ota update?
rolldroids said:
Welcome to the Lagsus 9 owners club [emoji6] Did it ship with latest android version, or did you ota update?
Click to expand...
Click to collapse
It had to update, actually had like 7 different updates, I'm pretty sure I'm returning it I'm really unimpressed and most of it is hardware issues that can't be fixed, lack of ram, light bleed, ****ty power and volume buttons, not exactly the thinnest lightest tablet. Don't get me wrong its a nexus and I do like it, but I don't plan on buying another tablet for at least three years and if I'm already feeling a little unhappy
dislplin01 said:
It had to update, actually had like 7 different updates, I'm pretty sure I'm returning it I'm really unimpressed and most of it is hardware issues that can't be fixed, lack of ram, light bleed, ****ty power and volume buttons, not exactly the thinnest lightest tablet. Don't get me wrong its a nexus and I do like it, but I don't plan on buying another tablet for at least three years and if I'm already feeling a little unhappy
Click to expand...
Click to collapse
I wish I would have returned it, but haven't because I thought they were fixing the memory leak. And after fixed it turned out that all other Nexus devices do well but not the n9.
Feel free to try my ROM if you're unsatisfied with what Google has done with stock.
NYCHitman1 said:
Feel free to try my ROM if you're unsatisfied with what Google has done with stock.
Click to expand...
Click to collapse
Does it have lower system ram usage? There are people (like me) who want just use their device as a normal user and get ota updates and not flash the device manually every few weeks. It's very nice that you are sharing it anyway!
Everyone try first "safe mode" on Nexus 9 for 3-5 days to see if this app or hardware problem!
Press and hold power button
pres and hold "power off" option
then choose OK.
If problems gone (lag, resetting) then do factory reset without backup, install app manually not all at once from backup. It helped mine Nexus 9
Sent from my Nexus 9 using Tapatalk
rolldroids said:
Does it have lower system ram usage? There are people (like me) who want just use their device as a normal user and get ota updates and not flash the device manually every few weeks. It's very nice that you are sharing it anyway!
Click to expand...
Click to collapse
I think you'll be happy. Popular quote that people often use is:
You have breathed new life into my Nexus 9.
Click to expand...
Click to collapse
With that said, it's entirely possible to flash one build and stick with it for however long as you wish. When you do decide to update, you simply create a backup, "wipe", and flash the newer build with some gapps. Something to keep in mind here is that Nexus devices were created to be fiddled with. If you aren't fiddling, you aren't getting the full experience. It is a developer's device, after all. :highfive:
If this is a road you do decide to travel down, just be sure to do a lot of reading and understand what you're doing prior to doing it.
NYCHitman1 said:
I think you'll be happy. Popular quote that people often use is:
With that said, it's entirely possible to flash one build and stick with it for however long as you wish. When you do decide to update, you simply create a backup, "wipe", and flash the newer build with some gapps. Something to keep in mind here is that Nexus devices were created to be fiddled with. If you aren't fiddling, you aren't getting the full experience. It is a developer's device, after all. :highfive:
If this is a road you do decide to travel down, just be sure to do a lot of reading and understand what you're doing prior to doing it.
Click to expand...
Click to collapse
It's a normal end user device, too. And for me the only choice. Don't like apple products at all. Don't want to buy a device and then not get updates. To be exactly, I want to know before I buy and not hope that Samsung, lg or whatever are so friendly to update. And, I don't like the modifications they do to the UI. So for me there is no other than Nexus. But I don't want this special fiddling experience. (For now. I will probably install a ROM on my Nexus 7 2012 some day)
According to this document
https://01.org/android-ia/user-guides/android-memory-tuning-android-5.0-and-5.1
64 bit indeed increases ram usage a lot...
I also have the impression that this is rather an issue with the Nvidia chipset or the general hardware design than with the system being 64bit.
This morning I had a very LOL moment when I read the Google Pixel C review of The Verve:
>>The specs are also huge: 3GB of RAM paired to the latest Nvidia X1 64-bit processor. That all seems good, but something is amiss with performance on the Pixel C. There are inexcusable pauses and latency, especially when launching and switching apps. <<
http://www.theverge.com/2015/12/8/9869980/google-pixel-c-tablet-review-android
So the problem still seems to be out of control. Too bad.
There are many threads about the Nexus 9 and memory issues but I have yet to see any reports of specific analysis of the issue on a problem device. I've had no memory issues with the Nexus 9, 7, 7(2013),5 and Asus tablets. I seen no evidence that there are hardware differences between Nexus 9's (except the pre release version tested for FCC emissions had a Miracast chip) and I believe it is down to the apps that users run. In support of this opinion:
Resets are recommended to clear the issues.
Google state at Investigating Your RAM Usage Although Dalvik and ART perform routine garbage collection (GC), this doesn’t mean you can ignore when and where your app allocates and releases memory. In order to provide a stable user experience that allows the system to quickly switch between apps, it is important that your app does not needlessly consume memory when the user is not interacting with it. Has anyone with memory issues looked at the recommended tests at the link above?
The quality of apps published. Anecdotal evidence (I hope it's wrong) that publishing an app on Google store can be done in 30 minutes but Apple requires "days". I've never owned an Apple product I'm just saying that to me, not a software developer, that the compliance standards imposed on the software tested may allow bad coding to slip through.
Hey everyone!
I just got a Kindle Fire HDX 7. I'm looking to install the LineageOS 14.1, but I just wanted to hear some opinions about stability and speed - can the kindle handle Android 7 well? I hear some people complaining about wifi and bluetooth issues, and also some buzz on headphones, on other OSes, does this happen on the lineageos as well?
I skimmed through the original LineageOS 14.1 thread here on XDA, but the it is over 110 pages, so forgive me for asking if this has already been replied to there!
mig_akira said:
Hey everyone!
I just got a Kindle Fire HDX 7. I'm looking to install the LineageOS 14.1, but I just wanted to hear some opinions about stability and speed - can the kindle handle Android 7 well? I hear some people complaining about wifi and bluetooth issues, and also some buzz on headphones, on other OSes, does this happen on the lineageos as well?
I skimmed through the original LineageOS 14.1 thread here on XDA, but the it is over 110 pages, so forgive me for asking if this has already been replied to there!
Click to expand...
Click to collapse
Short answer to thread title: Yes and Yes.
Above response actually applies to all custom ROMs for the HDX ranging from Android 4.2 to 7.1. From a speed perspective FireOS v4 is encumbered by numerous background processes (ie: Amazon bloat) that blog down the processor, consume memory and tax the battery. As for stability @ggow and the other ROM developers/maintainers have done a fine job ironing out the bugs in earlier releases. The choice of custom ROM is essentially akin to deciding what toppings to put on your ice cream. Obviously Nougat based ROMs (latest available for HEX devices) are both preferred and best supported.
There are a few issues to be aware of which apply equally to all custom ROMs:
- some apps rotate the screen 180 degrees from what one might expect; easy to remedy if it proves bothersome
- audio is imperfect but generally not objectionable (most noticeable with headgear)
- establishing initial bluetooth pairings can be challenging but there are workarounds; once paired devices tend to reconnect easily
- brief WiFi disconnects are most prevalent in mixed 2.4GHz/5GHz environments; they are annoying but not debilitating (and there are workarounds)
- forget about gaming; the GPU is anemic (applies to all ROMs)
While the above appears worrisome very few users return to FireOS as the benefits far outweigh the hick-ups.
Davey126 said:
Short answer to thread title: Yes and Yes.
Above response actually applies to all custom ROMs for the HDX ranging from Android 4.2 to 7.1. From a speed perspective FireOS v4 is encumbered by numerous background processes (ie: Amazon bloat) that blog down the processor, consume memory and tax the battery. As for stability @ggow and the other ROM developers/maintainers have done a fine job ironing out the bugs in earlier releases. The choice of custom ROM is essentially akin to deciding what toppings to put on your ice cream. Obviously Nougat based ROMs (latest available for HEX devices) are both preferred and best supported.
There are a few issues to be aware of which apply equally to all custom ROMs:
- some apps rotate the screen 180 degrees from what one might expect; easy to remedy if it proves bothersome
- audio is imperfect but generally not objectionable (most noticeable with headgear)
- establishing initial bluetooth pairings can be challenging but there are workarounds; once paired devices tend to reconnect easily
- brief WiFi disconnects are most prevalent in mixed 2.4GHz/5GHz environments; they are annoying but not debilitating (and there are workarounds)
- forget about gaming; the GPU is anemic (applies to all ROMs)
While the above appears worrisome very few users return to FireOS as the benefits far outweigh the hick-ups.
Click to expand...
Click to collapse
Thanks for your reply! It gave me confidence to try it out.
I had no idea where to start, but I found 2 posts very useful:
This with some common questions I also had: https://forum.xda-developers.com/kindle-fire-hdx/help/help-thor-4-5-5-3-unlock-bootloader-t3750801
And this one with a nice step by step: https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006
I was able to unlock my device and install LineageOS with gapps mini! It worked very well! I am only having some trouble with gapps, google play crashes all the time, but no matter, I want to try the Slim OS now anyway!
Thanks a lot for the reply here and for all the help you and all the others give to the community!
mig_akira said:
I was able to unlock my device and install LineageOS with gapps mini! It worked very well! I am only having some trouble with gapps, google play crashes all the time, but no matter, I want to try the Slim OS now anyway!
Click to expand...
Click to collapse
Play Store crash can be triggered by installing GApps after the initial boot of Lineage or an incomplete wipe of the suggested partitions (system, data, dalvik and cache). Slim, AEX and RR tend to be less fussy about when GApps is installed. Raise a post in the appropriate thread if the problem persists. Typically an easy fix.
Slim is a great ROM as are RR and AEX. Really can't go wrong with any of the five Android 7.x ROMs available for this device.
A nod of thanks for the kind remarks in a prior post.
Davey123, when you say "forget gaming" do you mean that the custom ROMs have less gaming capability than the original Fire OS? I really only want to be able to play Sim City Build It, which is not even available on the original OS. Thanks.
deewsee said:
Davey123, when you say "forget gaming" do you mean that the custom ROMs have less gaming capability than the original Fire OS? I really only want to be able to play Sim City Build It, which is not even available on the original OS. Thanks.
Click to expand...
Click to collapse
The GPU is weak on this device which limits the type of games that can be successfully played. Most low end phone have more gaming prowess. That said, custom ROMs will likey offer a superior experience given the more contemporary Android base.
Davey126 said:
The GPU is weak on this device which limits the type of games that can be successfully played. Most low end phone have more gaming prowess. That said, custom ROMs will likey offer a superior experience given the more contemporary Android base.
Click to expand...
Click to collapse
What is the easiest custom ROM to install? Am I actually better off keeping my Fire HD 7" than trying to install a custom ROM on this HDX that I thought would be an upgrade?
Has anyone installed CalyxOS on the Pixel 6 and might share the experience?
What works, what doesn't work. Is battery runtime affected....
They recently announced, that their stable channel is running on Android 13:
Another October update
Another October update
calyxos.org
I'm current running Android 13 stock rom. I should be save running the newest Android 13 CalyxOS, not bricking my phone due to the anti roll back bootloader, right?
Have installed it now and running for a few days.
Made sure that both bootpartitions where running a A13 bootloader and then just installed it through the browsers. I've installed a couple of different custom rom throughout the years and this was by far the easiest way to do it.
So far everything runs smoothly and very fast. Haven't notice any features/hardware/whatever not working, except for some apps, who require full google services. I can't make out any change in battery life compared to the stock rom. Not missing any google annoyances (like that assistance), however picture quality seems to be not too great. But I would need to test everything a bit more in depth.
riagriag said:
Have installed it now and running for a few days.
Made sure that both bootpartitions where running a A13 bootloader and then just installed it through the browsers. I've installed a couple of different custom rom throughout the years and this was by far the easiest way to do it.
So far everything runs smoothly and very fast. Haven't notice any features/hardware/whatever not working, except for some apps, who require full google services. I can't make out any change in battery life compared to the stock rom. Not missing any google annoyances (like that assistance), however picture quality seems to be not too great. But I would need to test everything a bit more in depth.
Click to expand...
Click to collapse
Do you may have considered anything about dropping calls / muting during call etc by using 2 Sim? (esim & Sim)
Currently I am using only esim, and I have not experienced any dropping/muting calls. Sample size and length of calls is small/short.
However I plan on using both esim & sim simultaneous soon, but so far I could not test this.
On a more general note, battery seems to be depleted slightly faster vs. the stock rom. By slightly I mean almost unnoticeable.
Not sure whether battery percentage is calculated the same way (I assume it does), but this is this only benchmark I have, because I have not manage to bring the battery below 50%.
One of my theories is that stock rom handles roaming or search for new network better.
Other than that, CalyxOS has been running reliably for 149 hours. Bluetooth connects a little slower, but I'd rather not sent out beacons all the time.
Planned on testing Project-Zephyrus and riceDroid though if I feel lazy I might just stay with this one.
So stayed with CalixOS. Features works as expected from an android OS.
"Aurora Store" delivered me a former version of a banking app, which I did not work and took some tinkering. This was my first point of contact with that app "store" . the popular android apps I installed did run fine.
Battery life still more than ****ing rock solid.
So far the only bad thing is bad quality standard display background img which will be taken care of.
Is there a recovery for the Pixel 6, like TWRP where I can dd like make backups and restore them byte by byte ?
So it has been my daily driver.
The (veryvery minor) issue of the background wallpaper was changed with the second latest update.
I did run run sim and esim simultaneously for two weeks just fine.
Search for mobile network (roaming) is magnitudes faster than I experienced before with LG G6. Presumably due to hardware,
Wireless charging works fine.
Stats on charging (voltage and power) are not present. I liked to see the charging rate in Havoc OS.
Very likely I'm gonna stay with Calyx OS. Not a huge fan of automatic updates, however might be a good idea.
Ran out of use cases to test, open for requests. Otherwise close this down, because this is almost turning into a monologue.
Vennerdes said:
CalyxOS is the first commercial web operating system to run on Android smartphones. The purpose of CalyxOS is to help open your Android phone up to a wider range of apps, services and capabilities unavailable today. By taking full advantage of the underlying mobile device hardware and running in parallel with Android itself, we're able to integrate all kinds of useful features without forcing users to install special apps or change their handset operating system (OS).
Click to expand...
Click to collapse
WTF? Calyxos is an AOSP *distribution*. It isn't in "parallel" with Android, it *IS* Android, and it most certainly does require you to change the operating system (from the google build to the calyxos build).
Does this rom include gapps? Didn't see an option?