Does anyone know what this service is? It is running non-stop on my phone when I have it connected to Monitor?
It will attempt six times to publish. Then it will fail and restart the loop. I have had serious battery issues lately and I've tried everything. Maybe it has something to do with this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have the same problem, running 7.1.1 NPF10C
When use catlog or adb logcat these lines appear not stop, even when I boot in safe mode.
What can be the reason for this?
I create two bug reports for this issue:
https://code.google.com/p/android/issues/detail?id=226122
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!topic/nexus/dZLorZCRAEc
If you have this problem too, please star them.
Thanks!!
Yes getting that one too constantly. Forwarder for AT commands? (SMS, MMS, ...)
Thanks for creating these problem reports. Stared.
I try to delete all my SMS/MMS and reboot, unlucky. After that, I update Google Messenger to 2.0.068 version and reboot the 6P, but it has not helped, failure still occurs.
Are we only 3 users affected by this bug? Weird..
---------- Post added at 22:54 ---------- Previous post was at 22:51 ----------
El Daddy said:
Does anyone know what this service is? It is running non-stop on my phone when I have it connected to Monitor?
Click to expand...
Click to collapse
What do you mean connected to Monitor? Miracast?
I'm getting this constantly.
rchtk said:
Are we only 3 users affected by this bug? Weird..
---------- Post added at 22:54 ---------- Previous post was at 22:51 ----------
What do you mean connected to Monitor? Miracast?
I'm getting this constantly.
Click to expand...
Click to collapse
Android Device Monitor (Formally DDMS) it's a program in the SDK.
Pixels are not affected by this issue, according to this message:
https://productforums.google.com/d/msg/nexus/dZLorZCRAEc/JWRKqtFcAwAJ
I hope that the development team can fix it as soon as possible for our 6P.
Status: Assigned
Labels: Defect-32422957
The issue still occurs in the Developer Preview 2 NPF26F in my Nexus 6P. :crying:
Build stable 7.1.1 NMF26F and still occurs :crying:
In the bugtracker https://code.google.com/p/android/issues/detail?id=226122, the status is Needsinfo
Hi,
From the bugreport , we have observed that atfwd.apk is the atcmdfwd service, without that atfwd_daemon can't init, atfwd.apk isn't included in the build.
So please provide the bugreport taken on NPF26F for further action
Click to expand...
Click to collapse
wweasel said:
Build stable 7.1.1 NMF26F and still occurs :crying:
In the bugtracker https://code.google.com/p/android/issues/detail?id=226122, the status is Needsinfo
Click to expand...
Click to collapse
Even if the bug probably has no effect, that's unacceptable bug handling. The Google answer doesn't make any sense. We guessed that it's trying to start a service that doesn't exists lol. Just check why the framework tries to start it?
Either they take into account bug reports or stop posting them. If this Billion $$ company cannot start a logcat on a stock image then they should just close the bug report or even the complete website...
One more reason to use a real community driven custom ROM.
Related
I am assuming once you root the phone and push a custom ROM onto the phone, this will fix HTC's introduced bugs?
Bluetooth
SMS battery drain
Reverting apps versions
Stuff like this.
No, because the custom ROM is just the Sprint ROM with a few additions and modifications.
Ouch.
ok, anyone working on compiling a 2.0 kernal?
Treefallingquietly said:
Ouch.
ok, anyone working on compiling a 2.0 kernal?
Click to expand...
Click to collapse
HTC
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Although the bugs are not fixed, rooting allow one to use various workarounds that would not be possible without, and in fact for EACH of the issues you have listed:
Bluetooth: http://community.sprint.com/baw/thread/23854?tstart=0
While I cannot personally vouge for this, I have seen many posts on Sprint and here that detail the workaround described in the post as effective.
SMS Battery Drain: I think this may have actually been the first big bug discovered, and also fixed without root! Unfortunately, the default messaging app is defective, so in the meantime it is recommended to use either chompSMS or Handcent SMS from the Market until an update is released.
See this post: http://community.sprint.com/baw/thread/23043
Finally...
Reverting Apps: This is addressed on both forums, but a workaround only exists with root, and is similar in fashion to the bluetooth fix but for a different directory.
http://forum.xda-developers.com/showthread.php?t=582176
http://forum.xda-developers.com/showthread.php?t=581806
Hope this helps! I intend on posting a very detailed guide on every step of rooting, backing up, and working around most of the detailed problems in the very near future, stay tuned!
What I'd like is a kernel that will have this working as intended. But really, I am not afraid of the work arounds and the hands on work required, but if my wife had this phone with these problems, she would have chucked it out the window within days.
One more...
You left out the original bug (mentioned by briankwest, one of the first rooters), the TCP timestamp issue:
echo 0 > /proc/sys/net/ipv4/tcp_timestamps
This could also be added to the MoDaCo init.rc so it is set at each boot (otherwise it will revert back to "1").
I use Perseus kernel for only one reason, the LED controls, but every time I open Synapse it says boot settings cancelled! The funny part is I don't even reboot the device, and that laughable error pops up, and the settings revert back to default and don't stick! I'm sure I'm not the only person facing this issue, so is there any solution to this?
God and I disliked S Tweaks! I should be ashamed
I'm on stock MK9 btw.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Really no one?
Issue still persists! How does people use this kernel actually?
I got this problem too.
No idea how to fix it, flashed so many different kernels.
In my case, after updated synapse doesn't say no more.
Sent from my SHV-E300S using Tapatalk
devilsdouble said:
I use Perseus kernel for only one reason, the LED controls, but every time I open Synapse it says boot settings cancelled! The funny part is I don't even reboot the device, and that laughable error pops up, and the settings revert back to default and don't stick! I'm sure I'm not the only person facing this issue, so is there any solution to this?
God and I disliked S Tweaks! I should be ashamed
I'm on stock MK9 btw.
Click to expand...
Click to collapse
What's your SELinux Status?
@7u5h4r
This is an old thread from 2014 :/
Sent from my GT-I9500
krasCGQ said:
@7u5h4r
This is an old thread from 2014 :/
Sent from my GT-I9500
Click to expand...
Click to collapse
So old...I'm seeing my embarassing "no experience + no search" post. :crying:
SOLUTION: The error is there when your phone is rejecting the new settings. If you're on the latest Synapse, you can disable it in the Settings of the app.
nicholaschum said:
So old...I'm seeing my embarassing "no experience + no search" post. :crying:
SOLUTION: The error is there when your phone is rejecting the new settings. If you're on the latest Synapse, you can disable it in the Settings of the app.
Click to expand...
Click to collapse
No, that doesn't work as well. You need to change your SELinux status to permissive.
7u5h4r said:
No, that doesn't work as well. You need to change your SELinux status to permissive.
Click to expand...
Click to collapse
That depends. Because I keep my kernel enforcing Selinux at all times and it applies settings fine.
Sent from my Nexus 6P using Tapatalk
So I'm assuming this isn't a serious issue since no one is bothering to respond?
jman1234 said:
So I'm assuming this isn't a serious issue since no one is bothering to respond?
Click to expand...
Click to collapse
Not at all. ?
Hey guys,
we all use and work on different ROMs, be it OmniROM, CyanogenMod or AOSPA. However we all use very similar (if not the same) device trees and for that reason, I have decided to create this thread. Anyone can post test builds, logs, experiences, commits or whatever here without having to clutter other threads or open new ones.
My kernel should be good to go (it is pretty much up to date with the latest CAF upstream of the A-family, which means none of the kernel commits on cm gerrit (android_kernel_sony_apq8064) are required.) I'll be pushing everything I commit here: android_kernel_sony_apq8064.
Looking forward to a successful/effective collaboration guys.
Sounds good to me
Gave SlimLP a go - it boots. Although I didn't test it for long, I did notice that RIL is broken. Everything else should be working. I've used the kernel mentioned in the OP to get it compiled. I'll probably continue working on this on the next weekend.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Olivier said:
Gave SlimLP a go - it boots. Although I didn't test it for long, I did notice that RIL is broken. Everything else should be working. I've used the kernel mentioned in the OP to get it compiled. I'll probably continue working on this on the next weekend.
Click to expand...
Click to collapse
Yeah RIL is broken due to old sepolicies, I haven't had a chance to update them for Lollipop yet. Should be pretty easy though, using either pabx's policies or mako's for reference.
SuperHanss said:
I haven't had a chance to update them for Lollipop yet.
Click to expand...
Click to collapse
Yea me neither, I just went for permissive SELinux and disabled our policies (in fusion3-common) as they were breaking the build. We'll see...
I have updated the kernel to LA.AF.1.1-01310-8064.0. More CAF upstream coming soon...
Bump (and this goes to everyone using any 5.1 ROM) - just out of curiosity; what kind of random reboots do you guys experience? Hard reboots? Soft reboots? Or something else?
Describe the issues as precise as possible and upload logcat, dmesg and last_kmsg (and mention what ROM build you use)
I use pabx lollipop 5.1 aosp as daily driver.
Absolutely great working rom, no issues, no reboots no freezes. I feel like i have a nexus
Guys the reboot issue has been solved for me after update and it only happened when phone was in charge any idea why I have a lot apps crashing specially on Google chrome
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yesterday I updated my Note 4 from 4.4.4 to 5.0.1. I did not reset the phone, did not wipe cache in recovery after the update.
Now, on LP, after every reboot I get the pop-up message as shown in the screenshot.
I did'n have this on 4.4.4 and haven't installed new apps.
Does someone have a clue which app is causing this?
henklbr said:
Yesterday I updated my Note 4 from 4.4.4 to 5.0.1. I did not reset the phone, did not wipe cache in recovery after the update.
Now, on LP, after every reboot I get the pop-up message as shown in the screenshot.
I did'n have this on 4.4.4 and haven't installed new apps.
Does someone have a clue which app is causing this?
Click to expand...
Click to collapse
can you try this
I think this is related to the RCS service. You can disable it from the settings menu for text messaging -> Open the inbuilt messaging app (the usual place you receive text messages) -> Find the settings menu -> scroll down and disable the RCS Service.
Click to expand...
Click to collapse
also check out Vodafone Message+ it might be coming from that
Have the same issue here at every reboot @henklbr and I'm thinking it has somehow to do with Vodafone in the Netherlands (we both have the same provider) Btw I did clear my cache before and after installing the update. Oh and I also got 2 german apps showing up which I did not install for sure myself pizza.de and some German Hotel reservation app. Im using standard messaging and I have no hangouts installed
---------- Post added at 10:58 AM ---------- Previous post was at 10:56 AM ----------
raveenf said:
can you try this
also check out Vodafone Message+ it might be coming from that
Click to expand...
Click to collapse
Thank you, I tried both but the message still pops up , don't have Message+ installed
I think Samsung is introducing a service like iMessage. I'm actually excited about it but I don't get the popup. ?
Can you check in Settings, search for "Share with contacts" and see if you have such entry?
iridaki said:
I think Samsung is introducing a service like iMessage. I'm actually excited about it but I don't get the popup. ?
Can you check in Settings, search for "Share with contacts" and see if you have such entry?
Click to expand...
Click to collapse
Have no such entry in settings ...
And finally we have stable Oreo, after removing the previous one for several failures
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
xMiguelin said:
And finally we have stable Oreo, after removing the previous one for several failures
Click to expand...
Click to collapse
I can't download it from mi.com. Where can I get it?
http://en.miui.com/a-234.html
There's latest global dev which is supposed to be Oreo version, but I guess they took it down from main download site for a reason
I also received the notification, but I will not update it. There are many bug reports in this version.
Is there anything for those who dont want to unlock the bootloader?
Who updated it can someone share ???
pi4a7a said:
Who updated it can someone share ???
Click to expand...
Click to collapse
https://cloud.mail.ru/public/Kz9i/eK8FDq4M6
xsbxhome said:
https://cloud.mail.ru/public/Kz9i/eK8FDq4M6
Click to expand...
Click to collapse
I got the update from the app. I'm asking for suggestion should update or not?
This update according to the forum of MIUI, brings too many bug, so they recommend noo update ..
regards,
JC
I would not recommend the update.
There are many current complaints about it, some of them pretty serious - soft Brick - and they are consistent.
Wait for Xiaomi to address this.
This is not the same "beta stable" that was released the 12 of Feb, this is just a bit more polished... Anyway for those who want to have the bootloader locked and an xiaomi rom, stick to developer version, they are more stable than the stable version...
Here's the full changelog.
I still haven't installed though....
NFC bugs
Please upvote
Code:
en.miui.com/thread-1902264-1-1.html
on MIUI forum this if you encountered problems with Google Pay after updating to 9.2.3.0
Alright....I lasted 24hrs.
I updated.
Annnnnd....can I just say that it is noticeably faster opening apps?
Also the screen sensitivity had been increased.
So, I'll stick with it and let you know if I have problems.
xsbxhome said:
https://cloud.mail.ru/public/Kz9i/eK8FDq4M6
Click to expand...
Click to collapse
Just updated and running smooth for now.
No issues found, connectivity working as normal, phone is fast...
Regards,
Last night when I checked there was only China Stable and China Developer roms on miui site, now it has Globals too. Looks like thats a true stable but with all that bugs reported...
After update, I can't install TWRP properly (permanently) and TWRP has no access to SD.
maciupeq said:
After update, I can't install TWRP properly (permanently) and TWRP has no access to SD.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=75326288&postcount=90
here we go =))
Hi, I have several problems with this new update. NFC pay doesn't work anymore, no sounds for email, emails notifications are shown twice, notification from running background apps can not hide anymore (VLC, Messenger,etc). All other things are ok
Will the bootloader relock if I update from OTA ?