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
Related
This is now considered a beta version of Ice Cream Sandwich for the HeroC. Please keep all comments/communication about this ROM in this thread, and keep the Development thread clean for people actively working on the ROM.
No guarantees that anything will work, or that your phone will not be turned into a brick or a toaster. Please backup if you value what is currently on your phone.
You can use this with or without gapps. If you load them both on the initial setup, be sure to select "Setup Wizard" when the system first comes up.
In its current state this ROM with GAPPS needs around 155M in /system. I am currently running firerats at 160/20 just to be safe for testing purposes. I would recommend at least 155 for system.
There are some obvious places where we can reduce the size, but that will come as we continue to refine and move forward. Performance in not great, but overall it is fairly functional. Gapps are just some a minimal version to get Market working.
THIS ROM TAKES A LONG TIME TO BOOT (ESPECIALLY FIRST BOOT).
Boot animation has been added in 26NOV version. Please be patient.
This is a work in progress and there remain many Opportunities for Improvement (the gentle euphemism for Defects).
Working (at least for me):
Touchscreen
Trackball
Phone
Data
WiFi
MMS
Audio
Bluetooth
SD Card
Market
GPS
Gallery
Boot Animation
LatinIME Keyboard
Prediction/Dictionary
Network Stats (Data Usage)
Headsets (Audio Jack & HTC 11 Pin)
Not Working:
Camera
Gallery2
Graphics Acceleration
TBD (Lots of other stuff)
25-NOV-2011 Initial Alpha release
TeamICS-4.0.1-25NOV-HeroC.zip
26-NOV-2011 Update with working GPS. Disabled broken qcom egl so that Google Maps works (slowly). FIXED LINK
TeamICS-4.0.1-26NOV-GPS-HeroC.zip
28-NOV-2011 Updated kernel for better alignment with ICS. Lots of additional updates. Updated to fix wifi issue (wlan.ko replacement)
TeamICS-4.0.1-28NOV-NEWKERN.zip
01-DEC-2011 Updated kernel to support network stats (Data usage). Modified LatinIME to show entire keyboard. Synced with CM/AOSP repos.
TeamICS-4.0.1-01DEC-HeroC.zip
06-DEC-2011 Updated with test fix for random app crashes (phone, exchange, popups, etc.)
TeamICS-4.0.1-01DEC-HeroC.zip
18-DEC-2011 Updated to latest AOSP/CM 4.0.3 source base. Fixed trackball. Replaced Gallery2 with older Gallery for the time being. This has major changes to the source base and limited testing, so backup is recommended.
TeamICS-4.0.3-18DEC-HeroC.zip - Currently offline while resolving some issues
18-DEC-2011 Updated to latest AOSP/CM 4.0.3 source base. Update from earlier post to add audio driver fixes, and su updates that restore Superuser functionality.
TeamICS-4.0.3-18DEC-HeroC-AUDIOFIX.zip - Currently offline while resolving some issues
20-DEC-2011 Back to 4.0.1 for the time being, until 4.0.3 issues can be resolved. This version has all of the standard fixes including radio/data, trackball, and audio. Also includes Gallery instead of Gallery2.
TeamICS-4.0.1-20DEC-HeroC.zip
22-DEC-2011 Minor update to include fixes for Headset (Audio Jack) and Dictionary/Prediction.
TeamICS-4.0.1-22DEC-HeroC.zip
25-DEC-2011 Add basic Bluetooth functionality. Additional testing in progress. Classification changed to Beta, as all major functionality is working except for Camera and Hardware Acceleration.
TeamICS-4.0.1-25DEC-HeroC.zip
01-MAR-2012 Integrating development with Evervolv team. Brings alignment with ICS 4.0.3 development.
Evervolv-ICS-2.1.0-01MAR-HeroC.zip
GAPPS
You can use the latest ICS Gapps from here. Or other Gapps of your choice.
FAQ / Fixes
DATA ISSUES
If you are having issues with Data try the following settings:
"Data enabled" checked
"Data roaming" unchecked
"System select" Home only
If you still have issues with data, please capture the output of "adb logcat -b radio" from boot to completely booted and post it to pastebin or equivalent.
KEYBOARD ISSUE
Attached below is a replacement keyboard that doesn't have the bottom row off-screen. This is just a quick hack to get a functional keyboard. After some clean up and testing, I will include it in the releases going forward. Just replace the existing /system/app/LatinIME.apk with this one for the time being.
Reserved 2
This is also reserved for later use.
Nice.
Sent from my HERO200 using XDA App
I've got work in an hour........ so here we go, I'll let you know what happens.
whoa man, already? YOU GUYS ARE AWESOME!!
p.s- happy thanksgiving btw!!
edit:btw downloading it right now,, going to give it a go
---------- Post added at 10:45 AM ---------- Previous post was at 10:03 AM ----------
hmmm after the HTC screen, i get a black screen showing nothing. Plugged the charger and shows charging light.. Still waiting for it, it's been like 3 minutes. im on 170 40 mtd settings. K nvm it setup just appeared. For those that are trying, wait for it.
EDIT: K been messing around with it (sorry for all these edit, just trying to prevent a lot of posts and I am awake this late so might as well show some heads up) but problems I found
1) Keyboard is half (missing space bar and the alt function)
2) Screen orientation is choppy
3) Im missing the actual market app, might be firerats issue
I found a pointless feature.. but using the trackball brings up a cursor lol didn't know it'd do that. Making it "click" u have to press the ball then scroll quickly rather than just keep clicking the ball.
Thank you ICS Team. Other than the items listed in the OP, I cannot get data to work. Phone is stuck on No Service and every few minutes will jump to roaming and then back to no service. If I try to call a number with the dial pad, the dial pad disappears after I press send, I assume this is because I have no cell signal. Could not test google apps due to no data. I was still able to play with the home screen, widgets, etc.
@ Majin101, my keyboad seems to be working ok, I do have the market app but haven't tried to use it yet. I am not using firerats mod. If anyone else tries to flash this, make sure you wait a few minutes for the rom to boot as mentioned in the above post. You will see a blank screen but it will eventually boot.
This is going to be a great rom. If you use a different keyboard you also get space and alt to show up.
Findings.
Okay, Seems nice. There is no bootscreen, so be patient, when setting up, choose "setup wizard"(this is kind of a no brainer, but you never know). Alright:
1. Data isn't working, I changed the roaming settings, but it didn't help.
2. As mentioned in an earlier post, the keyboard is missing some keys.
3. I do however have the market application. I used the gapps in the op and am using firerats 160 40
Really amazing work. The fact that this is even running on my hero amazes me. And they thought it would have trouble with eclair
Freeroot said:
Okay, Seems nice. There is no bootscreen, so be patient, when setting up, choose "setup wizard"(this is kind of a no brainer, but you never know). Alright:
1. Data isn't working, I changed the roaming settings, but it didn't help.
2. As mentioned in an earlier post, the keyboard is missing some keys.
3. I do however have the market application. I used the gapps in the op and am using firerats 160 40
Really amazing work. The fact that this is even running on my hero amazes me. And they thought it would have trouble with eclair
Click to expand...
Click to collapse
Data is working well for me with the following settings:
"Data enabled" checked
"Data roaming" unchecked
"System select" Home only
Try that, and if you still have issues with data, please capture the output of "adb logcat -b radio" from boot to completely booted and post it to pastebin or equivalent.
As i was installing in cwm i got an error stating "random offset: 0 x 150" yet the rom still installed. Any ideas as to what this was/is?
jaybob413 said:
Data is working well for me with the following settings:
"Data enabled" checked
"Data roaming" unchecked
"System select" Home only
Try that, and if you still have issues with data, please capture the output of "adb logcat -b radio" from boot to completely booted and post it to pastebin or equivalent.
Click to expand...
Click to collapse
Alright, that did the trick. Really nice work.
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
rizdog23 said:
As i was installing in cwm i got an error stating "random offset: 0 x 150" yet the rom still installed. Any ideas as to what this was/is?
Click to expand...
Click to collapse
I got the same error. It booted just fine and I thus ignored it. Would be nice to know though.
For those that want to fix the keyboard, just download ics keyboard from market. For those that cannot download from market, use root explorer to go into "cache" and create a folder named "downloads", for those that want to increase scrolling speed etc., flash the TweakZ.zip found in the android general forum here at XDA. I would also recommend setCPU.
I also got Random Offset 0x1ba. Once rebooted, HTC screen showed up then black screen. I waited 10 min but it looked frozen. So I pulled the battery. Then I accidentally formatted my SD card and the fun was over.
Sent from my HERO200 using Tapatalk
The "random offset" comment has to do with the flashing of the kernel. I'm not entirely sure but I think it has to do with the way the boot.img is packed. Should be harmless though..
Good to see you'll got this thing running though.
Sent from my PG86100 using Tapatalk
Another feedback!
pros
1) Ive been texting sending and recieving just fine no problems (havent tried mms)
2) Made calls talked fine (although my face kept hitting the end button..)
3) Installed swype, texting is fine now and changed the dictionary too english to get rid of those red lines under the words
4) Also increased pointer speed to just use the trackball if needed
other bugs:
1) Noticed that some of my notification doesn't make a sound or plays
2) When I play music its coming through the ear piece speaker rather than the back speaker
3) google map fails to login
Darn looks like I have to go back to CM7.1. People try to call me but my won't won't tell me someone is calling and their isn't any sound either. Also the gallery app opens but doesn't show pictures and apps are missing from the market but thats probably a build.prop issue.
-------
Just flashed without mtd and it seems to be working better. I'm receiving calls and can hear my sound now.
Great job guys! Running for about an hour and besides the above mentioned bugs, I've noticed one more.
When I put the phone on the charger it becomes unresponsive and the screen goes dark. No way to wake the phone nor is the charging led on.
The only way I can charge the phone is to do a battery pull and boot the phone while on the charger.
mines charging and im still able to use it?
Very Impressive, to say the least!
*note for the development team - you are the F-ing man!!!!
I just wanted to be sure that I am going to do this right.
Do I just go Settings > About phone > CyanogenMod updates > then download 10.1 and it will do all the work for me? Or do I have to make a nandroid backup (going to do that anyways), wipe cache and dalvik, flash boot.img then flash the rom?
Also, how stable is 10.1? Any known bugs?
kylepont said:
I just wanted to be sure that I am going to do this right.
Do I just go Settings > About phone > CyanogenMod updates > then download 10.1 and it will do all the work for me? Or do I have to make a nandroid backup (going to do that anyways), wipe cache and dalvik, flash boot.img then flash the rom?
Also, how stable is 10.1? Any known bugs?
Click to expand...
Click to collapse
The automatic updater will not work. At least if you're S-On. So flashing through recovery is the way to do it (wipes and boot.img flashing as usual also ofc). I believe flashing CM10.1 over CM10 might work without factory reset, but prepare for stuff not working and flashing it again with proper wiping.
Bugwise I'd say CM10.1 is absolutely ready as a daily driver. Wifi tether doesn't work when screen is off (same issue is with CM10). Performance is a bit lower than with CM10. You'll see some screen tearing when scrolling and switching home screens and in some games with intense graphics.
Give it a go! It's not too hard to go back to CM10 if it doesn't please you.
Sent from my One S. Please hit thanks if I helped.
zaak00 said:
The automatic updater will not work. At least if you're S-On. So flashing through recovery is the way to do it (wipes and boot.img flashing as usual also ofc). I believe flashing CM10.1 over CM10 might work without factory reset, but prepare for stuff not working and flashing it again with proper wiping.
Give it a go! It's not too hard to go back to CM10 if it doesn't please you.
Click to expand...
Click to collapse
This will be a tl;dr story so only read it if you can be bothered...
I did the automatic update, then as soon as it downloaded I had to run for the bus (one a bloomin' hour). I was then stuck on the htc splash screen for about ten minutes, did a soft reset, went into recovery, went back to CM10, restored the backup, not a problem. Then got home, pushed 10.1 onto the phone, flashed the new boot.img, then flashed CM10.1 and restored backup again. Worked fine. Then I had to try three different Gapps because two of them didn't actually work, and it was agonising that the website that I got them from only had an upload speed of around 0.4Mbs. But flashed that now, and everything works fine (although I had to delete and re-download NatWest and Play Music).
zaak00 said:
Bugwise I'd say CM10.1 is absolutely ready as a daily driver. Wifi tether doesn't work when screen is off (same issue is with CM10). Performance is a bit lower than with CM10. You'll see some screen tearing when scrolling and switching home screens and in some games with intense graphics.
Click to expand...
Click to collapse
Spotted a couple of bugs immediately. Syncing with facebook simply does not work (I only wanted contact pictures for caller IDs). Obviously the clock bug, but I know how that is fixed. Haven't had any screen tearing yet, and since Orange only give me 750MB there is nooooooooo way that I am going to use tethering, so that won't bug me. CM10.1 has fixed the music player bug, where the first song I play would take around 30 seconds to play, if I chose another song then it would restart the previous song, play that for five seconds, then play the selected song, and if I paused a song it would then start playing again for a couple of seconds after five seconds of being paused. That was irritating. Noticed it seems to be a fair bit more RAM heavy than CM10, but I miss the settings button on the top of the notification bar, that tiles thing just seems to take to long for my liking...
kylepont said:
Noticed it seems to be a fair bit more RAM heavy than CM10, but I miss the settings button on the top of the notification bar, that tiles thing just seems to take to long for my liking...
Click to expand...
Click to collapse
You can also swipe down with two fingers, or set a specific area that opens the Quick Settings immediately, in Settings
Sent from my One S using Tapatalk 2
usaff22 said:
You can also swipe down with two fingers, or set a specific area that opens the Quick Settings immediately, in Settings
Click to expand...
Click to collapse
Already knew about the sections thing, but because I'm right-handed every time I wanted to look at a notification I got settings, and setting it so that the settings open on the left side just seems a bit weird. I didn't know about the two fingers thing, and I like that, cheers.
Hey,
I purchased a used Nexus 5, 32GB edition (I think the model is D821) as my then current phone (a Samsung Galaxy S4) somehow had a magically broken screen after setting it down on a bed. I have since been able to access my old phone, but it isn't usable as a daily handset.
Anyways, wen I first obtained this phone, I wanted to be safe so I unlocked the bootloader, downloaded the necessary tools to use adb/fastboot, wiped the phones storage, and then flashed the latest version 5.0.1 LRX22C. After installing the normal things I had on my old phone and rooting the device, I have noticed that I get an absurdly abnormal amount of force closes. Mainly dealing with the launcher.
On a daily basis, the launcher, and it seems to mainly ONLY be the launcher (either Google Launcher or Nova, it isn't application specific) force close, freeze, or become unresponsive. I can come to this conclusion on the following basis:
1) The launcher screen shows the background, but doesn't show the dock or any of the shortcut/widgets on the launcher
2) All I can see is a black screen and the notification bar/tab. This is sometimes evaded by switching to the recent apps button and then switching back using the home button.
3) It will show the screen with all applications, but won't swipe between home screens.
There is no major physical damage to the device, there is a hairline crack from the previous owner.
I am guessing that I could go through the process of downloading the firmware and reflashing it, but I was wondering if anyone had ideas on how to solve it, besides flashing the device immediately. I don't want to go through the hassle of flashing firmwares and setting up a device again, especially during finals week. The problem is annoying enough that it would make me post this, but not annoying enough to spend an entire afternoon dealing with that and re-configuring applications and such.
Thanks for the help in advance.
slixzen said:
Hey,
I purchased a used Nexus 5, 32GB edition (I think the model is D821) as my then current phone (a Samsung Galaxy S4) somehow had a magically broken screen after setting it down on a bed. I have since been able to access my old phone, but it isn't usable as a daily handset.
Anyways, wen I first obtained this phone, I wanted to be safe so I unlocked the bootloader, downloaded the necessary tools to use adb/fastboot, wiped the phones storage, and then flashed the latest version 5.0.1 LRX22C. After installing the normal things I had on my old phone and rooting the device, I have noticed that I get an absurdly abnormal amount of force closes. Mainly dealing with the launcher.
On a daily basis, the launcher, and it seems to mainly ONLY be the launcher (either Google Launcher or Nova, it isn't application specific) force close, freeze, or become unresponsive. I can come to this conclusion on the following basis:
1) The launcher screen shows the background, but doesn't show the dock or any of the shortcut/widgets on the launcher
2) All I can see is a black screen and the notification bar/tab. This is sometimes evaded by switching to the recent apps button and then switching back using the home button.
3) It will show the screen with all applications, but won't swipe between home screens.
There is no major physical damage to the device, there is a hairline crack from the previous owner.
I am guessing that I could go through the process of downloading the firmware and reflashing it, but I was wondering if anyone had ideas on how to solve it, besides flashing the device immediately. I don't want to go through the hassle of flashing firmwares and setting up a device again, especially during finals week. The problem is annoying enough that it would make me post this, but not annoying enough to spend an entire afternoon dealing with that and re-configuring applications and such.
Thanks for the help in advance.
Click to expand...
Click to collapse
How did you install the stock firmware? Have you tried wiping cache and dalvik cache in recovery? I'd do that first, and if that doesn't work then try dirty flashing the same ROM (you won't lose anything). If you are still having issues after then flash a factory image with fastboot (do NOT use a toolkit). That should fix it.
_MetalHead_ said:
How did you install the stock firmware? Have you tried wiping cache and dalvik cache in recovery? I'd do that first, and if that doesn't work then try dirty flashing the same ROM (you won't lose anything). If you are still having issues after then flash a factory image with fastboot (do NOT use a toolkit). That should fix it.
Click to expand...
Click to collapse
I know this is a very late response.
The initial way that I installed the stock firmware was using fastboot, and installing each .img file separately.
I just re-flashed the factory image again (except for the recovery image), and am waiting for the phone to boot up (it seems like it takes ages for the phone to actually go from fresh install to fully booted), it has been over a 5 minutes now.
But once that is done, I will see what happens. Is there a way to check for bad hardware (I am specifically thinking flash storage)? Maybe that is causing the problem?
I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
what's the last 3 characters of your bootloader version?
heldc said:
I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
Click to expand...
Click to collapse
Have you tried changing kernel? I mean in the case of civz lollipop rom you do get an option of 2 different kernels try choosing the opposite to the one you had chosen before. Thank you, hope it helps.
I won a year ago 2 Note Pro, one works flawlessly while the other is slow af and it has the same issue that you speak about. If I stay on stock everything is good more or less (sometime little slow), but if I install Lineage or any other Custom Rom is too slow and has the same issue you speak.
I changed both batteries, but nothing to do. If anyone knows, text please.
Thank you!
Hi all, I have been facing a really weird problem for the past few weeks. Sometimes all of a sudden, my phone screen completely turns black, and the buttons (as well as the alert slider) stop responding. There is no indication whatsoever that it is NOT switched off. However when I try calling it from another phone, ring can be heard as if my phone is working fine. I don't understand where the problem lies. Any suggestions are welcome.
I am rooted with Magisk 19.3, Riru-EdXposed 0.4.5.1 Sandhook, Riru-Core v19.5.
Edit: Android Pie. OOS 9.5.10.GM21AA
I had this problem recently when accessing certain apks. Reflashing the firmware sorted it for me.
no root same problem to me after I update from Android 9 to Android 10
hallo dare said:
I had this problem recently when accessing certain apks. Reflashing the firmware sorted it for me.
Click to expand...
Click to collapse
Thanks I will try doing that.
Same problem here when opening quite a few apps. Issue didn't start until I updated to Android 10 (and rooted), on a converted T-Mobile variant. Wonder if that is the source of our problem. I'm sorely tempted to use the MSM tool and go back on TMO's Android 9 (and pray for a official update to 10). Unless someone can find a solution to this, rebooting the phone every time I want to open certain apps is a real pain.
NighthawkXL said:
Same problem here when opening quite a few apps. Issue didn't start until I updated to Android 10 (and rooted), on a converted T-Mobile variant. Wonder if that is the source of our problem. I'm sorely tempted to use the MSM tool and go back on TMO's Android 9 (and pray for a official update to 10). Unless someone can find a solution to this, rebooting the phone every time I want to open certain apps is a real pain.
Click to expand...
Click to collapse
It definitely is a A10 issue as I too have started to have this issue when opening games and ram extensive apps. A workaround is to open the game or app in split screen mode and once the app has started you can switch back to fullscreen mode or start the app from recents. That has worked for me 100% of the time. The 10.0.1 update seemed to make it worse because you have to reboot the phone to escape the black screen were as at first you could use gestures to escape the app.
mookiexl said:
It definitely is a A10 issue as I too have started to have this issue when opening games and ram extensive apps. A workaround is to open the game or app in split screen mode and once the app has started you can switch back to fullscreen mode or start the app from recents. That has worked for me 100% of the time. The 10.0.1 update seemed to make it worse because you have to reboot the phone to escape the black screen were as at first you could use gestures to escape the app.
Click to expand...
Click to collapse
Good idea using split screen, I'll have to start doing that for the time being. I moved over to Open Beta 3 and the issue is still there and worst as with 10.0.1. Hopefully OnePlus can nail this bug soon. It's turning a otherwise amazing phone into a headache.
I have the same problem. Running 10.0 rooted. For me, this has only happened when opening Youtube Vanced. One clever solution is to enable "Quickly turn on camera" and doublepress power if this happens. This launches camera and returns the screen to normal.
hallo dare said:
I had this problem recently when accessing certain apks. Re-flashing the firmware sorted it for me.
Click to expand...
Click to collapse
Experiencing this too, it does seem to be related to certain .apks, how bizarre is that? Really don't want to re-flash as I am encrypted... Can you dirty-flash with an encrypted system and not loose any data?
cantenna said:
Experiencing this too, it does seem to be related to certain .apks, how bizarre is that? Really don't want to re-flash as I am encrypted... Can you dirty-flash with an encrypted system and not loose any data?
Click to expand...
Click to collapse
I reflashed through TWRP and all data was fine. I'm encrypted too.
But it goes without saying, make sure you do a backup before flashing anything