4 ms·

Unconfirmed specs[1]: * 5.5-inch HD+, 720x1440 * Snapdragon 215 SoC * up to 3GB of RAM * 32GB storage * 2500mAh battery * Android 11 Go Edition If those

Unconfirmed specs[1]: * 5.5-inch HD+, 720x1440 * Snapdragon 215 SoC * up to 3GB of RAM * 32GB storage * 2500mAh battery * Android 11 Go Edition If those are indeed the specs, I'd call it a very good option for that price point. [1] https://www.indiatoday.in/technology/features/story/jiophone-next-launch-on-september-10-specs-features-india-price-finance-options-and-all-that-we-know-so-far-1849411-2021-09-05 https://www.indiatoday.in/technology/features/story/jiophone...

wdb 5y ago
Sounds like a nice developer phone to build Android apps without high cost. I want to make an Android app and looking for a good dev/test phone
- axegon_ 5y ago
  My thoughts exactly to be honest. It's a mid-range phone which, from what I take, won't be crammed up with bloatware. I got a Nokia 5.something(forgot what it was) for my mom some time ago with pretty much identical specs and it was in the $200-ish range. It was like a year ago but I recon it's still in the 130-40$. I was really pleasantly surprised with how well it behaved. The bigger screen aside, in terms of experience it was pretty much identical to my old pixel 2, having used it for ~2 years at the time. It'd be awesome if that phone can deliver something similar for a third of the price.
- mysterydip 5y ago
  There's built-in simulators with the android developer tools. Or are you looking to test how it would look/feel on an actual phone (which is a good idea as well)?
  - axegon_ 5y ago
    In my experience those always behave terrible under Linux, regardless of what hardware I use(including my current dual-xeon with combined 28 cores setup and 64gb of ram). Never tried the emulator under other OS-es, it might be alright there.
    - jeroenhd 5y ago
      I've honestly never had trouble with the Android emulator on either Ubuntu or Manjaro, except for lacking drivers from Intel and Nvidia. I assume you've already done the basic troubleshooting steps (forcing the emulator to a single NUMA node, giving it more RAM, etc) so I can't tell you what's going on, but I can share my experience for everyone else reading this: If you've got problems like choppiness or unresponsiveness, you should check if GPU hardware acceleration is enabled in the settings and if your GPU driver hasn't been blacklisted for known stability issues. Things like KVM should also be enabled of course, but I'm pretty sure you're warned about that if you don't have it enabled. AMD and Intel both had a mobile Linux GPU driver blacklisted for hardware acceleration for a while, which made the emulator on my old laptop switch back to software based rendering, which was slow as molasses for obvious reasons. I've also learned not to run Android emulators with less than 3GiB of RAM anymore because that's the minimum a mobile OS requires these days, apparently. Also give the emulator at least 2 cores and run everything from an SSD, bbecause those are the specs the OS expects. If you don't like Google's emulator, I've also found Android x86 in Virtualbox to be reasonably stable after messing with the config for a bit. You need to mess around with it to get ADB debugging to work and to get the screen in a phone-like resolution, and you need to follow a guide to get Google's APIs on there, but after that it's pretty much good to go as far as basic Android dev goes. It's much more configurable in terms of changing specs and it doesn't seem to mind the lack of GPU acceleration as much.
      - axegon_ 5y ago
        Yeah, done all that, it was never as smooth as an actual device. It's fine though, more screens for development and one dedicated to testing which is more comfortable for me at least(disclosure I only occasionally do apps, just a once in a while "hey that'd be cool to have").
  - wdb 5y ago
    Yeah, it's always better to have a real device to test on :) Things don't behave the same
- pcurve 5y ago
  Question… Does the fact that it’s Android Go edition make it less desirable than regular edition for the purpose of app development and testing?

wdb 5y ago

Sounds like a nice developer phone to build Android apps without high cost. I want to make an Android app and looking for a good dev/test phone

axegon_ 5y ago
My thoughts exactly to be honest. It's a mid-range phone which, from what I take, won't be crammed up with bloatware. I got a Nokia 5.something(forgot what it was) for my mom some time ago with pretty much identical specs and it was in the $200-ish range. It was like a year ago but I recon it's still in the 130-40$. I was really pleasantly surprised with how well it behaved. The bigger screen aside, in terms of experience it was pretty much identical to my old pixel 2, having used it for ~2 years at the time. It'd be awesome if that phone can deliver something similar for a third of the price.
mysterydip 5y ago
There's built-in simulators with the android developer tools. Or are you looking to test how it would look/feel on an actual phone (which is a good idea as well)?
- axegon_ 5y ago
  In my experience those always behave terrible under Linux, regardless of what hardware I use(including my current dual-xeon with combined 28 cores setup and 64gb of ram). Never tried the emulator under other OS-es, it might be alright there.
  - jeroenhd 5y ago
    I've honestly never had trouble with the Android emulator on either Ubuntu or Manjaro, except for lacking drivers from Intel and Nvidia. I assume you've already done the basic troubleshooting steps (forcing the emulator to a single NUMA node, giving it more RAM, etc) so I can't tell you what's going on, but I can share my experience for everyone else reading this: If you've got problems like choppiness or unresponsiveness, you should check if GPU hardware acceleration is enabled in the settings and if your GPU driver hasn't been blacklisted for known stability issues. Things like KVM should also be enabled of course, but I'm pretty sure you're warned about that if you don't have it enabled. AMD and Intel both had a mobile Linux GPU driver blacklisted for hardware acceleration for a while, which made the emulator on my old laptop switch back to software based rendering, which was slow as molasses for obvious reasons. I've also learned not to run Android emulators with less than 3GiB of RAM anymore because that's the minimum a mobile OS requires these days, apparently. Also give the emulator at least 2 cores and run everything from an SSD, bbecause those are the specs the OS expects. If you don't like Google's emulator, I've also found Android x86 in Virtualbox to be reasonably stable after messing with the config for a bit. You need to mess around with it to get ADB debugging to work and to get the screen in a phone-like resolution, and you need to follow a guide to get Google's APIs on there, but after that it's pretty much good to go as far as basic Android dev goes. It's much more configurable in terms of changing specs and it doesn't seem to mind the lack of GPU acceleration as much.
    - axegon_ 5y ago
      Yeah, done all that, it was never as smooth as an actual device. It's fine though, more screens for development and one dedicated to testing which is more comfortable for me at least(disclosure I only occasionally do apps, just a once in a while "hey that'd be cool to have").
- wdb 5y ago
  Yeah, it's always better to have a real device to test on :) Things don't behave the same
pcurve 5y ago
Question… Does the fact that it’s Android Go edition make it less desirable than regular edition for the purpose of app development and testing?