I have been using epinter's CM10.1 for Atrix 4g and following the Atrix 4g CM10.1 developer discussions. I am trying to get the camera flash to work. krystianp posted that one should extract from CM9, the files tcmd and tcmdhelp and put in /system/bin. But I cannot find a CM9 for the Atrix 4g (olympus) that has these files. Does anyone know where to find them? (Would have posted to the CM10.1 thread but don't have permission to do so.)
Search fo his cm9. It should have the libs you are looking for. Also, z's one shot cm10.1 might have them as well
Hit the damn thanks button instead!
Enviado desde mi MB860
Thanks
andresrivas said:
Search fo his cm9. It should have the libs you are looking for. Also, z's one shot cm10.1 might have them as well
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
Thanks... Downloading a CM9 from krystianp now. I was thinking of trying to get from z's one shot if that didn't work. (And yes I did hit the thanks button ). Now on to see if putting these files in /system/bin will actually get the flash to work. The only post I could find from someone who tried it suggests "no".
The problem I've been having is the flash not flashing at all when the "shutter" button is pressed. Instead the phone light comes on when I press the "focus" button and goes off when released (unless I've selected "no flash"). Seems like for other people the flash works but timing is off.
rhcohen said:
Thanks... Downloading a CM9 from krystianp now. I was thinking of trying to get from z's one shot if that didn't work. (And yes I did hit the thanks button ). Now on to see if putting these files in /system/bin will actually get the flash to work. The only post I could find from someone who tried it suggests "no".
The problem I've been having is the flash not flashing at all when the "shutter" button is pressed. Instead the phone light comes on when I press the "focus" button and goes off when released (unless I've selected "no flash"). Seems like for other people the flash works but timing is off.
Click to expand...
Click to collapse
I placed those files but flash is still not working, maybe you have better luck :fingers-crossed:
reply
Feche said:
I placed those files but flash is still not working, maybe you have better luck :fingers-crossed:
Click to expand...
Click to collapse
No, no better luck here. Copied files to /system/bin, changed permissions to 755, verified owned by root like other files in the directory, rebooted. Same behavior as before.
Did you try Krystianp's 12/31 kernel, which apparently has flash working for some? I downloaded it but haven't flashed it yet out of concern for the bad battery drain noted by someone.
rhcohen said:
No, no better luck here. Copied files to /system/bin, changed permissions to 755, verified owned by root like other files in the directory, rebooted. Same behavior as before.
Did you try Krystianp's 12/31 kernel, which apparently has flash working for some? I downloaded it but haven't flashed it yet out of concern for the bad battery drain noted by someone.
Click to expand...
Click to collapse
I currently have it installed, the flash with stock camera app doesn't work, but with CameraMX flash works fine. :good:
reply
Feche said:
I currently have it installed, the flash with stock camera app doesn't work, but with CameraMX flash works fine. :good:
Click to expand...
Click to collapse
For what it is worth, I just installed the 12/31 kernel and the flash with stock camera app now DOES work for me*, and the timing even seems to be OK. So someone ought to be interested in understanding the difference between your configuration and mine. (If anyone is actually following this, my sequence, executed over the past week or so, was a wipe/clean install of epinter's 12/11 CM10.1 rom, followed by his latest gapps, followed by a second flash of the 12/11 rom. Then this morning putting the tcmd and tcmdhelp files in /system/bin, with appropriate permisssions; and then finally flashing krystianp's 12/31 kernel.) Too soon to comment on battery life.
I think this kernel is supposed to be logging network disconnects (which I also seem to experience, about one a day, requires reboot to reconnect). Do you know where we find the resultant logs, and how (lacking permissions to post at the developers' site) we are supposed to deliver them to krystianp? I notice that, in response to a submitted log file, krystianp made a post about restarting the radio from a terminal, which didn't actually achieve a re-connection for the one person who tried it.
* small update: the flash works with stock app, but only if I do a spot ("touch") focus first. Small price to pay!
Great to know its working! As fir that "thanks" thing, it's my signature from tapatalk, nothing personal
As for the logs, on either cm9 or cm10 forum krystianp gave instructions on how to get those logs. One is dmesg and the other logcat, but can't remember exact commands
Hit the damn thanks button instead!
Enviado desde mi MB860
reply
andresrivas said:
Great to know its working! As fir that "thanks" thing, it's my signature from tapatalk, nothing personal
As for the logs, on either cm9 or cm10 forum krystianp gave instructions on how to get those logs. One is dmesg and the other logcat, but can't remember exact commands
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
Thanks --- so I found the relevant krystianp post on the logs:
http://forum.xda-developers.com/showthread.php?p=48954198&highlight=dmesg#post48954198
Specifically,
"To get kernel log just do (as root):
dmesg>/sdcard/kernel.log
And for radio log do:
logcat -b radio >/sdcard/radio.log
(Logcat works continuously so you might have to use ctrl+c to cancel it) "
Question is, what do I do with these logs? I could attach them to a reply at the developer forum if I had permission to reply....
Presumably I don't want to keep running this kernel with debugging turned on forever.
You can attach they here and nention krystianp so he get notified
Hit the damn thanks button instead!
Enviado desde mi MB860
reply
andresrivas said:
You can attach they here and nention krystianp so he get notified
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
Thanks, I will wait a couple of days so there is some accumulated info in the logs and do that. So far, no drops and one spontaneous reboot.
reply, to forward to krystianp
andresrivas said:
You can attach they here and nention krystianp so he get notified
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
OK, attached are kernel.log and radio.log (combined into the file atrixlogs.tar). Hopefully someone notifies krystianp.
Here is what they represent: I installed krystianp's kernel two days ago. Since then I have had two spontaneous reboots, and two more reboots that I initiated because in the first case the radio died; in the second case the radio didn't die (still had bars) but there was no data connection. In both cases rebooting restored full functionality.
Note in the case where the radio died, I went to no bars and stayed there; then when I tried turning airplane mode on and off, the network status symbol in the status bar disappeared (no triangle at all, rather than having an empty triangle).
Krystianp had suggested trying to stop/restart the radio from a terminal when the network drops; I did not try this as I was away from my computer and so did not have access to the instructions for the terminal command.
I hope these logs are of help.
rhcohen said:
OK, attached are kernel.log and radio.log (combined into the file atrixlogs.tar). Hopefully someone notifies krystianp.
Here is what they represent: I installed krystianp's kernel two days ago. Since then I have had two spontaneous reboots, and two more reboots that I initiated because in the first case the radio died; in the second case the radio didn't die (still had bars) but there was no data connection. In both cases rebooting restored full functionality.
Note in the case where the radio died, I went to no bars and stayed there; then when I tried turning airplane mode on and off, the network status symbol in the status bar disappeared (no triangle at all, rather than having an empty triangle).
Krystianp had suggested trying to stop/restart the radio from a terminal when the network drops; I did not try this as I was away from my computer and so did not have access to the instructions for the terminal command.
I hope these logs are of help.
Click to expand...
Click to collapse
have you tried turning radio on and off from testing tab from dialer *#*#4636#*#* then select phone info scroll down and there is a tab to turn radio off and on. saves time from a reboot.
You should have mention him by @krystianp . Not sure it will work from the phone
Hit the damn thanks button instead!
Enviado desde mi MB860
RE turning radio off and on
overboard1978 said:
have you tried turning radio on and off from testing tab from dialer *#*#4636#*#* then select phone info scroll down and there is a tab to turn radio off and on. saves time from a reboot.
Click to expand...
Click to collapse
No I haven't tried this. Does this do something different from krystianp's suggestion from Jan 2 at the 10.1 developer thread :
echo "shutdown" > /sys/class/radio/mdm6600/command
echo "powerup" > /sys/class/radio/mdm6600/command
which, per reply post from Feche (also Jan 2), succeeds in starting up the radio but not making a connection?
further update
rhcohen said:
No I haven't tried this. Does this do something different from krystianp's suggestion from Jan 2 at the 10.1 developer thread :
echo "shutdown" > /sys/class/radio/mdm6600/command
echo "powerup" > /sys/class/radio/mdm6600/command
which, per reply post from Feche (also Jan 2), succeeds in starting up the radio but not making a connection?
Click to expand...
Click to collapse
----------
OK I have a further update. Using the testing tab from the dialer gives me the option of turning the radio off; when I click it nothing changes -- in particular no option to turn the radio on.
When I try krystianp's echo "shutdown" and echo "powerup" commands, I get a system prompt back but no indication that anything has changed with the radio (though maybe it would be reflected in the radio logs). In any event, certainly no connection to the network.
With regard to including @krystianp in the mssage -- where am I supposed to include this (to get the log files to him)?
rhcohen said:
----------
With regard to including @krystianp in the mssage -- where am I supposed to include this (to get the log files to him)?
Click to expand...
Click to collapse
Doesn' t it appear as a link to his user profile? go there and select
Code:
send message -> send a private message to krystianp
.
I don't see a place to attach a file to the message, but you can link to this thread.
reply; and what is "uv"?
PolesApart said:
Doesn' t it appear as a link to his user profile? go there and select
Code:
send message -> send a private message to krystianp
.
I don't see a place to attach a file to the message, but you can link to this thread.
Click to expand...
Click to collapse
-------------
Thanks. Sending the logs may no longer be relevant; @krystianp posted a new kernel a day and a half ago. I flashed it yesterday, and so far, no radio drops. If I get any I will post another message with logs and also send a message to krystianp.
I notice in describing the new kernel he says he made changes to radio and UV. Can someone tell me what is UV? I tried a search in the 10.1 developer forum and a more general google search but find nothing useful (I suspect this use of "UV" does not mean "ultra-violet".)
As of today, he said the last kernel just adds more debug information. for me it didn't work for much time, with random reboots, probably caused by UV changes. UV is shorthand for "undervolting", an attempt to lower voltage to cpu (and perhaps some other devices) in order to preserve battery and generate less heat.
reply
PolesApart said:
As of today, he said the last kernel just adds more debug information. for me it didn't work for much time, with random reboots, probably caused by UV changes. UV is shorthand for "undervolting", an attempt to lower voltage to cpu (and perhaps some other devices) in order to preserve battery and generate less heat.
Click to expand...
Click to collapse
I saw today's post but didn't interpret it the same way. He had already said that this kernel, along with the one from 12/31, were for people with the disconnect errors (which I was getting), but when he posted the Jan 5 kernel he indicated there were changes to radio and UV; I thought today's notice was just reaffirming the purpose of both the 12/31 and 1/5 kernels.
The 12/31 kernel clearly did more than just turn on logging however, as it seems to have fixed the camera flash for many (including me).
And the 1/5 kernel seems to be working more stably for me -- 1 1/2 days now without a radio drop. Maybe just luck.
Related
Fixing mobile data (3g) after installing Cyanogenmod 7 (nightly)
Hello all. I'm writing this as a long-time lurker and custom ROM / kernel user, who has been helped along greatly by this forum.
I had a long-standing issue that I couldn't find any clarity on: my mobile data access didn't work after switching to custom Roms/Kernels from LG's original Froyo Rom.
After months of thinking it was just an odd bug, and something to live with (since I rarely use data), I decided to look a little deeper into the problem. I found it difficult to even find information on the problem - there's a lot of bad information, and a lot of hard-to-read information from friendly, but not perfectly fluent English speakers.
In short, I'm hoping that others who are struggling with this issue will find this post with some Googling, and won't have to be as confused as I was.
After doing the following, I have everything working perfectly and here's how I did it:
1) I knew that the right baseband (under About Phone, in Settings) had something to do with mobile connections, including 3g data authentication and transfer. I found that v10 (and older) basebands are considered the 'old' baseband, while v20 basebands are considered 'new' basebands.
2) Cyanogenmod often reports the baseband incorrectly, so finding out what baseband you're on is unreliable through the About Phone menu, if you're already on CM7.
3) There are some scary sounding techniques to update your baseband (one involves using a poorly documented program called 'LGMDP-v1.5.exe'). These techniques can apparently brick your phone, so I avoided them. I might be wrong on some of the details here, so let me know!
4) I instead obtained the latest baseband by simply letting the LG update software (in my case from LG.ca) update my phone to Android 2.3. I noticed that I now had baseband v20. My mobile data worked!
5) I then re-rooted the phone, using SuperOneClick.
6) Installed the latest CM7 nightly. Mobile data no longer worked
6.5) I should mention, I tried other ROM/Kernel combinations and ended up having crashes and hangs on boot - thankfully I could use 'adb reboot recovery' to get back to Clockwork Recovery, when even holding various keys on reboot to do this didn't work).
7) Installed the wonderful ta-gb 1.1 kernel (thanks to all of the devs who worked on this and others like it).
8) And lastly (and possibly most importantly) I came across this:
https://github.com/CyanogenMod/andr...gingerbread/prebuilt/common/etc/apns-conf.xml
It's a list of APN information, which corresponds to different carriers, and appears to be necessary for mobile data connections. My carrier (Koodo) was not listed here, and therefore appears to not be included in even the latest Cyanogenmod 7 (as of Feb 2012).
9) This led me to find this: http://code.google.com/p/cyanogenmod/wiki/APNlist
Which happened to include the APN information for my carrier that I needed to put in, under Mobile Networks > Access Point Names.
Inputting that information made my 3g connection start up instantly. I was able to check that things looked good by typing *#*#4636#*#* in the dialer, and looking under Phone Information.
Maybe you're a veteran CM7 user, and think this is obvious newb stuff, but I want to leave this thread here for any other users who were stuck as long as I was.
If you fixed this issue with a different method, please share what you did here. If you're a ROM/Kernel dev with more insight on anything that I covered, please comment.
Cheers.
Are you doing this on v20 baseband?
I also have trouble with data on nightly's. I know DJ posted on the cyanogen forum today, saying Adam got a new Sim (128k, the ones causing problems) for testing. There should be a fix soon, fixing this problem.
Sent from my LG-P500 using Tapatalk
Paulenski said:
Are you doing this on v20 baseband?
Click to expand...
Click to collapse
Yes. Is your carrier's APN information available to try all that I wrote above?
bambu85 said:
Fixing mobile data (3g) after installing Cyanogenmod 7 (nightly)
Hello all. I'm writing this as a long-time lurker and custom ROM / kernel user, who has been helped along greatly by this forum.
I had a long-standing issue that I couldn't find any clarity on: my mobile data access didn't work after switching to custom Roms/Kernels from LG's original Froyo Rom.
After months of thinking it was just an odd bug, and something to live with (since I rarely use data), I decided to look a little deeper into the problem. I found it difficult to even find information on the problem - there's a lot of bad information, and a lot of hard-to-read information from friendly, but not perfectly fluent English speakers.
In short, I'm hoping that others who are struggling with this issue will find this post with some Googling, and won't have to be as confused as I was.
After doing the following, I have everything working perfectly and here's how I did it:
1) I knew that the right baseband (under About Phone, in Settings) had something to do with mobile connections, including 3g data authentication and transfer. I found that v10 (and older) basebands are considered the 'old' baseband, while v20 basebands are considered 'new' basebands.
2) Cyanogenmod often reports the baseband incorrectly, so finding out what baseband you're on is unreliable through the About Phone menu, if you're already on CM7.
3) There are some scary sounding techniques to update your baseband (one involves using a poorly documented program called 'LGMDP-v1.5.exe'). These techniques can apparently brick your phone, so I avoided them. I might be wrong on some of the details here, so let me know!
4) I instead obtained the latest baseband by simply letting the LG update software (in my case from LG.ca) update my phone to Android 2.3. I noticed that I now had baseband v20. My mobile data worked!
5) I then re-rooted the phone, using SuperOneClick.
6) Installed the latest CM7 nightly. Mobile data no longer worked
6.5) I should mention, I tried other ROM/Kernel combinations and ended up having crashes and hangs on boot - thankfully I could use 'adb reboot recovery' to get back to Clockwork Recovery, when even holding various keys on reboot to do this didn't work).
7) Installed the wonderful ta-gb 1.1 kernel (thanks to all of the devs who worked on this and others like it).
8) And lastly (and possibly most importantly) I came across this:
https://github.com/CyanogenMod/andr...gingerbread/prebuilt/common/etc/apns-conf.xml
It's a list of APN information, which corresponds to different carriers, and appears to be necessary for mobile data connections. My carrier (Koodo) was not listed here, and therefore appears to not be included in even the latest Cyanogenmod 7 (as of Feb 2012).
9) This led me to find this: http://code.google.com/p/cyanogenmod/wiki/APNlist
Which happened to include the APN information for my carrier that I needed to put in, under Mobile Networks > Access Point Names.
Inputting that information made my 3g connection start up instantly. I was able to check that things looked good by typing *#*#4636#*#* in the dialer, and looking under Phone Information.
Maybe you're a veteran CM7 user, and think this is obvious newb stuff, but I want to leave this thread here for any other users who were stuck as long as I was.
If you fixed this issue with a different method, please share what you did here. If you're a ROM/Kernel dev with more insight on anything that I covered, please comment.
Cheers.
Click to expand...
Click to collapse
You should be able to get all your apn information from your carrier provider even if cyanogenmod doesnt have it.
Apn is nothing to do with being a veteran cm user or that, you used to always have to enter that kind of stuff in the old phones when you used g and 3g, in my case my carrier would sms me the settigs automatically, such as it still does for my nokia e63
deniso177 said:
You should be able to get all your apn information from your carrier provider even if cyanogenmod doesnt have it.
Apn is nothing to do with being a veteran cm user or that, you used to always have to enter that kind of stuff in the old phones when you used g and 3g, in my case my carrier would sms me the settigs automatically, such as it still does for my nokia e63
Click to expand...
Click to collapse
Good to know!
I have installed the nightlyfoure v3.8 and I am not getting 3g.I am getting edge connection. When I activate 3g it shows I have only gprs. I live in a place where 3g is available and I have v20g baseband.
Can you also tell us the procedure to edit/overwrite the original apns-config.xml if you did so? Thank you dude
geoemm said:
I have installed the nightlyfoure v3.8 and I am not getting 3g.I am getting edge connection. When I activate 3g it shows I have only gprs. I live in a place where 3g is available and I have v20g baseband.
Click to expand...
Click to collapse
Is your carrier listed in either of the links I posted about in step 8 or 9?
TheBlackHawkJr said:
Can you also tell us the procedure to edit/overwrite the original apns-config.xml if you did so? Thank you dude
Click to expand...
Click to collapse
I didn't edit 'apns-conf.xml', but I did find my carrier information in the link I posted in step 9) and typed it in manually into Access Point Names.
I suppose you could edit the apns-conf.xml file either in the source code, and compile CM7 yourself (time consuming). Or you could use the adb program that comes with the Android developer kit, and shell into the rooted phone (to see it, do: adb shell; cd /etc; ls). You could then probably edit it in place (might be risky), or pull the file, edit it, and then push it back with various adb commands that you can google
The code.google.com link I posted above might be the best way to request your APN details get added to the file in the next CM7 release.
bambu85 said:
I didn't edit 'apns-conf.xml', but I did find my carrier information in the link I posted in step 9) and typed it in manually into Access Point Names.
I suppose you could edit the apns-conf.xml file either in the source code, and compile CM7 yourself (time consuming). Or you could use the adb program that comes with the Android developer kit, and shell into the rooted phone (to see it, do: adb shell; cd /etc; ls). You could then probably edit it in place (might be risky), or pull the file, edit it, and then push it back with various adb commands that you can google
The code.google.com link I posted above might be the best way to request your APN details get added to the file in the next CM7 release.
Click to expand...
Click to collapse
Perfect, thanks but wait wait wait! You also faced the "not able to save APNs" problem? Also, I've just found out that my carrier (Vodafone IT) is listed among other carriers in APNlist you've linked... what's the deal?
(please be patient with me dude, I might seem really dumb but... I'm learning as I go )
My provider's APN is already added.
But sometimes, it fails to connect to DATA let it be 2G/3G.
Reboot solves it....
TheBlackHawkJr said:
Perfect, thanks but wait wait wait! You also faced the "not able to save APNs" problem? Also, I've just found out that my carrier (Vodafone IT) is listed among other carriers in APNlist you've linked... what's the deal?
(please be patient with me dude, I might seem really dumb but... I'm learning as I go )
Click to expand...
Click to collapse
Same issue.. pushed the updated apn-conf.xml to /etc but in my settings where the apns should show up do not. I also can not save the apn when i manually input it. (tmobile)
TheBlackHawkJr said:
Perfect, thanks but wait wait wait! You also faced the "not able to save APNs" problem?
Click to expand...
Click to collapse
I did not encounter this problem. Does anyone else have any input on this issue?
Thank you bambu85 I was stuck in the same situation for the longest time. I am using oxygen mod and your post helped me greatly. Data is now working! Sure the information might already be there but for us koodoers it's not so easy to decipher. Thanks
bambu85 said:
I did not encounter this problem. Does anyone else have any input on this issue?
Click to expand...
Click to collapse
Plus one when putting in the apn manually and press save it does not save it I only had this problem with new baseband ROMs
Sent from my HTC sensation 4g using Tapatalk
I have a Razr XT910 (GSM) with ICS 4.0.4, rooted.
Other changes besides apps are that I disabled Motorola Services (took too much battery) and I disabled the fast dormancy option in build.prop.
But the phone worked perfectly with all of the above for more than 4 months before it started making trouble.
Lately (3 months) I'm experiencing random reboots, sometimes when using the phone but mostly when not using it. If it is not plugged in then the phone would reboot; if it is plugged in it would boot to charge mode (large battery on display).
This happens every day or two in the last couple of months, with the longest run of the phone without reboot at 7 days (but second longest is 2.5 days).
I tried tracking my installed apps and remember when it all started, and I think it started after I installed Screebl (first lite then beta) and worsened when the Zooper Widget was installed, but I have long since uninstalled them and the problem remains.
I tried freezing several apps but couldn't find the culprit.
I tried getting information from the kernel panic logs, but couldn't find anything I could work with.
There are however several lines that show up in all the kernel panic logs:
] Internal error: Oops: 80000005 [#1] PREEMPT SMP
] Modules linked in: wl12xx_sdio vpnclient btwilink cifs wl12xx mac80211 cfg80211 compat evfwd [last unloaded: wl12xx_sdio]
] CPU: 0 Tainted: G W (3.0.8-g3c83d29 #1)
Click to expand...
Click to collapse
(with the Oops number different between logs)
and most logs have these or similar lines:
] Unable to handle kernel paging request at virtual address 400a48e4
] Unable to handle kernel NULL pointer dereference at virtual address 00000002
Click to expand...
Click to collapse
I can post some log here, but I'm not sure it would be useful as they are not very similar to each other other than the lines I mentioned above.
Is there anything else I should look into for debugging this issue?
It really is bothering...
Thanks!
Haggai said:
I have a Razr XT910 (GSM) with ICS 4.0.4, rooted.
Other changes besides apps are that I disabled Motorola Services (took too much battery) and I disabled the fast dormancy option in build.prop.
But the phone worked perfectly with all of the above for more than 4 months before it started making trouble.
Lately (3 months) I'm experiencing random reboots, sometimes when using the phone but mostly when not using it. If it is not plugged in then the phone would reboot; if it is plugged in it would boot to charge mode (large battery on display).
This happens every day or two in the last couple of months, with the longest run of the phone without reboot at 7 days (but second longest is 2.5 days).
I tried tracking my installed apps and remember when it all started, and I think it started after I installed Screebl (first lite then beta) and worsened when the Zooper Widget was installed, but I have long since uninstalled them and the problem remains.
I tried freezing several apps but couldn't find the culprit.
I tried getting information from the kernel panic logs, but couldn't find anything I could work with.
There are however several lines that show up in all the kernel panic logs:
(with the Oops number different between logs)
and most logs have these or similar lines:
I can post some log here, but I'm not sure it would be useful as they are not very similar to each other other than the lines I mentioned above.
Is there anything else I should look into for debugging this issue?
It really is bothering...
Thanks!
Click to expand...
Click to collapse
Do not make any kind of changes in system if ya not aware what ya gonna do or solution to save ya ass
Ok flash the ics fastboot using rsd lite because full wipe and factory restore ll not work .
Look out into the forum for appropriate fastboots
Edit : Why don't ya upgrade from ics to jb:thumbup:
Hit the thx button if i helped ya in anyways
anurag.dj2u said:
Do not make any kind of changes in system if ya not aware what ya gonna do or solution to save ya ass
Ok flash the ics fastboot using rsd lite because full wipe and factory restore ll not work .
Look out into the forum for appropriate fastboots
Edit : Why don't ya upgrade from ics to jb:thumbup:
Hit the thx button if i helped ya in anyways
Click to expand...
Click to collapse
Thanks, but I prefer to not flash anything right now but try to solve this issue with the current ROM if possible.
Haggai said:
Thanks, but I prefer to not flash anything right now but try to solve this issue with the current ROM if possible.
Click to expand...
Click to collapse
Then try to flash the same rom ya on by ss , bmm or bootstrap cwm . It will replace all ya incorrect files and build.prop
Hit the thx button if i helped ya in anyways
I think I've messed up again. Whenever I try to turn my wifi on, it gets stuck at the "turning on" status and then crashes after a couple of minutes. I have no error messages. It just closes after some time. The last thing I remember I did regarding wifi was to recover a stored password using Wifi Password Recovery App. Then this happened.
My phone is rooted and I have cwm. I've tried basic troubleshooting like power cycling, deleting wpa supplicant file (found in a post somewhere), tried turning wifi on using allsahare play, untweaking internet, but they just didn't work.
I'm ready to flash a stock ROM. But I'm just curious if you have any other suggestions before I do it because I've read some posts saying that reflashing didn't work as well.
Please help XDA Developers!
I guess no one has the solution yet. But I have discovered something, and I hope this would help. I found the file, init.qcom.wifi.sh, using root browser. I executed it and I got a script output stating an error. WI-FI chip ID is not specified. I have attached screenshots so you may as well check them out. Also, I noticed the files under date\misc\wifi are all 0.00 B which i think means they are empty. Please help experts.
theguynamedjake said:
I guess no one has the solution yet. But I have discovered something, and I hope this would help. I found the file, init.qcom.wifi.sh, using root browser. I executed it and I got a script output stating an error. WI-FI chip ID is not specified. I have attached screenshots so you may as well check them out. Also, I noticed the files under date\misc\wifi are all 0.00 B which i think means they are empty. Please help experts.
Click to expand...
Click to collapse
First of all you've got to flash any custom rom available in order to use wifi again !!!
Now regarding this issue u've just mentioned I'll try to investigate it further !!!
Thanks man. I flashed JASP ROM and its working fine now.
Didnt work
theguynamedjake said:
Thanks man. I flashed JASP ROM and its working fine now.
Click to expand...
Click to collapse
i tried all the above methods and even when on a full cleanrom install including the jasp rom but nothing has happened please help
Try reverting back to stock temporarely with Odin, this happens in my Note 3 and used to do the same in my S2, but only with the proximity sensor. The idea is the same, replace all settings to stock and flash whatever you want after (boot the stock though and test wifi just in case).
Why this works i have no idea, but it saved my arse loads of times. I can guess some internal devices might have flags configured which could be chip based rather then ROM/emmc related, but that is only my supposition.
On 2.9 version, mm 6.01, mokee rom, boost mode, experiencing constant 'sign in to network ' notifications for both cellular and WiFi networks while the network connection is ok.
Screen is attached.
I have the same issue. It even says 'no internet connection. But all works fine. Its bothering me though.
dimdimdim said:
On 2.9 version, mm 6.01, mokee rom, boost mode, experiencing constant 'sign in to network ' notifications for both cellular and WiFi networks while the network connection is ok.
Screen is attached.
Click to expand...
Click to collapse
And even more. I disabled all the settings in greenify one by one and then disabled the exposed module, then reboot, then deleted greenify via force stop/clear data/uninstall, then cleared all the caches and... Nothing happened. The notifications are still here.
The only difference I see the Internet speed is seemingly lower. So, I've run Google fiber test and found it says 'no servers responded '.
So, there is a problem.
Taking into account I see no other answers here, I will re-flash the rom keeping my data. Hope, the changes were made to system, so it should help.
I didnt have the issue by reflashing. It just suddenly started to happen. I gonna flash my ROM to the latest and hope it gets resolved. This is a dealbreaker for me. Hope it gets solved fast.
avsmartmobiles said:
I didnt have the issue by reflashing. It just suddenly started to happen. I gonna flash my ROM to the latest and hope it gets resolved. This is a dealbreaker for me. Hope it gets solved fast.
Click to expand...
Click to collapse
No, the problem occured not after a rom reflash, but just after greenify installation. I used system reflash in hopes to fix the issue. But it doesn't help. Seems, the changes are somewhere in data and I just don't know where.
dimdimdim said:
No, the problem occured not after a rom reflash, but just after greenify installation. I used system reflash in hopes to fix the issue. But it doesn't help. Seems, the changes are somewhere in data and I just don't know where.
Click to expand...
Click to collapse
Check this url: https://www.reddit.com/r/cyanogenmod/comments/4jo86y/cm13_wifi_connected_with_no_internet_sign_but/
I dont know how to do it. Do you know what we have to do?
avsmartmobiles said:
Check this url: https://www.reddit.com/r/cyanogenmod/comments/4jo86y/cm13_wifi_connected_with_no_internet_sign_but/
I dont know how to do it. Do you know what we have to do?
Click to expand...
Click to collapse
Okay, seems there is a way to fix it, close to what you've found: http://android.stackexchange.com/qu...ction-how-to-remove-exclamation-mark-on-wi-fi
The steps:
1. You should be rooted
2. Install any terminal emulator
3. Run it
4. Enter su
5. press enter
6. Enter
settings put global captive_portal_detection_enabled 0
7. Press enter
8. Reboot
I've check it and it works for me.
I'm not sure it's the best solution, but it works for this problem at least.
Damn im a noob i cant even post an Image here. I did the Steps u Said but I get : global captive_portal_detection_enabled 0
The program 'global' is not installed. Install it by executing:
apt install global
$
Van you print Screen it for me please ?
I cant seem to fix it. I get An error in the command. See printscreen. Please Help.
avsmartmobiles said:
I cant seem to fix it. I get An error in the command. See printscreen. Please Help.
Click to expand...
Click to collapse
You must enter first command
su
After that press
enter
And then copy the whole line of the command
settings put global captive_portal_detection_enabled 0
And then press
enter
again.
On the second screen you made it correct but forget to enter
su
before
dimdimdim said:
You must enter first command
su
After that press
enter
And then copy the whole line of the command
settings put global captive_portal_detection_enabled 0
And then press
enter
again.
On the second screen you made it correct but forget to enter
su
before
Click to expand...
Click to collapse
Thanks a lot men I think its fixed.
But now, as I supposed, the sign in to networks, which really need sign in (all public hotspots), doesn't throw out the notification.
I suppose it's still possible to sign via browser, but...
Worked for me
Thanks Bro! It worked for my mokee L 5.1 Rom on xiaomi Redmi 1s
dimdimdim said:
Okay, seems there is a way to fix it, close to what you've found: http://android.stackexchange.com/qu...ction-how-to-remove-exclamation-mark-on-wi-fi
The steps:
1. You should be rooted
2. Install any terminal emulator
3. Run it
4. Enter su
5. press enter
6. Enter
settings put global captive_portal_detection_enabled 0
7. Press enter
8. Reboot
I've check it and it works for me.
I'm not sure it's the best solution, but it works for this problem at least.
Click to expand...
Click to collapse
Thanks for this! I recently received the OTA update to 7.1.1 on my Nexus 6P. After the update, it kept pestering me to sign into my company's wifi portal page. When I clicked the alert, the page would load and then the entire window would close. If I tried again, the same thing would happen. The alert would immediately return and I couldn't figure out how to get rid of it. I'm not using Greenify so I hope this solution helps others who have a similar problem.
Thanks. It worked for me.
Hello,
I am having some battery problem.
I am currently on 10.3.12.0 (EU) build,( before that i was on 10.3.11.0 (EU)) which i flash directly via twrp, because i was not able to get the ota update, it always failed to install. Yes i followed the instructions for ota with magisk.
Since the 10.3.11.0 update, the battery get bad, i was getting around barely 10h sot, now it super bad- can not get even 3h SOT + there is massive heat issue 40° for no reason.
CPU frequencies are not loadable ( since the beginning ) in kernel auditor, gsm battery or any app. (see the screenshots)
It can be only monitored in real time, and it is showing for every scroll spikes to the maximum.
There is battery drain even in Stand by- 5-10 %.
What will you advise me.
Thanks in advance!
Some screenshots.
https://drive.google.com/folderview?id=16uFKuXgd1M5oR3F61j4pwTvsBzpnEUw3
Connect phone to the PC and:
- adb shell
- type in "su", allow root access on the phone
- type in "top"
- make screenshot/copy data, press ctrl+c
- type in "top -s 11"
- make screenshot/copy data, press ctrl+c
- post screenshot/data here
_mysiak_ said:
Connect phone to the PC and:
- adb shell
- type in "su", allow root access on the phone
- type in "top"
- make screenshot/copy data, press ctrl+c
- type in "top -s 11"
- make screenshot/copy data, press ctrl+c
- post screenshot/data here
Click to expand...
Click to collapse
Thank you for the fast answer!
I am using terminal emulator, because i am not able to use PC at the moment.
I will add later the proper data if needed.
Try to uninstall XDA navigation gestures app, reboot phone to reset stats and then check after 1-2 hours again with the same commands if the situation has been improved. Hopefully it's the only app triggering MagiskD (its CPU usage should be practically zero).
_mysiak_ said:
Try to uninstall XDA navigation gestures app, reboot phone to reset stats and then check after 1-2 hours again with the same commands if the situation has been improved. Hopefully it's the only app triggering MagiskD (its CPU usage should be practically zero).
Click to expand...
Click to collapse
Thank you !
I was just thinking about the same app, but i am using it since Sunday, and the problem is since the previous update( i was on the 10.3.10.0 only for 2 days)
But i am hoping this will solve everything!
Thank you again!
_mysiak_ said:
Try to uninstall XDA navigation gestures app, reboot phone to reset stats and then check after 1-2 hours again with the same commands if the situation has been improved. Hopefully it's the only app triggering MagiskD (its CPU usage should be practically zero).
Click to expand...
Click to collapse
Strange, the little cores are almost always maxed out 1804 Mhz.
But there is improvement since yesterday!
Now i am having around 1-1.2 %h drain.
By the way my old redmi 4 prime was way better, stand by drain- less than 0.5 %
alexandarpb said:
Strange, the little cores are almost always maxed out 1804 Mhz.
But there is improvement since yesterday!
Now i am having around 1-1.2 %h drain.
By the way my old redmi 4 prime was way better, stand by drain- less than 0.5 %
Click to expand...
Click to collapse
Could you upload the output from "top" commands somewhere else? Screenshots don't load via Tapatalk or web page of XDA, always giving me the error "can't load". Strangely the third picture loads fine everywhere
~1%/h doesn't sound so bad. My usual screen off usage is ~2%/h (wifi/data on, AOD enabled and often use of Whatsapp for web).On my wife's phone it's about 0.3%/h (wifi/data on, no AOD and only the "standard" apps).
_mysiak_ said:
Could you upload the output from "top" commands somewhere else? Screenshots don't load via Tapatalk or web page of XDA, always giving me the error "can't load". Strangely the third picture loads fine everywhere
~1%/h doesn't sound so bad. My usual screen off usage is ~2%/h (wifi/data on, AOD enabled and often use of Whatsapp for web).On my wife's phone it's about 0.3%/h (wifi/data on, no AOD and only the "standard" apps).
Click to expand...
Click to collapse
https://drive.google.com/file/d/19-wXJx249GfvroIe5eSDMPlHPRVvZyZL/view?usp=drivesdk - top
https://drive.google.com/file/d/18xJgNAl0Q7yi_gw-L7Z05jngqi1jaXLg/view?usp=drivesdk - top s11
I am not as worried about the 1%, as about the peaking processor, which is maybe leading to drain, and that not loading frequencies in every cpu tracking app( maybe kernel restrictions?)
alexandarpb said:
https://drive.google.com/file/d/19-wXJx249GfvroIe5eSDMPlHPRVvZyZL/view?usp=drivesdk - top
https://drive.google.com/file/d/18xJgNAl0Q7yi_gw-L7Z05jngqi1jaXLg/view?usp=drivesdk - top s11
I am not as worried about the 1%, as about the peaking processor, which is maybe leading to drain, and that not loading frequencies in every cpu tracking app( maybe kernel restrictions?)
Click to expand...
Click to collapse
Try switching to Facebook messenger lite at least for a while, the standard Messenger seems to be using an awful lot of CPU.
Which apps aren't working properly for you? I'll try them on my phone.
_mysiak_ said:
Try switching to Facebook messenger lite at least for a while, the standard Messenger seems to be using an awful lot of CPU.
Which apps aren't working properly for you? I'll try them on my phone.
Click to expand...
Click to collapse
Kernel adiutor on main screen showing " failed to load frequencies"
Gsam battery monitor cpu chart are not showing information about frequencies during the day.
About messenger, just one app force close did the work, now there is no cpu usage for that app.
Thank you for the guidance!
https://drive.google.com/folderview?id=16uFKuXgd1M5oR3F61j4pwTvsBzpnEUw3
alexandarpb said:
Kernel adiutor on main screen showing " failed to load frequencies"
Gsam battery monitor cpu chart are not showing information about frequencies during the day.
About messenger, just one app force close did the work, now there is no cpu usage for that app.
Thank you for the guidance!
https://drive.google.com/folderview?id=16uFKuXgd1M5oR3F61j4pwTvsBzpnEUw3
Click to expand...
Click to collapse
Kernel adiutor seems to be not working correctly, even for Mi A1 it required special version of the app. I guess it's not compatible with our device. Also it seems that it messed up the minimum CPU frequencies on my phone, try to uninstall the app and reboot, it might help "unstucking" your little cores.
About the CPU states, the issue is here:
testResults
file_not_exists:
/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
It's either stock Android Pie behavior or Xiaomi forgot to implement this feature.
Edit: someone at Xiaomi probably really forgot to enable this.. https://android.googlesource.com/ke...ease/Documentation/cpu-freq/cpufreq-stats.txt
I am now trying to use messenger lite, because really Facebook messenger is doing something wrong, there are plenty of posts about that app triggering the cpu, or draining battery.
Now i think the problem comes from installing the latest security patch, but i didn't do anything wrong, the update via twrp is not something unknown, and i had the same problems in the previous version.
alexandarpb said:
I am now trying to use messenger lite, because really Facebook messenger is doing something wrong, there are plenty of posts about that app triggering the cpu, or draining battery.
Now i think the problem comes from installing the latest security patch, but i didn't do anything wrong, the update via twrp is not something unknown, and i had the same problems in the previous version.
Click to expand...
Click to collapse
The only problem, well 2 problems, I see with updating via TWRP:
1. you can't update with stock OTA if you ever decide to
2. you can't really say what's in someone else's TWRP backup unless you inspect it. There is always a small chance that someone tampered the file system and included some "extras". I'm not saying that it happened, but with stock fastboot images there's zero chance of modification.
_mysiak_ said:
The only problem, well 2 problems, I see with updating via TWRP:
1. you can't update with stock OTA if you ever decide to
2. you can't really say what's in someone else's TWRP backup unless you inspect it. There is always a small chance that someone tampered the file system and included some "extras". I'm not saying that it happened, but with stock fastboot images there's zero chance of modification.
Click to expand...
Click to collapse
In fact maybe that is the case, after typing tune2fs i can see that mount count is FIVE, i think that is why Ota has a problem.
Maybe i should flash stock fastboot image ?
Sapper Morton said:
Indeed, it has been tampered with; you should flash system image again, and if you use TWRP, be sure to follow as _mysiak_ explained, don't allow remount; also, check for other partitions if you want to restore manually, or for it to be easier, just run flash_all_except_data_storage, and do the OTA installation afterwards, the latest Magisk patched files are up, in the [ROOT] thread, by Typhus.
Click to expand...
Click to collapse
Hi, sorry for the dumb question,
Is flash_all_except_data_storage, a MiFlash tool command?
Or it is for adb?
Also which version of Mi flash will recommend? I found some tutorials to work with it but either they differ in the instructions or are not applicable in the latest version i found
Like the last fastboot rom i found is tbz file, not zip, as mentioned in some instructions.
alexandarpb said:
Hi, sorry for the dumb question,
Is flash_all_except_data_storage, a MiFlash tool command?
Or it is for adb?
Also which version of Mi flash will recommend? I found some tutorials to work with it but either they differ in the instructions or are not applicable in the latest version i found
Like the last fastboot rom i found is tbz file, not zip, as mentioned in some instructions.
Click to expand...
Click to collapse
1. unpack fastboot rom (tgz - Tar Gnu Zip)
2. unpack unpacked file again (tar). Then you will see flashing script files and images.
3. connect phone via fastboot
4. switch to partition A
5. run flash_all_except_storage.bat
6. wait for it to finish, phone will reboot automatically
7. congrats, you have fully stock phone now
The latest version of MiFlash should work fine, though I never used it. In each case you must make sure that you are on partition A.
hi again,
i would like to flash latest fastboot rom,(flash_all_except_storage.bat) because maybe have done something and have several unusual problem- heating again+40°C, while riding my bike, that cause and battery drain(less than 5 sot), super slow booting, so is the procedure the same as before? is the android 10 script have something different?
thank you!
P.S
Did it like before. Not sure if that fix my previous problem