any fixes to these bugs on CM7 (1.3)???? - Thunderbolt Q&A, Help & Troubleshooting

1. 4g handoffs still dont work. (wiped data and reset apn)
2. after being somewhere with no signal i get 1x for a long time
3. making a phone call force closes the dsp equalizer
4. auto brightness not working
anyone else still experiencing any of these? is there a fix i dont know about. a zip, a kernel?
thanks in advance

I upgraded from 1.2 without wiping and I don't have any of those problems.
The only problems I have are some wake lock issues. The weather channel app and Android System both give me wake lock. Granted they did this on 1.2 as well, and it also seems to happen on any AOSP ROM I've tried, so it isn't just CM.

agreed. Not seeing any of these problems. Sounds like you may not have wiped when flashing so do that and try again.

Related

[Q] Misc. Atrix Problems

Ever since yesterday, I have been having problems with my Atrix. Yesterday, I was on CM7, but I switched over to beta 0.6.9.1 CM9 earlier today. I've had one problem that was started yesterday with CM7, and continued into CM7. It's my biggest issue:
My Wi-Fi does not work. Everytime I turn on the Wi-Fi to scan for networks, the subtext in Settings reads "Error". This is usually followed by the phone rebooting itself. This happened in both CM9 and CM7. I tried looking up this problem and didn't seem to find any similar cases. I think it's a faulty Wi-Fi radio, but I'm not entirely sure.
Everything else is problems with CM9. I've found answers on some, but I'll post them in case my information is incorrect/outdated:
1. Certain apps built in to the ROM crash frequently. This includes the Music app, Camera app, and Settings (not as frequently). The Camera app, from what I've read, is crashing for a lot of different people, so I'm not concerned about it. The Music app confuses me though, since it's only on certain albums that it crashes. Sometimes it does, sometimes it doesn't. But the album to the crashing of the app is always consistent.
2. I had installed the fingerprint-enabler.zip in CWM when I first installed CM9 and gapps, but when I go into the settings for sensor navigation, it tells me com.authentec.TrueSuiteMoble has stopped. Perhaps I either isntalled it wrong (I installed it as a .zip, just like CM9 and gapps) or it was a faulty zip, or outdated.
3. The volume up on the rocker does not work. When searching the Internet for CM9 files, I saw a .zip for a volume fix. I don't know if this is it, but I'm fairly certain it won't help, considering the volume up didn't work when I was in CWM either. If it's the rocker itself, which it most likely is, ignore this.
I'm pretty sure this is all my problems thus far. I'll update with fixes I find, or, hopefully not, more problems. Thank you all in advanced!
LightSwitchTTM said:
Ever since yesterday, I have been having problems with my Atrix. Yesterday, I was on CM7, but I switched over to beta 0.6.9.1 CM9 earlier today. I've had one problem that was started yesterday with CM7, and continued into CM7. It's my biggest issue:
My Wi-Fi does not work. Everytime I turn on the Wi-Fi to scan for networks, the subtext in Settings reads "Error". This is usually followed by the phone rebooting itself. This happened in both CM9 and CM7. I tried looking up this problem and didn't seem to find any similar cases. I think it's a faulty Wi-Fi radio, but I'm not entirely sure.
Everything else is problems with CM9. I've found answers on some, but I'll post them in case my information is incorrect/outdated:
1. Certain apps built in to the ROM crash frequently. This includes the Music app, Camera app, and Settings (not as frequently). The Camera app, from what I've read, is crashing for a lot of different people, so I'm not concerned about it. The Music app confuses me though, since it's only on certain albums that it crashes. Sometimes it does, sometimes it doesn't. But the album to the crashing of the app is always consistent.
2. I had installed the fingerprint-enabler.zip in CWM when I first installed CM9 and gapps, but when I go into the settings for sensor navigation, it tells me com.authentec.TrueSuiteMoble has stopped. Perhaps I either isntalled it wrong (I installed it as a .zip, just like CM9 and gapps) or it was a faulty zip, or outdated.
3. The volume up on the rocker does not work. When searching the Internet for CM9 files, I saw a .zip for a volume fix. I don't know if this is it, but I'm fairly certain it won't help, considering the volume up didn't work when I was in CWM either. If it's the rocker itself, which it most likely is, ignore this.
I'm pretty sure this is all my problems thus far. I'll update with fixes I find, or, hopefully not, more problems. Thank you all in advanced!
Click to expand...
Click to collapse
About your wifi. Is your Bluetooth working... if not then the broadcom chip is busted.
2. I think in they latest version you don't have to install the zip to make the sensor navigation to work.
Sent from my MB860 running Jokersax's CM9

[Q] Notification Pull Down Doesn't Work on Lock Screen

I was running AOKP for over a month and the notification pull down would work while on the lock screen with no problems at all. One day, it just stopped working and I have no idea why. I of course wiped the Dalvik cache and did a full reinstall and it still didn't work. I even switched over to Serendipity 9 and it also doesn't work on that ROM either. I've used the CM9 kernal and Fluxxi and it doesn't work on either. The weird thing is that if I restart my phone, the notification pull down will work ONCE after rebooting then stop working for all attempts after that. If it helps, I do not have my SIM card installed. I don't have any security set for my lockscreen. It's at the default slide unlock. Any ideas?
shadowcman said:
I was running AOKP for over a month and the notification pull down would work while on the lock screen with no problems at all. One day, it just stopped working and I have no idea why. I of course wiped the Dalvik cache and did a full reinstall and it still didn't work. I even switched over to Serendipity 9 and it also doesn't work on that ROM either. I've used the CM9 kernal and Fluxxi and it doesn't work on either. The weird thing is that if I restart my phone, the notification pull down will work ONCE after rebooting then stop working for all attempts after that. If it helps, I do not have my SIM card installed. I don't have any security set for my lockscreen. It's at the default slide unlock. Any ideas?
Click to expand...
Click to collapse
Im not on latest, on 6-7 still, and its working.
but it could be a fix from AOKP themselves, it could be a bug, tho I see it as a nice feature.
Or It could just be that you need to full wipe. Funny how you started a thread before doing that.
MotoMudder77 said:
Im not on latest, on 6-7 still, and its working.
but it could be a fix from AOKP themselves, it could be a bug, tho I see it as a nice feature.
Or It could just be that you need to full wipe. Funny how you started a thread before doing that.
Click to expand...
Click to collapse
I did several full wipes and reinstalls of AOKP and Serendipity. I believe I solved the issue: The SIM card needs to be in the phone during the first boot and can be taken out after that. So far it's been working for an hour without any problems.

[Q] Longhorn 2.9.3 Random Rebooting

Hi
I've been using Longhorn 2.9.3 from a fresh install and really love the rom.
Everything works great except where lately I've been having issues where the phone just reboots out of the blue.
This has happened on average 10-15 times this past week.
Can anyone help?
Cheers
Nico
niconedz said:
Hi
I've been using Longhorn 2.9.3 from a fresh install and really love the rom.
Everything works great except where lately I've been having issues where the phone just reboots out of the blue.
This has happened on average 10-15 times this past week.
Can anyone help?
Cheers
Nico
Click to expand...
Click to collapse
try to check which application that causing this.. a fresh install does not happen at all of random reboots.. not even once...
you could try to wipe cache, wipe dalvik cache and lastly wipe data .. do dell factory reset too if case is worsen...
deysmacro said:
try to check which application that causing this.. a fresh install does not happen at all of random reboots.. not even once...
you could try to wipe cache, wipe dalvik cache and lastly wipe data .. do dell factory reset too if case is worsen...
Click to expand...
Click to collapse
Cheers mate,
I haven't installed any apps since about a week before this started.
Do you know of any apps that may cause this? as removing them one at a time and waiting for it to happen again is going to take ages.
It seems to have gotten better this last week.. only 1 or 2 reboots.
Further Indications......
Hi folks,
I'm having the same issues with Longhorn 2.9.3 Final, but it only seems to randomly reboot when the the phone is left idle and the screen goes off, So my first attempt was to disable the lock screen - no effect, then I tried certain background apps, such as Go Launcher EX, followed now by Facebook, and a local taxi app, nothing as yet.
I have tried wiping various caches, but it made no difference unfortunately.
If anybody know anything relevant to this issue don't hesitate but to share it with us, please.
I really am very fond of this custom ROM, and don't want to abandon it.
Thanks in advance
Ben.
Found the problem on mine
fats19760 said:
Hi folks,
I'm having the same issues with Longhorn 2.9.3 Final, but it only seems to randomly reboot when the the phone is left idle and the screen goes off, So my first attempt was to disable the lock screen - no effect, then I tried certain background apps, such as Go Launcher EX, followed now by Facebook, and a local taxi app, nothing as yet.
I have tried wiping various caches, but it made no difference unfortunately.
If anybody know anything relevant to this issue don't hesitate but to share it with us, please.
I really am very fond of this custom ROM, and don't want to abandon it.
Thanks in advance
Ben.
Click to expand...
Click to collapse
After going through clearing caches, replacing internal and external SD cards, cleaning the back door blah blah blah I found the following.
When I ran the Maps app, it asked if I wanted to use wifi for location to which I responded yes... mistake! If the wifi location option is checked, the phone seems try to use wifi when it is asleep and ends up rebooting.
I found this by turning the wifi off which made the phone sleep without re-booting and then by turning wifi on and disabling wifi location in Maps.
A long, involved process but now my Streak is rock steady and I don't have to think about reverting to a stock ROM... hooray
.
.
.
Stability update...
Uptime 600h
Previously would reboot twice a day or more
Very happy with the ROM now
I am having this problem also
I have a reboot problem as described above. The problem is that when I disable the use wireless networks option it does not disable. That is I leave the screen. Go back to it and it is still checked.
Please Help.
Web....
what kernel and baseband have you using?
Same here...
I 've been faceing the same problem exactly... latest longhorn randomly reboots, usually first the 3 buttons flash a few times before the reboot...
I downloaded and installed the 407 baseband and radio, then longhorn, did all wipe and dell reset, still the same ...
I've read this forum a few times, still though, would anyone be so kind to direct me towards a link here, where I could in fact revert the dell to an official rom version, before trying anything else?
Tnx in advance
:cyclops:
[BUG]: Wifi Random Reboot Issue Confirm
SteveB56 said:
After going through clearing caches, replacing internal and external SD cards, cleaning the back door blah blah blah I found the following.
When I ran the Maps app, it asked if I wanted to use wifi for location to which I responded yes... mistake! If the wifi location option is checked, the phone seems try to use wifi when it is asleep and ends up rebooting.
I found this by turning the wifi off which made the phone sleep without re-booting and then by turning wifi on and disabling wifi location in Maps.
A long, involved process but now my Streak is rock steady and I don't have to think about reverting to a stock ROM... hooray
Click to expand...
Click to collapse
I ended up disabling the Wifi location and my Streak works great. I had some app installed that was messing with me disabling/changing the wifi location settings. Sometimes I could not even disable wifi.
I remove a ton of apps. Was able to disable location via wifi and my phone has been working great ever since.
I can confirm that I had a problem with this and disabling it fixed it.

GPS won't lock even after many attempts to fix

Hello XDA Developers,
I come to you all with a problem. I am having trouble with my GPS; it won't lock. I have tried these things:
Using GPS Status and other GPS fixers
Doing a factory reset using Mr. Cook's ROM Wipe Script
Clearing data and cache of my GPS apps (Waze and Google Maps)
Idk what else to do. Every time I use the GPS apps to pinpoint my location, after a navigation session, it goes back to getting stuck on "waiting for GPS".
Any help is appreciated.
What firmware are you running? Have you had the same problem with other firmware?
creepyncrawly said:
What firmware are you running? Have you had the same problem with other firmware?
Click to expand...
Click to collapse
I am currently on an unofficial nightly of CM11 ported by RenderBroken. When I was experiencing those problems, I was on Omni ROM for Android 4.4. I was on ShoStock3 before the Omni ROM, and it was the same problem.
I don't run anything AOSP based so I can't speak about how those might affect GPS, but since you have the problem across various roms, and even on SHOstock3, I wonder if the phone has a problem with the GPS hardware? Have you ever had good GPS at any point with that phone? If so what were you running at the time.
I've had some GPS issues in the past but am not having any issues currently. I've been on SHOstock3 for a long time. My issues were on an earlier version of SHOstock, I don't remember which one exactly. When my GPS would fail to lock, just as you described, a reboot would fix the issue and result in a fast lock, but then the next time I would try to use GPS, I would have to reboot again. It was very annoying. Someone said that to format cache, wipe dalvik cache and fix permissions would fix the problem, so I tried that, and yes I would then get a lock in 5 - 10 seconds and it would stay good for a few weeks until I would have to do it again. I never experimented to see which of those three things helped, or if you had to do all three. That was back around June or July of this year.
As I recall, the next base change on SHOstock completely eliminated the issue.
creepyncrawly said:
I don't run anything AOSP based so I can't speak about how those might affect GPS, but since you have the problem across various roms, and even on SHOstock3, I wonder if the phone has a problem with the GPS hardware? Have you ever had good GPS at any point with that phone? If so what were you running at the time.
I've had some GPS issues in the past but am not having any issues currently. I've been on SHOstock3 for a long time. My issues were on an earlier version of SHOstock, I don't remember which one exactly. When my GPS would fail to lock, just as you described, a reboot would fix the issue and result in a fast lock, but then the next time I would try to use GPS, I would have to reboot again. It was very annoying. Someone said that to format cache, wipe dalvik cache and fix permissions would fix the problem, so I tried that, and yes I would then get a lock in 5 - 10 seconds and it would stay good for a few weeks until I would have to do it again. I never experimented to see which of those three things helped, or if you had to do all three. That was back around June or July of this year.
As I recall, the next base change on SHOstock completely eliminated the issue.
Click to expand...
Click to collapse
I have had a lock before. When I used GPS Status, it would get a lock for a short while, but when I ran the navigation, it would get stuck at waiting for location again.

Bliss Mallow based on CM13

everyone who're fedup with Oxygen OS can try this new rom BlissMallow rom formerly known as Blisspop
works smooth & fine, you can use it as a daily driver
as usual LAF & FP not working as of now.
http://forum.xda-developers.com/oneplus-2/development/rom-blisspop-t3226519
Just flashed it yesterday, so far so good !
flashed it yesterday too, found it a little too buggy.. facebook app FC's, drop down menu FC's, gps was off, and alert slider doesn't work along with LAF & FP. Took crappy pic's. I'll stick with OOS with xposed modules for now. We aren't to far off from official 6.0 for OPT
Jr173 said:
flashed it yesterday too, found it a little too buggy.. facebook app FC's, drop down menu FC's, gps was off, and alert slider doesn't work along with LAF & FP. Took crappy pic's. I'll stick with OOS with xposed modules for now. We aren't to far off from official 6.0 for OPT
Click to expand...
Click to collapse
The rom is pretty stable, not a lot fc's for me and non at all at the dropdown menu.
Gps is worknig, camra is working and there is no diffrance in the pics from oos.
It's a good rom, and cloud be a daily use, even it's a bata.
I have two major issues with the latest rom :
1. rotation sensor not working.
2. proximity sensor not working.
clean flash 3 times , tried downloading the file two times to rule out bad download
also flashed it with/without Google apps , nothing helps so far
is anyone else facing those issues here or can someone please point me towards a solution?
thank you
moshikko said:
I have two major issues with the latest rom :
1. rotation sensor not working.
2. proximity sensor not working.
clean flash 3 times , tried downloading the file two times to rule out bad download
also flashed it with/without Google apps , nothing helps so far
is anyone else facing those issues here or can someone please point me towards a solution?
thank you
Click to expand...
Click to collapse
Do an advanced wipe. And wipe everything expect your SD card.
Flash Blissmallow and any gapps ( I use slim gapps) and then wipe dalvik and cache
AndroidBeginNinja said:
Do an advanced wipe. And wipe everything expect your SD card.
Flash Blissmallow and any gapps ( I use slim gapps) and then wipe dalvik and cache
Click to expand...
Click to collapse
giving it a try right now
edit: not working .
tried it twice and still no go, very weird
when trying any other cm13 based rom sensors works great, I think it has something to do with mahdi's device tree.
Just tried this today. So far:
1) Sometimes FC in settings when switching which SIM card to use for data
2) Waking up device by power button wakes the screen, but it's black and I can't input the PIN to unlock the device. Basically I have to force reset it. This happens every now and then.
3) Priority toggle: If you toggle too quick, the phone doesn't understand and misses it. I.e. you might be in "do not disturb" mode, but the phone didn't catch on so it thinks you're in "priority only", letting things through.
4) Camera seems to work OK, autofocus not an issue so far
5) No idea about battery life
6) Obviously no finger print scanner
I'm going to test it as a daily from now on, let's see how this goes. (coming from OxygenOS)
moshikko said:
giving it a try right now
edit: not working .
tried it twice and still no go, very weird
when trying any other cm13 based rom sensors works great, I think it has something to do with mahdi's device tree.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591
Mohit31 said:
Try this
http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591
Click to expand...
Click to collapse
:good: :good: :good: :good:
Will do right now , thnx
edit: THANK you very much
finally it works, tried many things but this is the only solution that works
you are my new hero!!!!
moshikko said:
I have two major issues with the latest rom :
1. rotation sensor not working.
2. proximity sensor not working.
clean flash 3 times , tried downloading the file two times to rule out bad download
also flashed it with/without Google apps , nothing helps so far
is anyone else facing those issues here or can someone please point me towards a solution?
thank you
Click to expand...
Click to collapse
I have exactly the same issue and have flashed stock using the recovery tool, and factory reset and refashed oxyslim and I still have no proximity snesor and not rotation at all.
I cant find a modem thread for the a2003 op2, some say they modem maybe wrong.
Two posts above there is a solution that works, you need to wipe persist and flash the one in the link above
Just follow the instructions and youre all set
Good luck
How can I check if LAF is working? How can it be enabled? Is a special camera app recommended?
Deacon-Frost said:
How can I check if LAF is working? How can it be enabled? Is a special camera app recommended?
Click to expand...
Click to collapse
if you're on late version that has LAF working just look at the camera and you'll see a red dot underneath it.
I use the camera that comes with the rom and its great
Great ROM
Hi All
Like this rom. This is the ONLY rom that has been stable enough to tempt me away from oos.
I did a clean flash for the initial install, then dirty flash with the updates. Current Running the 20160224-1305 build
Very few issues. Good enough for my daily driver. The only bugs I've found so far..
Lock Screen Notifications. Double Tap to launch doesn't work. Screen just shuts off again.
Bluetooth Pulldown. Pressing the "x" next to a connected device should disconnect. But actually does nothing.
Battery life seems a little poorer
TouchScreen sensitivity issues. Occasionally touchscreen goes a bit nuts and it becomes difficult to type with unintended keys being hit, and becomes difficult to access pulldown menu. Have to reboot to solve.
Minor Wifi issues. I'm getting disconnection issues when I connect to specific public wifi points which didn't occur under oos.
I had an issue with SnapChat being unable to access the camera but I solved this. If you restore from titaniumbackup the camera connect error occurs. If you then wipe cache/data for the SnapChat app and log back in it works fine.
djmarkm said:
Hi All
Like this rom. This is the ONLY rom that has been stable enough to tempt me away from oos.
I did a clean flash for the initial install, then dirty flash with the updates. Current Running the 20160224-1305 build
Very few issues. Good enough for my daily driver. The only bugs I've found so far..
Lock Screen Notifications. Double Tap to launch doesn't work. Screen just shuts off again.
Bluetooth Pulldown. Pressing the "x" next to a connected device should disconnect. But actually does nothing.
Battery life seems a little poorer
TouchScreen sensitivity issues. Occasionally touchscreen goes a bit nuts and it becomes difficult to type with unintended keys being hit, and becomes difficult to access pulldown menu. Have to reboot to solve.
Minor Wifi issues. I'm getting disconnection issues when I connect to specific public wifi points which didn't occur under oos.
I had an issue with SnapChat being unable to access the camera but I solved this. If you restore from titaniumbackup the camera connect error occurs. If you then wipe cache/data for the SnapChat app and log back in it works fine.
Click to expand...
Click to collapse
1. You have to 'disable double tap screen on lock screen to lock to sleep' on the settings/bliss settings/lock screen.
Cant help with the other issues though!
djmarkm said:
Hi All
Like this rom. This is the ONLY rom that has been stable enough to tempt me away from oos.
I did a clean flash for the initial install, then dirty flash with the updates. Current Running the 20160224-1305 build
Very few issues. Good enough for my daily driver. The only bugs I've found so far..
Lock Screen Notifications. Double Tap to launch doesn't work. Screen just shuts off again.
Bluetooth Pulldown. Pressing the "x" next to a connected device should disconnect. But actually does nothing.
Battery life seems a little poorer
TouchScreen sensitivity issues. Occasionally touchscreen goes a bit nuts and it becomes difficult to type with unintended keys being hit, and becomes difficult to access pulldown menu. Have to reboot to solve.
Minor Wifi issues. I'm getting disconnection issues when I connect to specific public wifi points which didn't occur under oos.
I had an issue with SnapChat being unable to access the camera but I solved this. If you restore from titaniumbackup the camera connect error occurs. If you then wipe cache/data for the SnapChat app and log back in it works fine.
Click to expand...
Click to collapse
1. Try not double tap that fast on the notification.
Aduck79 said:
1. Try not double tap that fast on the notification.
Click to expand...
Click to collapse
Thanks., Tofuboi01 had the right solution. It was a setting in Bliss Settings->Lockscreen

Categories

Resources