Database Users

[Q] HD2 using MIUI 1.7.8 and WiFi Tool for FritzBox

Hello,
I'm using the newest Version of [10 JUL 11]PATs JW MIUI Sense like v1.7.8 v2 Multilanguage[MAGLDR/cLK]
http://forum.xda-developers.com/show....php?t=1138088
I'm very pleased with this ROM but I have a crash problem
with the tool FRITZ!App Fon.
https://market.android.com/details?id=de.avm.android.fritzapp&feature=search_result
With former ROMs I have no problems to connect to my FritzBox and
use my HD2 as mobile.
With this ROM every time the App connects to the FritzBox it crashes,
but stays as inactive in background. The icon is shown already in headline.
I have to reboot to get the App stopped.
Is there any solution?
Thanks for your help.
Regards
NattyGuy

Had the reboot problem with the same rom with Sipdroid, but the reboot occurs when I will make a call. Installed FRITZ!App Fon from my backup and the same reboot problem after a call.
You have to open the blue SuperUser app and set Phone Rights to Allow for the FRITZ!App Fon app. This was working for me for SipDroid and the Fritz app.
In Su app you will see a reject logitem for your app, when it was rebooted.
The answer in rom thread
Edit: I can make a call, but settings and phone book will close the app, but no reboot. I use Sipdroid for calling and BoxToGo for the Fritz call list, change call redirections (Rufumleitungen) and disable WLAN. The call quality of the Fritz app was too bad for me and it didn't work via 3G.

....You have to open the blue SuperUser app and set Phone Rights to Allow for the FRITZ!App Fon app....
Click to expand...
Click to collapse
I have done this before I posted this, but nothing changes.
Seems MIUI and Fritz!App has a Problem using WiFi.

are you familiar with Logcat? If yes then try to take one and upload it. It can help a lot solving this kind of problems.

Thank You!
Adolf1994 said:
are you familiar with Logcat? If yes then try to take one and upload it. It can help a lot solving this kind of problems.
Click to expand...
Click to collapse
Thank you very much for your help and your post in PAT's thread!
I'm not familiar with Logcat, but I have found it in market and would try to use it this evening.

Update, but no fix!
Hello,
have made the update to 1.7.8 V3 and today
[17 JUL 11]PATs JW MIUI Sense like v1.7.15 Multilanguage[MAGLDR/cLK]
Sadly the issue is the same!

Error Log
Hello,
I have made a Logcat file and extracted the errors forced by Fritz!App.
Anybody an idea what this means!?
E/InputDispatcher( 274): Received spurious receive callback for unknown input channel. fd=247, events=0x8
E/InputDispatcher( 274): channel '4080f318 de.avm.android.fritzapp/de.avm.android.fritzapp.gui.FeaturesActivity (server)' ~ Channel is unrecoverably broken and will be disposed!

NattyGuy said:
Hello,
I have made a Logcat file and extracted the errors forced by Fritz!App.
Anybody an idea what this means!?
E/InputDispatcher( 274): Received spurious receive callback for unknown input channel. fd=247, events=0x8
E/InputDispatcher( 274): channel '4080f318 de.avm.android.fritzapp/de.avm.android.fritzapp.gui.FeaturesActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
Click to expand...
Click to collapse
i have the same problem...
FC with Ladymiui V31b. on EU HD2.....
FritzAPP Crashs.....

Gps not working

Hi,
if i turn my gps on, statusbar display nothing but gps should be on.
I found this error in my logcat:
E/LIBGPS ( 2254): [gps_lcsapi_init][line = 552] : Failed to call BrcmLbs_init(errno = 111)
Running evo x3 with hells 50#
Can any1 help?

Solved by reflashing rom.
But if anyone can explain this error
feel free to write.

random reboots

Hy to all,
I have every third day a random reboot. And i don´t know why. The last reboot was today at 14:20 clock. I tried to make a logcat. I hope i make it right. when it´s wrong please tell how to make it and wait 2 or 3 days.
i am on PA 3.69 (07/22) and Franco 165
Thanks to all

To be honest, my gut tells me there is a deep derp in the hybrid engine since pa 3.0 that is causing all these random reboots. However, strangely it affects only certain group of people.
Many have tried to raise the issue, but the same answer was used to dismiss all of us: "Currently there is no known random reboot issue, do a clean install and gtfo". (Ok, they never said gtfo, it automatically appended in my mind.)
Don't blame them though, because the reboot is so random in nature, it can't be fix easily unless you want them to dig deep into 1 year+ of works and fix this derp for minority of users.

My Nexus 4 will get stuck and eventually (after about a minute of a black screen) reboot if I leave it charging after its already charged. Don't know WTF that's about, but I just try to check it and unplug it if its charged.

I took a quick look at your logs, the reboot happens when you were using whatsapp, twice, is it correct?
08-13 14:19:46.719 I/ActivityManager(506): START u0 {cmp=com.whatsapp/.Conversations} from pid 8481
08-13 14:19:47.049 E/WindowManager(506): Window Session Crash
08-13 14:19:47.049 E/WindowManager(506): java.lang.RuntimeException: Could not open input channel pair. status=-24
08-13 14:19:47.049 E/WindowManager(506): at android.view.InputChannel.nativeOpenInputChannelPair(Native Method)
08-13 14:19:47.049 E/WindowManager(506): at android.view.InputChannel.openInputChannelPair(InputChannel.java:91)
08-13 14:19:47.049 E/WindowManager(506): at com.android.server.wm.WindowManagerService.addWindow(WindowManagerService.java:2264)
08-13 14:19:47.049 E/WindowManager(506): at com.android.server.wm.Session.addToDisplay(Session.java:160)
08-13 14:19:47.049 E/WindowManager(506): at android.view.IWindowSession$Stub.onTransact(IWindowSession.java:111)
08-13 14:19:47.049 E/WindowManager(506): at com.android.server.wm.Session.onTransact(Session.java:123)
08-13 14:19:47.049 E/WindowManager(506): at android.os.Binder.execTransact(Binder.java:351)
08-13 14:19:47.049 E/WindowManager(506): at dalvik.system.NativeStart.run(Native Method)
Click to expand...
Click to collapse

MastaPole said:
Hy to all,
I have every third day a random reboot. And i don´t know why. The last reboot was today at 14:20 clock. I tried to make a logcat. I hope i make it right. when it´s wrong please tell how to make it and wait 2 or 3 days.
i am on PA 3.69 (07/22) and Franco 165
Thanks to all
Click to expand...
Click to collapse
Did you restore your hybrid settings throw the hybrid settings if you did that's your issue. Do a clean install and don't restore your hybrid settings.
Sent via BLACKED OUT LTE N4

ksilver89 said:
I took a quick look at your logs, the reboot happens when you were using whatsapp, twice, is it correct?
Click to expand...
Click to collapse
yes, that is right.
spaceman860 said:
Did you restore your hybrid settings throw the hybrid settings if you did that's your issue. Do a clean install and don't restore your hybrid settings.
Sent via BLACKED OUT LTE N4
Click to expand...
Click to collapse
I am on a clean install. Maybe my n4 is defect. Because sometimes my status bar freez and i can't scroll down
Sent from my Nexus 4 using xda app-developers app

[Q] Nexus 10 hangs every night - something in libEGL/OpenGL?

Hi!
I have a Nexus 10 and it's been working flawlessly since I bought it, running CyanogenMod 10.1 most of the time. After I upgraded to 4.4 it started to hang, become unresponsive when being left on with screen turned off for a couple hours. Wouldn't last a night without hanging, regardless if it was being charged or not. Every time after that I had to hard reboot (press power button for longer than 8-10 seconds). This would happen on stock 4.4, stock 4.3, CM 10.2, stock kernel, francoKernel. Even on fresh install with no apps installed.
When I left it connected to USB with ADB logging, I could see that the last thing in the log before it hangs was usually something related to libEGL, GL, GL Operation, glDrawArrays.
For example:
Code:
11-23 13:08:34.250 W/System.err( 1012): java.lang.RuntimeException: GL Operation 'glDrawArrays' caused error 505!
(I found somewhere that this is GL Out of Memory error)
Code:
11-23 13:08:38.955 W/ ( 1012): GLES-MALI OOM error: execution failed (gles_fbp_read_pixels at vendor/arm/mali6xx/gles/src/fb/mali_gles_fb_read_pixels.c:693)
Code:
12-15 21:06:40.813 D/libEGL (16985): glGetIntegerv(GL_FRAMEBUFFER_BINDING_OES, (GLint *) 0x426e3be0);
12-15 21:06:40.813 D/libEGL (16985): glBindFramebuffer(GL_FRAMEBUFFER_OES, 2);
12-15 21:06:40.813 D/libEGL (16985): glGetError();
This is the latest log on CM 10.2 with OpenGL tracing in logcat (just the last part):
http://pastebin.com/6rpmfYca
The full log:
http://www61.zippyshare.com/v/5060489/file.html
This is some previous log:
http://pastebin.com/J9dNBBZS
What is causing this? What app/service is it dying in (there is MovieMaker in the log before the issue happens, but WTH?)? How can I debug this further?

_anarion_ said:
Hi!
I have a Nexus 10 and it's been working flawlessly since I bought it, running CyanogenMod 10.1 most of the time. After I upgraded to 4.4 it started to hang, become unresponsive when being left on with screen turned off for a couple hours. Wouldn't last a night without hanging, regardless if it was being charged or not. Every time after that I had to hard reboot (press power button for longer than 8-10 seconds). This would happen on stock 4.4, stock 4.3, CM 10.2, stock kernel, francoKernel. Even on fresh install with no apps installed.
When I left it connected to USB with ADB logging, I could see that the last thing in the log before it hangs was usually something related to libEGL, GL, GL Operation, glDrawArrays.
For example:
Code:
11-23 13:08:34.250 W/System.err( 1012): java.lang.RuntimeException: GL Operation 'glDrawArrays' caused error 505!
(I found somewhere that this is GL Out of Memory error)
Code:
11-23 13:08:38.955 W/ ( 1012): GLES-MALI OOM error: execution failed (gles_fbp_read_pixels at vendor/arm/mali6xx/gles/src/fb/mali_gles_fb_read_pixels.c:693)
Code:
12-15 21:06:40.813 D/libEGL (16985): glGetIntegerv(GL_FRAMEBUFFER_BINDING_OES, (GLint *) 0x426e3be0);
12-15 21:06:40.813 D/libEGL (16985): glBindFramebuffer(GL_FRAMEBUFFER_OES, 2);
12-15 21:06:40.813 D/libEGL (16985): glGetError();
This is the latest log on CM 10.2 with OpenGL tracing in logcat (just the last part):
http://pastebin.com/6rpmfYca
The full log:
http://www61.zippyshare.com/v/5060489/file.html
This is some previous log:
http://pastebin.com/J9dNBBZS
What is causing this? What app/service is it dying in (there is MovieMaker in the log before the issue happens, but WTH?)? How can I debug this further?
Click to expand...
Click to collapse
I can't offer a solution, but I have the same problem. Mine started when I moved to KitKat. I thought the problem was occurring when on a charger and the charge level reached FULL. But I also have the OLD MovieMaker app loaded. I am going to uninstall it and see if that has any effect.
Have you had any luck tracking down the problem?

rlrbjr said:
I can't offer a solution, but I have the same problem. Mine started when I moved to KitKat. I thought the problem was occurring when on a charger and the charge level reached FULL. But I also have the OLD MovieMaker app loaded. I am going to uninstall it and see if that has any effect.
Have you had any luck tracking down the problem?
Click to expand...
Click to collapse
Hi!
I was able to find some old threads about this aptly named Sleep of Death issue, here for example.
Unfortunately no conclusion, most people seem to return their devices :/
Now I think this is indeed some massive memory leak, becasue I was able to see ADB logs with all processes stopping, and the screen blinking with lock screen once when this happened.
As for MovieMaker, this might be misleading - I froze it in TitaniumBackup but the issue still exists.
My plan now is to write a script that would run
Code:
adb shell dumpsys meminfo
every couple seconds/minutes and plot the memory usage until the issue strikes.
I will report here if I find anything.
Best regards,
anarion

I uninstalled Movie Editor (rather than freezing it) and my system is much better (so far). I have not had a single lockup. It still too early to know if this is a god long term solution but I will keep you informed.
Sent from my Nexus 10 using Tapatalk 4

[ASK] Oppo a37

my phone sometimes hang but its kinda weird bcs if happening when im wathing video the video is still running for about 1 min but back button, home button and all things are not working.
and im trying to downloading logcat and show error like this:
ABS y overstep the boundary !!!
Device driver report y =1900, but max is 1745
(i've found this so much! and idk what to do)
https://image.ibb.co/krQ6f7/Screenshot_2018_03_12_17_00_51_95.png
protecteyesinit, try to dlopen arm32 so:/system/lib/libprotecteyes.so
protecteyesinit, dlopen arm32 so, dlhandle null: open ***fail****,now dlerror info:: dlopen failed: "system/lib/libprotecteyes.so" is 32-bit instead of 64-bit
protecteyesinit, try to open 64so, now dlerror info : (null)
protecteyesinit, dlopen arm64 so:/system/lib64/libprotecteyes.so, open ***success****, now dlerror info : (null)
Detect_Icon_Margin Bottom failed ! PixelIndex = 9264, templineSize = 9215
any solution without reflashing os? when its happen, i should restart 3-4 times for get everything back to normal.
pls help