Related
Anyone else having a problem with the genie widget today?
I can't get mine to load anything, and a message pops up:
"Sorry, unable to connect. Please try later."
I have to guess google accidentally changed something on their end that the widget is connecting to, that is failing, for retrieving the necessary data.
I am seeing the following in logcat:
Code:
D/Genie ( 835): Requesting data...
D/Genie ( 835): Request in-flight, ignoring.
D/Genie ( 835): [b]Making MASF Request to http://www.google.com/m/appreq - g:gne[/b]
/r: GenieRequest [no fake location] type: [15, 16] with ma
xAge: 21600000 at 4:16pm, June 16
D/Genie ( 835): Network status: CONNECTED
D/Genie ( 835): MASF cache miss
D/Genie ( 835): ctrl.requestData has finished.
D/Genie ( 835): RefreshService: Waiting for requestlatch to clear...
D/Genie ( 835): MASF cache miss
D/Genie ( 835): [b]Request failed, and nothing in cache[/b].
I/Genie ( 835): Next data refresh scheduled for: 10:16pm, June 16 (basetime w
as 4:16pm, June 16)
D/Genie ( 835): [b]Request failed at, 4:16pm, June 16 next auto-refresh time =21[/b]
Just want to see if I am the only one...
Nope, your not. I'm having the same problem. It was fine yesterday. Today it doesn't work.
I also found a post here where some Nexus One users reported the same (including one who is unrooted).
On another forum somewhere withe an Evo is having the same problem.
All of this only today. So it much be a Google thing.
What version are you guys using? Mine works perfectly fine...
I may be running an older version, as I keep carrying the one I have forward from ROM to ROM, based on customizations I'm too lazy to re-do.
Mine shows as 1.1.7 RC6.
Nope just checked mine after I saw ur post. Did a refresh and it works perfectly
-------------------------------------
Sent via the XDA Tapatalk App
JsChiSurf said:
I may be running an older version, as I keep carrying the one I have forward from ROM to ROM, based on customizations I'm too lazy to re-do.
Mine shows as 1.1.7 RC6.
Click to expand...
Click to collapse
Mine is 1.2.02 RC2. And shes purrin along...
gomorrah said:
Mine is 1.2.02 RC2. And shes purrin along...
Click to expand...
Click to collapse
Do you have a link to that version anywhere? All the ones I keep finding are the same version as mine, which, from what I'm reading is probably the cause of the problem.
Thanks.
JsChiSurf said:
Do you have a link to that version anywhere? All the ones I keep finding are the same version as mine, which, from what I'm reading is probably the cause of the problem.
Thanks.
Click to expand...
Click to collapse
Gimmie a sec. I only have my themed one, it might be the same one that comes in DD. Ill check.
Try this one and let me know. I didnt check, Im just assuming...
Posted one in above link^^^^
EDIT- Verified its the newer version.
gomorrah said:
Posted one in above link^^^^
EDIT- Verified its the newer version.
Click to expand...
Click to collapse
Dang. New version, same result! I appreciate you taking the time to post it.
Now I'm wondering if the issue is based on location, or if you guys have a cache that you are running off of, where my cache is blank, and therefore failing.
Do you see anything in your logcat regarding successful update, or, how old our your latest news updates?
im using DC 2.0.9.1 and the genie widget is working just fine
Yea, this is not ROM dependent / specific. A quick google search shows it's popping up everywhere. I suspect when your cache expires, everyone's will bork too, unless a remote fix is done before this happens.
The same version on my wife's hero was working when I got home from the office, and has now stopped as well.
If someone who has it still working can remove and re-add, while watching their logcat, to see what messages appear regarding success / fail on the call to google, it would help immensely.
ill give it a shot
heres what i got
D/Genie ( 856): Location Listener has stopped listening for updates.
D/LocationManager( 856): removeUpdates: listener = com.google.android.apps.geni
[email protected]
D/LocationManagerService( 433): Released wakelock
D/NetworkLocationProvider( 433): removeListener(): apps.genie.geniewidget
D/NetworkLocationProvider( 433): setMinTime: 300000
D/Genie ( 856): Got updated location: 33.21527777777778, -97.14527777777778 +
/-1000.0
D/Genie ( 856): Requesting data...
D/Genie ( 856): Making MASF Request to http://www.google.com/m/appreq - g:gne
/r: GenieRequest 33.21527777777778,-97.14527777777778[no fake location] type: [1
5, 16] with maxAge: 0 at 8:56pm, June 16
D/Genie ( 856): Network status: CONNECTED
D/Genie ( 856): Cached entry too old
D/Genie ( 856): MASF cache miss
D/dalvikvm( 856): GC freed 4962 objects / 442080 bytes in 196ms
D/Genie ( 856): Request failed, falling back to cached data.
D/Genie ( 856): Got response: GeniePayload: isCached: true payload: 41 and up
dated model: READY: showing news 0 of 40 weather=Partly Cloudy at, 8:56pm, June
16 with timestamp: 3:33am, June 16 next auto-refresh time = 0
D/Genie ( 856): Refresh Complete, notifying success.
D/Genie ( 856): Refreshing widget.
D/Genie ( 856): RefreshService: Done, fetching news and weather icons.
D/Genie ( 856): NewsImageCache: Cache: 100 items in index, and 101 files on d
Click to expand...
Click to collapse
Thanks. Yep, exactly as expected.
Code:
[b]D/Genie ( 856): Request failed, falling back to cached data.[/b]
here's mine, left it complete just in case (had to zip to upload here)
edit: mine does not fail, and I show version 1.1.7 rc6
no problem
danaff37 said:
here's mine, left it complete just in case (had to zip to upload here)
Click to expand...
Click to collapse
Yours appears to be working. Do you know your version number?
haha I edited my post the exact minute you asked. lol
danaff37 said:
haha I edited my post the exact minute you asked. lol
Click to expand...
Click to collapse
I see it now . Shoot, that's the same version I was running originally. This makes me think it must be a location issue, or maybe you are pulling the data from a different server based on location.
Guess those it's not working for have to wait it out, as I'm not sure how we could fix it based on the variability and the fact that the same version is working for some and not for others...
if it is location based, in tampa, fl area here for comparison sakes
Hi everybody !
In the attachment you will find nfc.golfu.so which is the firmware for HTC Desire C with NFC (phone model PL01110). I get it from RUU_GOLF_U_ICS_40A_H3G_UK_1.45.771.3_Radio_10.11.98.09H_1.06.98.13M2_release_266089_signed.exe that you can find on the net.
I upload firmware here because I have spend 3 weeks to get it working with [STABLE][ROM][4.1.2][JZO54K] CyanogenMod10 | BUILD #3.
On this rom, we see the NFC option but it can not enable it and we get the error hw_get_module() failed with logcat and the option stick unchecked.
With the attachement to this post, NFC is working (at least with JZO54K CM10 build#3), see logcat :
I/NfcService( 477): Enabling NFC
D/NFCJNI ( 477): Start Initialization
I/dalvikvm( 315): Jit: resizing JitTable from 4096 to 8192
D/NFCJNI ( 477): NFC capabilities: HAL = 8150100, FW = a76d0c, HW = 620003, Model = 10, HCI = 1, Full_FW = 109, Rev = 12, FW Update Info = 0
D/NFCJNI ( 477): phLibNfc_SE_GetSecureElementList()
D/NFCJNI ( 477):
D/NFCJNI ( 477): > Number of Secure Element(s) : 1
D/NFCJNI ( 477): phLibNfc_SE_GetSecureElementList(): SMX detected, handle=0xabcdef
D/NFCJNI ( 477): phLibNfc_SE_SetMode() returned 0x000d[NFCSTATUS_PENDING]
I/NFCJNI ( 477): NFC Initialized
So what to do do with this nfc.golfu.so ?
Uncompress file nfc.golfu.zip and you will get nfc.golfu.so
Put the file (nfc.golfu.so) on /system/lib/hw/ on your phone.
chmod 644 /system/lib/hw/nfc.golfu.so
Then reboot your phone and now, you can check NFC option and you can use it (at least with phone having NFC AND rom having NFC enabled)
roms2000 said:
So what to do do with this nfc.golfu.so ?
Uncompress file nfc.golfu.zip and you will get nfc.golfu.so
Put the file (nfc.golfu.so) on /system/lib/hw/ on your phone.
chmod 644 /system/lib/hw/nfc.golfu.so
Then reboot your phone and now, you can check NFC option and you can use it (at least with phone having NFC AND rom having NFC enabled)
Click to expand...
Click to collapse
And the phone is not working, now. I tried to reboot, it's never completing the bootstrap. I can use the recovery console, I tried to fix permissions but it's always the same. How can I remove that file from recovery console?
fankool said:
And the phone is not working, now. I tried to reboot, it's never completing the bootstrap. I can use the recovery console, I tried to fix permissions but it's always the same. How can I remove that file from recovery console?
Click to expand...
Click to collapse
It doesn't work for me
Bootstrap? Is that stuck on boot animation?
If so:
You can reflash the current rom. That removes all the installed mods but not the apps or any sdcard data.
/*Worked for me, maybe not for you...*\
julian6457 said:
It doesn't work for me
Bootstrap? Is that stuck on boot animation?
If so:
You can reflash the current rom. That removes all the installed mods but not the apps or any sdcard data.
/*Worked for me, maybe not for you...*\
Click to expand...
Click to collapse
Yes, there's always the boot animation. But If I reflash the current rom I'll loose the data saved on phone and I have to reinstall the applications.
fankool said:
Yes, there's always the boot animation. But If I reflash the current rom I'll loose the data saved on phone and I have to reinstall the applications.
Click to expand...
Click to collapse
As I know flashing a new rom witout a /system wipe will not delete the applications.
You can also remove the micro SD (If you have one) there are multiple ways to cpoy the files to a pc from like micro>usb
Flasing roms only disable xposed modules and reinstall the stock apps.
Maybe a backup will come in handy the next time
julian6457 said:
As I know flashing a new rom witout a /system wipe will not delete the applications.
You can also remove the micro SD (If you have one) there are multiple ways to cpoy the files to a pc from like micro>usb
Flasing roms only disable xposed modules and reinstall the stock apps.
Maybe a backup will come in handy the next time
Click to expand...
Click to collapse
My recovery is not finishing backup for 4 months. Before it works perfectly.. so, I have only old bakcup (fbefore the last rom flashing).
I tried by adb to remove nfc.golfu.so from /system/lib/hw/ but the phone still stucks on boot, so I'll not try to copy file by memory card (it will not be useful).
I reflashed the rom without erasing anything and the phone was rebirth. Thank you!
A strange fast blinking on the screen is annoying me now, why? It's like the old crt monitor using 60Hz frequency. I restarted the phone but it's still blinking, from the white screen after switch on. Can anyone help me to understand what's happening?
---------- Post added at 11:31 AM ---------- Previous post was at 11:25 AM ----------
fankool said:
A strange fast blinking on the screen is annoying me now, why? It's like the old crt monitor using 60Hz frequency. I restarted the phone but it's still blinking, from the white screen after switch on. Can anyone help me to understand what's happening?
Click to expand...
Click to collapse
Replying to myself: I only disabled "developer options" (my phone is in italian language, I suppose this is the translation), restarted the phone and removed the battery and now works perfectly. But still I don't know why it was blinking.
Well roms2000,
thank you for your job (even if it's not working on my phone) if you are interested now I can continue the tests on my mobile phone to use NFC, I know how to quickly recover my phone (I also updated my cwm and now the backup works perfectly).
I'm wondering why it stucks (I disabled boot animation at start so I can't say exactly when it freezes) and what is the logfile I can read to understand what's happening (obviously my phone has NFC, is the O2 version).
I'm using NOPE kernel v2.6 850MHz (but at 800MHz) on miniCM v6 (a derivation of cm10). I just followed the instruction, I copied nfc.golfu.so in /system/lib/hw using x-plore and with the same application I changed the attributes to 644 (maybe, but it's difficult, I could set a wrong attributes, but in this case I think android simply ignores the library).
Also removing the file (by adb from recovery) the phone always stucks.
Sorry for long response, I did not check this post, so i couldn't received notifications.
@fankool : do you have the NFC version of HTC Desire C ? If not, you can't enable NFC, and the file won't do anything for you.
For NFC, I have simply take the module on the official rom to get it working, if your rom is base on android 4.1.2, it should work. Try to use logcat to see some message about error and NFC.
--- Edit :
I don't think MiniCM has NFC soft enabled : check on your phone : Settings / Wireless & Network (More...) / NFC
If you have a check box for NFC, rom embed NFC soft, else, it is not and I don't think firmware / module will do anything.
my desire c has NFC (it's an O2 desire c, and with stock rom and the revolution 4.0.4 it worked), but the option to enable NFC disappeared, also trying with prometheus or nope. I installed many different roms based on 4.1.1 (cm, minicm, miui..) but always NFC was not working. How can I use logcat?
Can you try this rom : JZO54K CM10 build#3, like I did ?
For logcat, it will not be useful if you do not have the option to enable NFC.
htc desire c nfc
roms2000 said:
Hi everybody !
In the attachment you will find nfc.golfu.so which is the firmware for HTC Desire C with NFC (phone model PL01110). I get it from RUU_GOLF_U_ICS_40A_H3G_UK_1.45.771.3_Radio_10.11.98.09H_1.06.98.13M2_release_266089_signed.exe that you can find on the net.
I upload firmware here because I have spend 3 weeks to get it working with [STABLE][ROM][4.1.2][JZO54K] CyanogenMod10 | BUILD #3.
On this rom, we see the NFC option but it can not enable it and we get the error hw_get_module() failed with logcat and the option stick unchecked.
With the attachement to this post, NFC is working (at least with JZO54K CM10 build#3), see logcat :
I/NfcService( 477): Enabling NFC
D/NFCJNI ( 477): Start Initialization
I/dalvikvm( 315): Jit: resizing JitTable from 4096 to 8192
D/NFCJNI ( 477): NFC capabilities: HAL = 8150100, FW = a76d0c, HW = 620003, Model = 10, HCI = 1, Full_FW = 109, Rev = 12, FW Update Info = 0
D/NFCJNI ( 477): phLibNfc_SE_GetSecureElementList()
D/NFCJNI ( 477):
D/NFCJNI ( 477): > Number of Secure Element(s) : 1
D/NFCJNI ( 477): phLibNfc_SE_GetSecureElementList(): SMX detected, handle=0xabcdef
D/NFCJNI ( 477): phLibNfc_SE_SetMode() returned 0x000d[NFCSTATUS_PENDING]
I/NFCJNI ( 477): NFC Initialized
So what to do do with this nfc.golfu.so ?
Uncompress file nfc.golfu.zip and you will get nfc.golfu.so
Put the file (nfc.golfu.so) on /system/lib/hw/ on your phone.
chmod 644 /system/lib/hw/nfc.golfu.so
Then reboot your phone and now, you can check NFC option and you can use it (at least with phone having NFC AND rom having NFC enabled)
Click to expand...
Click to collapse
can i flash this zip file with stock rom
Stock rom should have it.
If you flash with stock I don't know if it will enable NFC.
roms2000 said:
Stock rom should have it.
If you flash with stock I don't know if it will enable NFC.
Click to expand...
Click to collapse
Well, this firmware enabled NFC on Cyanogenmod 11 - confirmed working by one of users, so thanks for this.
I've flashed Stock ROM and deodexed ROM, neither had NFC working (although it's meant to be) so it could be in boot if it works or not as my handset is 100% known to have NFC but my Bootloader is 1.31 and not 1.28
Sent from my B1-730HD using XDA Free mobile app
Hello, I have a little problem with Xposed (this is my first with this application is perfect!).
When I install a module, I check the box and restart my phone.
Everything seems ok but the modules are not loaded when did consult the log, there is this message:
13 june 2014 16:39:22 UTC
Loading Xposed v54 (for zygote)...
Running Rom '16.0.B.2.6' with fingerprint 'sony/C2305_1276-3349/C2305:4.2.2/16.0.B.2.6/eng.admiistrator.13656745:user/release-key'
Loading modules from /mnt/asec/com.ramis.keepchat-2/pkg.apk
File does not exist
Click to expand...
Click to collapse
Of course I checked and the file is there!
I have that for all modules installed. I tried reinstalling the rom, reinstall Xposed but nothing works...
I also try reloading the backup I had on Titanium Backup
I'm in a bind, and I did find any similar error on the forum.
Thank you for your help!
P.S : Sorry if my English is wrong, I'm french ^^ (google translate is too bad :3 )
RasmusDesign said:
Of course I checked and the file is there!
Click to expand...
Click to collapse
Yeah, but not during the early boot phase when Xposed and the modules are initialized. Move the module to internal storage, then it should work.
@Cpasjuste,
In the image headers I noticed that the ramdisk and tag addresses have changed.
ramdisk addr: 0x02000000 -> 0x01000000
tags addr: 0x01e00000 -> 0x00000100
Please correct me if I'm wrong...
The bootloader (lk) loads the ramdisk and kernel tags (device tree) at these physical RAM locations.
@ggow
Yes i saw that but it have no effect. I'm focusing on the .dt part because I found a few things :
- The DT images can correctly be extracted with a tool named "mkboot".
- When using the DT image from kk kernel, the bootloader complains about DT not found (fastboot boot boot.img)
- Opened both DT image in hex editor, noticed some differences in the headers. I switched kk DT headers by jb DT headers, the bootloader don't complain
anymore so I guess it can now found it. But the kernel will just hang immediately.
- The DT syntax seems to have changed (arch/arm/boot/dts/thor.dtsi), this may be the problem for our old bootloader ?!
- Now I'd like to use compiled dt from kk kernel, but has you may have noticed the DT compilation fail about "fb_mem" not declared. I think I need to fix this, then maybe use old jb tools ( $KERNEL_OUT/scripts/dtc/dtc -p 2048 -O dtb -o thor-v1.dtb arch/arm/boot/dts/thor-v1.dts) to compile them, unlike kk kernel which now compile them with the kernel.
From what iv read dt, kernels and bootloaders are linked together, so there is also maybe some changes to be done in the dt sources. But this start to be out of my knowledge.
I asked to hashcode for that but I guess he is very busy.
Cpasjuste said:
@ggow
Yes i saw that but it have no effect. I'm focusing on the .dt part because I found a few things :
- The DT images can correctly be extracted with a tool named "mkboot".
- When using the DT image from kk kernel, the bootloader complains about DT not found (fastboot boot boot.img)
- Opened both DT image in hex editor, noticed some differences in the headers. I switched kk DT headers by jb DT headers, the bootloader don't complain
anymore so I guess it can now found it. But the kernel will just hang immediately.
- Now I'd like to use compiled dt from kk kernel, but has you may have noticed the DT compilation fail about "fb_mem" not declared. I think I need to fix this, then maybe use old jb tools ( $KERNEL_OUT/scripts/dtc/dtc -p 2048 -O dtb -o thor-v1.dtb arch/arm/boot/dts/thor-v1.dts) to compile them, unlike kk kernel which now compile them with the kernel.
From what iv read dt and kernels are linked together, so there is also maybe some changes to be done in the dt sources. But this start to be out of my knowledge.
Click to expand...
Click to collapse
I noticed the "fb_mem" not declared error and couldn't find any reference to it anywhere. I switched the dt.img header also and got to the point where the kernel was not dumping out to fastboot any more, but instead bootloops.
I have messaged amazon once again to post the source code for apollo and thor for update .4.1.1 .
Hehe we are at the same point it seems (nowhere)
Today I did spent a lot of time on this. After a lot of dt hacks/test I'm unable to resolve this problem for now. So I had another idea and started to port kexec hardboot for our device. I'm at the point where is successfully load kernel and DT (something is different for our device, the msm_id struct, which I solved) and reboot but will hang or restart just after a few seconds of the reboot. I think I'm almost there but I may have some problem to find correct memory addresses which are not overwritten by the boot loader. Let me know if you want to take a look I'll upload patches. But well even if we succeed we may still encounter the same DT problem.
In the "dt.img" there is 3 dtb files in, which are scanned by the bootloader for the correct hw revision. I did find that our device use the "thor-v2-apq.dts/.dtb" dt file for booting (not the thor-v1 nor v2) which correspond to our hardware revision. This is in correlation to the 4.1 kernel which only compile this dtb.
When loading the 4.1 dt image with kexec I was able to debug and see that while the header of each dtb parts have changed, there's still the correct hw revision included (of course!?). This one is correctly loaded by kexec and so probably by the bootloader (but in the new dt.img we still need to modify the img header for our bootloader to find it). By the way, I wonder how this final dt.img is built !?
I just don't know yet what is the thor.dtsi file in the 4.1 kernel, the one missing the fb_mem def. This is not included in the dt.img so should it be modified to match our old thor-v2-apq.dts instead the new one ?
By the way manual compilation (and decompilation!) does work with the dtc utility (apt-get install device-tree-compiler).
Yes, upload the the patches for kexec. Definitely interested in taking a look. I have configured a kernel last night with kexec config enabled (great minds think alike)
This DT problem is troubling me. Perhaps not everything is included in this kernel for Apollo or Thor to boot.
I received a reply from amazon, they said they will post the missing source for the last 3 updates very soon (no idea of time frame).
Sent from my Full Android on C6603 using Tapatalk
I don't think the sources are the problem as we have it on stock 4.1 boot.img. I'll upload the patches tomorrow with a little briefing.
@ggow : 4.1.1 kernel booted (not from sources. As you noted this sources may be incomplete).
I'll post the kernel this night, with a clean 4.1.1 system if i have the time.
Cpasjuste said:
@ggow : 4.1.1 kernel booted (not from sources. As you noted this sources may be incomplete).
I'll post the kernel this night, with a clean 4.1.1 system if i have the time.
Click to expand...
Click to collapse
Good News, well done
ggow said:
Good News, well done
Click to expand...
Click to collapse
Finally, sorry for the delay So here is the modded 4.1.1 boot image. In short : binary extract correct dts from 4.1.1 stock dt image and happend it to 4.1.1 stock zImage.
Didn't had the time to finish my gapps rom based on 4.1.1 but should not be too long
http://android.mydedibox.fr/hdx/boot-4.1.1.img
Cpasjuste said:
Finally, sorry for the delay So here is the modded 4.1.1 boot image. In short : binary extract correct dts from 4.1.1 stock dt image and happend it to 4.1.1 stock zImage.
Didn't had the time to finish my gapps rom based on 4.1.1 but should not be too long
http://android.mydedibox.fr/hdx/boot-4.1.1.img
Click to expand...
Click to collapse
Good work looking forward to testing it out.
Sent from my Optimus G using XDA Free mobile app
cdub50 said:
Good work looking forward to testing it out.
Sent from my Optimus G using XDA Free mobile app
Click to expand...
Click to collapse
This is a wip for you. You need to wait for a root exploit on 4.1.1 for using it !
Cpasjuste said:
This is a wip for you. You need to wait for a root exploit on 4.1.1 for using it !
Click to expand...
Click to collapse
Ah gotcha. Hopefully that will be sooner than later.
Sent from my Optimus G using XDA Free mobile app
Cpasjuste said:
Finally, sorry for the delay So here is the modded 4.1.1 boot image. In short : binary extract correct dts from 4.1.1 stock dt image and happend it to 4.1.1 stock zImage.
Didn't had the time to finish my gapps rom based on 4.1.1 but should not be too long
http://android.mydedibox.fr/hdx/boot-4.1.1.img
Click to expand...
Click to collapse
Thanks for that
Which number dts is the correct one (there are 3). I need to do the same for Apollo...
ggow said:
Thanks for that
Which number dts is the correct one (there are 3). I need to do the same for Apollo...
Click to expand...
Click to collapse
From what i remember this is the third (which is thor-v2-apq.dtb)
Well, cm is still a ***** to get ported :/, tree days on it without success.
Else the new odex framework is not deodexable by baksmali. If you ever have a solution let me know (You may not need that but I'm in a dead end).
So @ggow, did you made some progress on resurecting your device ?
In the meantime i did get msm aosp up and running ! (but no wifi, qcmediaplayer not found for no apparernt reason which prevent some audio to work, slow ui transitions and probably more stuff to fix).
Cpasjuste said:
So @ggow, did you made some progress on resurecting your device ?
In the meantime i did get msm aosp up and running ! (but no wifi, qcmediaplayer not found for no apparernt reason which prevent some audio to work, slow ui transitions and probably more stuff to fix).
Click to expand...
Click to collapse
So far no...
What I think could have happenned is the synaptic dsx firmware and configuration has been updated or corrupted by the new kernel.
I am in the process trying to figure out exactly what I need to do to fix it. I have found a utility which can be used to force an update to an older version of synaptic firmware.
I might have to write a utility to extract the firmware and configuration area from a working device.
Will let you know what I find.
Sent from my Kindle Fire HDX 7 using Tapatalk
ggow said:
So far no...
What I think could have happenned is the synaptic dsx firmware and configuration has been updated or corrupted by the new kernel.
I am in the process trying to figure out exactly what I need to do to fix it. I have found a utility which can be used to force an update to an older version of synaptic firmware.
I might have to write a utility to extract the firmware and configuration area from a working device.
Will let you know what I find.
Sent from my Kindle Fire HDX 7 using Tapatalk
Click to expand...
Click to collapse
Yep i was just going to talk you about this. I'm trying to fix wifi on the aosp build and discovered this lines in dmesg :
<6>[ 6.404807] synaptics_dsx_i2c 2-0020: fwu_start_reflash: Requesting firmware image Synaptics.3.B.thor.img
<6>[ 6.414184] synaptics_dsx_i2c 2-0020: Firwmare size 45056, config size 512
<6>[ 6.421216] synaptics_dsx_i2c 2-0020: Device firmware id 1509905.
<6>[ 6.427045] synaptics_dsx_i2c 2-0020: Device config ID 0x13, 0x07, 0x00, 0x02
<6>[ 6.434233] synaptics_dsx_i2c 2-0020: .img config ID 0x13, 0x07, 0x00, 0x02
<6>[ 6.441127] synaptics_dsx_i2c 2-0020: Nothing needs to be updated
<6>[ 6.447230] synaptics_dsx_i2c 2-0020: fwu_start_reflash: No need to do reflash.
Click to expand...
Click to collapse
Thank you for your work! I hope your problem will spill over into different firmware for our device. With the support of LTE I hope.
Hey I could really appreciate some help with that problem and please excuse all style problems it's my first post.
Information:
OnePlus 5T
OxygenOS 5.1.3
Magisk V 16.0
So here's the Problem:
Everytime I try to deactivate or delete a module named Adaptive icons Round Mask my device gets into a bootloop. I tried to uninstall it with the manager app and in recovery. Also i uninstalled magisk but it got still into the bootloop. I think that there's still a modifaction left that tries to load the module which i have to delete but i have no plan where it could be. I also found an error in the android_boot.log:
Code:
06-23 12:43:11.553 3144 3144 W ziparchive: Unable to open '/vendor/overlay/RoundMaskOverlay.apk': No such file or directory
06-23 12:43:11.553 3144 3144 W zipro : Error opening archive /vendor/overlay/RoundMaskOverlay.apk: I/O error
06-23 12:43:11.553 3144 3144 D asset : failed to open Zip archive '/vendor/overlay/RoundMaskOverlay.apk'
06-23 12:43:11.553 3144 3144 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 3144 (main), pid 3144 (main)
06-23 12:43:11.584 3178 3178 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone
06-23 12:43:11.584 1048 1048 I /system/bin/tombstoned: received crash request for pid 3144
06-23 12:43:11.587 3178 3178 I crash_dump64: performing dump of process 3144 (target tid = 3144)
Thanks for any help.
Same issue...
I can only restore my nandroid backup now.
Edit:
As the repo is already deleted, I find this in Google cache:
https://webcache.googleusercontent....Icons-Round-Mask/issues/4+&cd=1&hl=en&ct=clnk
But anyway, it's not a permanent solution. Can anyone advise how to remove this module completely? Thanks!
PS. The module is here: https://forum.xda-developers.com/showpost.php?p=76861990&postcount=794
edison0354 said:
Edit:
As the repo is already deleted, I find this in Google cache:
Click to expand...
Click to collapse
I'm using the same temporary solution as mentioned in that google link.
Finally, find a solution...
Tested on Nexus 5 & Nexus 7 2013, both on LineageOS 14.1, but, do it on your own risk, better do a nandroid backup before.
1. Disable this module in Magisk manager;
2. Install Substratum https://play.google.com/store/apps/details?id=projekt.substratum&hl=en ;
3. Open Substratum using legacy root mode, in manager page, you will see a null module, select and delete it;
4. Reboot, everything should be fine.
In your case, I think you only need to delete the module using substratum manager.
How do i use legacy root mode?
Edit:
Ok i think i found the magisk module but it says it can't be installed on Oreo and above.
And in my manager page aren't any modules.
RDM.NSA said:
How do i use legacy root mode?
Edit:
Ok i think i found the magisk module but it says it can't be installed on Oreo and above.
And in my manager page aren't any modules.
Click to expand...
Click to collapse
I'm on 7.1.2, so by default it goes to legacy mode because Nougat doesn't support the newer mode...
Please check if there's any trigger in setting or somewhere else to switch to legacy mode, my Oreo device doesn't have this magisk module install so I can't help you, sorry...