I have an incompatible ROM(I think) It puts a red box around
Around screen, gives low memory warning,and
stops apps at random.
Related
I flashed to the new HTC WM6 Europe Pre-release ROM today... all went very well until I tried to use the camera.
I got "Unable to start camera. Not enough storage is available to complete this operation."
I have plenty of space in storage. The camera just refuses to work.
Searching the forums, I cannot find anyone who has gotten this error message (the first part, but not the last).
Is this a bug in the new ROM?
Anyone have an idea as to what this could be?
This is in the manual that came with your phone. Perform a soft reset and you should be ready to go with the camera.
You'll also find an icon on the phone display. It will either look like a memory chip or a memory card. Once you get into the application, ensure that you are setting it to use the memory card as storage.
Thanks... but I have already done that.
As I stated previously, this is not likely a storage issue. I just flashed to this ROM. I have almost a gig on the microsd, 30 mb + in free storage, and almost 30 mb program memory available.
One interesting side note... Cool Camera works fine.
I am thinking that there is an issue in this new ROM.
same problem here, i think i'm going to try with some other rom versions, cause this one is like "factory default", but runs very quick.
I've received this message a few times. I have VJLumosIII installed on my hermes (this app uses some part of the camera functionality to make the screen brighter) and I used to use it all the time. If I forgot to turn it off when I went to use the camera, sometimes I would get this error message.
The weird thing is that it was only sometimes; perhaps 1 out of 3 times. The other times the camera would just work.
I quit using VJLumosIII, though, because it drained the battery too quickly, and haven't seen that error message once since.
Probably unrelated, but thought I'd throw it out there.
had the same problem do a hard reset fixed it for me
When intensive using my trinity it stops running all applications and seems to
hang. After resettting it , it displays a shifted image of the startup screen (or other). I have to cool down it (waiting for a long time with battery removed or put it in the fridge) and than it starts working normally. Any idea what's the source of my problems. It started to show that behaviour after installation of a new display.
My G1 (one of the originals, October 2008), running Cyanogen's latest, has developed a nasty little habit.
When I close the keyboard, the G1 dies. And it dies suddenly - no message, no flash of light, just ... black screen and no power. This doesn't happen 100% of the time - probably around 50% of the time. It doesn't seem to make a difference if I close it gently or close it hard. I can't find a pattern there.
\
So far, it has always booted right up when I power it back on, so as long as I don't want to use the keyboard, the phone is just fine.
Has anyone else had this problem? Any solutions? Or is the hardware dying out after a year's heavy use?
50% failure rate is repeatable in a store. Put it on stock firmware, if it still happens, visit T-Mo and they'll likely replace it assuming you got it within a reasonable time frame.
Recovery
Nandroid
Wipe
Reboot.
Check and see.
Hello guys,
I did something stupid.
Couple of days ago I decided that I am sick with this constant freezes of the GSM module on my defy. The core problem was that sometimes when the GSM radio is making rach-reselect of the current cell, and I am making/receiving a call in this exact moment, the Phone process is freezing. If I kill it and then kill the rild, the signal bar is empty, and my phone is declared as switched off to everyone who gives me a call. I am also unable to make outgoing calls.
Anyway long story short. I was running Froyo kernel with CM7 ontop on Defy (Red Lense). The hardware is MBM525.
Decided to give a chance to CM11 by quarx2k. Made a full dd image of all my eMMC partitions and followed the guide on quarx2k website. Flashed the bootstrap and the tried to resize, but nothing. I was just locked with frozen Google/CM7 logo.
Got into stock recovery, wiped data/cache partitions. Again I was locked with the logo.
No adb, no TWRP, no nothing. So I did flashed the original SBF with RSDLite, that my phone was comming with. Nothing, just black screen and white led. Looked here and there and found a ROM that will definately power up the device:
Code:
DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
True. The Defy powered, and the red Moto logo showed up (flashing this SBF was not the smartest thing I've ever done for my phone, this SBF was for MBM526).
The Android GB started and I was happy. Red a bit further on the CM11 thread and it turned out that I was with incorrect kernel, and that is why I got issues flashing the bootstrap in the first place. Now I got the correct one, so I rooted the phone with this SBF:
Code:
DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf
Installed SndRecovery and Custom recovery, got adb interface before android and flushed the bootstrap image to mmcblk (where /system is located). Installed the resize.zip. Rebooted, got into nice looking interface, flushed cm11 from a zip file to the newly repartiioned eMMC... etc.
Finished with CM11 Kitkat on my Defy. Wonderfull!!! Realy amazing.
However I've some issues with this version:
1) my battery is lasting less than 10hours, if I use my phone as usual (on froyo with cm7 the mileage was between 2 and 3 days, depending how many calls I made). If I have 2-3 calls for average of 15minutes (45min total GSM calls, no 3G etc), the battery life is less than 6 hours.
Tried to disable every fancy animation, downclock the CPU to 300MHz.. etc. No luck. I got around:
* 20 hours with no calls at all
* 8 hours with 5 calls, 3 minutes each.
and the Phone UI is not working correctly (the bug with the keypad not showing up).
I checked the reasons for this and with ssh did found that systemui is consuming a lot of CPU cycles.
Check with the battery applet, and com.android.systemui is taking around 40% of my battery time, Screen is 20%, AndroidOS 23%, Cell Standby 10%.
On CM7 it was something like Cell Standby 20%, Screen 40%.
Perhaps the problem is related with the fact that the battery is not charging to more than 4160V
2) The video playback using hardware decoder is not working correctly in my opinion. When I run a movie with MX player with h/w decoder the /system/bin/mediaserver is taking around 60%-80% of the CPU (same config - MX player with hw decoder, took around 5%-10% on CM7). If I go to S/W decoder, the CPU usage is the same but in favor of MX player process.
3) When I receive calls and the screen is in Landscape mode, I do not have the Phone UI where I can pick up the call. It simply does not show. There's two solutions:
* Wait 'till the end of the ringing, the person calling me hangup - I've missed call.
* Assign custom hardware key for pickin'up of incomming calls.
The second one is working, but I am unable to view who is calling me. Sometimes this is critical, since I am on a meetings and I should know who is calling me (I can ignore my coleagues, but not my boss).
I do use landscape alot. This is the only normal way for me to write on this small screen.
4) When I am starting outgoing call, It takes 2-4 seconds before the Phone UI shows up on screen. Tried various solutions. No luck.
5) Heavy RAM usage. With CM7 I got something like 200-250MB free ram, I was able to load more than 60tabs in Opera, and having FBreader loaded in Background. Now I've less than 94MB Free, and on Opera tab number 20, the app simply crashes. I know that this is not something that could be corrected. Android is a heavy OS, quite normal. Java is very heavy in terms of resources.
6) When I press and hold the Home button in order to display the recently opened applications, it is not showing right away. The lag is between 5 to 6 seconds. This means holding the home button for 3 seconds, releasing, waiting for another 6 seconds before the list shows up.
Apart from these, the UI is very responsive, and fast. I would say it is much faster than CM10 and CM9. The system is behaving wonderfull, realy nice. In some circumstances even better then CM7.
Right now on my questions:
What are the chances to go back to CM7 with GB kernel or Froyo kernel?
I know that I've flashed non-fixed SBF, which is BL7 (my bootloader version is 9.10), but I red that there's a CM7 runing with GB kernel. Where can I find this?
Is it possible to run CM7 on quarx2k kernel?
Is it possible to modify the bootstrap process so that it can run various kernel versions?
Perhaps too much talk for a single post
Hello guys,
i created this first thread on this forum because my Moto G4 Plus doesn't work like it should.
I have display burnings (and i think it's getting worse).
I don't have a rooted device and i can't use a trick which requires root because i've banking apps which requires an unrooted phone.
Additionally the phone is getting slower and slower. When i click something sometimes i have to wait 2-3 seconds until it shows the expected result.
Chrome is slow. Google photos is slow. I think every app is slow except of one or two.
I can't remember that it was like this at the beginning.
Does anyone can help me?
Thanks,
Daniel
If you're getting display burn in, you could try the S-filter app as mentioned in this thread: https://forum.xda-developers.com/moto-g6/how-to/guide-how-to-fix-screen-burn-image-t3820594 credit to the MotoG sub Reddit page https://www.reddit.com/r/MotoG/comments/91hjne/how_to_fix_image_persistence_on_all_motorola/
I'm currently testing out a similar app - iBlue from the Play Store and it seems to be limiting the display burn in (I have a LG LCD panel on my G4 Plus). I'm not rooted (and in fact have re-locked my device's bootloader).
As for the slowdowns, is this persisting across networks (i.e. do you see the same behaviour on Wi-Fi and on 3G/4G LTE)? Have you tried to wipe cache or consider wiping data and starting over with a clean device? How much free space is left on your device's internal storage?
I'm using Twilight at the evening for a blue filter. Is it a similar app and should i only use one app?
My free space is low. I think the smartphone is slower if the battery is empty. I didn't recognize any difference between wifi and 4g/3g.
I will try a cache clear.
danieldaeschle said:
I'm using Twilight at the evening for a blue filter. Is it a similar app and should i only use one app?
My free space is low. I think the smartphone is slower if the battery is empty. I didn't recognize any difference between wifi and 4g/3g.
I will try a cache clear.
Click to expand...
Click to collapse
If Twilight works for you, you may as well stay with it. I did notice slight lag when the filter was on, though the trade-off is worth it for less burn-in and easier on the eyes.
Hmm, you may wish to clear some space on your internal storage - if I recall, my device slowed down when I had less than 1-2 GB of free space internally. Also, if your battery is nearly empty, your device will slow down because of Battery Saver (if you have it on), since battery saving clocks down your CPU/disables the high powered cores so you've only got 4 low powered cores until you charge. It may also be that a low battery can't provide enough power to your CPU for full operation.
Ok, a cache clear helped a little bit. I will try to reset my phone and test it if it helps.
I also noticed the slowness when the battery is low... then it is very slow...
Something on this device wrong... Motorola misconfigured anything. This shouldn't happen.
Your device should slow down when your battery is low as I wrote above, especially if you have Battery Saver active on your device. Does your navigation bar turn orange at below 15 % battery?
Only at 5%
danieldaeschle said:
Only at 5%
Click to expand...
Click to collapse
Thus, at 5% your device CPU clocks down and shuts off the 1.5 GHz cores, leaving you on the 4 low power 1.2 GHz cores at a reduced clock speed. Under those conditions, your device will slow down until you plug your device in https://www.howtogeek.com/242472/how-to-use-and-configure-androids-battery-saver-mode/
Instead of doing a factory reset, I'd uninstall some unnecessary apps if possible, see if you can free up some more space - it doesn't have to be a full wipe (which will erase all your data).
I always uninstall apps which i don't use and i clean all cache data and junk data with the Android Go Files app.
Maybe i have to remove old pictures from my phone...
I cleared my storage now by deleting apps. I have 3gb free space now.