Hi all
I am running CyanogenMod 10.1 (cm-10.1-20130304-EXPERIMENTAL-evita-M2.zip) on my Telstra One XL, and have encountered an issue with music playback.
When I am using latest Winamp (or Apollo) in the foreground as music player, all is well and it can run for ages without issue, even when the screen lock comes on etc. However, when I try to do anything else e.g. feedly, web browser, etc., the music will play for a little while and then just cut out. If I switch back to Winamp, the current song flips back to something that was playing several songs ago - not the point where it paused.
I am suspecting that a background process might be killing the music service, but have no idea how to verify/prevent. My wife has an international One X with stock ROM and has no such playback issues when doing other things. In her case, she is streaming music, but I have issues even using local mp3s.
Is there a known issue with CM/JB in this area? Anything I can do to prevent the background music service from stopping/restarting etc?
I am S-Off/SuperCID, HBoot 2.14, TWRP 2.3.0.0 recovery, downgraded touchpanel.
Cheers,
Coffman
I'm pretty sure that has something to do with the memory leak bug found on those older builds of cm based ROMs. Try updating to one of the newer builds with the 3.4 kernel.
Sent from my Evita
timmaaa said:
I'm pretty sure that has something to do with the memory leak bug found on those older builds of cm based ROMs. Try updating to one of the newer builds with the 3.4 kernel.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the quick reply, timmaaa. Wasn't aware of a memory leak bug. I picked this version as it was the latest non-nightly CM release.
I'm enjoying this ROM so far (had it on for a week), but there are a few annoyances... this music one, device encryption doesn't work, and plugging the locked phone into usb prompts to mount storage, at which point the "sdcard" can be mounted and accessed. Bit of a security hole that one. Don't know if that's a CM issue, or JB though.
coffman said:
Thanks for the quick reply, timmaaa. Wasn't aware of a memory leak bug. I picked this version as it was the latest non-nightly CM release.
I'm enjoying this ROM so far (had it on for a week), but there are a few annoyances... this music one, device encryption doesn't work, and plugging the locked phone into usb prompts to mount storage, at which point the "sdcard" can be mounted and accessed. Bit of a security hole that one. Don't know if that's a CM issue, or JB though.
Click to expand...
Click to collapse
Unfortunately I don't think device encryption works on cm based ROMs, I vaguely remember something like that but I could be wrong.
I'm terms of the storage mounting during Lockscreen, I think the accessible lockscreen notification pull down feature was part of the JB update. I'm super careful with my phone and never leave it anywhere so that feature has never worried me.
Do you actually have a pattern lock setup on your phone? I've just tested with mine, and with pattern lock enabled I can't access the pull down, so mounting the storage world be impossible. I am on a Sense ROM though, so it may be different on cm, I can't remember.
Sent from my Evita
timmaaa said:
Unfortunately I don't think device encryption works on cm based ROMs, I vaguely remember something like that but I could be wrong.
I'm terms of the storage mounting during Lockscreen, I think the accessible lockscreen notification pull down feature was part of the JB update. I'm super careful with my phone and never leave it anywhere so that feature has never worried me.
Do you actually have a pattern lock setup on your phone? I've just tested with mine, and with pattern lock enabled I can't access the pull down, so mounting the storage world be impossible. I am on a Sense ROM though, so it may be different on cm, I can't remember.
Sent from my Evita
Click to expand...
Click to collapse
Regarding the device encryption, I queried that in another thread and exad said the same thing - he had a theory that S-OFF/unlocked bootloader affects device encryption somehow.
I use pin unlock. When locked, the status bar is visible, but the notification pulldown is not available. However, when USB is connected, the "USB mass storage" dialog is presented full-screen (android image with USB-arm) with the [Turn on USB storage] button. Pressing the button mounts storage and fully accessible while still locked. I am also super careful with my phone but still consider this a hole. It's as if the USB storage has priority over the lockscreen. I appreciate that this could be useful to some people, but it would be better as a configurable option.
As I mentioned in OP, my wife has a One X running stock Sense 4.1.1 and doesn't have this USB storage issue either.
Hmm ok well that's a shame about the storage mounting being available. I funny think it's a configurable option either. Bummer.
Sent from my Evita
Related
So now that we're into the 4th month without an update on CM7 nightly builds, I think its time for me to jump ship. However, I've been out of the game for a few months so I need some help seeing how to keep certain features and transition smoothly.
I'm thinking of going to Supreme Sense, and if I don't like the primary interface, I can still use ADW Launcher, so that should be fine.
However I need a few features and not sure if I can find them outside of CM7.
First and foremost, can I keep my ext partition intact or do I need to start it over? I'm using the S2E app which from what I remember is CM7 only. How do I smoothly transition over to Supreme Sense and configure an ext partition? It's currently ext3 but I'd like to go to a proper ext4 if possible.
Second, and also very important, and what I think will be the harder find, is this: CM7 has a feature under Tablet Tweaks to Disable lockscreen. This prevents the phone from locking entirely, even when a password is enabled. I have my work email on my phone which enforces a security policy requiring an 8-character alpha-numeric password. Without this feature, I have to enter this password every time I open my phone, which is incredibly annoying normally, and downright dangerous in the car. Any thoughts?
I'm also interested in suggestions on a good kernel to mate with Supreme Sense for OC/UV, or other Rom/kernel combination suggestions that are rock-solid stable.
Thanks for any help!
I'm pretty sure Supreme Sense has a apps 2 sd version, so you could easily utilize your sd-ext.
As far as the lock screen, I'm not sure. I haven't used supreme so i don't know if it has miktweaks, or if miktweaks even offers that option. You could try removing the lockscreen altogether, but again not sure if that would work
As far as Kernels, you have 2 options with Sense.. Either Dodge or x99's kernel. Both are solid and i think are more about personal preference. My suggestion would be to try both and see which works best for you.
Sent from my PG06100 using Tapatalk
Supreme Sense v9.1 has an A2SD version. Both Supreme Sense and MikShifted G have MikTweaks. Yes in MikTweaks you have an option to choose what Lockdscreen you use. The 3.0 LS , ICS LS , Stock Android LS. Also a BUNCH of other tweaks. If you want to keep your A2SD dodge's kernel is your choice. Because I believe x99's is not A2SD enabled.
TEAM MiK
Mik Roms Since 3/13/11
Thanks for the info guys, I definitely want a2sd, so I'll use 9.1 with Dodge's kernel. I'm guessing I won't be able to keep my apps on it though, and will need to format the partition clean. But hopefully titanium backup will be able to restore them back to the new ext partition.
The Miktweaks for lockscreen customization sound cool but what I need is that the phone does not lock when you turn off the screen. So when you turn it back on, you're right there in the launcher (or whatever other app was open when you turned off the screen). Yes, the likelyhood of accidental screen presses increases, but I modify the keypad.kl fileso that only the power button wakes the screen and its kinda hard to accidentally press on this phone. It works well for me.
However, I'm open to any other potential solutions to not have to enter a password each time i open the phone, when there is a security policy in place on the phone.
cmags said:
Thanks for the info guys, I definitely want a2sd, so I'll use 9.1 with Dodge's kernel. I'm guessing I won't be able to keep my apps on it though, and will need to format the partition clean. But hopefully titanium backup will be able to restore them back to the new ext partition.
The Miktweaks for lockscreen customization sound cool but what I need is that the phone does not lock when you turn off the screen. So when you turn it back on, you're right there in the launcher (or whatever other app was open when you turned off the screen). Yes, the likelyhood of accidental screen presses increases, but I modify the keypad.kl fileso that only the power button wakes the screen and its kinda hard to accidentally press on this phone. It works well for me.
However, I'm open to any other potential solutions to not have to enter a password each time i open the phone, when there is a security policy in place on the phone.
Click to expand...
Click to collapse
nolock in the market disables lock screen. May be along the lines of what your looking for.
I just tried this, and it doesn't seem to work in CM7, but that doesn't mean it won't work in SS. I thought I had tried it and it only disabled the lockscreen but left the password screen intact, but the help seems to indicate that you can't enter a password when its functioning, so maybe this will work. Thanks for the input, I'll be trying this out in the next day or two.
NoLock should work on Supreme Sense, or MikShifted G. If not you can always remove the Lockscreen apk.
Interesting idea, is the password entry also within the lockscreen apk? I wonder if that would trick the security policy, or if the policy would fail due to an inability to confirm that the password is enabled and up to snuff.
Not sure
works on ssv9.1 no clue about the securities though.
Btw in the first post it says no update on cm7 in 4 months. Not true? There's a couple of new cm7 roms out. Sure they aren't nightlies but they are from the latest changes in the source code with a few cherry-picks in them.
Are these CM7 or CM7-based roms? I was talking about CM7 directly from cyanogenmod.com, where the latest build was the nightly 255 version, from 11/16/11.
But I had been waiting since version 140 or so when i started playing around with CM7 for the GPS to work properly, and it always worked fine in stock Sense, so I figure I'll try a Sense rom for a while.
BTW, the SS9.1 a2sd version says to format a 512mb ext partition. I already have a 1gb partition - will it use it or complain about it not being the right size? The zip is downloading now.
cmags said:
Are these CM7 or CM7-based roms? I was talking about CM7 directly from cyanogenmod.com, where the latest build was the nightly 255 version, from 11/16/11.
But I had been waiting since version 140 or so when i started playing around with CM7 for the GPS to work properly, and it always worked fine in stock Sense, so I figure I'll try a Sense rom for a while.
BTW, the SS9.1 a2sd version says to format a 512mb ext partition. I already have a 1gb partition - will it use it or complain about it not being the right size? The zip is downloading now.
Click to expand...
Click to collapse
the 512 is more of just a minimum 1 gb will work fine
Sent from my PG06100 using Tapatalk
Thanks, I figured as much. Just sanity checking.
I have a 2GB partition. I don't usually have a lot of apps, but I only wanted to partition once. Not that I'll run out of space any time soon with a 32GB card .
TEAM MiK
Mik Roms Since 3/13/11
cmags said:
Are these CM7 or CM7-based roms? I was talking about CM7 directly from cyanogenmod.com, where the latest build was the nightly 255 version, from 11/16/11.
But I had been waiting since version 140 or so when i started playing around with CM7 for the GPS to work properly, and it always worked fine in stock Sense, so I figure I'll try a Sense rom for a while.
BTW, the SS9.1 a2sd version says to format a 512mb ext partition. I already have a 1gb partition - will it use it or complain about it not being the right size? The zip is downloading now.
Click to expand...
Click to collapse
Yes they are built from cm repo sources if that's what you mean. My versions of cm's roms include apps2ext already.
Xplod
Well if you want an Alternate rom from CM7 try Xplod , I can't post a link because I'm just a newb, so just Google, Xplod Shift Rom, then download it
Sorry if my post doesn't help at all..
So I've got ss 9.1 and dodge kernel installed, most apps back running, and my work email synced, but both Nolock and No Lock Screen fail to prevent the phone from locking. It seemed that when I restored nolock from titanium backup, it worked for a while but when the security policy was enabled it stopped. Anyone beat a security policy like this?
Also, I have root access (can change cpu speeds etc) but for some reason, I can't get rootexplorer to mount any system directories r/w...?
Sent from my Evo Shift running CM7 via the XDA app
Confirmed, if I disable the security policy (and remove access to my work mail), No Lock works fine to prevent the lockscreen, but once the policy is re-enabled, the lockscreen forces itself regardless of the No Lock setting.
I did find that I can change the password lock timeout to up to 30 mins, which is a bit better, but still not perfect. I can also set the phone not to sleep while plugged in, but then it charges a little slower.
Is there any way to figure out how CM7 does it? It seems like the *only* thing that worked...
Also, still confused on the r/w access. I discovered that I can go into miktweaks and mount /system as r/w and then open my rootexplorer to access files, but can't do it from rootexplorer directly...?
If I am playing music then every time I press something on my screen (such as an app or an app button - basically any time a press is detected and activates an action) the music will lag/stutter for about a second. Scrolling does not cause lag, nor does pressing hardware buttons (power, volume, home) or the menu/back buttons under the screen. For example, the music will stutter when I open the Gmail app and also when I "click" (press) on an email to open it.
I am currently rooted on the latest rootbox (3.9.1) although this problem has occurred with several other ROMs including AOKP and CM. Also occurs on all music playing apps I've tried (Google music, Android music, etc.). I believe the problem occurs with MP3 files but not FLAC files (although I have not tested this extensively).
I believe this is different from the buffer problem whose solution is to download a music player with the option to increase the buffer size. The problems I am having seem to be different. Any help would be greatly appreciated and thank you for your time.
timramos94 said:
If I am playing music then every time I press something on my screen (such as an app or an app button - basically any time a press is detected and activates an action) the music will lag/stutter for about a second. Scrolling does not cause lag, nor does pressing hardware buttons (power, volume, home) or the menu/back buttons under the screen. For example, the music will stutter when I open the Gmail app and also when I "click" (press) on an email to open it.
I am currently rooted on the latest rootbox (3.9.1) although this problem has occurred with several other ROMs including AOKP and CM. Also occurs on all music playing apps I've tried (Google music, Android music, etc.). I believe the problem occurs with MP3 files but not FLAC files (although I have not tested this extensively).
I believe this is different from the buffer problem whose solution is to download a music player with the option to increase the buffer size. The problems I am having seem to be different. Any help would be greatly appreciated and thank you for your time.
Click to expand...
Click to collapse
Does this happen with the stock rom? or TW based roms?
Watanuki-Kun said:
Does this happen with the stock rom? or TW based roms?
Click to expand...
Click to collapse
Never had this problem on stock. Only since rooting has this occurred.
timramos94 said:
If I am playing music then every time I press something on my screen (such as an app or an app button - basically any time a press is detected and activates an action) the music will lag/stutter for about a second. Scrolling does not cause lag, nor does pressing hardware buttons (power, volume, home) or the menu/back buttons under the screen. For example, the music will stutter when I open the Gmail app and also when I "click" (press) on an email to open it.
I am currently rooted on the latest rootbox (3.9.1) although this problem has occurred with several other ROMs including AOKP and CM. Also occurs on all music playing apps I've tried (Google music, Android music, etc.). I believe the problem occurs with MP3 files but not FLAC files (although I have not tested this extensively).
I believe this is different from the buffer problem whose solution is to download a music player with the option to increase the buffer size. The problems I am having seem to be different. Any help would be greatly appreciated and thank you for your time.
Click to expand...
Click to collapse
Ahhh that would actually make a lot of sense. An app I was making would make the glitch sound thing with .mp3 but not .wav
Sent from GS3 runnung CM10.1 and blacked out theme.
timramos94 said:
Never had this problem on stock. Only since rooting has this occurred.
Click to expand...
Click to collapse
My line of thinking was that since you did not have this problem on stock, it would be probably a AOSP/AOKP/CM Rom issue. I would of likely thought kernel, maybe your phone did not like a certain kernel version 3.0 vs 3.5 or kernel from a certain kernel developer or the scheduler/cpu governor combination. I am uncertain now since you said that only since rooting which I assume you mean you were on stock rom and you just rooted it instead of flashing a different rom with root already included.
Watanuki-Kun said:
My line of thinking was that since you did not have this problem on stock, it would be probably a AOSP/AOKP/CM Rom issue. I would of likely thought kernel, maybe your phone did not like a certain kernel version 3.0 vs 3.5 or kernel from a certain kernel developer or the scheduler/cpu governor combination. I am uncertain now since you said that only since rooting which I assume you mean you were on stock rom and you just rooted it instead of flashing a different rom with root already included.
Click to expand...
Click to collapse
I am currently on Rootbox. I flashed several other ROMS including AOKP and CM immediately after unlocking the bootloader and rooting, all which have had this problem. It is probably most definitely a ROM issue but I have found no other information on this specific problem. Would using a different kernel help considering flashing several other ROMS hasn't solved this issue? Not sure if they all used the same/similar kernels. I don't extensively understand the importance of kernels.
Still have yet to find a solution to this. Any help would be appreciated.
i saw in the deviant xone thread that it stops if you disable touch sounds and screen lock sound, it should fix the issue.
insanulous said:
i saw in the deviant xone thread that it stops if you disable touch sounds and screen lock sound, it should fix the issue.
Click to expand...
Click to collapse
disabling touch sounds and screen lock sound fixed the issue for me .... Thank you
My phone is rooted and I have Jelly 'beans' ROM installed. Everything was going well (been running for a week) until I installed ActiveNotifications (https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications). I'm not stuck on my lock screen and the touch screen does not respond to unlock it. There is also a hand icon in the status bar that I've never seen before. I can't (as far as I know) use adb to uninstall because the phone is not in USB debugging.
Any thoughts short of wiping and re-installing the ROM?
TIA
ffeingol said:
My phone is rooted and I have Jelly 'beans' ROM installed. Everything was going well (been running for a week) until I installed ActiveNotifications (https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications). I'm not stuck on my lock screen and the touch screen does not respond to unlock it. There is also a hand icon in the status bar that I've never seen before. I can't (as far as I know) use adb to uninstall because the phone is not in USB debugging.
Any thoughts short of wiping and re-installing the ROM?
TIA
Click to expand...
Click to collapse
Yeah, neat app huh? I did the same thing myself. I think to use it you have to have a PIN unlock. Anyway, if you can pull down your notification shade, go into settings and uninstall it. Also if you have no security set for your lock screen, try to call your phone or send a text, something that will immediately get you into the main UI, then uninstall it.
Power it off the press at the same time power>home>vol up and boot into recovery and reflash the rom..
Sent from the future via Tapatalk 4
ffeingol said:
My phone is rooted and I have Jelly 'beans' ROM installed. Everything was going well (been running for a week) until I installed ActiveNotifications (https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications). I'm not stuck on my lock screen and the touch screen does not respond to unlock it. There is also a hand icon in the status bar that I've never seen before. I can't (as far as I know) use adb to uninstall because the phone is not in USB debugging.
Any thoughts short of wiping and re-installing the ROM?
TIA
Click to expand...
Click to collapse
Maybe consider restoring from your most recent nandroid? I know that it's losing some progress, but you might be able to save yourself some time. Short of that, I think you'll need to re-flash your ROM, unfortunately.
I've been in situations like this one before, and that's the big reason why I've made it my standard operating procedure to maintain two backups: one for pre-flash and on stable post-flash for every new ROM. It's been helpful so far (in the extremely limited experience I have with custom software on my phone).
I'm going to wait just a bit to see if anyone else has some great suggestion, but I think I'll have to re-flash (after I finally got my home screen the way I want it). I do have PIN lock on. Can't pull the notifications down. With the ROM I'm using the AOSP lockscreen and I when you touch the circle to unlock none of the icons show.
Not a happy camper
ffeingol said:
I'm going to wait just a bit to see if anyone else has some great suggestion, but I think I'll have to re-flash (after I finally got my home screen the way I want it). I do have PIN lock on. Can't pull the notifications down. With the ROM I'm using the AOSP lockscreen and I when you touch the circle to unlock none of the icons show.
Not a happy camper
Click to expand...
Click to collapse
Try to hit the menu button while you're on the lockscreen, sometimes that'll bypass the lock screen.
Sent from my SCH-I535 using Tapatalk 2
After wiping and re-installing the ROM (several times) I think I may have found the culprit. My phone suddenly thinks that my 32 GB external SD card is bad and is stuck in a fsck. If I put the card out everything is happy. Time to backup the sdcard and reformat.
My phone learned a new trick last week: launch an app, and the screen turns dead black after the app's splash loading screen.
It doesn't happen with every app or every time certain apps are launched, but if it is going to happen, it is always just after an app loading screen and before the app itself would be displayed. It never happens on a system or preference screen, or in an app without a splash animation.
Button back-lighting, volume control, and haptic seem to remain active and respond as normal, but the app seems to be locked into the foreground with a black screen, and can't seem to do anything to stop it but reboot the phone via power button hold.
I'm running CM 12.1 nightlies on a Verizon S3. I've been updating the CM nightlies, well, nightly since last week in hopes a fix would be included in one of them, but I'm not sure this is a ROM issue. I've also wiped Dalvik/Cache several times, with and without a ROM update. I saw black screens on some phones were caused by theme window animations, so I've disabled these in CM, but hasn't made a difference.
Just a guess on my part, but if the nightlies do not fix this you may end up needing to do a clean flash. Hopefully you do not have to go as far as formatting /system.
dawgdoc said:
Just a guess on my part, but if the nightlies do not fix this you may end up needing to do a clean flash. Hopefully you do not have to go as far as formatting /system.
Click to expand...
Click to collapse
Thanks, but wouldn't a "clean flash" require wiping `system`?
I'm wondering whether this is possibly a hardware problem too: this phone's been pretty beaten up, not sure how to determine that though.
deesto-xda said:
Thanks, but wouldn't a "clean flash" require wiping `system`?
I'm wondering whether this is possibly a hardware problem too: this phone's been pretty beaten up, not sure how to determine that though.
Click to expand...
Click to collapse
I'd wipe everything, including system and your internal SD card, then you'll know for sure if it's hardware related or not.
deesto-xda said:
Thanks, but wouldn't a "clean flash" require wiping `system`?
I'm wondering whether this is possibly a hardware problem too: this phone's been pretty beaten up, not sure how to determine that though.
Click to expand...
Click to collapse
Yeah, I was thinking internal sdcard, like @BadUsername said.
I've finally decided to flip the switch, so the 14.1 nightly builds are running (though they are built only once a week, due to the current infrastructure limitations).
The official builds are signed with private keys (for good security reasons), so there's no plan to provide any unofficial builds by me, to avoid the hassle of switching between different keys.
I'd like to thank @Loader009 for the donation of his retired xt897 devices to me, it greatly helped to make the transition from 13.0 to 14.1 much less painful.
Please let me know about the issues you encounter when running 14.1. In the case of the device crashes, I need to see the output of "cat /proc/last_kmsg" from adb shell, captured after the device rebooted after the crash. Thanks in advance.
I've got it flashed on my RAZR HD XT925 JBBL with the DPI changed to 320. I bought it secondhand and it came with KKBL so I downgraded to JBBL. Most things run fine but some apps that render off the GPU like Temple Run 2 and Subway Surfs show artifacts (random black squares and multicoloured artifacts). This occurs both in Lineage OS 13.0 and 14.1, what's the cause of this to occur?
I've noticed only two problems:
1 - NFC doesn't work properly. I can't read any tag. Android Pay also says, that device is not supported to use NFC.
2 - I use 2 custom layouts for physical keyboard and hot-keys like CTRL+Space don't work. I tried to modify the layout to make it work, but it doesn't work while typing (since space key in use, maybe)
I just installed it yesterday after a complete wipe (and format data/cache f2fs), and think I've got it all set up the way I like except launcher, and didn't run into any real problems yet.
I can't figure out how to get the expected shift/capslock behaviour from hardware keyboard. Still playing with settings.
It didn't come with an APN for freedompop but I found that info on another thread here, before applying that I didn't get LTE, only 3G or no data at all (at the places I've been in last day or so).
I dunno anything about NFC, but Android Pay installed for me with Aroma Gapps, haven't tried using it, doubt it'll work for tap-to-pay tho, as it didn't work for the last few versions of CM either, something to do with PN544 driver or something.
Did LineageOS come with trebuchet? I ended up with only the google now launcher, but maybe my gapps install erased trebuchet, I used aroma for the first time and may have selected things wrong... this one seems I can't customize much, can't get rid of google search bar, can't set background as solid color, can't set background color of app drawer at all which is back to a grid like kitkat.
Play store says firefox not compatible... dunno why. Maybe something I didn't select right with Aroma gapps, although every other app installed fine. Totally unrelated to LineageOS or our phone, but I wish I could find an idiots guide for aroma app selection, explaining what each app is for, particularly system apps I'm not familiar with.
edit: had one reboot, also had errors about MTP host stopping pop up...
enigma9o7 said:
I just installed it yesterday after a complete wipe (and format data/cache f2fs), and think I've got it all set up the way I like except launcher, and didn't run into any real problems yet.
...
Did LineageOS come with trebuchet? I ended up with only the google now launcher, but maybe my gapps install erased trebuchet, I used aroma for the first time and may have selected things wrong... this one seems I can't customize much, can't get rid of google search bar, can't set background as solid color, can't set background color of app drawer at all which is back to a grid like kitkat.
Click to expand...
Click to collapse
Trebuchet is the default launcher for LineageOS. Your Gapps deleted it. Also, if you use a smaller GApps, there is no google search bar ie its not installed. I personally use OpenGapps Pico.
Nightly build from 2017-07-28. Wi-Fi not working. Is it just me?
//EDIT: Tried older builds, too. Wi-Fi did not work with any of them. Flashed back to CM 11.0 and it worked again. Tried LineageOS 13.0 and Wi-Fi worked, too.
//EDIT2: Okay, I think I've figured it out. When I flashed the LineageOS 14.1 after I flashed the phone with previous versions, the Wi-Fi worked alright. It stopped working after changing File system to f2fs.
//EDIT3: Fine, I actually don't know, what happened, but I just changed the File system to f2fs again, flashed the phone with LineageOS 14.1 one more time and the Wi-Fi surprisingly works. I have absolutely no clue, why it did not work after the first flashing.
Shift key not working as expected
I already posted this in a seperate thread a few days ago, but I've got no response and it's driving me crazy, and I assume anyone who is still using this device is because of the physical keyboard, so probably relevant to all.
How do restore traditional "shift" behavior? I want to be able to press then release shift, and the next key I press is shifted. Right now I have to hold shift and another key simultaneously if I want capital letters or symbols from the numbers. I think there even used to be an LED that light up when shift was pressed/released until the next keypress, although I'm more concerned about how it actually works than the led...
I've played with most of the settings on the attached screenshot, other settings only seem to make things worse, sometimes making nothing happen at all for shift, sometimes putting out garbage, sometimes messing with capslock behavior (which is working normally with these settings, although no LED either)... but I certainly haven't tried everything.
If this is standard behavior for everyone using L14.1 and not a setting, is there a file I can modify or a 3rd party app, or anything, to get behavior I want?
rootdefyxt320 said:
I've got it flashed on my RAZR HD XT925 JBBL with the DPI changed to 320. I bought it secondhand and it came with KKBL so I downgraded to JBBL. Most things run fine but some apps that render off the GPU like Temple Run 2 and Subway Surfs show artifacts (random black squares and multicoloured artifacts). This occurs both in Lineage OS 13.0 and 14.1, what's the cause of this to occur?
Click to expand...
Click to collapse
hi
the version that you flashed in your xt925 was the oficial one released by LOS?
did u do any kind of port or mod?
enigma9o7: I've had the same problem sometimes back with the older builds of LineageOS 14.1. Try to clean flash it with the newest build from yesterday. I just tried to type something with the physical keyboard and the Shift button just worked "correctly".
EDIT: Okay, I think I've figured out your problem. You probably use the Asanti v2 keyboard setting. Switch it to Asanti v1 and the Shift key should work as expected.
Krlos Eduardo said:
hi
the version that you flashed in your xt925 was the oficial one released by LOS?
did u do any kind of port or mod?
Click to expand...
Click to collapse
It's the official 14.1 one for XT897.
rootdefyxt320 said:
It's the official 14.1 one for XT897.
Click to expand...
Click to collapse
without doing any port?
Should updates work thru the updater?
I just tried doing it, it downloaded succesfully, then rebooted into TWRP, but didn't do anything. So I tried installing myself (took me a while to find the file btw) and it failed zip signature verification. So I downloaded it on my PC, copied it over via USB, then tried again, and still fails.
kabaldan said:
I've finally decided to flip the switch, so the 14.1
Click to expand...
Click to collapse
@kabaldan, I noticed that a number of device trees in LineageOS now have a new branch of "lineage-15.0", but the xt897 does not. Is this an ominous sign that the xt897 will not be built for Oreo?:crying: or is just a timing thing at this early stage:fingers-crossed:
any hope for running it on mb886?
mb886 - atrix HD - ...you can test it if is your bl unlocked and twrp installed.
Mainboard have same base - msm8960. But i am now 100% sure if your phone is bl free unlockable. if not, then you can test to unlock it via sunshine.
I have installed this and for a while all was fine. But I was browsing in chrome when all of a sudden it froze and the phone restarted and went into a boot loop just showing the bootloader unlocked screen. I cleared the cache and dalvik cache from TWRP, which makes it boot, but any attempt to uninstall or launch chrome makes it happen again. Now it just seems to be happening at random without even opening chrome.
How can I wipe my device completely and start again? I know I can do a factory reset, but is there a lower level way to wipe it? I also saw something about changing the filesystem, is that worth doing (can it make it a bit faster)?
I have ordered a gemini PDA that I hope will arrive by late january or sometime in february, but I need this phone to get me through a couple more months!
Installed this a couple weeks ago, upgrading from a 4.4.4 CM after a number of apps I run on this finally dropped support. I did a complete wipe including the f2fs formats as suggested and it installed without incident.
I cannot believe how well it runs: keyboard works and lights up on pull out, turns off on close, hdmi port works, gps, camera+flash works. It really didn't lose any speed from my older install. Really well done, I was afraid there would be bigger problems but only a couple small ones so far.
The couple things I noticed: slow to get carrier signal and voice is garbled when using freedompop's dialer or google hangouts on the bottom mic. Slow signal seems normal, even 4.4.4 had this issue, though it can sometimes take a few minutes. Using a sound recorder shows the bottom mic working, but using fpop/hangouts dialer makes it garbled. Top mic, speaker phone, always works though. I don't have regular service to see is default dialer has same issue though, just freedompop free service which is just voip.
Still, this is a pretty awesome breath of life on this old thing. Ram holds it back somewhat but it's still pretty useful.
So I just wiped everything, repaired filesystems, and reinstalled. Data and cache were already f2fs so nothing to do there. But I noticed that during install it says:
twrp patching system unconditionally
unknown command [log]
unknown command [log]
Do I need a newer version of TWRP? I have 2.8.6. I noticed that at least 3.0 is available: https://forum.xda-developers.com/showthread.php?t=1887070
Here is 3.1.1-0 for you
https://drive.google.com/file/d/1vO4_nq3FNquuO3neHrOzuIb5gnmN11AZ/view?usp=sharing
CornholioGSM said:
Here is 3.1.1-0 for you
https://drive.google.com/file/d/1vO4_nq3FNquuO3neHrOzuIb5gnmN11AZ/view?usp=sharing
Click to expand...
Click to collapse
Thanks!
I've now installed the latest TWRP and reinstalled Lineage, gapps and su, and I didn't get any errors this time
But I have a really odd problem which I was hoping this would fix and it hasn't - I can't download certain applications from the play store, they say "Downloading" but they never actually start to download. Eventually either it mysteriously stops trying to download or I get an error message with code 492. It seems to be applications that are over a certain size. I've been googling but can't find any solutions that work. I have a lot of free space in all partitions. Did something with the directory structure get screwed up maybe? Seems like some problem with the dalvik cache I think, but wiping doesn't seem to help. I have no idea at this point