xeros2

Members
  • Content count

    231
  • Joined

  • Last visited

Community Reputation

26 Excellent

About xeros2

  • Rank
    Enthusiast

Previous Fields

  • Your Current Device(s)
    Coolpad F1 8297W

Recent Profile Visitors

872 profile views
  1. Right, I suggest to root phone & freeze stock SMS app with for example Titanium Backup and set your favorite SMS app as system app. I've fixed the same problem by replacing stock SMS/MMS app with Hangouts this way (stock mms.apk is still there, but frozen and Hangouts is set as system app). No problems with SMS since then.
  2. Wow! Thanks a lot. These values for 3D & UX are much higher than on optimized, still smoth, CoolUI 4.2.2! To compare, CoolUI 4.2.2 results on the same Antutu 6.0.1 (after freezing / uninstalling most Coolpad stuff, using light CM Launcher, greenified most other apps, tweaked CPU settings (but keeping full performance when screen is on), schedulers, buffers, etc... but using the same ROM since more than a year): 3D: 1825 UX: 5348 CPU: 12586 RAM: 5219 It's very tempting to finally change ROM for something newer & give that your RR re-make a try. So far I've keept CoolUI 4.2.2 for camera speed + quality (I make many photos and need fast & good enough camera) and 3D performance in Asphalt 8.
  3. Thanks a lot for your re-make & detailed description. How would you compare it to other ROMs? (especially CM, SGN4, AMOI,...) Is it ready to be a "keeper" for daily use? How's battery life? Any things that don't work properly or compatibility issues? Could you please make any screenshots with benchmarks for your ROMs, for example Antutu to compare performance of different components? (I'm not talking about the overall score but details) +1 for that, I can't understand around half of google-translated version.
  4. Thanks slime00, I wonder if it's ResurrectionRemix 5.6.4 (mentioned release in official RR changelog with today's date) or 5.6.3 (from Feb 13th). Edit: Oh, it's 5.5.9. Kernel is not "built from source" - it's KK kernel like everywhere (including device drivers), just the upper Android layers are built from source (adapted for KK kernel, like in CM 12.1 and others). Anyway, it seems to be interesting choice, especially that they claim it "bugless".
  5. Nice, thanks! Looking at the screenshots it looks similar to AOSP. What about xposed modules? Did you test any for compatibility? For comparision, on CoolUI around half of xposed modules are not fully compatibile. How would you compare camera quality & speed (& functionality) to other ROMs? (I'm curious about comparision with CoolUI with stock camera). And what do you mean "almost 100% functional"? Does it have any issues? Too bad that we're loosing dakok, jakethedogg,... and few other members (who bought new phone) that brought much to F1 community. At the other side - great choice! In F1 now I really miss gyroscope & magnetometer/compass that are essential for VR, but I'm still not going to replace my F1 in next 1-2 years yet.
  6. If this happened after flashing single ROM and you didn't have issues before then it might not be flash issue but rather incompatible ROM which might have changed partitioning. Still, it should be possible to fix it. I think the easiest way would be flashing complete stock firmware (including use of scatter file) first to fix the issue and later flash your chosen correct ROM.
  7. So try first with: 1. Installing ADB client on PC & ADB drivers (you can find many instructions for that), then: Next commands in recovery shell (inside connected ADB shell): to ensure that it's symlink to /dev/block/mmcblk0p9. You should get output like: (prompt can differ, depends on recovery which you'll use) Next try to recreate EXT4 filesystem on it with bad blocks check: If you'll get no errors then you can try to mount it: If still no problems then, unmount it, sync & reboot phone: You should have now working /cache partition. & next time reflashing ROMs you should try to avoid formating /cache (erase its content instead) as most likely next formating of this partition via recovery might use also bad blocks. It's just quick & dirty instruction written ad-hoc, based on my general UNIX & embedded devices experience, tried to be as simple as it could and I haven't checked if it works on any recoveries on F1. At least going carefully through these steps it shouldn't break anything as in yours case /cache is already corrupted and needs to be cleaned anyway, just ensure that symlink above is correct & don't make any typo. Other things that you may try if above wont help: 1. Make current filesystem check & repair: This should do automated check forcing all answers for "yes" for any fix proposals, with bad blocks check, forcing even if fs is marked as clean & higher verbosity of log output. 2. (as alternative) Erase all /cache partition area and try to format it again via recovery option:
  8. Can't tell for sure without seeing any detailed log, but I could guess that there could be some bad block in built-in flash in 'cache' partition area. I suggest to: - connect to phone via ADB when you're in recovery or use terminal (still in recovery if it's touch recovery, like TWRP), - use Linux low level tools to create fs and mark bad blocks (ensuring that it's normal EXT4 filesystem, not some modified one and that you have the tools in your recovery) - "badblocks" & "mkfs.ext4" ("mke2fs") - try to search for some docs on that. I have done such things few years ago with old Android 4.0.3 AllWinner A10 tablet - despite many bad blocks (which I have marked as bad and ommited to not use for data), including /system & /data areas, it's still working up to now. At that time this tablet got bricked because my daughter connected completely drained tablet to USB charger which didn't have enough power to keep tablet awake and it was constantly starting & resetting all the time for whole day (& maybe night, too), which resulted in built-in flash corruption.
  9. Sure, I use fast Kingston 64GB Class 10 U3 MicroSDXC (90MB/s Read / 85MB/s Write) without any issues since around beginning of this year. One thing is that I had to format it as FAT32 as kernel in F1 doesn't have exFAT support compiled in.
  10. Battery Drain suggestions

    Well, generally MT6592 is power hungry SoC, but... If you're interested mostly in YouTube then I would suggest to limit screen light and maybe use Tasker app (or sth similar) to disable 6 CPU cores & limit CPU+GPU frequency+voltage (to minimum required for fluent YouTube playback) when YouTube is started and return previous state when YouTube is stopped or other apps get started. In my case I have noticed quite big battery drains even when phone was in sleep state (but with 3G or WIFI enabled) so I've set it using Tasker to do such tricks for display off/on events and hibernate most apps in sleep state and it has improved battery drains in sleep mode quite much. I still have huge battery drains in high end gaming (around 3-3.5h SOT only in heavy games that take advantage of all 8 CPU & 4 GPU cores) so I should profile that better also, but at least phone waiting for IM messages, SMS, phone/video calls, e-mails... does not drain that much. Edit: I see also that you have much Cell standby and WLAN power usage - I could suggest to switch cellular connectivity to GSM (if you don't need 3G) - it should improve range & battery usage (it can be also profiled with Tasker to switch to 3G when you enable data connection) and increase WLAN scan intervals in build.prop.
  11. I think it's the same rumour like with L for F1. MMX gets ROMs from Coolpad so I doubt that it will get official L, too. Sadly speaking, I think that development for F1/MMX has stopped. But I wish I was wrong.
  12. Did anyone got such issue that bluetooth "just stopped working"? When I try to enable it it's getting disabled in few secs. What I've found it's getting enabled in configuration (1 value for "bluetooth_on" in /data/data/com.android.providers.settings/databases/settings.db "system" table) but in menu it's still disabled and doesn't search for devices and it's not reachable. Other things that I've found (compared to backup with BT working) is that MAC address in "secure" table has been reset to 00:00:00:00:00:00 but even after changing it back to proper one it's still not working with the same result. In dmesg I found suspicious text: <5>[ 571.378340] (0)[1:init]init: starting 'bt_mac' <6>[ 571.378787] (0)[1:init]init: PropSet [init.svc.bt_mac:running] Start>> <6>[ 571.378933] (0)[1:init]init: PropSet [init.svc.bt_mac:running] Done <7>[ 571.402719] (0)[9002:write_bt_mac][exec] /system/bin/write_bt_mac(3) <7>[ 571.448608] (1)[9002:write_bt_mac][9002:9002:write_bt_mac] exit <7>[ 571.448893] (1)[9002:write_bt_mac][9002:write_bt_mac] sig 17 to [9000:sh]but googling didn't show anything for such exit signal from this process. Setting "bluetooth_on" to "0" in "system" table and reboot makes logs outputs a bit better for first attempt to enable BT (at first sight they look like it should work), but it still gets disabled afterwards. I have checked /data/nvram files for BT and [email protected] and there it looks similar to backup and nothing useful in /proc & /sys to check from kernel side. I was thinking about some hardware problems as I've been using BT for connection to car engine computer few times for 7-8h/day of car driving and it seams it might have stopped working when I tried it once more or it could have been some unplanned phone reboot due to hang of launcher/app. Other than that, everything else works fine (just this BT isn't working). Just for info - I didn't try to clean data & ROM reflash - I've got used to repair broken things instead going easy way & start configuration/reinstallation from scratch (I have almost 300 apps & many of them are tightly integrated with system and specially configured that backup restore wouldn't be so easy in my case). Did anyone have such problem also and what was resolution for it?
  13. Well, I (& all of us here, I think), was really counting on this 5.1 update because I'm looking for its features & fixes (including better compromise between performance & power consumption), because as I still use 4.2, I don't have any objections for performance, but battery life is very weak (even after removing, killing, freezing, hibernating most of apps), especially on when using more heavy tasks just for a couple of minutes each day. I really miss other kernel features that are not available in released JB & KK kernels so far, like I/O accounting, USB 3.0 charging support, USB Host (even non-powered), ExFAT & other FS support, better CPU & IO schedulers and CPU frequency scaling fixes (like CPU goes to static ~1142MHz in sleep state, regardless of cpufreq kernel settings for any scheduler to set min/max/cur frequencies, but from power consumption it looks like ~750-850MHz frequencies with 6 cores disabled (using only 2 cores) seem to be most power effective for sleep states for MT6592). Other things are mentioned GPU drivers - other phones with MT6592 & KK have better GPU kernel drivers for our MALI 450 (for example Lenovo A8/A806,...), which are better in both performance & power consumption. There are even more things waiting for fixes on Coolpad side, but these are the first things that come to my mind for kernel side.
  14. Cases/covers

    You're right, I shouldn't try to glue this metal ring - this part is ugly now. But... anyway, it still looks better than previous ugly silicone case (especially after that it changed it's color).
  15. Cases/covers

    Sorry, but I can't take a picture of phone with cover. I don't have any other device with camera with me (besides laptop with very poor 0,3M camera) to make a photo. All I could do is just cover photo without a phone, using F1 after removing it from cover: http://postimg.org/gallery/lg65x98o/ That metal ring for camera is not from this cover - it's the one that I have glued for use with external lens (and I sill have glue around it, which I'll have to clean). Originally camera hole looked exactly like on photos from case offer.

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.