Dear concerned,
I am using Lenovo k3 note since last two years. When internet is on in the phone, after some intervals a pop up window covering the whole screen occurs where "I am not a robot" is written with a check box. If I click on the check box it redirects to some software download page in play store. The problem does not occur when phone is offline or in power saver mode. After exiting the pop up, the page where I was in reloads Everytime. That's the main problem. Kindly help me if there is any technical support for this problem and let me know if anybody else is also facing such problems.
Related
Some days ago I had some problems with vibration, which stopped working for notifications. I installed an application called "Sound Manager" and was able to solve that issue. Now, I find my phone to be extremely slow on some things. For example, grabbing and dragging the notifications panel takes something like 5 or 7 seconds, and the "settings" button (the virtual button left of the Home button) also takes a lot to respond. OS Monitor tells me that "/system/bin/immvibed" is taking a whole 98% of CPU load. I don't know if this two things are related, but from the process's name, i suspect it has something to do with vibration settings (I cannot find any useful information online about such service). Annoyingly, I can't kill it, because it comes back to life immediately.
Is there something I can do? What does this process do?
Any help is appreciated
Solved
Apparently, all I needed do was a system restart!! Funny I failed to think about that before... Now the process is using no CPU resources. I still wonder what triggered it into that strange "all your CPU are belong to us" mode, though.
Anyway, problem solved.
Some crazy continuous loop most likely.
After I boot the diamond (GSM) the phone starts behaving in an erractic manner. The task drop down list in the upper right corner keeps getting triggered automatically without any input. Any applications which I open get automatically closed after a few minutes. It appears that the close button which appears in the right hand corner is being pressed automatically.
I thought that this was something to do with the ROM so I reflashed it with a new ROM. I was on Don Salari ROM earlier and now have Gen.Y R5.5 but still the issue reoccurs. Recently changed the battery to a high capacity compatible one, thought that it might be the issue but the behavior persists even when using the old battery. I've also recalibrated the screen but the issue persists.
I've uploaded a video of the odd behavior to youtube but can't the post the outside link in the forum yet. If required please PM me and I'll pass on the link.
Any one has experienced similar behavior? Any troubleshooting guidance and solutions are welcome.
anyone please???
Hi, I looked for other threads in which someone else faced the same problem, but I have not found any answer nor good solution.
The problem is that the screen of my S3 MINI turns on automatically.
I changed the ROM twice (2 different ones, CM 10 and 11), so I don't think the reason is a single "defective" app: I believe in another explanation, according to which the reason would be a broken pin inside the microUSB port of the smartphone.
That pin let turn the screen on like if it was put /unput in charge.
The Question: is there a ROM / KERNEL / APP that prevent the screen from making this error?
How much is hard to edit a rom/kernel in order to avoid that the screen lightness wolud depend from that pins?
And if the reason is a defective app, has someone ever discovered which one is?
I'm afraid it's a way to screw the consumer: this automatic and uncontrollable activity of the display destroys the battery life. It's like if the smartphone is broken: you should change it.
I cannot accept that a 440€ smartphone acts in this way. I'll never buy a Samsung product.
I won't talk about the home button broken (could someone give me an advice on which app that simulates the virtual buttons is better?).
Thank to you all!
Pietro C.
UPDATE 28/12/2014 h14:34 ITA
I did a screenshot and I also photographed with a camera the display while it was showing the CPU activity. I noticed something (an app? a opened file? a function?) that appears only when the display turns on automatically. Some green words. I'm going to upload photos.
UPDATE 16:30
Cannot upload photos. Here are the scripts that appears on my phone:
com.android.system
surfaceflinger
system_server
com.teslacoilsw.launcher
kworker/u4
com.android.phone
com.facebook.katana
com.facebook.orca
kworker/2
kworker/6
kworker/1
irq/72...
irq/474
mmcqd
ueventd
rild
mediaserver
admsrv
org.cyanogenmod.voiceplus
dhd_dpc
com.google.processo.location
org.whispersystems.whisperpush
com.textra
com.google.android.googlequicksearchbox.search
AND the last 5 listed down here are the green scripts that appears only when the phone turns on automatically.
migration/I
kworker/I:0
ksoftirqd/I
watchdog/I
kworker/I:I
UPDATE 03.01.2015
I fixed the issue at the moment. I installed CM 11-20140823 after wiping and formatting data.
I installed the lowest number of Google Apps (here I chose Nano Modular Package: http://forum.xda-developers.com/showthread.php?p=44417509#post44417509 ).
I'm quite sure it's a issue caused by a unidentified google app, because when the phone was "clean", the screen kept turned off ALWAYS, unless I pressed the accension button.
Now that I installed ONLY Google Play and Google Services, the screen is ok.
So I will download only the most useful Google Apps, hoping that won't find the one infected (if I'm right about the cause of the automatic flash of the screen).
I also discussed about this issue here , and I discovered that many people are searching for a solution.
Maybe someone could confirm or contradict my theory.
I've had my new Seat Leon for a week now and have been using Android Auto a little in this time. I really like it but it seems buggy. For example when using maps, the images will freeze, only updating every couple of minutes. When you are trying to follow an on screen map while travelling at 60mph, this can be very annoying. The other bug I seem to have is that my car seems picky when connecting to my phone (Nexus 5) sometimes. It will say 'not compatible' and will refuse to connect. The only way to solve these two issues is to restart my phone and sometimes to also toggle the USB debugging check box.
Is there anywhere to report bugs to Google? I'd like to help the community in ironing out these issues.
nimdy said:
Is there anywhere to report bugs to Google? I'd like to help the community in ironing out these issues.
Click to expand...
Click to collapse
Open the Android Auto app.
Tap the 3 dots at top right.
Select "Help & Feedback" and then select Feedback at the bottom.
I'm honestly not sure it will help too much though. There are no idle employees waiting for problem reports who spring into action at a new report.
But if Google sees 100 reports of Problem X, it might move X a bit higher in their priority list.
The freeze problem is actually new to Android Auto, and it started for me on July 31th. Google changed something server-side because even two clean installs didn't solve the issue, and it was working flawlessy until that day. No solutions found so far, had to switch to an iPhone to navigate. Read my report here:
http://forums.androidcentral.com/as...-5-android-auto-lags-when-using-gps-maps.html
themcfly said:
The freeze problem is actually new to Android Auto, and it started for me on July 31th. Google changed something server-side because even two clean installs didn't solve the issue, and it was working flawlessy until that day. No solutions found so far, had to switch to an iPhone to navigate. Read my report here:
http://forums.androidcentral.com/as...-5-android-auto-lags-when-using-gps-maps.html
Click to expand...
Click to collapse
That seems to be the same issue I'm getting. But strangely this isn't happening all the time. The pattern seems to be when I connect the phone to the car, set up the Google maps navigation, stop and disconnect the phone (for example getting lunch on my way into work), then connect again and continue the navigation. When connecting for the second time I get the issue whereby the refreshing doesn't seem to happen. As you say in your other forum post, this seems to update when you touch the screen.
Hopefully if this bug has only appeared in the last few days, hopefully someone will spot it and report back to get a fix. I've written a brief feedback note saying that I have found a bug and am interested to help them get it fixed!
I see a lot of people having problems with certain phones. I have Note Edge and never a problem. My wife has a s6 and used to have problems about 10 minutes into a drive (Black Screen, no control, most other probs mentioned here). Read somewhere if you load the "Android Auto App" on the phone first and then plug in. She has never had a problem Since. Something happens on App load that is not happening on "Auto Launch on detection" (My gut feeling is something to do with bluetooth). Just wanted to pass it along for those people having issues. I am sure google will fix at some point but give it a try and see if it solves your issues. It did ours.
nimdy said:
That seems to be the same issue I'm getting. But strangely this isn't happening all the time. The pattern seems to be when I connect the phone to the car, set up the Google maps navigation, stop and disconnect the phone (for example getting lunch on my way into work), then connect again and continue the navigation. When connecting for the second time I get the issue whereby the refreshing doesn't seem to happen. As you say in your other forum post, this seems to update when you touch the screen.
Hopefully if this bug has only appeared in the last few days, hopefully someone will spot it and report back to get a fix. I've written a brief feedback note saying that I have found a bug and am interested to help them get it fixed!
Click to expand...
Click to collapse
BPryde said:
My gut feeling is something to do with bluetooth.
Click to expand...
Click to collapse
Yes! If something fails with Bluetooth, then the AA connection disconnects. I hope Google fix this soon.
Hi,
Two days ago I received the new Pro Camera App firmware.
I imemdiately recognized that all of a sudden, my Phono App was closed automatically after a certain time. Phono shows the logo of the network operator in the status bar as well as on the lock screen. Additonal info is shown when opening the app.
This is very strange since this did not even happen once in the past. It seems that the phone closes running apps in the background without any intervention from the user.
I tried to track the issue down, but the closing process is randomly and also not related to a certain time.
It is also strange that even Phono is set to Autostart after a phone restart, it doesn't start. I have to manually start it again.
The only workaround is to place a Phono widget on the main screen in order to keep it running.
There have been similar reports on the Nokia Mobile Phone Forum.
Would be interesting to see if you have encountered similar things.
super_joe said:
Hi,
Two days ago I received the new Pro Camera App firmware.
I imemdiately recognized that all of a sudden, my Phono App was closed automatically after a certain time. Phono shows the logo of the network operator in the status bar as well as on the lock screen. Additonal info is shown when opening the app.
This is very strange since this did not even happen once in the past. It seems that the phone closes running apps in the background without any intervention from the user.
I tried to track the issue down, but the closing process is randomly and also not related to a certain time.
It is also strange that even Phono is set to Autostart after a phone restart, it doesn't start. I have to manually start it again.
The only workaround is to place a Phono widget on the main screen in order to keep it running.
There have been similar reports on the Nokia Mobile Phone Forum.
Would be interesting to see if you have encountered similar things.
Click to expand...
Click to collapse
i have the same issue and found a thread in the community of nokia:
https://community.phones.nokia.com/support/discussions/topics/7000027437
i tried this workaround and it seems to help