Related
THIS ROM HAS NOW BEEN SUPERCEEDED BY MODACO ROM 2.0. I WILL NO LONGER BE PROVIDING UPDATES/SUPPORT FOR THIS ROM.
12/18/09 Update
Here is my most recent version of the updated MoDaCo rom. I have fixed the version display info.
This rom should be safe to upgrade from stock or MoDaCo 1.1 roms.
If you experience force closures the issue is with your dalvik-cache or your boot-cache.
You can clear your dalvik cache from the recovery mode. Do not do a factory wipe. Choose the dalvik-cache wipe/clear.
You can clear your boot-cache from adb as a temporary fix by typing:
rm -r /data/boot-cache
reboot
Changelog:
1.3a:
-rebuilt properties file
-shuffled some apk's around
1.3:
-no longer requires wipe to install/upgrade
-fixed ssh password in about screen
-fixed version info to show correctly
-all market apps should show correctly
-updated to busybox without color codes (this is for the windows users using adb shell)
-upgraded to latest relase of wifi tether
-minor performance tweaks and optimizations
-minor interface tweaks (new lockscreen animations)
1.2c:
fixed issue with protected apps not showing up in market
reverted displayed version # in phone settings (sprint update is still there though)
1.2b:
fixed builld/version info
fixed force close issues for people who upgrade from MoDaCo 1.1
1.2a:
manually patched Sprint Maintenance Release to MoDaCo 1.1 rom.
Get 1.3 here.
Install from the recovery console. No wipe should be necessary!
Please post here if you have problems.
Just flashed from 1.1, getting a bunch of force close messages on boot can't use internet, software version 1.29 so no update, don't know if I should've flashed from stock but thought id try from 1.1.
I'll look into it later right now I need sleep. FYI I updated from a stock patched Rom freshly rooted. You may need to do a wipe for it to work properly. Also i hand copied the individual patched files into the modaco 1.1 to make this work. I am new to this so I do not know how to update the version # by hand editing yet.
getting a bunch of force close messages also,plus it lags pretty much
dunno why but i tried it,thx anyway..time to flash again .
Is the bluetooth audio streaming working?
works great nice job man
i would also like to know if you can play media via bluetooth speakers on this ROM...all ROMs w/ the MR update don't seem to be able to do it, but the Sprint MR update w/ no custom ROM installed can
I got a bunch of force closes when it booted up. I also noticed the browser and some google apps will no longer open and just force close.
mine works perfect
Works fine for me. I did revert back to stock before doing the update and reset my data to be sure.
The build number in the "about" screen is the old number, but things do seem to be updated to the new stuff anyway. To change the build number, I think you need to edit the /system/build.prop file.
Great work!
My force closures have healed themselves! Well, except for the "market" app but I bet I can uninstall/reinstall it.
Obelisk, hopefully this description of my steps helps in finding some answers...
Last night, before I saw obelisk's first few posts regarding his experiment, I had decided to bite the bullet and flash back to the stock Sprint RUU.
First I copied all of my app and app-private folders to my SD card. Then, I did a nandroid backup and then flashed the RUU. I let Sprint download and install the MR. Then I rooted and flashed the recovery image. This is when I found obelisk's posts and decided to try it out. After I flashed his "unofficial" update I booted up and then rebooted (it stated "reboot required" in the menu\settings\about phone\build number after "MoDaCo Custom ROM"). At that point everything was working fine. No force closures, phone was sleeping correctly, I had mute and speaker phone buttons in the call screen, etc...
I decided to copy my apps back, restore my nandroid backup (even though I knew this would undo everything I had just done) and then reflash obelisk's updated modaco again. After doing that I rebooted and got a ton of force close errors. I just closed them all and went to bed!
HERE"S THE WEIRD PART! I woke up this morning and the only force close I'm getting now is with the market app (and ONLY if I try to open it). All my other restored apps are working fine. I am about to go to work but I will play around with this some more. I'm keeping it for now!
I just rebooted and all of the force close errors came back. I guess I'm going to go back to my original pre-MR nandroid backup.
i think the problem is related to the software version number which i haven't figured out how to update yet, so a lot of the apps, and yes there were about 20, that were patched in the maintenance release don't get updated properly until i increment the rom version somehow. i'll mess with it tonight when i get home from work.
did a fresh ruu, and updated this custom rom over a rooted stock, did a factory reset after the install and absolutely no issues.... A+ job buddy
johnsongrantr said:
did a fresh ruu, and updated this custom rom over a rooted stock, did a factory reset after the install and absolutely no issues.... A+ job buddy
Click to expand...
Click to collapse
How do you go about doing a fresh ruu?
I'm going off of memory here but...
1. download the sprint RUU
2. install HTC Sync on your pc if you have not already done so
3. connect your phone to your computer
4. run RUU (it's an executable file)
5. Follow prompts
6. Reboot phone into stock un-rooted goodness/badness depending on your opinion.
obelisk79 said:
I'm going off of memory here but...
1. download the sprint RUU
2. install HTC Sync on your pc if you have not already done so
3. connect your phone to your computer
4. run RUU (it's an executable file)
5. Follow prompts
6. Reboot phone into stock un-rooted goodness/badness depending on your opinion.
Click to expand...
Click to collapse
im getting an error 107. the ruu nor htc sync connects to my phone anymore
ABNinja said:
im getting an error 107. the ruu nor htc sync connects to my phone anymore
Click to expand...
Click to collapse
Is your battery fully (or at least mostly) charged?
EDIT: Sorry, I just noticed that's a different error.
Great Rom
I came from a rooted stock Rom wither the Mr update...wiped, flashed...apps2sd, then reboot. Worked flawlessly! I also added the extras from another Rom and everything is running fine. Great work on this..
are you getting error code 107 or 170? google provides no help for error code 107...
Barebone SGS4G KJ6 ROM
Use at your own risk, I take no responsibility for anything that may happen to your phone because of this ROM.
Here is a ROM that I made for myself, but what the heck, let's share. This ROM is very stock-like with just few usability mods.
Features
Will not wipe your programs or data, /data is preserved upon install
Heavily debloated. Most essentials apps are still there (like WiFi Calling)
No extra programs added, you need to add your own
ODEXed to save space in /data
CarrierIQ is completely removed
Extended Power Menu (including Screenshot)
Extended Quick Panel (10 buttons, including Data toggle)
1% battery (horizontal)
CRT-Off
Time zone version 2012b
/etc/hosts to cut ads out of the box (keep up to date with AdAway or similar)
Few conservative presets in build.prop and init.d
Basic with a Twist 1.1.3 kernel included
Notes
* Don't get confused about ODEXing, it's actually better to run and saves quite a bit of space in /data.
* Some Google apps (Maps, Streets, Voice) and Adobe Flash are removed from /system. Install them from market. Benefit - they can be moved to SD card this way.
* Original Swype is removed, is somebody needs it flash this.
* In case you need it, use this thread to add some bloat back.
* Factory Reset is removed from Settings->Privacy, use CWM if you ever need to reset all data.
* KJ6 modem included. Use this thread to flash a different modem if needed.
Install
Flash with CWM. Wait until the system boots up, then wait few more minutes for it to settle.
Download
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.8
Changelog
1.1.3
Removed "Mobile data connection disabled. Connect?" popup on boot
1.1.2
Removed Factory Reset from Settings->Privacy
Updated kernel
1.1.1
Fixed voicemail notifications not working without Visual Voice Mail installed
1.1.0
CIQ is properly removed
Some neutral cosmetics (logo, animations)
Minor update to the kernel
1.0.8
Fixed slow stock browser scrolling
1.0.7
Extended Quick Panel
1.0.6
Added Screenshot to power menu
1.0.5
Removed DriveSmart and Software Update from Settings menu
1.0.4
Put original framework-res.apk certificate back
1.0.3
Added power menu mod
1.0.2
Original public release
does it have a screenshot option from the power menu??
m0bstr said:
does it have a screenshot option from the power menu??
Click to expand...
Click to collapse
Nope, never bothered with power menu. I don't reboot the phone too often and to say the truth don't even remember when last time I needed to take a screenshot. I use ShootMe and QuickBoot when I need to, they both do the job just fine.
Yes, power menu is fully modded now, including Screenshot option.
Thank you for this, Anton! Love your kernel. Is this ROM ok for OC/UVing with you OC/UV kernel? I think this will be the second ROM I have ever installed. Haven't bothered to try anything since first getting Val Final.
Download link is not working
Sent from my SGH-T959V using XDA
Does this come pre-rooted?
Blaggah said:
Does this come pre-rooted?
Click to expand...
Click to collapse
Yeppers it does.
I updated the link. I actually took it down on purpose, wanted to look at something but never had time.
I was troubleshooting an error message during boot time, so I traced it to the CIQ trying to execute some on-boot code, which was removed by Krylon. Strangely the original code itself doesn't do much, it's initilizing a broadcast receiver with an empty onReceive method. Removing this was a moot point, it probably didn't do much. I disabled the BOOT_COMPLETED permission for the service to avoid the error message.
So I looked at the CIQ more closely. What I found is a little peculiar. The main CIQ code is integrated quite deeply into the framework, it cannot be removed easily, there are just too many calls that send various metrics to the CIQ Agent. The main CIQ classes are not in the framework.jar, they are in ext.jar. Probably that's why nobody noticed them and never tried to modify them. What is strange that many calls seem to be not implemented. For example the sumbitMetric is an empty method, shouldSubmitMetric always returns zero, etc.
It's possible that T-Mobile decided not to use CIQ on our phone (at least extensively), but instead of removing it completely just plugged few calls.
I'm removing the "CIQ removed" description because it's actually not removed, although may not be doing much.
I cannot get it to boot. After the "Galaxy S 4G" screen, the screen goes back then nothing ever happens. I rebooted into CWM (which still shows Team Acid's logo) and tried fixing permissions to no avail.
Given that the OP says it won't wipe programs, data, etc, was it possibly a Bad Idea™ to have wiped everything before installing this ROM?
Update:
Indeed, installing from a blank phone (literally, I wiped everything) didn't work for me. I flashed Bryan's one-click with CWM, it booted, rebooted into recovery, flashed this, and it booted. Now for testing. Thanks, Anton!
I had the same issue as well... Thought it was just my phone
Sent from my SGH-T959V using xda premium
Would be interesting to look at the logcat to see where it's stuck.
There was a possible problem with 1.0.3 that I pulled off. The current one that I re-uploaded - I tried to install in on both fresh phone (after factory reset) and on top of a running ROM , everything seemed fine.
The problem was with framework-res.apk. I had to resign in because I changed some permissions in AndroidManifest.xml (related to CIQ), but something went wrong the first time.
There is a little bit of controversy with signing of framework-res.apk. Some say it's OK, some say the original cert should be kept. Maybe somebody else would chime in and tell me if I screwed it up or not.
wont flash
I wipe everything, the ROM installs, and then black screen...noting. Let it sit for 20min however this did not resolve issue. I was able to install Valhalla no prob. flashed your rom on top of Valhalla and then my phone boots your rom. Do i need to install on top of another rom? I should just be able to whipe my phone and install your rom correct?
AntonX said:
Would be interesting to look at the logcat to see where it's stuck.
Click to expand...
Click to collapse
I can probably capture that because I can use adb to get into the OS. I ran top to see what, if anything, was hogging CPU but there was nothing obvious & CPU usage was minimal. I have the phone running now but I'm willing to wipe it again and re-flash. Mind you, I did more than factory reset. I was quite literally trying to start from scratch, so here's what I did (if this helps at all):
Backed up /efs to my PC
Backed up the SD card to my PC
Wiped cache
Wiped Davlik cache
Wiped battery stats
Performed a nandroid backup
Copied the backup from /sdcard/clockworkmod/backup to my PC
Formatted /data, /system, & /sdcard
Rebooted back into recovery
Copied the ROM to the SD card
Flashed it
Let it cook for ~20 minutes
So it was quite literally a blank slate.
AntonX said:
There was a possible problem with 1.0.3 that I pulled off. The current one that I re-uploaded - I tried to install in on both fresh phone (after factory reset) and on top of a running ROM , everything seemed fine.
The problem was with framework-res.apk. I had to resign in because I changed some permissions in AndroidManifest.xml (related to CIQ), but something went wrong the first time.
There is a little bit of controversy with signing of framework-res.apk. Some say it's OK, some say the original cert should be kept. Maybe somebody else would chime in and tell me if I screwed it up or not.
Click to expand...
Click to collapse
I appreciate all of your hard work. When I get the chance I'll download the latest, follow my steps above, & let you know what I find.
stephen_w said:
I appreciate all of your hard work. When I get the chance I'll download the latest, follow my steps above, & let you know what I find.
Click to expand...
Click to collapse
Wow, you really wiped everything from your phone
I'd appreciate if you send me the log. All you need to do is to save the file with "adb logcat -d >MyLogFile.log" after couple of minutes of this black screen. On an factory reset phone ODEXed ROM should boot very fast the first time because it doesn't have to build Dalvik.
I just tried downloading from my own link and reinstalling, everything seems OK. I also tried installing after full phone reset yesterday, it went fine too. I don't want to reset and restore everything anymore, too lazy
If it proves to be the certificate in the framework-res.apk, I may need to put the original AndroidManifest.xml back.
Hey Anton,
You can snag the logcat from here. In case anyone wants them & to clarify what I did, here are the steps I followed (similar to above but more detailed):
- Boot into CWM
adb reboot recovery- Disable voodoo lagfix
- voodoo lagfix- disable lagfix- /system lagfix off- Reboot
- Create a backup directory structure on your PC (mine is in C:\Users\username\Downloads\SGS4G)
mkdir backupscd backupsmkdir efs nandroid sdcard- Backup /efs to your PC
cd efsadb pull /efs/- Backup /sdcard to your PC
cd ..\sdcardadb pull /sdcard/- Boot into CWM
adb reboot recovery- Wipe cache
- wipe cache partition- Wipe Dalvik cache
- advanced- Wipe Dalvik Cache- Wipe battery stats
- Wipe Battery Stats- Create a nandroid backup
- +++++Go Back+++++- backup and restore- backup- Copy the backup to your PC
cd ..\nandroidadb pull /sdcard/clockworkmod/backup/- Format /data
- mounts and storage- format /data- Format /sdcard
- format /sdcard- Format /system
- format /system- Reboot into CWM (necessary for CWM to see the sdcard contents)
- +++++Go Back+++++- advanced- Reboot Recovery- Copy the ROM to the sdcard (this is from the directory in which the ROM is located on your PC)
adb push ROM-sms-T959V-GB2.3.6-antsvx.1.0.3.zip /sdcard/- Flash the ROM
- install zip from sdcard- choose zip from sdcard- ROM-sms-T959V-GB2.3.6-antsvx.1.0.3.zip- Reboot & let it sit for ~10 minutes
Sorry for the lengthy post, but I wanted to ensure there was transparency in what I did.
stephen_w,
Seems that it's not framework-res.apk issue, it's not complaining about any certificates.
A lot of unknown permissions in the log, but it's OK, we've removed some of the system packages that grant those permissions but they do more harm than good in the end.
The crash has something to do with that: *** FATAL EXCEPTION IN SYSTEM PROCESS: PowerManagerService. Hm......
Question. If after loading the ROM you shut down completely (power off) first and then boot instead of rebooting right from CWM, will it still do the same?
Btw you don't have to clean everything that extensively. Just do factory reset to erase /data and flash. Dalvik and /cache are cleared but the installer, the /system is completely overwritten anyway.
Weird...it flashed fine for me with no wipe....
I did move on and never gave it a break in....but it did work
Sent from my SGH-T959V using xda premium
AntonX said:
stephen_w,
Question. If after loading the ROM you shut down completely (power off) first and then boot instead of rebooting right from CWM, will it still do the same?
Btw you don't have to clean everything that extensively. Just do factory reset to erase /data and flash. Dalvik and /cache are cleared but the installer, the /system is completely overwritten anyway.
Click to expand...
Click to collapse
I usually don't do it that extensively at all. I was writing a process for myself in case I wanted to really clean it out So this gave me a good excuse to test it. I was having some weirdness which prompted me to write the instructions for myself.
I haven't tried shutting it down after the install. I can certainly try that for you, if you like.
So its something to do with power management. That's weird. Is there something we did to our phones before that is causing the issue now?
Sent from my SGH-T959V using xda premium
Lawful123 said:
So its something to do with power management. That's weird. Is there something we did to our phones before that is causing the issue now?
Click to expand...
Click to collapse
Doubtful. Nothing I can think of, off-hand. I have to wait until later this afternoon/evening to reflash it and try powering off vs. rebooting from recovery. If you have the chance, please feel free and let us know what happens.
After OTA update from LRX22C to LRY47I, device reboots with:
"Android is starting... Optimizing app xx of xx." (few minutes)
"Starting apps." (few seconds) "Unfortunately, System UI has stopped. Report/OK"
Whatever is pressed, pop-up just reappears.
Clearing cache from recovery restarts app optimization, but error persists.
Basically it's unusable but everything works in the background.
If e-mail arrives, notification sound is heard. Already set alarms work. Notification LED works.
Device is without any modifications, bootloader is locked and usb debugging isn't enabled.
Is there any way to access data?
Is sideloading customized kernel with usb debugging possible with locked bootloader?
Can application for wi-fi access be pushed via google play with preconfigured options and started automagically?
Anyone tried to rescue data after factory reset with dumping disk image and doing forensics?
Any other ideas are welcome.
Btw, there is a thread on Google's Nexus support group were users reported same issue:
(as a new user I can't post direct link here so search for "Android 5.1 is Here!" on google)
From one message it looks as if they are working on this but there was no official answer yet.
Have you pressed playstore? Id a similar problem and it was a playstore system app needed to be updated. Got a message when pressed playstore
zerosum0 said:
Have you pressed playstore? Id a similar problem and it was a playstore system app needed to be updated. Got a message when pressed playstore
Click to expand...
Click to collapse
I wish it would be that simple. There isn't anything on the screen except pop-up.
Hi,
I've just updated from 5.0.1 to 5.1 (Nexus 5) and I'm having the same problem. The device won't go past a black screen with the error popping up every time.
I have tried wiping the cache twice but the problem persists. I don't want to factory reset because I haven't backed up my data in ages and I'm unable to retrieve that data via USB or whatever.
I believe the problem is caused by the launcher (stock in my case), when attempting to draw the wallpaper based on the info posted in Google's productforums by another user who had the same problem (xda won't let me post the URL since my account has too few posts).
I thought of sideloading a launcher from the recovery menu, considering that maybe it will be able to draw the wallpaper and the other stuff, but I don't know if that will work as I think.
Any ideas, please? Right now my Nexus is software bricked.
heatley said:
Hi,
I've just updated from 5.0.1 to 5.1 (Nexus 5) and I'm having the same problem. The device won't go past a black screen with the error popping up every time.
I have tried wiping the cache twice but the problem persists. I don't want to factory reset because I haven't backed up my data in ages and I'm unable to retrieve that data via USB or whatever.
I believe the problem is caused by the launcher (stock in my case), when attempting to draw the wallpaper based on the info posted in Google's productforums by another user who had the same problem (xda won't let me post the URL since my account has too few posts).
I thought of sideloading a launcher from the recovery menu, considering that maybe it will be able to draw the wallpaper and the other stuff, but I don't know if that will work as I think.
Any ideas, please? Right now my Nexus is software bricked.
Click to expand...
Click to collapse
i had the same problem. i think it was a rogue setting in an app. all fixed now.
Go to settings>apps>system ui and clear the cache and restart the phone. It worked for me
---------- Post added at 06:49 PM ---------- Previous post was at 06:45 PM ----------
fpga said:
After OTA update from LRX22C to LRY47I, device reboots with:
"Android is starting... Optimizing app xx of xx." (few minutes)
"Starting apps." (few seconds) "Unfortunately, System UI has stopped. Report/OK"
Whatever is pressed, pop-up just reappears.
Clearing cache from recovery restarts app optimization, but error persists.
Basically it's unusable but everything works in the background.
If e-mail arrives, notification sound is heard. Already set alarms work. Notification LED works.
Device is without any modifications, bootloader is locked and usb debugging isn't enabled.
Is there any way to access data?
Is sideloading customized kernel with usb debugging possible with locked bootloader?
Can application for wi-fi access be pushed via google play with preconfigured options and started automagically?
Anyone tried to rescue data after factory reset with dumping disk image and doing forensics?
Any other ideas are welcome.
Btw, there is a thread on Google's Nexus support group were users reported same issue:
(as a new user I can't post direct link here so search for "Android 5.1 is Here!" on google)
From one message it looks as if they are working on this but there was no official answer yet.
Click to expand...
Click to collapse
Go to settings>apps>system ui and clear the cache and restart the phone. It worked for me
Gekko2 said:
i had the same problem. i think it was a rogue setting in an app. all fixed now.
Click to expand...
Click to collapse
But what did you do? I can't do anything, it won't show the app drawer, it won't even let me enter the PIN for the sim card. Either I do stuff from recovery or nothing, and wiping the cache didn't solve it.
heatley said:
But what did you do? I can't do anything, it won't show the app drawer, it won't even let me enter the PIN for the sim card. Either I do stuff from recovery or nothing, and wiping the cache didn't solve it.
Click to expand...
Click to collapse
i was getting the same error loop and i was trapped in the loop with no way out.
here's what i did -
1. wiped cache partition, NO factory wipe - did this 2X - problem persisted.
2. hard reset device wipe back to factory state, then synced Google data, and reinstalled all apps and load all app settings backup files - problem persisted.
3. hard reset device wipe back to factory state, then synced Google data, and reinstalled all apps. this time i did not load my app settings backup files (Nova Launcher Prime, Fancy Widgets Unlocker, Calendar Status Pro, eWeather HD, Deliveries Package Tracker) on the hunch that perhaps there was an incompatible conflicting setting with 5.1 UI and one of the old app settings backups. AND i seemed to remember that the problem started as soon as i loaded the Calendar Status Pro backup settings file. i loaded all of the backup app settings files except for that one and had no problems. then i deleted that old backup file and started fresh with Calendar Status Pro and i've had no problems since.
so my guess is that you need to do a factory wipe and then reinstall all apps fresh. there may be an old setting from an old app that's conflicting with 5.1.
this is probably not what you wanted to hear but my fix required a hard reset and then starting fresh with the culprit app. yes it's a PIA and i spent most of the afternoon and my battery life fixing this problem.
let us know what you discover.
good luck!
I had the same problem: Seems that Calendar Status Pro is causing these issues.
This seems to be a huge problem with Nexus 5 and Nexus 6 users. You can see the complaints in Google's product forum.
Google Product Forums regarding the random reboots
On Android 5.1 I have been getting random reboots. There is no way to predict when it will happen. First time I was sending a message through line and phone went to a boot loop. I thought the power button was broken/stuck. Eventually it stopped boot looping and went through optimizing apps (I think i was holding down the power button). I thought I had a bad flash so i flashed the stock android 5.1 LRY47I through fastboot using the most recent usb drivers. Also wiped the device/set to default. Worked for a while and got Google Play and Gapps errors. Again I flashed the image through fastboot, reformatted/set to default settings in recovery. The third time I was getting gapps errors again so I reflashed/reformatted image through fastboot manually and not using the flash-all.bat. It seemed to work and put in all my settings again. Again I was looking at my phone, put it down, the screen was fading for sleep mode and then it boot looped and got it working and again went to optimizing apps. It booted then 2 minutes later it happened again when swiping apps away. Then a 3rd time. Clearing the Ui seemed to temporarily stop the boot loops. I am using a N5 unlocked, stock android. I thought it was a hardware problem until I saw a large number of users having the same issue on two different devices. Is there any way to create a system log to track down this problem? Thank you for suggesting the UI cache thing, but I am assuming it will boot loop/optimize apps again soon. This seems to be a huge problem for users. I hope this will be fixed soon.
chrisinsocalif said:
This seems to be a huge problem with Nexus 5 and Nexus 6 users. You can see the complaints in Google's product forum.
Google Product Forums regarding the random reboots
On Android 5.1 I have been getting random reboots. There is no way to predict when it will happen. First time I was sending a message through line and phone went to a boot loop. I thought the power button was broken/stuck. Eventually it stopped boot looping and went through optimizing apps (I think i was holding down the power button). I thought I had a bad flash so i flashed the stock android 5.1 LRY47I through fastboot using the most recent usb drivers. Also wiped the device/set to default. Worked for a while and got Google Play and Gapps errors. Again I flashed the image through fastboot, reformatted/set to default settings in recovery. The third time I was getting gapps errors again so I reflashed/reformatted image through fastboot manually and not using the flash-all.bat. It seemed to work and put in all my settings again. Again I was looking at my phone, put it down, the screen was fading for sleep mode and then it boot looped and got it working and again went to optimizing apps. It booted then 2 minutes later it happened again when swiping apps away. Then a 3rd time. Clearing the Ui seemed to temporarily stop the boot loops. I am using a N5 unlocked, stock android. I thought it was a hardware problem until I saw a large number of users having the same issue on two different devices. Is there any way to create a system log to track down this problem? Thank you for suggesting the UI cache thing, but I am assuming it will boot loop/optimize apps again soon. This seems to be a huge problem for users. I hope this will be fixed soon.
Click to expand...
Click to collapse
i bet many problems are the result of incompatible apps/settings. mine was. try a fresh device with no apps installed and see if you get the same errors. it's easy to blame Google/Android/Lollipop but i don't think you can blame them if you install a rogue/incompatible/conflicting app or setting. Developers are not perfect and they often do not update their apps. the OS is only as stable as what you load onto it.
---------- Post added at 01:39 AM ---------- Previous post was at 01:37 AM ----------
alephh said:
I had the same problem: Seems that Calendar Status Pro is causing these issues.
Click to expand...
Click to collapse
tell me more. did you load the app backup file? how did you fix? fresh app settings?
try a fresh device with no apps installed and see if you get the same errors.
Click to expand...
Click to collapse
I did, fresh install with wipe/default and when I typed in my email address and not restoring from saved profile got a Google Play Services and Gapps error before anything was installed. The flash was through fastboot. Plus the HUGE number of users getting the reboot/optimization problem in the Google forums affecting the Nexus 5 & Nexus 6, it's definitely the software.
Gekko2 said:
i was getting the same error loop and i was trapped in the loop with no way out.
here's what i did -
1. wiped cache partition, NO factory wipe - did this 2X - problem persisted.
2. hard reset device wipe back to factory state, then synced Google data, and reinstalled all apps and load all app settings backup files - problem persisted.
3. hard reset device wipe back to factory state, then synced Google data, and reinstalled all apps. this time i did not load my app settings backup files (Nova Launcher Prime, Fancy Widgets Unlocker, Calendar Status Pro, eWeather HD, Deliveries Package Tracker) on the hunch that perhaps there was an incompatible conflicting setting with 5.1 UI and one of the old app settings backups. AND i seemed to remember that the problem started as soon as i loaded the Calendar Status Pro backup settings file. i loaded all of the backup app settings files except for that one and had no problems. then i deleted that old backup file and started fresh with Calendar Status Pro and i've had no problems since.
so my guess is that you need to do a factory wipe and then reinstall all apps fresh. there may be an old setting from an old app that's conflicting with 5.1.
this is probably not what you wanted to hear but my fix required a hard reset and then starting fresh with the culprit app. yes it's a PIA and i spent most of the afternoon and my battery life fixing this problem.
let us know what you discover.
good luck!
Click to expand...
Click to collapse
Thanks for the post. I thought the same, that some app must be causing trouble due to some misconfiguration. I've tried booting in safe mode and the problem persists. I'll try a couple things via ADB and if not I'll give up, lose all my data and wipe to factory state.
Hi All,
I'm the developer of Calendar Status
I'm not sure yet if my app is the cause for the issue but Ill happy to assist with whatever I can.
I tried to look for LRY47I but couldn't find anything .. (I did find LMY471 but not LRY471, is it typo?)
Did anyone install fresh copy (Downloaded from Play Store) and get systemui crash ?
Does anyone who restored a backup file and got this crash still have the backup file ? (can be found under sd-card/calendarstatus/preferencesBackup.xml the other files aren't relevant)
In case it's relevant, I didn't/don't have Calendar Status installed in my device yet I suffer from the System UI error.
heatley said:
In case it's relevant, I didn't/don't have Calendar Status installed in my device yet I suffer from the System UI error.
Click to expand...
Click to collapse
Well
I know it isn't "Calendar Status bug", it is definitely an Android bug which is triggered by one of the configurations in Calendar Status (and in some other apps too)
---------- Post added at 06:32 PM ---------- Previous post was at 06:22 PM ----------
I suspect this to be due to 'transparent icon'.
Is anyone who experienced the crash can confirm he had an application (any application) with transparent icon ? (transparent isn't like 'no icon', it looks like an empty spot on the status bar)
I know from one of the backup files which were sent to me it is the case, and might be why the app crashed after restore (the default is white icon while the backup file has transparent icon selected)
SagiLo said:
Well
I know it isn't "Calendar Status bug", it is definitely an Android bug which is triggered by one of the configurations in Calendar Status (and in some other apps too)
---------- Post added at 06:32 PM ---------- Previous post was at 06:22 PM ----------
I suspect this to be due to 'transparent icon'.
Is anyone who experienced the crash can confirm he had an application (any application) with transparent icon ? (transparent isn't like 'no icon', it looks like an empty spot on the status bar)
I know from one of the backup files which were sent to me it is the case, and might be why the app crashed after restore (the default is white icon while the backup file has transparent icon selected)
Click to expand...
Click to collapse
i'm currently using transparent icon with no problems. my guess is problem is a specific font/size/number of events configuration is the culprit.
Gekko2 said:
i'm currently using transparent icon with no problems. my guess is problem is a specific font/size/number of events configuration is the culprit.
Click to expand...
Click to collapse
It was a long shot...
The log doesn't say much (thank you Google).
Ill try keep looking for the issue, if anyone have more info ill be happy to get it. (backup files / scenarios to reproduce / any thoughts..)
Bug was found (and submitted to Android issues)
https://code.google.com/p/android/issues/detail?id=163385&thanks=163385&ts=1428445417
What happened was a different notification (the one shown when no events available, like when setting the events interval to small value) was built in a specific way (as described in the bug).
The restore actually restored the interval value and this is why this bug happened after restore.
I believe there are more apps doing the same as I did (it should be fine), I hope the bug will help them to fix the issue (it is an easy workaround).
Thanks for the assistance guys.
SagiLo said:
Hi All,
I'm the developer of Calendar Status
I'm not sure yet if my app is the cause for the issue but Ill happy to assist with whatever I can.
I tried to look for LRY47I but couldn't find anything .. (I did find LMY471 but not LRY471, is it typo?)
Did anyone install fresh copy (Downloaded from Play Store) and get systemui crash ?
Does anyone who restored a backup file and got this crash still have the backup file ? (can be found under sd-card/calendarstatus/preferencesBackup.xml the other files aren't relevant)
Click to expand...
Click to collapse
It was a typo, should've been LMY47I.
Frank is my testing source, I don't regularly update it unless I am testing something new.
Don't ask me for features, I won't give them because I only add what is considered essential
FRANK
Layers
Day/Night theme switcher from first M preview
Init.d support
Advanced reboot
SuperSu 2.52 flashed with the rom
Volume rocker wake
Volume rocker cursor control
Long press quick settings control
Stock Like feel, please don't ask for features
Known Bugs
Nothing else that I know of, if something doesn't work, check runtime permissions in /settings/app/
Project Fi requires setting runtime permissions in settings or it won't work once app is installed
Installation
Roms can change from update to update that sometimes you can dirty flash but if you have errors that other users don't then you will have to clean flash
First Time Installation:
Download the ROM and Gapps Below.
Connect your Nexus 5X to the PC and transfer all the zips to the root of your device’s storage.
Reboot into recovery mode (Shut down, press VolDown + Power buttons. In bootloader mode, select Recovery mode)
Wipe the following partitions: System, Data and Cache
Install the ROM zip file along with Gapps package
Let it boot. Setup now and wait for the ROM to settle.
Reboot into Recovery again and Install any other zip files you may choose to use.
Updating from previous version:
1.Download the ROM and Other Optional files ie kernel.
2.Connect your Nexus 5X to the PC and transfer all the zips to the root of your device’s storage.
3.Reboot into recovery mode (Shut down, press VolDown + Power buttons. In bootloader mode, select Recovery mode)
4.Wipe the following partitions: Dalvik-cache and Cache
5.Install the ROM zip file along with Gapps
6.Reboot now
7.Let it boot. Setup now and wait for the ROM to settle.
8.Reboot into Recovery again and Install any other zip files you choose to use.
9.If have issues with dirty flash, reboot and redo steps wiping DATA also
Sources
GPL Kernel Source: Prebuilt Aosp provided by Google
Rom Source: Click here
Changelog
Code:
11-8-2015
sprint switching on fi (sprint dm has crashed), update 2 fixed camera
11-7-2015
Update to r26, add support for bullhead
Removed .25 and .75 animation options
Removed ambient display revert
(Gotta remerge them cause of merge conflicts, just was trying to get bullhead up and running.)
Added back debugging code so I can debug everything and find any hidden errors
Downloads
Current Build = https://www.androidfilehost.com/?fid=24269982086990814 11-8-2015 update 2
Gapps = https://androidfilehost.com/?fid=24269982086987891 banks
Current layers themes will only work on light themes until adapted
OT talk is welcomed in my threads and development is done in the open. I encourage involvement in the project in any way.
Please do not complain about OT, it encourages a fun and relaxed environment
Like the work I did, consider donating. I'm currently not working so it helps feed me
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=BPFLE54YPRV92
Yes, my PayPal account is thatguy32404, I like to keep my banking stuff separated from my social account
XDA:DevDB Information
Frank, ROM for the LG Nexus 5X
Contributors
sykopompos
Source Code: https://github.com/marshmako
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 11-8-2015 update 2
Stable Release Date: 2015-11-08
Created 2015-11-08
Last Updated 2015-11-07
Found the sprintdm bug, beanstown fixed it up for me
Going to flash this, love your work on layers. I'm sure I'm gonna enjoy this!
Edit: It booted, with a little bit of nostalgia, lollipop boot animation with a twist. nice! However it went straight into "android is optimizing" even after a clean flash. Will report back after I've played a little.
k.s.deviate said:
Going to flash this, love your work on layers. I'm sure I'm gonna enjoy this!
Edit: It booted, with a little bit of nostalgia, lollipop boot animation with a twist. nice! However it went straight into "android is optimizing" even after a clean flash. Will report back after I've played a little.
Click to expand...
Click to collapse
Did you make sure to wipe your caches? Coming from the factory image, you should mount your system in twrp, wipe it, wipe dalvik and dalik-caches and most likely data
I'm working on fixing the camera, didn't realize it was broken till I took a actual picture (I just loaded it up and checked but didn't take a picture)
sykopompos said:
Did you make sure to wipe your caches? Coming from the factory image, you should mount your system in twrp, wipe it, wipe dalvik and dalik-caches and most likely data
I'm working on fixing the camera, didn't realize it was broken till I took a actual picture (I just loaded it up and checked but didn't take a picture)
Click to expand...
Click to collapse
I didnt mount and wipe.. crap. i temp went back to my backup and now my password isn't recognized..
Edit: a proper wipe and restore did not restore my password.
k.s.deviate said:
I didnt mount and wipe.. crap. i temp went back to my backup and now my password isn't recognized..
Edit: a proper wipe and restore did not restore my password.
Click to expand...
Click to collapse
I had that even on stock
sykopompos said:
I had that even on stock
Click to expand...
Click to collapse
ive restored a few times and never encountered it until now. did a factory reset to solve.
k.s.deviate said:
ive restored a few times and never encountered it until now. did a factory reset to solve.
Click to expand...
Click to collapse
I had it the very first time after I flashed twrp ?
11-8 update 2 is up. Camera and fi switching to sprint is fixed thanks to beanstown (stupid symlinks)
As soon as Graphite is stable on stock I'm flashing this bad boy.
Cheers mate.
Frank up and running
Elementalx kernel has anyone managed to boot...
tried flashing zip not booting
Nice work, installed correctly. Sound levels is very low tho.
My only question is if Android Pay is verified working?
added to index
[INDEX] LG NEXUS 5X Resources Compilation Roll-Up
vampire36 said:
Frank up and running
Elementalx kernel has anyone managed to boot...
tried flashing zip not booting
Click to expand...
Click to collapse
I have to take a look at what flar is doing on the 5x
NisseGurra said:
Nice work, installed correctly. Sound levels is very low tho.
Click to expand...
Click to collapse
We used to have to change out some files on the n5, probably is that.
I'll take a look into it later
buru898 said:
My only question is if Android Pay is verified working?
Click to expand...
Click to collapse
? Android pay works by cts verification, people are having a hard enough time on even keeping it working on stock with root, it will be a long while till we get it on working on aosp.
Been running it for few hours now, no major bugs so far.
Missing the camera app in the rom tho.
Using snap camera and it is as good as the stock one
NisseGurra said:
Been running it for few hours now, no major bugs so far.
Missing the camera app in the rom tho.
Using snap camera and it is as good as the stock one
Click to expand...
Click to collapse
I remove old aosp apps since most people replace them with Google apps or equivalent, that includes aosp browser, MMS, and a few others which is pretty standard in aosp ROMs since the apps still look like ics (I kept gallery because quickpic was bought out)
sykopompos said:
I remove old aosp apps since most people replace them with Google apps or equivalent, that includes aosp browser, MMS, and a few others which is pretty standard in aosp ROMs since the apps still look like ics (I kept gallery because quickpic was bought out)
Click to expand...
Click to collapse
Ok, i am old timer so i added some apps back: aosp browser, old calendar etc. I still looking for an functional mms.apk, the one from cm etc gives fc.
Very good ROM, no lock function
NisseGurra said:
Ok, i am old timer so i added some apps back: aosp browser, old calendar etc. I still looking for an functional mms.apk, the one from cm etc gives fc.
Click to expand...
Click to collapse
There is a themable MMS by Dave Wilson that works for aosp.
I don't have the link but I will post it once I get it from Dave
Hello,
something went wrong during my Update from 7.1.0 (Europe, NDE63U, Nov 2016) to 7.1.1 (NMF26O, Dec 2016). My System UI behaves cracy. Examples:
- click on the Multitask Button doesn't pop up recent apps, does actually nothing
- long click on home shows the assistant icon but nothing happens
- I don't get any notification (Mail, SMS, Telegram, ...) nothing
- if I pull down to the notifications and quick settings I can change WLAN and BT.
-- if I click on Mobile Data it is always off although I seem to be connected.
-- if I clicked on mobile data quick tile and close / reopen the notifications area I still see the mobile data view
-- I can't pull down the notifications again to get the bigger setting toggles
- I tried Google Pixel Launcher as well as the Microsoft Arrow Launcher, both the same
Else the system behaves OK, I can start all Apps, they behave normally. Also the new dt2w or l2w work.
How can I reset my System UI without resetting the whole phone? I am bootloader unlocked and rooted (v2.78 SR3 without TWRP installed).
Thank you very much!
KobiP
Last the story how I reached that state:
- I updated from 7.1.0 to 7.1.1 by flasing the imgs manually. Something went wrong and I got stuck in a bootloop
- reflashed 7.1.1 again. This time it booted but I got a message that something is wrong and I should contact the vendor. I could not get any mobile connection, WIFI was working
- Nothing except reflashing 7.1.0 helped. With 7.1.0 I got already the behaviour described above
- Flashed again the 7.1.1 with the flash-all.bat (removed the -w parameter to keep my data). This time I could boot 7.1.1 and get cellular connection, no error message appeared. But still the cracy behaviour described above.
Get Google firmware package and flash all . You can chase your tail or spend 15 min to properly flash.
Sent from my Pixel using Tapatalk
maulich said:
Get Google firmware package and flash all . You can chase your tail or spend 15 min to properly flash.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Hey,
I have used the flash all bat without the "-w" flag. Thats how I could get 7.1.1 running with the Cellular connection. Still cracy System UI behaviour.
This is slightly off topic, bit I'm going to throw it in here anyway.
I'm dual booting, stock with elementalX kernel on slot_a, rooted on slot_b. I have been using the altered flash all scripts in post 2 or3. It never works. The initial firing flashes only the bootloader and the radio, I have to copy the update command section from the .bat file and paste.it manually into fastboot for the system and vendor to update.
I don't know if others may have been copying the scripts and altering them to their own needs, but the final step in the batch file has never worked for me as is.
dtrud0h said:
This is slightly off topic, bit I'm going to throw it in here anyway.
I'm dual booting, stock with elementalX kernel on slot_a, rooted on slot_b. I have been using the altered flash all scripts in post 2 or3. It never works. The initial firing flashes only the bootloader and the radio, I have to copy the update command section from the .bat file and paste.it manually into fastboot for the system and vendor to update.
I don't know if others may have been copying the scripts and altering them to their own needs, but the final step in the batch file has never worked for me as is.
Click to expand...
Click to collapse
Hey,
you are using Linux? I could just run the script in Windows Batch and it was working smooth.
To fix the Issue I tried to clear the Data of the System UI, Settings, Google and loads of other Google Apps. Nothing helped. Then I realised that I could not even reach my Data via USB as I could not see the Notification where I can change between charging and data mode. So I made a Titanium Backup to Google Drive and reset my phone with the original flash-all.bat Script (with -w Parameter). It was working smooth, now my phone is reset and thanks to Titanium I have most of my stuff back.
Cheers