Related
I really need to be able to post in the development section but sadly this forum doesn't allow it for noobs.
I did the following:
Flashed the LBC Wipe zip
Flashed LBC 0.6
Ran through the setup procedure
Ran Titanium Backup to restore previous apps
Flashed Sense 3 3D launcher
After than the phone gets stuck at the green android animation. If i press the power button it will do the CRT animation and turn the screen off. Likewise if I press it again i see the CRT animation on the android animation comes back.
This suggests that the phone is trying to load sense but is getting stuck. Can someone raise the question for the correct order to install it in the development section?
Thankfully I have managed to restore back to base LBC 0.6 so it isn't an urgent matter.
Thanks.
Another thing i noticed is that when I run the Market for the first time, it seems to automatically install a number of apps that have been removed from this rom such as maps.
Is there any way to stop it from happening?
Toxicshadow said:
Another thing i noticed is that when I run the Market for the first time, it seems to automatically install a number of apps that have been removed from this rom such as maps.
Is there any way to stop it from happening?
Click to expand...
Click to collapse
Google backups and synchronises settings (including apps) to your Google account. Whenever I add a Google account in a fresh ROM it also starts downloading the apps I've previously had. There should be an option to disable this in settings. If I remember correctly, you can choose this during the initial setup.
Toxicshadow said:
I really need to be able to post in the development section but sadly this forum doesn't allow it for noobs.
I did the following:
Flashed the LBC Wipe zip
Flashed LBC 0.6
Ran through the setup procedure
Ran Titanium Backup to restore previous apps
Flashed Sense 3 3D launcher
After than the phone gets stuck at the green android animation. If i press the power button it will do the CRT animation and turn the screen off. Likewise if I press it again i see the CRT animation on the android animation comes back.
This suggests that the phone is trying to load sense but is getting stuck. Can someone raise the question for the correct order to install it in the development section?
Thankfully I have managed to restore back to base LBC 0.6 so it isn't an urgent matter.
Thanks.
Click to expand...
Click to collapse
(Opps, Must add that if you use EXT4 recovery and the associated APK recently released then remove the APK for it from the LBC v0.6.0 ZIP file and ensure that you un-install the program (not recovery) from your v0.5.4 system once you've restored it as the program was going through several pre beta releases and fails to upgrade after v0.6.0 install otherwise).
I detailed my install order HERE. Now if you don't have a v0.5.4 backup, I'd say simply run a full wipe and then proceed in the order that I did.
Even though my stages above don't mention the 3d rosie that's as I personally don't like it, but don't fear I did try it. I followed the steps above, then rebooted the device , setup as per normal then rebooted back to RECOVERY took a backup..(as didn't want to go through that process again!) and then flashed the 3D Launcher.ZIP to try it out - which I did but choose to revert to the backup as it wasn't for me!
Good luck.
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.
The ROM is retired. The final version can be downloaded from here:
http://forum.xda-developers.com/showpost.php?p=58493801&postcount=339
Click to expand...
Click to collapse
This is a tweaked versions of CARBON-JB-UNOFFICIAL-B11 so all credit goes to killersloth for the ROM. Without his work this ROM wouldn't be possible. So if you like this ROM please go to the CARBON ROM thread and click the "Thanks" button.
Changes Made:
Replaced Trebuchet launcher with Nova launcher.
Replaced stock gallery with Sony Z Album and Movie app (Facebook & Twitter integration working.)
Added Sony Z Walkman app with UPNP/DLNA Media Server.
Replaced the default kernel with the kernel from CM10.1 Stable by verygreen.
Added BeatsAudio+xLoud+ClearAudio for audio effects and ViPER4Android for the sound engine. Settings I am using.
Added Mobile BRAVIA® Engine for improved video processing.
Modified Adobe Flash 11.1 with Hulu support.
Host level ad blocking. If you are having issues with adblocking see attachments to remove it.
Forced all rendering to be done on the GPU. Should help with gaming and make things more smoother. To help improve performance even further see this post.
GoogleEars.
Kick Ass Kernelizer
Auto-zipalign and defragdb on boot
Auto Calibration on boot. Only does a few programs each boot. So may take a few reboots to calibrate all of them.
Plus many improvements taken from this thread.
I also added some terminal commands.
Run each command with SU first then the command.
fixfc - Fix apps force closing.
sclean - Clean the dalvik cache and cache partition
v6 - run the V6 SuperCharger script. I would run this as soon as the ROM is setup..
Know bugs
Not a bug as such but something you should be aware of. It does take a few reboots to optimise all the apps.
V4A XHiFi may do a hot reboot when first getting root, same with Root Browser. This will only happen once and will work fine afterwards. This is only normally an issue if you try getting ROOT on first boot. On the second reboot this doesn't happen.
Wifi will turn off then back on while it is setting up wl1271-nvs.bin. Once the file is created Wifi shouldn't disconnect.
Any more issues please report them.
Xperia-2.3.9-CARBON-JB-B11-ovation.zip - 294.19 MB
MD5: 05483bc421eb793c9ccf0113323b406d
For the latest version using Google Now Launcher use this rom: http://forum.xda-developers.com/showpost.php?p=58493801&postcount=339
Wallpaper: http://blankid.deviantart.com/art/Escape2-347788407
If you would like to use the WALKMAN app from the Sony Xperia Z Ultra you can do so by flashing this: Xperia-Ultra_WALKMAN_SemcMusic.zip. Make sure you boot into the ROM before flashing. If you flash this without booting into the ROM first it will not work.
Most of the features in the Sony Xperia Z Ultra WALKMAN are working but "Music Unlimited" service isn't.
Thank you, I will give it a try.
Do we use the gapps from the original carbon threads?
And how do you flash the scrips? Just like any other zip file? Can it be done when installing this ROM ?
JDMpire said:
Do we use the gapps from the original carbon threads?
And how do you flash the scrips? Just like any other zip file? Can it be done when installing this ROM ?
Click to expand...
Click to collapse
I just added the scripts as a separate download so other devs can take a look at them without downloading the whole ROM. All the scripts are included in the ROM. Everything you need is built into the ROM. Just download it and install.
unstable
I installed on top of Carbon B9 without wiping anything and everything was forceclosing.Then I wiped cache partiion and Dalvick cache and reinstalled ,it was usable thistime but several apps still forceclosing including Chrome,I went back to Carbon.
akramarshad said:
I installed on top of Carbon B9 without wiping anything and everything was forceclosing.Then I wiped cache partiion and Dalvick cache and reinstalled ,it was usable thistime but several apps still forceclosing including Chrome,I went back to Carbon.
Click to expand...
Click to collapse
If you did not install with full wipe I am note sure it is fair to mark it as unstable. Did you even attempt to clear the app data for the apps foreclosing?
have not tried this yet but just thought labeling the effort as unstable prior to proper install is not fair.
akramarshad said:
I installed on top of Carbon B9 without wiping anything and everything was forceclosing.Then I wiped cache partiion and Dalvick cache and reinstalled ,it was usable thistime but several apps still forceclosing including Chrome,I went back to Carbon.
Click to expand...
Click to collapse
Just installed with full wipe restoring apps and data from TB. So far everything is ok.
Feels slightly less laggy than B9.
Dunno about battery life yet.
This is working great for me.
I did a dirty flash over RootBox and it's really nice.
Been the best rom for me on my Nook so far. Pinguy1982, please keep the thread updated mate.
Only issue I had was my usual
Android.process.acore has stopped
Which I resolved by following the text below. (cribbed from somewhere on the net)
If you go to Settings/Applications/Manage Applications/ then choose the All tab. Scroll down to Contacts open it and clear the data cache. Now do the same again but this time open Contact Storage and also clear the data cache. This issue is related to an Android bug and affects many devices. It's related to apps that use the sync function.
Works for me.
Cheers all
mcord11758 said:
If you did not install with full wipe I am note sure it is fair to mark it as unstable. Did you even attempt to clear the app data for the apps foreclosing?
have not tried this yet but just thought labeling the effort as unstable prior to proper install is not fair.
Click to expand...
Click to collapse
I agree completely and would urge the poster to revise his comment or certainly remove the subject. Way too hasty and unfair to make such a quick judgment certainly in the absence of a full or data wipe.
RustedRoot said:
I agree completely and would urge the poster to revise his comment or certainly remove the subject. Way too hasty and unfair to make such a quick judgment certainly in the absence of a full or data wipe.
Click to expand...
Click to collapse
Sorry if I offended you.My understanding is that you wipe data only if you are installing in place of different ROM.It was carbon on top of Carbonand I did not feel I needed to wipe data partition.
akramarshad said:
Sorry if I offended you.My understanding is that you wipe data only if you are installing in place of different ROM.It was carbon on top of Carbonand I did not feel I needed to wipe data partition.
Click to expand...
Click to collapse
Dude it's all cool. But I have changed a fair bit to the ROM so just installing over it probably won't work. I have made drastic changes to how dalvik works so using pre-installed apps from a previous install probably won't work.
Sent from my Nook HD+ using Tapatalk HD
Do you mind building a version for the Nook HD ?
so using apps from titanium backup would be a problem?
bckrupps said:
so using apps from titanium backup would be a problem?
Click to expand...
Click to collapse
Apps no, dalvik cache maybe. Restoring apps settings and the apps won't be a problem, but using the dalvik cache might be.
The cache is in /data/dalvik-cache. Using that maybe an issue.
pinguy1982 said:
Apps no, dalvik cache maybe. The apps settings and the app won't be a problem, but using the dalvik cache might be.
The cache is in /data/dalvik-cache. Using that maybe an issue.
Click to expand...
Click to collapse
thanks.I always clear out dalvik cache anyway when I try new stuff. I was thinking of trying it. the new build of cm 10.1 seems to match up with my tablet perfectly so we will see. thanks for the ROM. the more the better
akramarshad said:
I installed on top of Carbon B9 without wiping anything and everything was forceclosing.Then I wiped cache partiion and Dalvick cache and reinstalled ,it was usable thistime but several apps still forceclosing including Chrome,I went back to Carbon.
Click to expand...
Click to collapse
I did this too, but wiped dalvik, no force closes, but status bar is gone and can't get it back... going to try flashing again...
Just flashed a couple of hours ago and seems pretty rad so far. I'll give it some time to "settle" before passing judgement. Definitely like the idea!
Good to see more options around here. My hat goes off to all devs.
Sent from my Nook HD+ using xda app-developers app
Just flashed it ... Can't see the option "Reboot into recovery" when holding the power button. Is there anyone I can enable it ?
nocloo said:
Just flashed it ... Can't see the option "Reboot into recovery" when holding the power button. Is there anyone I can enable it ?
Click to expand...
Click to collapse
Settings-system-power menu-reboot menu
Battery drain so far seems to be no worse than B9 for me.
Definitely like this ROM, it is faster and smoother than any other I tried for my Nook, seems quite stable as well (no random reboots etc.)
I start with a fresh wipe of my phone and then install BeanStalk with gapps (I'm currently using BS version 4.4.275 with gapps 20140105. Everything is fine for months. Then a couple of apps will start to crash a few times (the camera, dialer, browser and google apps). I've stopped using titanium backup and clockwork mod to restore my data because they were causing issues. Then the force closes become more and more frequent. I ran fix permissions and i have know clue if it helped or not. Then finally all hell breaks loose and everything begins to force close and give errors of no space left on phone. No launcher will stay open everything just bugs out. This seems to be an on going matter. It doesn't seem to resolve no matter what rom I run. I've gone through every folder sizing it and my phone is not out of space. I am getting very frustrated with my Infuse. I don't understand what some of the stuff means in my catlog file. If someone could help I'd greatly appreciate it.
i found out that Google+ and Google Drive might be the cause (such as when you upload or backup your photos to those clouds)
if you have time, go read those last 10 pages of BeanStalks, you will see what others have offered to resolve this issues
as for me, I'd do full wipe, specially format the sdcard0 (keep the Rom and Gapps to your SDcard1), and stop using the two Google services mentioned above. and use another Gapps (I am using the minimal one) Good luck!
Same problem with Unofficial CM 11.2 also
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Unable to get RSA prompt
Well I went ahead with a factory reset, installed Unofficial CM11_2 from Scott. Got the latest gapps from goo.im and phone seems normal again. But that is the expected behavior untill it starts acting up again.
I tried a lot to connect the phone through ADB and each time it remains unauthorized.
I tried on 2 different laptops, Windows 7, Windows Vista as well as Ubuntu - it always remained unauthorized and no matter what i tried ... changing USB ports , OS machines...nothing helped.
I never got the RSA signature prompt on my phone so could not do anything with ADB.
Any body has any ideas ?
hemen_kap said:
Well I went ahead with a factory reset, installed Unofficial CM11_2 from Scott. Got the latest gapps from goo.im and phone seems normal again. But that is the expected behavior untill it starts acting up again.
I tried a lot to connect the phone through ADB and each time it remains unauthorized.
I tried on 2 different laptops, Windows 7, Windows Vista as well as Ubuntu - it always remained unauthorized and no matter what i tried ... changing USB ports , OS machines...nothing helped.
I never got the RSA signature prompt on my phone so could not do anything with ADB.
Any body has any ideas ?
Click to expand...
Click to collapse
This has been an issue for a while, if the problem is showing up like this:
http://forum.xda-developers.com/showthread.php?t=2175261
Honestly haven't tried ADB with the newer stuff (namely Beanstalk), I just know that ADB as been a problem in the past for Scott's ROM's.
joel.maxuel said:
This has been an issue for a while, if the problem is showing up like this:
http://forum.xda-developers.com/showthread.php?t=2175261
Honestly haven't tried ADB with the newer stuff (namely Beanstalk), I just know that ADB as been a problem in the past for Scott's ROM's.
Click to expand...
Click to collapse
Yes, it is the same problem. Any suggestions ? How is the AOSP based Carbon ROM, any idea if it has the same issue too ?
hemen_kap said:
Yes, it is the same problem. Any suggestions ? How is the AOSP based Carbon ROM, any idea if it has the same issue too ?
Click to expand...
Click to collapse
Not sure about the other ROM's. I could go on a flashing journey, but I have two new devices I'm getting adjusted to right now. If you are not tied down to CM (don't know if it's your DD), I would suggest trying Carbon or CyanFox.
Me, I didn't need ADB that much at the time so I stuck with what I have. Not a solution, but I hope you find a ROM that works (partnered with a minimal gapps).
joel.maxuel said:
Not sure about the other ROM's. I could go on a flashing journey, but I have two new devices I'm getting adjusted to right now. If you are not tied down to CM (don't know if it's your DD), I would suggest trying Carbon or CyanFox.
Me, I didn't need ADB that much at the time so I stuck with what I have. Not a solution, but I hope you find a ROM that works (partnered with a minimal gapps).
Click to expand...
Click to collapse
Unfortunately the infuse is the only phone I have (so my DD)...but the lure to test the ADB on carbon is also compelling for me. Let me try moving to a non smart phone and try this out.
OK. So i installed the Carbon KK nightly, and encountered the same issue. adb devices always lists the phone as
0123456789ABCDEF unauthorized.
Also i never received the rsa prompt...
Moreover the device key seems to suggest it is some default value as compared to an actual device key.
Got it Working !!!
Ok so finally got it working.
I moved away from Scott's Unofficial CM11_2 on my daily driver and moved to Carbon ROM. Loving the new rom so far.
Once i moved to this ROM, I started adb on my desktop (adb kill-server, adb start-server) and was waiting
then on phone enabled Developer options and Android debugging over USB and connected the phone to desktop, and zingggg I get the RSA prompt.
One important thing it read is that you phone should be unlocked when you connect it to your desktop, so in case you have things like PIN or gestures that lock your screen....ensure that your screen is not locked when the phone is being connected.
Not sure if this was the issue or if it was the CM rom,,,but issue is resolved, I am loving Carbon...so not going back to CM to check the lockscreen theory....but worth a try for someone who is pulling his/her hair out like i was.
Ciao !!!
---------- Post added at 05:00 PM ---------- Previous post was at 04:41 PM ----------
missed mentioning that do not worry about the device id of 0123456789ABCDEF....i noticed it does not change for me even when adb connects properly.
It is the unauthorised state that needs to change to device.
What's the default launcher on Carbon, or does it give you a choice like Beanstalk?
Will be retiring the Infuse soon, so am thinking on what ROM to put on when I go to sell it (or give away). The requirement is that is not overwhelming to a new user. Cyanogenmod has a lot of customization, but it doesn't necessarily get in the way. I'd call it borderline overwhelming. Beanstalk is quite overwhelming, because you are forced to pick a launcher right from the beginning (even though I like it for the Jellybean qualities).
Because of these, I just may return it to stock, but have it rooted and with CWM.
joel.maxuel said:
What's the default launcher on Carbon, or does it give you a choice like Beanstalk?
Will be retiring the Infuse soon, so am thinking on what ROM to put on when I go to sell it (or give away). The requirement is that is not overwhelming to a new user. Cyanogenmod has a lot of customization, but it doesn't necessarily get in the way. I'd call it borderline overwhelming. Beanstalk is quite overwhelming, because you are forced to pick a launcher right from the beginning (even though I like it for the Jellybean qualities).
Because of these, I just may return it to stock, but have it rooted and with CWM.
Click to expand...
Click to collapse
I do not see any option to select a launcher like Scotts CM had. So i guess there is no direct option to select it.
Quick search in the running apps shows Launcher 3 running, and apk also available in the priv-app folder in rom, so can conclude launcher is Launcher3.
I did not find it overwhelming in any way.
-Hemen
hemen_kap said:
I do not see any option to select a launcher like Scotts CM had. So i guess there is no direct option to select it.
Quick search in the running apps shows Launcher 3 running, and apk also available in the priv-app folder in rom, so can conclude launcher is Launcher3.
I did not find it overwhelming in any way.
-Hemen
Click to expand...
Click to collapse
I flashed it last night (latest nightly), and it gave me the option of either Launcher3 or Google Now Launcher. I think if someone who was new to the device would be stumped a little by this, but would probably select the Google Now one (the question would be would they press once or always) and be done with it.
Having something recognizable runs at an advantage here compared to Beanstalk, where, unless you know CyanogenMod (or have played with a lot of launchers) you wouldn't know what to select. That would be overwhelming.
Anyway, I wiped the data again, breezed through setup (skipped everything but language and time zone), so it's all ready to go. If need be I can get them set up with a network and Google account before I throw them to the wind.
EDIT:
I see why I got the prompt ... I used the Paranoid Android micro apps package, which includes ... the Google Now Launcher.
hemen_kap said:
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Click to expand...
Click to collapse
Hi,
I was using CM 10.1 from Scott for like a year and didn't have any trouble at all, really the best ROM. Only had two small problems: wouldn't film on 720p without bugging, and MHL to HDMI was not working.
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Sent from my SGH-I997 using XDA Free mobile app
jloibman said:
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Click to expand...
Click to collapse
Not sure about this, but I think CM 11.2 is referred to as KitKat 4.4.4, which would be latest in the CM thread. So you are probably already running it.
Sent from my Asus MeMO Pad 8"
jloibman said:
Hi,
I was using CM 10.1 from Scott for like a year and didn't have any trouble at all, really the best ROM. Only had two small problems: wouldn't film on 720p without bugging, and MHL to HDMI was not working.
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Sent from my SGH-I997 using XDA Free mobile app
Click to expand...
Click to collapse
apart from the issues that i mentioned - my experience with CM 11.2 has been great. There are some obvious things like MHL etc that do not work, but those are known issues.
joel.maxuel said:
I flashed it last night (latest nightly), and it gave me the option of either Launcher3 or Google Now Launcher. I think if someone who was new to the device would be stumped a little by this, but would probably select the Google Now one (the question would be would they press once or always) and be done with it.
Having something recognizable runs at an advantage here compared to Beanstalk, where, unless you know CyanogenMod (or have played with a lot of launchers) you wouldn't know what to select. That would be overwhelming.
Anyway, I wiped the data again, breezed through setup (skipped everything but language and time zone), so it's all ready to go. If need be I can get them set up with a network and Google account before I throw them to the wind.
EDIT:
I see why I got the prompt ... I used the Paranoid Android micro apps package, which includes ... the Google Now Launcher.
Click to expand...
Click to collapse
You can download the Nova Launcher from the google play store if you want to have the same experience as with Scotts Beanstalk. I love the carbon ROM but I am so accustomed to the Nova launcher that I cant live without it.
hemen_kap said:
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Click to expand...
Click to collapse
OK the exact same problem has started again today on Carbon ROM. Wonder if this is a Cyanogen thing, as that seems to be common between the two.
Anyone else facing this ?
-Hemen
hemen_kap said:
OK the exact same problem has started again today on Carbon ROM. Wonder if this is a Cyanogen thing, as that seems to be common between the two.
Anyone else facing this ?
Click to expand...
Click to collapse
Hmm, don't think I kept a ROM on my Infuse long enough to encounter this problem (except for my several months with CM 10.1, no issues). As for other phones, I use Jellybean on my semi-retired HTC and did not have this problem (closest I came was when I tried out Fly-On mod - lag closures often). But I don't think It's a Jellybean problem.
I think (and this may have been covered already) this has to do with the piddly datadata partition filling up. One way to check is open a terminal emulator (app on the phone of adb shell) and type:
Code:
df
Look for datadata in that listing. If it is in the 90% range, that spells trouble. If that is the case, you could try one of two solutions.
I don't know what possessed the developers to separate the data partitions in KitKat (I know, for "performance reasons") but leave 1/2 a GB for it. Lower end phones these days give you twice that.
Over the past few years or so I've installed ROMs going back to ICS. 99% of the time there was absolutely no issue. I habitually do a (1) factory wipe, (2) dalvik wipe, (3) system format, (4) sdcard0 format, (5) install ROM zip, (6) install gapps, (7) wipe cache and (8) wipe dalvik.
In the hundreds of ROMs I've installed and tested, 1 or 2 were bad compiles, and everyone soon knew it. They were immediately removed from any host site. So, if you're having issues, (1) install you ROM as above, (2) perhaps install a smaller gapps, and/or (3) check that you're not overloading your phone from the PlayStore.
The last and rarest issue could be your phone, but rule of thumb that works 99% of the time is: (1) assume it's always your fault first, and (2) read, read, read, read, read.
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