Related
Hi, after installing a new kernel with multitouch and norefresh through CWM, and considering installing the overclocked one by guevor (update: installed oc kernel), but I had some newbie questions about restoring the Kernel in case I wanted to go back to stock or update to 1.2.1.
I have taken full factory backups at 1.0.1 with noogie by copying the physical disk with diskimage, and another backup with the 1.2 rooter gui. I have since updated to 1.1 (no backup on 1.1) and rooted before I installed the new kernel. Is there any way to revert to the default kernel on 1.1.0?
Also, Is there any way to adjust the contrast in fastmode? The text is barely readable and an unusual amount of gosting (maybe something is wrong), but it's super fast.
Thanks so much, and this community has been a lifesaver since last night when I got my nook. Go easy on me since I've only had my nook for a few hours, I've been reading a lot and searching these forums for hours.
Also, bonus questions:
1. Is it possible to set a custom wallpaper (behind the icons)
2. Is it possible to actually decode/play videos? no video apps seem to work, even p2p ones.. also youtube videos / flash doesn't work which is strange because android 2.1 should support video right?
3. What's the consensus about screen damage/use using fast mode? Brand new nook.... lol. I'm not sure if I'm shortening the 10 year life of the e-ink display to 1 week.
jun127 said:
Hi, after installing a new kernel with multitouch and norefresh through CWM, and considering installing the overclocked one by guevor (update: installed oc kernel), but I had some newbie questions about restoring the Kernel in case I wanted to go back to stock or update to 1.2.1.
I have taken full factory backups at 1.0.1 with noogie by copying the physical disk with diskimage, and another backup with the 1.2 rooter gui. I have since updated to 1.1 (no backup on 1.1) and rooted before I installed the new kernel. Is there any way to revert to the default kernel on 1.1.0?
Also, Is there any way to adjust the contrast in fastmode? The text is barely readable and an unusual amount of gosting (maybe something is wrong), but it's super fast.
Thanks so much, and this community has been a lifesaver since last night when I got my nook. Go easy on me since I've only had my nook for a few hours, I've been reading a lot and searching these forums for hours.
Also, bonus questions:
1. Is it possible to set a custom wallpaper (behind the icons)
2. Is it possible to actually decode/play videos? no video apps seem to work, even p2p ones.. also youtube videos / flash doesn't work which is strange because android 2.1 should support video right?
3. What's the consensus about screen damage/use using fast mode? Brand new nook.... lol. I'm not sure if I'm shortening the 10 year life of the e-ink display to 1 week.
Click to expand...
Click to collapse
I. http://nookdevs.com/Nook_Simple_Touch_restore_to_stock
II. No. Try to change font in your reader. http://forum.xda-developers.com/showpost.php?p=20069292&postcount=10
or use NoRefresh to read text.
or try different reader for eg. https://code.google.com/p/apv/downloads/list
1. if you change your launcher from 'ReLaunch' to for eg. 'LegacyLauncher' then yes.
2. RockPlayer + software decoding = playing videos
https://play.google.com/store/apps/details?id=com.redirectin.rockplayer.android.unified.lite&hl=en
3. Your battery will probably die faster than the screen. I used NoRefresh and FastMode from the start and the screen still works fine. On the other hand my battery died (2 weeks before the end of warranty).
osowiecki said:
I. http://nookdevs.com/Nook_Simple_Touch_restore_to_stock
II. No. Try to change font in your reader. http://forum.xda-developers.com/showpost.php?p=20069292&postcount=10
or use NoRefresh to read text.
or try different reader for eg. https://code.google.com/p/apv/downloads/list
1. if you change your launcher from 'ReLaunch' to for eg. 'LegacyLauncher' then yes.
2. RockPlayer + software decoding = playing videos
https://play.google.com/store/apps/details?id=com.redirectin.rockplayer.android.unified.lite&hl=en
3. Your battery will probably die faster than the screen. I used NoRefresh and FastMode from the start and the screen still works fine. On the other hand my battery died (2 weeks before the end of warranty).
Click to expand...
Click to collapse
Thanks for your help! I've seen you around the forums quite a bit and learned a lot from reading your past posts.
I was able to play rmvb with rockplayer (still in beta?), but couldn't figure out how to make the streaming p2p tv applications work (also rmvb) such as PPTV, and PPS which usually work on everything (although they installed properly and also tried downloading and installing codecs. I had to download the rmvb file from pptv and play it manually on rockplayer.
Thanks for the Legacy Launcher tip, looks great! Edit: Unfortunately I can't get wallpapers to work there either. When I select wallpaper, it gives me 2 options, from pictures, or from wallpapers. pictures shows "no media", and wallpapers are just a few standard wallpapers. I can't find anywhere to select a picture from the SD card, and I can't find any "media" or wallpaper folder in file browser. UPDATE: I was able to get wallpapers by downloading the app "wallpaper changer" and "ES file explorer".
Interesting to know about the battery, I was also worried about that. I managed to suck through 35% of the battery in 5 hours. I didn't buy the official wall charger, but I used a chinese 5 volt adapter I had laying around after I kept getting the following problem:
Another problem I've been having is that when I plug the NST into my computer via USB everything goes ballistic on my nook, it rapidly connects and drops USB mode, and then if I go into settings both internal storage and SD card are greyed out "unavailable". What could cause that?
Finally, is there anyway to get ADB on windows without downloading the entire android SDK? I want to apply the IMEI fix to install whatsapp, but I can't get ADB to work at all. UPDATE: I solved it, adb.exe baby and I guess you can use that with commander. My problem was the default wireless adb app wasn't working, I installed wifi adb and it worked. Very odd, since usb connection didn't work, but at least I got my IMEI and whatsapp. Any methods for getting working contacts on NST? I'm going to try the contacts.db workaround if there is no other options, but I'm hoping for something less risky and automated.
I also wanted to note that I solved the 24 hour wait time on google market, go to gmail and add a second contact and sync that contact. The first google account will automagically work.
jun127 said:
...
Click to expand...
Click to collapse
1. I think that 'nook' launches 'hardware video decoding' by default when you try to open up a stream from the apk so the only option is to download videos and play them locally. 'TubeMate' is able to do this.
http://m.tubemate.net/
On the other hand if the apk contains a video player with 'software decoding' this could work like it should.
I know that 'BeyondPod' was able to play audio podcasts from within application. Haven't tested it on videos.
https://play.google.com/store/apps/details?id=mobi.beyondpod&hl=en
2. Don't forget to turn all useless animations in the Launcher off and get "Minimalist Black - ADW Theme'. You can find it in 'TouchNooter' package.
3. Try to use a different micro usb cable. Sounds like yours is broken.
4. In the current version of NookManager, ADB through USB is not supported.
5. Can't help you with that right now.
For the sake of completeness (most of you will have noticed this app already): For a change, Samsung have done a fantastic job and released a great app called "Game Tuner". It's simple to use, doesn't even need root, and renders all of the stuff I wrote below obsolete!
What it does is, it renders each game at an individual screen resolution, frame rate, and texture quality (texture quality only working for me since MM upgrade).
All you have to do is install Game Tuner from Google Play (above link), start it, follow the instructions to install GameMode through Galaxy Apps, and you're good to go. Create a custom profile, set default values (e.g. 75% resolution=1080p), activate the profile. Set different resolutions for other games. And if you want to control apps other than games, tap top left menu, and chose "Apps".
I've done the same benchmarks as with the method below, and the results were exactly the same, so it's really working, but without messing up the UI or impairing system apps like the camera.
Hey folks,
I've decided to put together a little wrap-up of the stuff I found regarding the sometimes rather poor 3D performance of the Note 4. This is only for experienced users who are familiar with things as rooting, backups, adb, in general: unbricking their phone if bad things happen. As usual, I don't take any responsibilty if you brick your phone or destroy it in any other way. Just make sure to activate USB debugging, and if anything goes wrong, either follow this guide, or simply reflash your ROM.
Just make sure you make a Nandroid or at least Titanium backup before you try this. Better safe than sorry...
It comes as no surprise that running a cpu at almost 3GHz takes its toll. Demanding games such as Real Racing 3 or XCOM:EW, or emulators such as PPSSPP cause the cpu to heat up rapidly, until it reaches ~80°C, before it gets mercilessly downclocked to cool down. At this point, you start noticing more or less pronounced performance drops. There isn't really much you can do, except using a custom kernel to downclock cpu & gpu, before your phone does.
But apart from that, there is another, even greater performance hog, which is also one of the main reasons for the overheating issue: the QHD resolution of our Note 4's screen. We're talking about a 3.69 megapixel resolution, that's almost twice as much as Full HD (2.07 MP), and exactly four times as much as HD (0.92 MP). Gorgeous and brilliant, beautiful to look at during everyday use, but pushing the Adreno gpu to its limits when it comes to gaming.
So, an ingenious guy called NOMone has created a nifty little tool called "NOMone Resolution Changer", already some time ago. It's available for free at Google Play. It's been widely discussed here on xda and on other forums, but I want to share my experience specifically on the Note 4.
Btw, it seems he only posted here two times, so he's most likely not active anymore, but you should head over and thank him anyway.
Now, if you're thinking "no way, why should I deliberately sacrifice my QHD resolution?", read on nonetheless. Because this tool is extremely easy to use, and if you only switch the resolution before playing a game, and revert afterwards (it's only one click), you won't have to sacrifice any visual quality. The settings stick after a reboot, so make sure to really restore defaults if you want to go back to QHD.
The trick is to use the appropriate resolution and dpi values, so your screen doesn't get mixed up.
The results are impressive, sometimes even staggering. Has anyone ever wondered why PPSSPP doesn't perform better on a Note 4 than it does on a Note 2? Here's the reason. PPSSPP gains so much performance , it's almost unbelievable.
I've also done some benchmark runs to measure the improvements (yeah, I know, benchmarks are bad, but still :angel: ). The improvement is clearly visible and, even more important, reproducable:
GFXBench GL Benchmark 3.1 (Manhattan):
1. 1440p: 449,4 frames, 7.2 fps
2. 1080p: 800,6 frames, 13 fps (+78%)
3. 720p: 1621 frames, 26 fps (+261%)
4. 480p: 2728 frames, 44 fps (+507%)
This is plain awesome. The Note 4 is listed even lower, with 434 frames, in the device list, while the 1080p Galaxy S5 reaches 775 frames.
AnTuTu (gpu score only):
1. 1440p: 16210
2. 1080p: 21253 (+31%)
3. 720p: 22524 (+40%)
4. 480p: 22523 (+40%)
Obviously, by comparing scores 3 and 4, the Note 4 hits the fps limit at HD resolution, so there's no more room for improvement in AnTuTu.
Seascape Benchmark (detail setting: Very High):
1440p: 26.9 fps
1080p: 46.6 fps (+73%)
720p: 53.4 fps (+99%, sometimes hits the frame limit of 59.0 fps)
480p: 59.0 fps (+119%, hits the frame limit constantly).
This is a beautiful OpenGL ES 2.0 test, so no cpu scores interfering with the result. Again the fps limit prevents a higher score, but nonetheless, this is pretty amazing.
Other benefits: if you're using a custom kernel, you can run gpu-intensive games at lower cpu speeds to keep the cpu temperature in check. In my case, XCOM:EW runs smoothly @ 30% (!!) cpu speed. This way, the cpu doesn't heat up to more than 60°C, which means it doesn't get downclocked while playing. If you like, you can also automate the process of setting the cpu speed with the aptly named app "Automate" . Which is fantastic, btw.
Now what about visual quality?
Seriously: it's hard to tell the difference. If you look very closely, you can see the display isn't as sharp in FHD as in QHD. But if you look that closely, you're in constant danger of triggering some random app with the tip of your nose. At normal viewing distance, especially while gaming, it's impossible to tell the difference.
So, are there any drawbacks?
Yes, there are: the UI gets messed up a bit (e.g. bigger status bar, some Samsung apps don't fit on screen anymore), and NOMone Resolution Changer doesn't seem to work with CM12.1. Well, at least for me, and other users reported so as well. I tested it some time ago, while I was on CM12.1, and even thought it was a fake app, which it isn't! Seems that the resolution is somehow hard coded into CM12, and you can only switch dpi. There's probably nothing you can do when you're running CM, except try your luck.
But if you are running a Touchwiz ROM, stock or custom, it should work as intended (Emotion Revolution ROM r10.1 in my case). And you can simply ignore the UI issues, as long as you only switch the resolution for gaming. It's not a real issue then, because the status bar is hidden anyway while the game is running.
If you want to keep your device running at FullHD permanently, it's a bit more complicated: first, you'll need Xposed, so you can use the App Settings module to set Android System and SystemUI to 480 dpi. This'll fix the UI (Not needed. Just reboot)
Some apps like phone, contacts, S-Note scale down to the lower dpi setting, whereas Samsung keyboard and the camera won't (camera works, see post #10 below).
So you'll have to install another keyboard like SwiftKey (if you don't have it already), find a working camera app (3rd party or hacked Note 4 camera), and clear your Google Play data (at least I had to, it wouldn't install any apps after the changes), and you're good to go. There might also be other issues I'm not aware of yet. But apart from the ones I described, everything's working fine so far.
Have fun!
you don't need root to change the dpi and the resolution.
enable usb debugging and adb the following:
adb shell wm density 480
adb shell wm size 1080x1920
adb reboot
if you want to revert back:
adb shell wm size reset
adb shell wm density reset
adb reboot
the changes persist after reboot.
I am using it like that for some time. Everything is much faster. Even the browsing..
the only 2 bugs I noticed is the Samsung keyboard (i switched to swiftkey) and the action memo (c'mon Samsung devs, code properly..)
mitko76 said:
you don't need root to change the dpi and the resolution.
enable usb debugging and adb the following:
adb shell wm density 480
adb shell wm size 1080x1920
adb reboot
if you want to revert back:
adb shell wm size reset
adb shell wm density reset
adb reboot
the changes persist after reboot.
I am using it like that for some time. Everything is much faster. Even the browsing..
the only 2 bugs I noticed is the Samsung keyboard (i switched to swiftkey) and the action memo (c'mon Samsung devs, code properly..)
Click to expand...
Click to collapse
You're right, you don't necessarily need this tool. All it does is simplify the process. And you should really be able to use adb commands to fix your phone when you mess it up. But NOMone's tool comes in very handy when you're away from your pc and need to switch resolutions quickly. In my case, it's when I want to use the camera: the UI is messed up at 1080p and I haven't found a way to fix it yet, except switch back to QHD. Or the other way round: if you want to play a demanding game on the train at lower resolution, but go back to QHD again.
I'm using 1080p resolution permanently now, because I get a smoother UI, a cooler phone, better battery life, and much better performance. I hope they don't give us 5" UHD screens next...
Could you please explain what is wrong with the camera on 1080p 480dpi? I am using these settings and have 0 problems with the camera. Just curious.. If possible please attach a screen shot. Cheers
The UI is messed. I can't see most of the buttons, and can't take a photo, see attached screenshot.
Xelasarg said:
The UI is messed. I can't see most of the buttons, and can't take a photo, see attached screenshot.
Click to expand...
Click to collapse
Using my method and my values, it is absolutely fine for me. Do you restart after changing the resolution and the dpi?
I am on UK BTU 5.1.1
mitko76 said:
Using my method and my values, it is absolutely fine for me. Do you restart after changing the resolution and the dpi?
I am on UK BTU 5.1.1
Click to expand...
Click to collapse
I even wiped /cache and /dalvik. Strange. My device is a Snapdragon N910F. Is yours an Exynos N910C perhaps? If not, would you mind sending me your camera apk for testing?
Thanks!
Xelasarg said:
I even wiped /cache and /dalvik. Strange. My device is a Snapdragon N910F. Is yours an Exynos N910C perhaps? If not, would you mind sending me your camera apk for testing?
Thanks!
Click to expand...
Click to collapse
very strange indeed. My device is n910f as well. Not rooted and fully stock. I used the Debloater app to disable all unused apps (works via adb) and the method descried in my other post to change the resolution and dpi. The camera is working absolutely fine i.e. no visual changes or glitches. As I am not rooted I am not sure if I can give you the camera apk. It is basically the same apk as in the stock 5.1.1 BTU rom. Try my method on the stock rom with my values and I am sure it will work.
Cool
mitko76 said:
very strange indeed. My device is n910f as well. Not rooted and fully stock. I used the Debloater app to disable all unused apps (works via adb) and the method descried in my other post to change the resolution and dpi. The camera is working absolutely fine i.e. no visual changes or glitches. As I am not rooted I am not sure if I can give you the camera apk. It is basically the same apk as in the stock 5.1.1 BTU rom. Try my method on the stock rom with my values and I am sure it will work.
Click to expand...
Click to collapse
Well, I went ahead and downloaded _alexndr's COI3 stock debloated rom base (Deodexed), extracted SamsungCamera3.apk, replaced the one in my /system/app dir, set permissions, rebooted, and everything's working fine now. :good:
No idea what the Emotroid guys did to the camera app.
I've attached the apk to this post in case anyone else is having this issue.
Man, I've been playing XCOM:EW at 720p, and my phone didn't get warmer than 59°C, even after 2+ hours. And the performance boost is just so incredible... Turns out I don't even mind the 720p resolution in 3D games, it didn't bother me at all.
Just a warning:
I just managed to render my phone useless with this. After changing resolution and DPI, the phone did a soft reboot (as it should), startet booting, then, after the initialisation of systemUI reboots. Has been Bootlooping the past hour. ADB doesn't work, as reboot it's unauthorised and boot loop doesn't allow for any authorisation. Tried resetting via build.prop and userinit.sh. Even Direct Script Injection into init.rc didn't work.
Cache wipe -> no chance
System wipe and reflash -> Nope
In the End i ended up factory resetting and reflashing complete rom. This did work. Not to rant or anything, just a little story for those that are not capable to troubleshoot problems: This might screw your Installation!
domsch1988 said:
Just a warning:
I just managed to render my phone useless with this. After changing resolution and DPI, the phone did a soft reboot (as it should), startet booting, then, after the initialisation of systemUI reboots. Has been Bootlooping the past hour. ADB doesn't work, as reboot it's unauthorised and boot loop doesn't allow for any authorisation. Tried resetting via build.prop and userinit.sh. Even Direct Script Injection into init.rc didn't work.
Cache wipe -> no chance
System wipe and reflash -> Nope
In the End i ended up factory resetting and reflashing complete rom. This did work. Not to rant or anything, just a little story for those that are not capable to troubleshoot problems: This might screw your Installation!
Click to expand...
Click to collapse
Hence the warning at the beginning of the thread.
But seriously: which method did you use? The NOMone app or the adb commands? Because only the adb command needs a reboot to take effect, NOMone does not reboot: it changes the resolution on the fly, then waits 10 seconds for confirmation and switches back to default resolution otherwise.
It's impossible to tell what went wrong in your case, might have been anything from a bad adb command to a malfunction of the app or your rom. I guess if you enter bad values, both methods might break your SystemUI. I managed to do so by using Automate to activate the shell commands on app launch (no bootloop, though, only permanent FC of SystemUI), but I was able to fix it with adb easily.
It's a shame it didn't work for you, most people who are using this method are very happy with it.
THANKS !
dooes this improve battery as well /
gonna try this
Boody hegan said:
THANKS !
dooes this improve battery as well
Click to expand...
Click to collapse
Yes, it does, at least a bit. The screen does still burn a lot of juice because it's so big and bright, but the cpu stays much cooler. Less heat=less power consumption.
Thanks alot , i'm on simplrom v5c and googy max kernel v2
can this still work ..
Xelasarg said:
Hence the warning at the beginning of the thread.
But seriously: which method did you use? The NOMone app or the adb commands? Because only the adb command needs a reboot to take effect, NOMone does not reboot: it changes the resolution on the fly, then waits 10 seconds for confirmation and switches back to default resolution otherwise.
It's impossible to tell what went wrong in your case, might have been anything from a bad adb command to a malfunction of the app or your rom. I guess if you enter bad values, both methods might break your SystemUI. I managed to do so by using Automate to activate the shell commands on app launch (no bootloop, though, only permanent FC of SystemUI), but I was able to fix it with adb easily.
It's a shame it didn't work for you, most people who are using this method are very happy with it.
Click to expand...
Click to collapse
It was completely my fault. I knew what i was getting into, so no problem. It's just that, the "mistakes" i did could easily be done by accident by some less experienced users.
First off, i'm on CM12. NOMones Sollution doesn't seem to work there. CM does a "Hot Reboot" to reload the system UI. No matter what you set in NOMones app, the resolution doesn't change. DPI does though. This seems to be a CM related issue. Maybe they hardcode the resolution at build time...
After that i tried another app, which had the Orientation labeled backwards. So it set 1920x1080 landscape instead of portrait. After that the Phone Bootlooped the System UI. It would always boot up to the PIN Enter Screen and then reboot.
As said, no big Problem. I knew what to do and was able to bring my phone back to working state. Just make sure that you are 100% sure about the numbers you put into such apps and keep in mind that even with such "small" changes you should always have a up to date Backup of everything.
Boody hegan said:
Thanks alot , i'm on simplrom v5c and googy max kernel v2
can this still work ..
Click to expand...
Click to collapse
It should, unless SimplROM is CM12-based. NOMone Resolution Changer, as well as similar apps and the adb method, aren't limited to specific devices. In theory, they may all work on all Android phones. You'll have to try it out yourself, just make a backup before you do so!
domsch1988 said:
It was completely my fault. I knew what i was getting into, so no problem. It's just that, the "mistakes" i did could easily be done by accident by some less experienced users.
First off, i'm on CM12. NOMones Sollution doesn't seem to work there. CM does a "Hot Reboot" to reload the system UI. No matter what you set in NOMones app, the resolution doesn't change. DPI does though. This seems to be a CM related issue. Maybe they hardcode the resolution at build time...
After that i tried another app, which had the Orientation labeled backwards. So it set 1920x1080 landscape instead of portrait. After that the Phone Bootlooped the System UI. It would always boot up to the PIN Enter Screen and then reboot.
As said, no big Problem. I knew what to do and was able to bring my phone back to working state. Just make sure that you are 100% sure about the numbers you put into such apps and keep in mind that even with such "small" changes you should always have a up to date Backup of everything.
Click to expand...
Click to collapse
Right, thanks for clarification. I don't remember the hot reboot in CM12, but I know the resolution switch didn't work when I tried it on my Note 2 some time ago. Funny that for once Touchwiz is more customizable than CM.
If you're still interested, but hate the Samsung colour scheme (like me), you can try out Emotion Revolution ROM r10.1. It's based on the latest COI3 TW firmware, but they themed the notifcation/status bar and toggles to somewhat more like stock Android, see attached screenshot. Looks pretty sleek, performance is easily on par with CM12, and the Emotion kernel has tons of great tweaking options. Or you can go for their Port Note 5 r2.1 ROM, also based on COI3, which should offer full Theme Store support. That's the one I'll flash next. :good:
Xelasarg said:
Right, thanks for clarification. I don't remember the hot reboot in CM12, but I know the resolution switch didn't work when I tried it on my Note 2 some time ago. Funny that for once Touchwiz is more customizable than CM.
If you're still interested, but hate the Samsung colour scheme (like me), you can try out Emotion Revolution ROM r10.1. It's based on the latest COI3 TW firmware, but they themed the notifcation/status bar and toggles to somewhat more like stock Android, see attached screenshot. Looks pretty sleek, performance is easily on par with CM12, and the Emotion kernel has tons of great tweaking options. Or you can go for their Port Note 5 r2.1 ROM, also based on COI3, which should offer full Theme Store support. That's the one I'll flash next. :good:
Click to expand...
Click to collapse
Nah, TW is no option... I choose CM because of the straight forward no bllsht Apps approach. Plus Nightly builds via OTA... In no possible way am i going back to TW
AnTuTu Benchmark @ 1080p, performance governor, stock cpu frequency (2.65 GHz): :highfive:
(OK, cpu was also very cool when benchmark started, 28°C).
Hello, everyone, the Phoenix system x86 version v1.1 released. We added several new features to this version. For example, root permissions support, keyboard mapping function, Ethernet settings, you may not know where to open these functions, I will give you a detailed presentation.
Download：http://files.phoenixos.com/os/PhoenixOSInstaller-v1.1.0.exe
Update：
System
Add root access；
Add keyboard mapping function；
Add Mirror output function like HDMI;
Add Ethernet settings[font=宋体]：[/font]Boot default Ethernet connection
Add Resolution adjustment function;
Add Graphics adapter, mainly contains GTX700\800\900 series;
Repair Game can't connect network;
Optimized Reduce the maximum volume of the broken sound models;
Optimized Reduce the probability of crash by Atom processor;
The task bar & Notification Center
Revision notification center icon
Start menu
Optimize the display of large screen devices;
Browser
Optimizing UA display logic;
Update ad blocking list;
CZ FileManager
Increase picture and wallpaper images (Picture directory);
Network neighbors will pop up after the addition of success;
Repair the bug that desktop icon disappeared after the application upgrade;
Fix the bug that APE format file has no playback application optional;
Application of the market will not prompted to upgrade of FileManager;
Fix the bug that native music applications failed to add music;
Fix some other bug;
Enhanced stability;
More info:
http://bbs.phoenixstudio.org/en/showthread.php?tid=1716
Official mirror uploaded by @Dante_xu - it will soon be added to the official download site and it's already added on the official forum:
https://mega.nz/#!VgNCGJTD!y62XM6nge9OTkKMp-nRbZoGKYoHqGB0nYiLyxhbBN7I
It is worth mentioning that in this release, if we toggle the root ON, we can freely modify the system partition! No need for any custom files!
Does "Pokemon Go" app works with this version?
good update but remix os is still far superior.
@slybunda At what? I can also say my bike is superior without listing it's pros.
more stable and better 3d support
It all comes down to specific hardware @slybunda . On my devices Phoenix is more stable and has more features at the same time plus a better design. I personally don't care about 3D acceleration - android-x86 would be enough for games because those are usually ran in fullscreen, so no desktop UI needed.
Sent from mobile
I love your rom so much @Regnas I updated a port that already existed for the vzw gs4 just so I could keep using it for my own personal use. It's the best rom ever, 10,000xlove. Sorry that's a little off topic because it's not really the same rom. This is just the first post I've seen from you and had to shoutout some love
@tdct12 do have in mind that this is an official release by Chaozuo @Regnas does deserve the love for publishing it though
tdct12 said:
I love your rom so much @Regnas.....
Click to expand...
Click to collapse
Lol...... see post above....
Still playstore not included?
It is included
Sent from mobile
Has anyone had any luck booting this from USB? I have tried from USB and SD, but have had no luck. I was able to dual boot from my SSD drive, but it seemed to make my Win 10 OS lag a lot. I ran the installer and selected install to U, and let it install. I do have bios setup to boot from USB first and even tried it through the boot menu. It almost seems like the drive is not bootable though. Any ideas or thoughts?
Verification failed error 15. Any work around?
I have an ebay unit. RK-A701 is printed on the face of it. Theres not a whole lot of info on the web that I can find on this specific model.
It is running 4.4.4
Chip: RK3188
7" display
1200x600 resolution (that's what the description in the add says)
But it seems to me that the display is 800x400, everything just seems very large on the screen. I found the password to enter the factory settings, which is "66668888" and while going through there I found a setting to change the display size from 7" all the way up to 10". I didn't try to change it yet because I don't want to end up not being able to change it back if it ends up not displaying correctly. So I wanted to see if anyone knows anything about this setting? Ive been searching for some details about this setting but I cant seem to find anything.
With a 7" display, if I changed it to 10" will I mess it up? This may be a dumb question, and I apologize in advance. Im just very new to the android head unit scene. So im trying to learn as much as I can without bricking my unit.
Thank you!
I changed the display resolution of my android headunit to 1200x600 and only around 3/4 of the screen was shown. I panicked because the button to revert the changes back got hidden on the bottom right of the screen. Thankfully, I was able to restore the original screen resolution. Not sure if the same will happen to your unit, but based on what I experienced, keep your default screen resolution.
Sent from my SM-G935F using Tapatalk
lester77701 said:
I changed the display resolution of my android headunit to 1200x600 and only around 3/4 of the screen was shown. I panicked because the button to revert the changes back got hidden on the bottom right of the screen. Thankfully, I was able to restore the original screen resolution. Not sure if the same will happen to your unit, but based on what I experienced, keep your default screen resolution.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Thank you for the response! I tried messing around with the screen size after figuring out how to get kingroot to work. It actually didn't change anything.
What I am having trouble with is keeping a live wallpaper set. Everytime I restart it the wallpaper resets to default
thatsbk said:
I have an ebay unit. RK-A701 is printed on the face of it. Theres not a whole lot of info on the web that I can find on this specific model.
It is running 4.4.4
Chip: RK3188
7" display
1200x600 resolution (that's what the description in the add says)
But it seems to me that the display is 800x400, everything just seems very large on the screen. I found the password to enter the factory settings, which is "66668888" and while going through there I found a setting to change the display size from 7" all the way up to 10". I didn't try to change it yet because I don't want to end up not being able to change it back if it ends up not displaying correctly. So I wanted to see if anyone knows anything about this setting? Ive been searching for some details about this setting but I cant seem to find anything.
With a 7" display, if I changed it to 10" will I mess it up? This may be a dumb question, and I apologize in advance. Im just very new to the android head unit scene. So im trying to learn as much as I can without bricking my unit.
Thank you!
Click to expand...
Click to collapse
Hey. You need a root, get root, looking build.prop /system/build.prop file, edit it in the PDI line set 200 or 160. This will change the resolution of your screen. More https://4idroid.com/kak-izmenit-kolichestvo-tochek-na-dyujm-dpi-na-ekrane-android-root/ use google translator. Do not forget to install rw/r/r build.prop file after the change and editing, and then reboot the device. To edit, you can use https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer&hl=ru
HELP
Okay so ive encountered a problem. I installed nova launcher, and slightly adjusted the DPI on my unit. BUT now the unit boots up like it normally would but the homescreen is blank! The screen still reacts to touch, I can slide the notification bar down Bluetooth and wifi still connect to my phone. But no access to settings or ANY apps so I can set the default launcher!
I have been unable to boot into recovery either. I cant figure out how to do it. I'm at a total loss on what to do now. I really need some help on how I can possibly fix this. Would hooking my laptop up via USB allow me to execute commands through ADB to force a reset? Or uninstall a certain app? Ive never had to do something like this before so I'm open to try anything at this point!:crying:
I have two questions:
1. How do you go about changing the resolution?
2. How do you go about to factory reset the HU?
I have updated mu HU and now it is only showing part of the screen as it is displaying in a different resolution. The HU is a Alps FF5000 Model 8227L and I have tried a lot of different roms, but with no success.
I have the same problem, screen showing 3/4 only of the whole screen the rest is hidden... any solution anyone?? pleaseeee
i have the same issue what to do
Same Issue
I have CAR Din radio, with bellow details,
Model :- PX3 (800 x 480 o)
Android version :- 7.1.2
MCU Version :- MTCE_KSP_V3.07_1 (Mar 13 2019 10.05.46)
Serial number :- D31644CC3D2DEAB7
Build No :- px3-Malaysk 7.1.2 NHG47L eng.hct.20180426
I have updated the machine and now facing issue of screen resolution,
The App icons are out of box, and unable to operate the same.
Please need your help to fix it....
Explain in steps to fix it....Thank you in advance
SHEKHARSHINE said:
I have CAR Din radio, with bellow details,
Model :- PX3 (800 x 480 o)
Android version :- 7.1.2
MCU Version :- MTCE_KSP_V3.07_1 (Mar 13 2019 10.05.46)
Serial number :- D31644CC3D2DEAB7
Build No :- px3-Malaysk 7.1.2 NHG47L eng.hct.20180426
I have updated the machine and now facing issue of screen resolution,
The App icons are out of box, and unable to operate the same.
Please need your help to fix it....
Explain in steps to fix it....Thank you in advance
Click to expand...
Click to collapse
Do you have hammer
Very scarce info everywhere, but quite a few people already use this $80 super-powerful watch including me (which is basically a micro-smartphone).
Many video reviews already.
I personally think that such powerful watch (much more powerful than my cheap 2016 tablet on previous Mediatek chip with less RAM) is a such small smartphone with illusion like it’s watch made by very modified version of Circle launcher with edited Android 6. I don’t see any limitations on this watch to run full stock Android OS here from the M6737M series smartphones, if ported. Even now all full-featured apps from Google store made for smartphones are perfectly runs here, including very big navigation apps and even the full “battery saver” function present from smartphones (first one which I see on Android watch ever). The only limitation which I noticed is very small display (specific apps cannot fit) and badly edited Android OS (like completely deleted status bar from OS, any 3rd-party status bar apps are installing fine but crashing on settings). Most 3rd-party launchers from Google store and open sources are installing here (only with few exceptions) - the most stable one I’ve found is open source “Essential Launcher” ver. 1.3.
My feeling from “lift wrist turn on” function with “swipe pages” makes almost iPhone X experience here, no any buttons needed, very stable power on only by view and swiping windows (including closing them by swiping to the right) makes very good feedback to the user.
Everything spoiled only by edited OS - awful work with fonts, too many illogical Menu lists, deleted functions like not present “Storage” in OS settings(only shortcut to file explorer) - the USB storage media not adding because of edits on OS level, considering normal micro-USB & even if you turn on “usb media” in developer settings.
Very few watch-faces with no way to install any others, it’s obviously fake feature to make you feel and use them as watch.
So, what I think many would be glad to see here - the root is the most important goal for now(developer menu allows bootloader unlock-not sure if it’s true because USB media settings there not works), maybe putting the normal Android is the next goal.
The root is very needed to firewall for very shady apps here, it’s very powerful device so it have full smartphone spyware, like notorious MTK Logger & Thermal Manager, which can work at sleep mode (it is almost suspicious that they broke USB media function so user can’t bypass network connection for installs). Root needed to work with display resolution and etc.
Edit: the processor by Aida app recognized as MT6737M but on Aliexpress you can find watch easily by search term processor "MTK6737M" (only like 7 sellers total).
I have the H5 as well, and you're correct! The main draw back is the stripped down OS, for example the call forwarding features are missing..
Ordered one of these a few weeks ago, should be getting delivery soon. Interesting to see how it performs, my last android watches have been mt6572 & mt6580, both of these I ported full Android versions to, I may give it a go at porting a full Android version to this in the future
Check this also:
https://forum.xda-developers.com/sm...dorid-6-0-finow-q1-pro-smartwatch-4g-t3745271
Well I got mine today, seems good so far. As for alternative launchers tried a few that work OK, if you want to change the clockskins for now I have found that Universal Launcher New Gen works just fine (you add clockskin folder +clockskins)
https://play.google.com/store/apps/details?id=com.ricktop.ClockSkinCoco
I use mine at least 2 weeks maybe. Without root (which I plan to do but don't have time right now) I do not connect them to any Internet, so I'm using them as just watch (it's my first smartwatch). Files I'm sending through bluetooth from my Android phone, quite neat that you can install apps from bluetooth menu right away.
About battery - very good, if you don't connect them to networks at all, with battery Saver on & "wrist move activation" off they can work whole week on 1 charge (this includes some extensive using in 2 days on winter street with GPS apps, camera-video, constant time checking and etc.). They CAN HOLD MORE days, after the full charge, watch calculated the battery to the 15 days of work - which is believable, as I see now if you will check only time manually they can easily save 1 charge to 12-13 days. I use charger with them only once at week, it's quite shocking to read Apple Watch forums where people making that every 2-3 days.
They're quite powerful - making the zip archive internally from 250Mb photos/videos takes something like 2 minutes.
Because the step-counter here work always (even if you take them to the other room) - this device is just made for the SmartNavi (open source navigation app which use mainly step-counter with rare or no GPS connection for battery saving).
Can't wait for a custom recovery to be made for it, so I can root it. Tried all the rooting apps out on the web and none work so far.
Well I have managed to get Root access, using Magisk, and flashing patched boot image, struggling to create a TWRP recovery. Hoping someone out there can come up with a custom recovery.
Managed to port TWRP to it, but it is in miniature! going to have a play around with it to see if I can make it usable. Anyone with suggestions be grateful - well gave up on trying to amend TWRP resolution, and installed flashify - just flashed an AOSP ROM to the H5, happy days!
Well done stevea76
A step by step or point in the right directions kinda 'guide' would be really appreciated, cos the H5 with its stock funos is far from fun... sure its usable but no fun.
Wizard2004 said:
Well done stevea76
A step by step or point in the right directions kinda 'guide' would be really appreciated, cos the H5 with its stock funos is far from fun... sure its usable but no fun.
Click to expand...
Click to collapse
I will put something together at the weekend, by then I should have something usable, don't want people breaking their new toys!
stevea76 said:
I will put something together at the weekend, by then I should have something usable, don't want people breaking their new toys!
Click to expand...
Click to collapse
It would be interesting to find if there's any "recovery mode" on stock ROM image at all, considering that there's only 1 button. On similar watches from Samsung and etc they have quite awkward way to enter recovery - like some swipe to the left in time of logo showing and etc. I tried to repeat any swiping during boot - nothing...
Also, by the usual use of watch (almost a month now) I can say that in my case of use the battery holding 1 full charge for 7 days, so a week, the same amount calculated by OS also. That's the battery regime or mode which is now constant in my case (it can be different in situation of other people).
The battery here can be saved even more for a week - I managed to notice that "sleep stat" function are working here at all times and cannot be turned off like step counter in this Android OS, at the night time it randomly turning on the pulse checker light even if you not wearing them, which using the battery (not a big deal, but using some).
Wizard2004 said:
Well done stevea76
A step by step or point in the right directions kinda 'guide' would be really appreciated, cos the H5 with its stock funos is far from fun... sure its usable but no fun.
Click to expand...
Click to collapse
Here is the link to the AOSP ROM I ported to the H5.
I must express it is a long winded way to flash it as I am not technically minded, just playing at it, and only do this if you have the stock ROM downloaded as a backup to revert back to and don't mind the possibility of wrecking your toy!, the only reason for me doing it this way is that the recovery TWRP I ported is functional, but not set for the screen size for the H5 so unless you have bionic eyes it is nearly impossible to use, hence the reason for my 'workaround' (note: If anyone can make the TWRP scaled for the watch, just flash the ROM in the usual way)
Here is a 'sort of' guide and link to files.
https://www.androidfilehost.com/?w=files&flid=252561
1. Flash
Microwear_Magisk_Patched_Boot_IMG using splash tool, reboot device.
2. Install Magisk Manager from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page4
Open Magisk manager and go to settings, set default action to 'Grant'
You now have root.
3. Flash
Microwear_H5_Recovery_TWRP using spflashtool.
4. Install
Flashify (for root users) from the Playstore.
5. Download directly to the watch (or to Computer and transfer to the watch) Microwear_H5_AOSP ROM AND the GAPPS of your choice (Open Gapps arm64 nano was my choice)
6. Use Flashify to install zip(s) making sure you click TWRP as recovery option and also tick the wipe cache, data etc (add the Gapps as well if you want Google)
Click Reboot on flashify.
Hopefully the watch boots to recovery and installs the ROM and gapps!
First boot sticks on boot animation, so if not starting after 3 or 4 minutes power off the watch and reboot, after another 5 to 10 minutes you should see 'android is starting'
Nav Bar is by default on permanently, to make this and notification bar 'hide' (fully Immersive) I used this method.
1. install on pc ADB (Guide below)
2. Enable developer options and USB debugging on watch.
3. connect watch (switched on)
4. Open ADB on pc.
5. Type: adb devices (click enter)
(should see you device is connected)
6. Then type: adb shell - (click enter)
7. Then type this line:
settings put global policy_control immersive.full=*
Now the navigation bar will pop up when you pull down or up slightly on the screen and will auto hide after a couple of seconds.
As for sensors I don't think any are working.
I have included 3 launchers on this ROM, so make your choice!
Please, please, please DO NOT ATTEMPT THIS if you don't know how to revert back to stock rom. I bear no responsibility for broken toys!
Guys, who already have a scatter file for this watch, i really want to make a backup of current ROM before checking for any new updates (which is quite good version from January and there's nowhere on Internet any firmware files for this watch, so saving and sharing ROM is important). If i manage to download ROM i will post it on Google drive.
I wanted to force watch go into it's own recovery but my ADB installation don't see this watch connected - there's a primitive subsystem on watch beside Android OS, it can be seen when you turn Android OS "power off" and connect USB for charging - it will show the battery, i'm puzzled how to enter into any settings of that subsystem.
The stock firmware is on the Microwear Website.
http://m.microweartech.com/en/MicrowearFirmware.html
stevea76 said:
The stock firmware is on the Microwear Website.
http://m.microweartech.com/en/MicrowearFirmware.html
Click to expand...
Click to collapse
Yeah, i noticed only now, strangely but i remember that a month ago there was nothing about H5 model on their site when i searched…maybe because they just released it.
Also the firmware have the same scatter file - the first one which i found myself for some cheap smartphone on 6737 chip, as i remember i found it on reddit.
As i seen no updates of firmware for now.
crustier said:
Yeah, i noticed only now, strangely but i remember that a month ago there was nothing about H5 model on their site when i searched…maybe because they just released it.
Also the firmware have the same scatter file - the first one which i found myself for some cheap smartphone on 6737 chip, as i remember i found it on reddit.
As i seen no updates of firmware for now.
Click to expand...
Click to collapse
No updates as yet. I have ported an AOSP version, pretty much stock Android to the H5, it is basic, but I like the 'stock experience' on a square watch. Not got the sensors set up, but not really bothered about how many steps I have done on any given day or my heart rate for that matter.
Also if you want fancy clockskins then Eric's launcher works just fine on it.
stevea76 said:
No updates as yet. I have ported an AOSP version, pretty much stock Android to the H5, it is basic, but I like the 'stock experience' on a square watch. Not got the sensors set up, but not really bothered about how many steps I have done on any given day or my heart rate for that matter.
Also if you want fancy clockskins then Eric's launcher works just fine on it.
Click to expand...
Click to collapse
As i understand correctly - here they simulated or just copied clock skins from Apple watch?
Where to find Eric launcher?
For everyone else i will write again link to the firmware from Microwear site here – https://drive.google.com/drive/folders/1WaktAl-cjCTE1l0jffA7BnevzESdlCwc?usp=sharing
because chinese support is very short in time and can vanish with website very easily (for example to find an older firmwares to my Onyx Boox ereader i used "webarchive" service, thanks gods we have it - only from this saved archived copies of pages i found the sharing links to the older firmwares, still i cannot find the first version of RemixOS release for KitKat-if anyone have the alpha - please message me)
Eric's launcher is here:
https://play.google.com/store/apps/details?id=com.ricktop.ClockSkinCoco
All about the clockskins mainly for round Full Android watches here:
https://plus.google.com/communities/109827242607524552712
For square Full Android Watches here:
https://plus.google.com/communities/118413074291213420811
A useful forum for Full Android watches (round) with guides how to install custom watch faces:
http://roundandroidwatches.proboards.com