Hello
Did anybody got the app working? I just tried a version on the internet cause i wanna be sure it works if i buy it. It just fc's
I got fc to
҉ Envoyé depuis mon Samsung Galaxy 3 avec Kyorarom 5.2 ҉
Does this app need amrv7 maybe?
Awww. I tried the 1.1.1 update in which they said the fc prob would be gone but it still fc's
Humpie said:
Awww. I tried the 1.1.1 update in which they said the fc prob would be gone but it still fc's
Click to expand...
Click to collapse
Are you in 2.2 or 2.3?
I tested with Kyorarom (2.2)
Edit: i trid the 3 version and got fc
҉ Envoyé depuis mon Samsung Galaxy 3 avec Kyorarom 5.2 ҉
could anybody with 2.3 try this?? I run on kyrillos 2.2 btw
If you can get logcat while the app fc i can try to give some uggestions, but i'm not going to install it.
Humpie said:
could anybody with 2.3 try this?? I run on kyrillos 2.2 btw
Click to expand...
Click to collapse
i tryed...fc's on gb too..
edit: it's not found on market either...i guess it won't work at all
~~~~~~~~~~~~~~~~~~~~~~~~~
Sent from Galaxy
Kyrillos' ROM v10 GWK74 beta
powered by
CM7-kernel 1.3 H.V.
~~~~~~~~~~~~~~~~~~~~~~~~~
OK here's the link to my logcat: http://db.tt/iyoplTbx
I suggest you filter it to tsf. I tried to run it two times...
After a quick research i found out that this exception prevents the app to run:
Code:
java.lang.UnsupportedOperationException: glGenFramebuffersOES
03-06 08:30:54.688 E/AndroidRuntime( 5876): at com.google.android.gles_jni.GLImpl.glGenFramebuffersOES(Native Method)
03-06 08:30:54.688 E/AndroidRuntime( 5876): at com.tsf.shell.workspace3D.f.b.a(Unknown Source)
03-06 08:30:54.688 E/AndroidRuntime( 5876): at com.tsf.shell.workspace3D.b.n.<init>(Unknown Source)
03-06 08:30:54.688 E/AndroidRuntime( 5876): at com.tsf.shell.workspace3D.b.k.<init>(Unknown Source)
03-06 08:30:54.688 E/AndroidRuntime( 5876): at com.tsf.shell.workspace3D.h.a(Unknown Source)
03-06 08:30:54.688 E/AndroidRuntime( 5876): at com.tsf.shell.workspace3D.bh.a(Unknown Source)
03-06 08:30:54.688 E/AndroidRuntime( 5876): at com.censivn.C3DEngine.a.q.onSurfaceCreated(Unknown Source)
03-06 08:30:54.688 E/AndroidRuntime( 5876): at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1317)
03-06 08:30:54.688 E/AndroidRuntime( 5876): at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1116)
03-06 08:30:54.743 W/ActivityManager( 2834): Force finishing activity com.tsf.shell/.Home
I'm not an expert in opengl stuff but i made a little research with google and found that this error comes out with some devices (mainly samsung) that run opengl 1.1. It runs correctly with opengl 2.0.
Unfortunately our phone has bad graphic driver based on 1.1 version so i do not think you can use this louncher in little time.
In the future maybe tom3q will implement opengl 2.0 in his openfigm project but this will take a lot of time as the project is in development stage for v1.1.
I strongly suggest you not to ask him to base openfigm on gl2.0 as his already doing a very big job.
With a little hope you can try running TSF again in you phone when openfigm is complete... maybe it'll work.
We can contact the devs of Tsf to ask if they can fix this bug in future release
҉ Envoyé depuis mon Samsung Galaxy 3 avec Kyorarom 5.2 ҉
SerkSerk said:
We can contact the devs of Tsf to ask if they can fix this bug in future release
҉ Envoyé depuis mon Samsung Galaxy 3 avec Kyorarom 5.2 ҉
Click to expand...
Click to collapse
Yes you can, but i highly doubt he will be able to do so as this issue seems to be device-specific and not app-related.
whoaaa.....i tryed this thingy on my girlfriends ideos x5 u8800....it's awesome.....i like it....would be nice if it could run on our g3 though......
but even on ideos x5....with 512mb of ram and cpu at 1ghz it takes time to load at first start....but it's smooth and very good looking home replacement
~~~~~~~~~~~~~~~~~~~~~~~~~
Sent from Galaxy
Kyrillos' ROM v10 GWK74 beta
powered by
CM7-kernel 1.3 H.V.
~~~~~~~~~~~~~~~~~~~~~~~~~
Related
hey! i want to unbrick my X10 with the flashtool.
But i have some problems.
I always get this error.
please connect Xperia in flash mode.
Drücken Sie eine beliebige Taste . . .
C:\Users\abc\Downloads\handy\xda flash tool\X10Flash_Unbrick>java -jar X10flash
.jar
13.08.2010 17:20:00 X10flash main
INFO: start
java.io.IOException: Unable to open channel, GetLastError=0
at com.sonyericsson.cs.usbflashnative.impl.USBFlashNativeImpl.openChanne
l(Native Method)
at X10flash.main(X10flash.java:410)
Exception in thread "main" java.lang.NullPointerException
at java.lang.String.<init>(Unknown Source)
at X10flash.testPluged(X10flash.java:103)
at X10flash.run(X10flash.java:375)
at X10flash.main(X10flash.java:417)
Drücken Sie eine beliebige Taste . . .
what can i do?? pls help me!!
kind regards
Edit deviceID.txt so it contains your device id.
Hi, I'm writing from Argentina, I read the post to install ICs in my X10A, install X10_2.2.25_MIUIV4-MILAD407-FXP129.ftf and then not boot the phone anymore, it stays on the screen "sony ericsson"
superuser had installed and installed debug options
Can you help me please?, try to flash it but it did not work with older firmwares newer, other files ftf with Flashtool.
The problem begans after try to install this firmware: http://forum.xda-developers.com/showthread.php?t=1792045&page=6
While booting x10 flash mode FlashTool recognizes the phone, but when trying to flash it gives multiple errors
flashsystem.X10FlashException: ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
at flashsystem.X10flash.uploadImage(X10flash.java:225)
at flashsystem.X10flash.sendLoader(X10flash.java:233)
at flashsystem.X10flash.flashDevice(X10flash.java:344)
at gui.FlasherGUI$45.run(FlasherGUI.java:1092)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
java.io.IOException: Read error :31 : Uno de los dispositivos conectados al sistema no funciona.
at win32lib.JKernel32.readBytes(JKernel32.java:57)
at flashsystem.io.USBFlashWin32.windowsReadS1Reply(USBFlashWin32.java:51)
at flashsystem.io.USBFlash.readS1Reply(USBFlash.java:45)
at flashsystem.X10flash.openDevice(X10flash.java:432)
at flashsystem.X10flash.openDevice(X10flash.java:372)
at gui.FlasherGUI$45.run(FlasherGUI.java:1091)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
java.lang.NullPointerException
at flashsystem.X10flash.processHeader(X10flash.java:187)
at flashsystem.X10flash.uploadImage(X10flash.java:203)
at flashsystem.X10flash.sendLoader(X10flash.java:233)
at flashsystem.X10flash.flashDevice(X10flash.java:344)
at gui.FlasherGUI$45.run(FlasherGUI.java:1092)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
flashsystem.X10FlashException
at flashsystem.X10flash.uploadImage(X10flash.java:225)
at flashsystem.X10flash.sendLoader(X10flash.java:233)
at flashsystem.X10flash.flashDevice(X10flash.java:344)
at gui.FlasherGUI$45.run(FlasherGUI.java:1092)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
padevoto said:
Hi, I'm writing from Argentina, I read the post to install ICs in my X10A, install X10_2.2.25_MIUIV4-MILAD407-FXP129.ftf and then not boot the phone anymore, it stays on the screen "sony ericsson"
superuser had installed and installed debug options
Can you help me please?, try to flash it but it did not work with older firmwares newer, other files ftf with Flashtool.
The problem begans after try to install this firmware: http://forum.xda-developers.com/showthread.php?t=1792045&page=6
While booting x10 flash mode FlashTool recognizes the phone, but when trying to flash it gives multiple errors
flashsystem.X10FlashException: ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
at flashsystem.X10flash.uploadImage(X10flash.java:225)
at flashsystem.X10flash.sendLoader(X10flash.java:233)
at flashsystem.X10flash.flashDevice(X10flash.java:344)
at gui.FlasherGUI$45.run(FlasherGUI.java:1092)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
java.io.IOException: Read error :31 : Uno de los dispositivos conectados al sistema no funciona.
at win32lib.JKernel32.readBytes(JKernel32.java:57)
at flashsystem.io.USBFlashWin32.windowsReadS1Reply(USBFlashWin32.java:51)
at flashsystem.io.USBFlash.readS1Reply(USBFlash.java:45)
at flashsystem.X10flash.openDevice(X10flash.java:432)
at flashsystem.X10flash.openDevice(X10flash.java:372)
at gui.FlasherGUI$45.run(FlasherGUI.java:1091)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
java.lang.NullPointerException
at flashsystem.X10flash.processHeader(X10flash.java:187)
at flashsystem.X10flash.uploadImage(X10flash.java:203)
at flashsystem.X10flash.sendLoader(X10flash.java:233)
at flashsystem.X10flash.flashDevice(X10flash.java:344)
at gui.FlasherGUI$45.run(FlasherGUI.java:1092)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
flashsystem.X10FlashException
at flashsystem.X10flash.uploadImage(X10flash.java:225)
at flashsystem.X10flash.sendLoader(X10flash.java:233)
at flashsystem.X10flash.flashDevice(X10flash.java:344)
at gui.FlasherGUI$45.run(FlasherGUI.java:1092)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
Click to expand...
Click to collapse
Your problem is that your bootloader is still locked. To flash a custom kernel, you need to unlock your bootloader (instructions can be found in this thread http://forum.xda-developers.com/showthread.php?t=1254087), then flash the kernel and finally the ICS rom.
You should probably flash the stock 2.3.3 firmware from flashtool to get your phone working again properly first (looks like there's only 2.1 for the X10a in this thread http://forum.xda-developers.com/showthread.php?t=920746), then unlock bootloader, then flash custom kernel, and finally the custom rom.
You might want to be careful about what you flash, though, because I'm not sure if these methods do work for X10a. Someone else might be able to confirm this for you
Panzerfaust101 said:
Your problem is that your bootloader is still locked. To flash a custom kernel, you need to unlock your bootloader (instructions can be found in this thread http://forum.xda-developers.com/showthread.php?t=1254087), then flash the kernel and finally the ICS rom.
You should probably flash the stock 2.3.3 firmware from flashtool to get your phone working again properly first (looks like there's only 2.1 for the X10a in this thread http://forum.xda-developers.com/showthread.php?t=920746), then unlock bootloader, then flash custom kernel, and finally the custom rom.
You might want to be careful about what you flash, though, because I'm not sure if these methods do work for X10a. Someone else might be able to confirm this for you
Click to expand...
Click to collapse
everything works same for x10a or x10i
as for 2.3.3 stock roms you can find link in my signature. just grab the global generic one.
Resolved
THeLogiC said:
everything works same for x10a or x10i
as for 2.3.3 stock roms you can find link in my signature. just grab the global generic one.
Click to expand...
Click to collapse
very good news!, the original problem was to use a kernel bug and not have released the bootloader.
I had to work hard to discover that something as simple as flashing the phone went wrong for any problems with drivers, REMOVE EVERYTHING!, jellyfish, 1stool, flashtools, drivers, and companion seus!, REGCLEAN run,
reboot, install went back to FlashTool, i use Sony Ericsson X10i_2.1.A.435_GLOBAL GENERIC 1232-9897 firmware, reboot, root with Super OneClik, install superuser, busybox, make sure everything works well, reboot again and run qsd8250_semc.cmd and.....
I am everything perfect!
After this install the kernel and MILAD47 rom and everything works perfect!
Thanks a lot!!!
muy buenas noticias!!, el problema original del fallo fue usar un kernel y no tener liberado el bootloader.
tuve que trabajar bastante hasta descubrir que algo tan sencillo como flashear el celular salia mal por algun problema con los drivers, DESINSTALE TODO!!, medusa, 1stool, flashtools, drivers, seus y companion!!,
ejecute REGCLEAN, reinicie, volvi a instalar Flashtool, baje Sony Ericsson X10i_2.1.A.435_GLOBAL-GGL GENERIC 1232-9897, inicie, rootee con Super OneClik, instale superuser, busybox, verifique que todo funciona bien, reinicie ejecute qsd8250_semc.cmd y quedo todo perfecto!!
luego de esto instale el kernel y rom de MILAD47 y todo funciona perfecto!
[Q&A] ★[ROM][26 September] ★ Galaxy S5 Mini Alpha 4.0 ★ [4.4.2][AROMA]★
Q&A for ★[ROM][26 September] ★ Galaxy S5 Mini Alpha 4.0 ★ [4.4.2][AROMA]★Your S3 Fly !★
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Problema di flash
Ciao ho riscontrato il problema della fotocamera, scarico i due .zip che metti come link, eseguo il flash del primo (da recovery-install from SD Card), reboot, flash del secondo ma la situazione resta invariata. Cosa sbaglio? Grazie
Volley10 said:
Ciao ho riscontrato il problema della fotocamera, scarico i due .zip che metti come link, eseguo il flash del primo (da recovery-install from SD Card), reboot, flash del secondo ma la situazione resta invariata. Cosa sbaglio? Grazie
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=55700797&postcount=3123
install kernel QS, open camera, :laugh: , reboot
install kernel boeffla :fingers-crossed:
RISOLTO
Grazie ho risolto facendo il flash al contrario di come l'hai proposto tu. Non so se si tratta di un procedimento ortodosso ma almeno funziona regolarmente.:good:
Oxyitel"naja sborka. Sovetuju...
problems with installation
Hi, when installing zip2 for S5 Mini Alpha Edition 4.0 mi my device reports: installation aborted.
link download ........thank
sefa
4.4.4 download link?
link download Alpha 5.0 thank
link download....thank
download version v5 18/10/2014
Where is the download version v5 18/10/2014 I can not find?
Upload link
Not working rom!
4.4.4 new rom not installing?
---------- Post added at 11:05 PM ---------- Previous post was at 10:39 PM ----------
4.4.4 not workİng İnstallen faİled
any idea when can we expect a changelog on v5
no change log and installation instruction,,,?
Galaxy S5 Mini Alpha 5.0
rom is very slow and freezing
ussd code also not working
whenever phone reboots icons placed folders reset
Galaxy S5 Mini Alpha 4.0 ★ [4.4.2]
In new rom contact application often shows "Unfortunately, contacts has been stopped"
solution please.
I did update to 4.4.2 and everything was fine , except the calendar widget looks weird and 650-700 RAM memory all the time , and agenda are those names , but does not recognize the message or calls from people agenda .
I used Boeffla kernel 6.1 beta 6, and everything is ok.
I returned to 4.4.2 .
---------- Post added at 08:28 AM ---------- Previous post was at 07:56 AM ----------
I did update to 4.4.2 and everything was fine , except the calendar widget looks weird and 650-700 RAM memory all the time , and agenda are those names , but does not recognize the message or calls from people agenda .
I used Boeffla kernel 6.1 beta 6, and everything is ok.
I returned to 4.4.2 .
I tried it and do not work : bluetooth , wifi direct , web browser , play store , does not recognize the external sd , internal memory , it lacks the ultra energy saving
Problems with email
Thanks for this great rom
When trying to change the email signature on the application is closed
Q&A for [ROM] SM-G850F ★ Galaxy S6 Rom ★ Ozcan Aroma
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] SM-G850F ★ Galaxy S6 Rom ★ Ozcan Aroma. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
it works in Galaxy Alpha G850M?
no sry
only on the F Modell the Unlocked
Sent from my SM-G850F using XDA Free mobile app
can you port s6 settings, message , contacts apps?
with s6 frameworks?
Hey is it possible to disable "living" clock icon? It changes according to time but it causes microstutters when swiping through app pages. And another thing, can we expect themes working in next update?
Besides that, rom runs nicely - Antutu scores around 53K. Good job!
11111
It works in Galaxy Alpha G850k?
s6 failed and contacts
Caller ID and emergency dial pad working got this port from friend S4 i9505 dialer is still the stock one
Sorry for bad english
wahaj0892 said:
Caller ID and emergency dial pad working got this port from friend S4 i9505 dialer is still the stock one
Sorry for bad english
Click to expand...
Click to collapse
Link of these apps?
thank you alot
wahaj0892 said:
Caller ID and emergency dial pad working got this port from friend S4 i9505 dialer is still the stock one
Sorry for bad english
Click to expand...
Click to collapse
How can I install this inCallUi app?
i ask to the developer to port the S6 Settings i hope he can manage it :thumbup:
Sent from my SM-G850F using XDA Free mobile app
Bugs ohne ende.....
1. Telefon app hängt sich bei einem anruf auf und es bleibt nur der Button zum ran -> Telefonieren unmöglich!!!!
2. Nach reboot ist der sperrbildschirm der ganz normale zum streichen obwohl pin aktiviert ist. muss dann wieder neu eingestellt werden
3. adapt sound nicht vorhanden
4. hardware tasten leuchten ab und zu obwohl diese deaktiviert sind....
3 ist zwar kein bug wär aber gut wenns mit reinkommt. Ansich ne super rom aber zum gebrauch des handys nicht möglich wird wieder runtergenommen bis das gefixt wird.
Sorry google übersetzer: I have a bad english
1. Phone app locks up when a call and it remains only ran the button to - > call impossible !!!!
2. After reboot the lock screen is to emphasize normal though pin is activated . then has to be readjusted
3. adapt sound absent
4. hardware keys from light and although these are disabled ....
3 is not a bug but would be good wenns with comes in . Ansich ne super Rome but for use of mobile phones is not possible again taken down until the fixed.
themes
thanks for this wounder full ROM but maybe you can active the themes store in next update
Fingerprint
Does the fingerprint scanner work in this rom?
Yes
There isn't smart manager Perhaps I have not done all the wipe. I installed it a an upgrade ti version 2.0
Menu Button not working
Hi Team, Love the new rom, its great !!!
I have however run into a problem... The "Options/MEnu Button" is not working since I installed the rom. Can anyone help me out ??
Thanks
Work for A500M i am peru
---------- Post added at 01:56 PM ---------- Previous post was at 01:52 PM ----------
Work for A500M i am Peru
Bonjour j'ai un problème avec la ROM ! Le capteur d'empreinte ne fonctionne pas pour le " mode privé " et quand je recharge la batterie et que le portable est éteint j'ai un bug sur l'écran . Merci de me renseigné pour régler ces problèmes. cordialement
scan
does the fingerprint scanner work??
{
"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"
}
This is our port of LineageOS 14.1 to the 2015 Moto E LTE (surnia). LineageOS is effectively a continuation of the CyanogenMod project. This ROM should run reliably, provided you are running a modem from 5.1 or newer.
Changelog:
CMXLog official nightly changelog
Downloads:
Official weekly builds
Lineage su addon
XDA:DevDB Information
LineageOS 14.1 for Moto E LTE, ROM for the Moto E 2015
Contributors
squid2, Alberto97, scritch007
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2016-12-10
Last Updated 2017-01-26
i'm on cm14.1-20161209 buid,there is a bug,when i receive a call data connection gets off and i cant't turn it on untill i restart my phone (surnia xt1521,operator jio 4g).
Irfan_ said:
i'm on cm14.1-20161209 buid,there is a bug,when i receive a call data connection gets off and i cant't turn it on untill i restart my phone (surnia xt1521,operator jio 4g).
Click to expand...
Click to collapse
Grab a log - otherwise - it didn't happen
Devs are not wizards
where i can get the log?
---------- Post added at 07:05 PM ---------- Previous post was at 07:03 PM ----------
Zokhii said:
Grab a log - otherwise - it didn't happen
Devs are not wizards
Click to expand...
Click to collapse
where i can get the log?
I just updated from 13.0-20161122-NIGHTLY to 14.1-20161210-NIGHTLY on my Motorola Moto E 2015 LTE (surnia). Unfortunately, com.android.phone keeps crashing now, and I can't unlock my SIM card (it simply says "SIM PIN operation failed!").
There's a lot of logs, so it's hard to tell where the issue lies exactly, but this crash happens basically every second so it seems relevant:
Code:
12-10 19:15:14.869 4210 4210 E AndroidRuntime: FATAL EXCEPTION: main
12-10 19:15:14.869 4210 4210 E AndroidRuntime: Process: com.android.phone, PID: 4210
12-10 19:15:14.869 4210 4210 E AndroidRuntime: java.lang.RuntimeException: Error receiving broadcast Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) } in com.qualcomm.ims.vt.LowBatteryHandler$1
@17ba168
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:1132)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:751)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:95)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6126)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: Caused by: java.lang.SecurityException: getImsPhoneId: Neither user 1001 nor current process has android.permission.READ_PHONE_STATE.
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at android.app.ContextImpl.enforce(ContextImpl.java:1585)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1617)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at android.content.ContextWrapper.enforceCallingOrSelfPermission(ContextWrapper.java:707)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at org.codeaurora.ims.QtiImsExt.onGetImsPhoneId(QtiImsExt.java:89)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at org.codeaurora.ims.QtiImsExtBase$QtiImsExtBinder.getImsPhoneId(QtiImsExtBase.java:97)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at org.codeaurora.ims.QtiImsExtManager.getImsPhoneId(QtiImsExtManager.java:167)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at org.codeaurora.ims.utils.QtiImsExtUtils.getImsPhoneId(QtiImsExtUtils.java:260)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at org.codeaurora.ims.utils.QtiImsExtUtils.getConfigForDefaultImsPhoneId(QtiImsExtUtils.java:229)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at org.codeaurora.ims.utils.QtiImsExtUtils.isCarrierConfigEnabled(QtiImsExtUtils.java:205)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at org.codeaurora.ims.utils.QtiImsExtUtils.allowVideoCallsInLowBattery(QtiImsExtUtils.java:216)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at com.qualcomm.ims.vt.LowBatteryHandler$1.onReceive(LowBatteryHandler.java:97)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:1122)
12-10 19:15:14.869 4210 4210 E AndroidRuntime: ... 7 more
12-10 19:15:14.875 1169 2142 W ActivityManager: Process com.android.phone has crashed too many times: killing!
12-10 19:15:14.923 278 278 I ServiceManager: service 'sip' died
12-10 19:15:14.923 278 278 I ServiceManager: service 'simphonebook' died
12-10 19:15:14.923 278 278 I ServiceManager: service 'iphonesubinfo' died
12-10 19:15:14.923 278 278 I ServiceManager: service 'isms' died
12-10 19:15:14.923 278 278 I ServiceManager: service 'phone' died
12-10 19:15:14.923 278 278 I ServiceManager: service 'carrier_config' died
12-10 19:15:14.923 278 278 I ServiceManager: service 'ims' died
12-10 19:15:14.923 278 278 I ServiceManager: service 'qti.ims.ext' died
12-10 19:15:14.923 278 278 I ServiceManager: service 'isub' died
12-10 19:15:14.923 4337 4452 I ActivityThread: Removing dead content provider:[email protected]
12-10 19:15:14.924 1169 1947 D ConnectivityService: unregisterNetworkFactory for PhoneSwitcherNetworkRequstListener
12-10 19:15:14.924 1169 1947 D ConnectivityService: unregisterNetworkFactory for TelephonyNetworkFactory[0]
12-10 19:15:14.926 1169 3094 I ActivityManager: Process com.android.phone (pid 4210) has died
Irfan_ said:
where i can get the log?
---------- Post added at 07:05 PM ---------- Previous post was at 07:03 PM ----------
where i can get the log?
Click to expand...
Click to collapse
Google how to make a logcat
Thanks for the thread....
Was waiting for it...
SylvieL said:
I just updated from CyanogenMod 13.0-20161122-NIGHTLY to 14.1-20161210-NIGHTLY on my Motorola Moto E 2015 LTE (surnia). Unfortunately, com.android.phone keeps crashing new, and I can't unlock my SIM card (it simply says "SIM PIN operation failed!").
There's a lot of logs, so it's hard to tell where the issue lies exactly, but this crash happens basically every second so it seems relevant:
Click to expand...
Click to collapse
Did you do a clean install or direct update? It requires a clean install.
mykenyc said:
Did you do a clean install or direct update? It requires a clean install.
Click to expand...
Click to collapse
I did do a direct install because that's what CM Updater did. I'll try a factory reset.
SylvieL said:
I did do a direct install because that's what CM Updater did. I'll try a factory reset.
Click to expand...
Click to collapse
I would suggest a clean install as in re-downloading open gapps and cyanogen.
mykenyc said:
I would suggest a clean install as in re-downloading open gapps and cyanogen.
Click to expand...
Click to collapse
I don't use Gapps so I guess a factory reset is the only thing left then.
Edit: Someone else tried this already and they seem to still be getting the crash.
Irfan_ said:
i'm on cm14.1-20161209 buid,there is a bug,when i receive a call data connection gets off and i cant't turn it on untill i restart my phone (surnia xt1521,operator jio 4g).
Click to expand...
Click to collapse
This is because VoLTE is not implemented completely yet.I am facing same problem with same rom on xt1521. So i am using aicp_surnia_n-12.1-NIGHTLY-20161208 version and it works fine and VoLTE is also working. or wait for new versions of CM14.1.
SD card problem
How to resolve this issue. Facing this issue everytime whenever I select sd card. Same thing happens in root access mode.
Badrikesh said:
How to resolve this issue. Facing this issue everytime whenever I select sd card. Same thing happens in root access mode.
Click to expand...
Click to collapse
See if the issue persist using another file manager like amaze. Also check the permissions.
Issue switching to mobile data after being on WiFi
If mobile data fails to activate after you've been using WiFi for a while, please read this post on the osprey thread: http://forum.xda-developers.com/showpost.php?p=70027645&postcount=1672
For some reason the Wifi is not working, even with a completely clean install. Also, Squid Kernel is not compatible for me? Battery also seems to drain quickly on this build. Clean experience otherwise though...
AndersCF said:
For some reason the Wifi is not working, even with a completely clean install. Also, Squid Kernel is not compatible for me? Battery also seems to drain quickly on this build. Clean experience otherwise though...
Click to expand...
Click to collapse
There's no squid kernel for Nougat yet. Try reflashing CM14.1 to see if WiFi starts working again. It works fine for me.
VenomMOD said:
There's no squid kernel for Nougat yet. Try reflashing CM14.1 to see if WiFi starts working again. It works fine for me.
Click to expand...
Click to collapse
Tried flashing over the existing install and wipe flash/dalvik. It works now.
Anyone else having an issue with the cLock widget when you click on the weather the popup text is black?
Audio volume is very low
First my english is very bad but i'll try to say the most important .
1. Thank you , your work with this room is amazing, now all the process is very smooth, now my moto e surnia is very fast ,im so glad for that reasons, the updates from the playstore now are faster , very!
THE BIG PROBLEM FOR ME
The volumen is very low , my friend has the same device with marshmallow official and the volumen is the same level if you compare with the official room android lollipop.
But the problem appears with this room (7.1) the volumen is no the same any more.
I got to compare the same device between moto e surnia marshmallow vs moto e surnia nougat (7.1) and the level volume from marshmallow is bether.
PLEASE FIX THIS PROBLEM BECAUSE A LOT OFS USERS LOVE SPOTIFY WITH A GOOD HEADPHONES BUT THIS PROBLEM ES VERY IMPORTANT FOR US.
About the moto radio, to be honest the best app to listen radio offline is from moto. and with this room is impossible to use the moto radio app , it says this app ( radio moto) is not compatible.