Hey guys,
Is it possible to make the "new update available" notification that appears when a new nightly is available show the date/name of the update? Maybe as an expandable? It's really just a convenience thing - 1 click less to determine whether to flash or dismiss (I don't always flash every new nightly). If I didn't flash the nightly from the other day the notification (from the day I didn't flash) will pop up even if there is no new update/more recent update.
I hope you know what I mean .
Thanks for your work anyway
chuSmu said:
Hey guys,
Is it possible to make the "new update available" notification that appears when a new nightly is available show the date/name of the update? Maybe as an expandable? It's really just a convenience thing - 1 click less to determine whether to flash or dismiss (I don't always flash every new nightly). If I didn't flash the nightly from the other day the notification (from the day I didn't flash) will pop up even if there is no new update/more recent update.
I hope you know what I mean .
Thanks for your work anyway
Click to expand...
Click to collapse
this feature has been implemented in recent nightlies i believe :good:
spiderman_pink said:
this feature has been implemented in recent nightlies i believe :good:
Click to expand...
Click to collapse
Can you please point me in the right direction to find this feature? I can't find it...I'm on yesterday's nightly.
Thanks.
Edit: Apparently there is currently a problem with this feature which I believe is just found under "About phone". See this post:
http://forum.xda-developers.com/omni/general/omnirom-ota-nexus-5-t2883226
Related
Hi guys most of you might find this question silly but there are some of us newcomers who are still getting into this!
So, I rooted my phone, have ROM Manager and CWM Recovery, version 3 and my question is how we're going to update to official GB when it becomes available? Will we do it through official T-Mobile update, or will some of you guys make it available for us?
Thank you all!
Yes...
you should be about to get it either way. If you get the official update you will probably lose root... If you wait a few there will be a rooted version posted by one of the many xda members...
Sent from my butt using XDA Premium App
BobbyDukes707 said:
Yes...
you should be about to get it either way. If you get the official update you will probably lose root... If you wait a few there will be a rooted version posted by one of the many xda members...
Sent from my butt using XDA Premium App
Click to expand...
Click to collapse
One more dumb question: Why is everybody so excited about the official GB update, when we have right now a few GB leaked versions with some custom ROMs (Bionix from TeamWhiskey, etc... ) available, for which as I hear, many say are excellent? Is this official one gonna be better in any significant way than these custom already out? Thanks! )
krekabl said:
One more dumb question: Why is everybody so excited about the official GB update, when we have right now a few GB leaked versions with some custom ROMs (Bionix from TeamWhiskey, etc... ) available, for which as I hear, many say are excellent? Is this official one gonna be better in any significant way than these custom already out? Thanks! )
Click to expand...
Click to collapse
It will come with an official GB kernel and hopefully updated battery drivers and A2DP functionality...Amongst other LG fixes (again, hopefully).
sryan1983 said:
It will come with an official GB kernel and hopefully updated battery drivers and A2DP functionality...Amongst other LG fixes (again, hopefully).
Click to expand...
Click to collapse
OK, I get it... So, all these unofficial GBs are sort of limited because they lack these LG stuff they're (hopefully) putting into the official one. That's why it's smart to wait a bit more.
Hopefully it will fix most or all the problems.
Sent from my LG-P999 using XDA Premium App
krekabl said:
OK, I get it... So, all these unofficial GBs are sort of limited because they lack these LG stuff they're (hopefully) putting into the official one. That's why it's smart to wait a bit more.
Click to expand...
Click to collapse
Yes, that's the case. The leak has issues (which makes sense, it's not a finished build), and almost all Gingerbread mods are based on the leak so they have the same issues. I know CM7 is using the Gingerbread source instead and has fixed a lot of the issues, but not all of them.
The official update is not only going to be completely stable (hopefully) but will come bundled with better drivers/kernel support which will fix most of the common issues with the phone (hopefully).
I've gone through an Over The Air update to Android before, and if it's like what I experienced, you're going to get a pop-up that asks if you want to update now or later. Choose later if you want to keep root, someone here will have the official build rooted probably within the hour but definitely within the first couple of days.
In the mean time though, don't be scared of trying out one of the ROMs that are available. I swear by CM7, but I've heard wonderful things about EagleBlood and Ultimate too.
LordButtersI said:
Yes, that's the case. The leak has issues (which makes sense, it's not a finished build), and almost all Gingerbread mods are based on the leak so they have the same issues. I know CM7 is using the Gingerbread source instead and has fixed a lot of the issues, but not all of them.
The official update is not only going to be completely stable (hopefully) but will come bundled with better drivers/kernel support which will fix most of the common issues with the phone (hopefully).
I've gone through an Over The Air update to Android before, and if it's like what I experienced, you're going to get a pop-up that asks if you want to update now or later. Choose later if you want to keep root, someone here will have the official build rooted probably within the hour but definitely within the first couple of days.
In the mean time though, don't be scared of trying out one of the ROMs that are available. I swear by CM7, but I've heard wonderful things about EagleBlood and Ultimate too.
Click to expand...
Click to collapse
I have heard that official updating the rooted phone could actually brick it? And when a mod is nightly version, does it mean it it not completely stable? I am interested in CM7, but I could not find a stable version on their site.
Thanks!
i have question also since it's related to thread title. i'm running stock right now but rooted. once i update to gingerbread cm7, will i have to install all apps and settings all over? and will call log and stuff like that disappear also?
dn3g3l said:
i have question also since it's related to thread title. i'm running stock right now but rooted. once i update to gingerbread cm7, will i have to install all apps and settings all over? and will call log and stuff like that disappear also?
Click to expand...
Click to collapse
You should be able to get all of that stuff after startup my hitting the square boxes in the initial setup. Worked for me yesterday with the Eagleblood 2.3.4 ROM, when someone recommended it to me rather than Titaniumbackup which screwed up my phone a lot because I went from Froyo to GB
dn3g3l said:
i have question also since it's related to thread title. i'm running stock right now but rooted. once i update to gingerbread cm7, will i have to install all apps and settings all over? and will call log and stuff like that disappear also?
Click to expand...
Click to collapse
When I did an OTA update, it kept all of my apps and settings. I can't remember if it preserved call log.
I have heard that official updating the rooted phone could actually brick it? And when a mod is nightly version, does it mean it it not completely stable? I am interested in CM7, but I could not find a stable version on their site.
Thanks!
Click to expand...
Click to collapse
I don't know if it will brick or not, my OTA was not rooted. And CM7 nightlies are NOT completely stable, but they're on build 58 by now and the ROM works perfectly fine. The only issue I can see with the phone is the top bar they added to the notifications menu that has toggle-able settings like WIFI, GPS, etc sometimes doesn't show up and in the camera, it calls both cameras "back" instead of one being "front".
But if you're concerned with stability that much, use the leak or EagleBlood.
I just installed cyanogenmod 10.2 on my tab 2 7.0 and i turned on bluetooth however my bluetooth keyboard which worked in stock doesn't show up when scanning. I'm not sure if bluetooth is even working at all.
Jxt. said:
Hello,
does it scan other nearby devices?
Is your tablet visible to other devices?
Click to expand...
Click to collapse
Ok the keyboard connected after a while. It was actually the keyboard that was having issues since after a while I was able to see my neighbors in the dorm next to me s mac book showing up on bluetooth. The only issue I have still is that the delete key doesn't really function as backspace I have to highlight a chunk of text then hit it to delete. I downloaded an app called delete key as backspace but I can't figure out how to set that up. I looked in the screenshot instructions but cannot find a section for physical keyboard.
Jxt. said:
did you check the keyboard layouts?
Click to expand...
Click to collapse
where is that exactly I looked and all I can seem to fine are languages but I looked and theres nothing in there about delete as backspace
I have a P5113 running cm 10.2 nightly. It seems to be finicky with bluetooth. I use sixaxis to connect my PS3 controller, but sometimes it just won't connect. Have to manually turn on/off bluetooth a few times, wait a few seconds, try again. It eventually will work though.
Jxt. said:
Did you see this in your language input settings?
Click to expand...
Click to collapse
No when the keyboard is connected I still don't see physical keyboard options
Jxt. said:
Nightlys are always buggy, i also use the ps3 sixaxis but i never have trouble getting the bluetooth to stay on.
You should check out Pacman ROMs. :laugh:
Click to expand...
Click to collapse
I'm using a version called cm-10.2-20130919-UNOFFICIAL-p3110 It's not a nightly or even an official cyanogenmod supported version I think. I just ended up with it by following a youtube tutorial. This makes me think that when cyanogenmod for the tab 2 7.0 progresses I won't be able to update through cyanogenmod update.
If this is the case will I be able to just flash a rc version of 10.2 when it becomes available without having to wipe data factory reset? I really hate having to reinstall everything
please tell my you can put the home back and multitasking buttons back to normal in that rom. I really don't like what they have done with hiding them and having you drag your finger up from the bottom to get at them.
Really I just want the lightest rom possible using the least amount of resources on my tablet
Jxt. said:
I don't understand how yours look.. screenshot please
Click to expand...
Click to collapse
Uploaded with ImageShack.us
the home button and back and task switch buttons are normal in mine but they r in that annoying circle you have to swipe up to get in pac rom. I looked at a few roms before jumping on the cyanogenmod bandwagon
Jxt. said:
I don't see a circle...
Click to expand...
Click to collapse
no i am running cm 10.2 and pac rom has a half wheel thing. Look at the screenshots in this thread suggested earlier. I was just stating that I don't really like the way the buttons are in that rom as I looked into it earlier
http://forum.xda-developers.com/showthread.php?t=2202854
mikee286 said:
No when the keyboard is connected I still don't see physical keyboard options
I'm using a version called cm-10.2-20130919-UNOFFICIAL-p3110 It's not a nightly or even an official cyanogenmod supported version I think. I just ended up with it by following a youtube tutorial. This makes me think that when cyanogenmod for the tab 2 7.0 progresses I won't be able to update through cyanogenmod update.
If this is the case will I be able to just flash a rc version of 10.2 when it becomes available without having to wipe data factory reset? I really hate having to reinstall everything
Click to expand...
Click to collapse
I see you switched to PAC Rom already but back to your original question.
There was a Bluetooth keyboard problem with CM 10.2 early versions.
I think you were using Cody's version of CM 10.2 in the latest versions of CM 10.2 they fixed the "Bluetooth Keyboard Bug" so if you want to use CM 10.2 you just need the latest versions or you can install an app to fix the Keyboard problem and keep using the older versions.
https://play.google.com/store/apps/details?id=com.heightdev.ganhou&hl=en
hcfte said:
I see you switched to PAC Rom already but back to your original question.
There was a Bluetooth keyboard problem with CM 10.2 early versions.
I think you were using Cody's version of CM 10.2 in the latest versions of CM 10.2 they fixed the "Bluetooth Keyboard Bug" so if you want to use CM 10.2 you just need the latest versions or you can install an app to fix the Keyboard problem and keep using the older versions.
https://play.google.com/store/apps/details?id=com.heightdev.ganhou&hl=en
Click to expand...
Click to collapse
thank you I am downloading the app. I have not switched to pac rom I was debating it but I ended up going with cm because its not bloated.
As I mentioned in an earlier post I think I am using an unofficial build of cm 10.2 built sometime in september. Would I be able to flash an official nightly build without having to wipe data factory reset Again the file I have currently flashed is cm-10.2-20130919-UNOFFICIAL-p3110
mikee286 said:
thank you I am downloading the app. I have not switched to pac rom I was debating it but I ended up going with cm because its not bloated.
As I mentioned in an earlier post I think I am using an unofficial build of cm 10.2 built sometime in september. Would I be able to flash an official nightly build without having to wipe data factory reset Again the file I have currently flashed is cm-10.2-20130919-UNOFFICIAL-p3110
Click to expand...
Click to collapse
I think this http://forum.xda-developers.com/showthread.php?t=2391355 is the Rom you are using it's the same one I use on my P3113. When CM 10.2 first came out they had a BT problem and that app worked for me.
I believe CM fixed the problem before Cody's last release and my keyboard has been working again without needing the App to fix it.
I just checked my Backspace button and it works fine on my BT 3.0 keyboard.
I did switch the Kernel to Next 2.1.2 so I don't know if that makes any difference.
I would ask in Cody's thread about being able to flash the latest CM 10.2 over Cody's without doing a clean install.
I have been a user of Cyanogenmod on my Verizon Galaxy S3 for a while now. I'm what most would call a newbie as far as android tech flash custom rom stuff. But I can get around...
My question is I just flashed Beanstalk and everything seems good so far. Loveing 4.4 (why I switched from Cyanogenmod) I get an OTA notification about a new version of Beanstalk but the numbers don't seem to be NEWER.
Current Beanstalk: 4.4.215-20140117-d2vzw
Update Version: 4.3.1009-20131016-d2vzw
Doesn't make sense to me, is there something wrong with the OTA app, or are they falling back to a previous version for some reason...anyone with info or help. Thanks!
I noticed the same thing. I believe the OTA updater may be broken or not updated. You have the latest build.
I get the same thing here
Been getting this since installing beanstalk that included the beanstalk OTA app....love the idea of it but it looks like the OTA app is broken or beanstalk is reporting itself as the wrong version.
I am running the most current 4.4.285 i believe but yet i get update notifications that new versions are available.
The "new" versions message i get is:
2 updates available for download
Beanstalk-4.3.1015-20131227-d2att.zip
Beanstalk-4.3.1009-20131015-d2att.zip
anyone figure this out as i am getting these older versions but not an actual new versions (and newer did exist while getting this message)?
When I was using beanstalk it was the same issue it would warn me of a lower version update. I don't know why it seems like to do that but just ignore it
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
ShapesBlue said:
When I was using beanstalk it was the same issue it would warn me of a lower version update. I don't know why it seems like to do that but just ignore it
Click to expand...
Click to collapse
Me too. The only AOSP ROM I've ever used that actually had a working OTA updater was C-ROM.
Hi guys,
I tried to flash the Franco kernel with the CM11 snapshot M9, for some reason i get pixel distortion top right. Where the cell bars show, sometimes over the complete right side of the screen.
Thereafter i re-flashed the rom directly following with the franco kernel, same result though.
Any ideas?
Thanks!
Its known issue. Graphics overlay on screen touch.
Workaround: Goto 'Developer Options' and disable Hardware Overlays.
U have to do this every time u reboot the phone.
Update your ROM, you're using a outdated ROM thats lacking the commits. Easier to update your ROM than to do a workaround on every reboot.
zephiK said:
Update your ROM, you're using a outdated ROM thats lacking the commits. Easier to update your ROM than to do a workaround on every reboot.
Click to expand...
Click to collapse
You're saying there is an update for stable version?
Or do you mean flashing the latest nightly?
Thanks for the answers guys!
Waanzin said:
You're saying there is an update for stable version?
Or do you mean flashing the latest nightly?
Thanks for the answers guys!
Click to expand...
Click to collapse
Latest nightly.
What samflorin said, M10 is out for some phones. OnePlus One is still being worked on so they didn't push M10 yet. When it does, it should be very close to the OTA.
M9 was a very old build that lacked the commits causing conflict on the kernel side of things. Once you update, all should be good
I've installed a variety of custom ROMs on my OP9 (EvolutionX, Nameless, Extended) and they all have the exact same problem: audio doesn't work properly, buggy, randomly would not connect to my Google account, etc. Since they all had the exact same issues, my guess is that it's a problem with my phone and not the ROMs themselves.
Does somebody know anything about the problem and what can I do to fix them? I'm fed up with OOS and would really like to use another ROM.
Ok everything you have listed is built from Lineage aosp. Therefore everything is gonna have same bug. If you notice the lemonade/p official lineage builds have stopped around the 12th and 14th of February .New ones are coming soon with merged patch that fixes all issues. Then devs from other roms will build on new fixed source and so on. Like throwing a pebble in a pond. Takes time for the ripple to get out. Watch lineage os website/downloads/op9
rodri_rebag5 said:
I've installed a variety of custom ROMs on my OP9 (EvolutionX, Nameless, Extended) and they all have the exact same problem: audio doesn't work properly, buggy, randomly would not connect to my Google account, etc. Since they all had the exact same issues, my guess is that it's a problem with my phone and not the ROMs themselves.
Does somebody know anything about the problem and what can I do to fix them? I'm fed up with OOS and would really like to use another ROM.
Click to expand...
Click to collapse
maybe you flashing over incompatible firmware
mattie_49 said:
Ok everything you have listed is built from Lineage aosp. Therefore everything is gonna have same bug. If you notice the lemonade/p official lineage builds have stopped around the 12th and 14th of February .New ones are coming soon with merged patch that fixes all issues. Then devs from other roms will build on new fixed source and so on. Like throwing a pebble in a pond. Takes time for the ripple to get out. Watch lineage os website/downloads/op9
Click to expand...
Click to collapse
That makes a lot of sense. I was wondering how the same issues presented with every ROM I installed. Thanks for the reply, I will wait for the new builds to start rolling out and then test them again.
Eric_Lev said:
In progress ... Be patient !
https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_sm8350/+/349350
Workaround : https://forum.xda-developers.com/t/rom-official-lemonade-13-lineageos-20.4536697/post-88176351
Edit about workaround : 4 days of uptime without the binder issue.
Click to expand...
Click to collapse
Try the workaround until the fix is included.
downhere said:
Try the workaround until the fix is included.
Click to expand...
Click to collapse
This looks very promising, apparently it solves most of the issues I was experiencing. The only thing I'm scared of is that issues such as my Google account not loading would not be fixed.
rodri_rebag5 said:
This looks very promising, apparently it solves most of the issues I was experiencing. The only thing I'm scared of is that issues such as my Google account not loading would not be fixed.
Click to expand...
Click to collapse
That setup with cached_apps_freezer fixes the Google issues. No issues for me any more.
downhere said:
That setup with cached_apps_freezer fixes the Google issues. No issues for me any more.
Click to expand...
Click to collapse
Then it's a miracle, I genuinely thought this was unfixable. Thanks a lot.
Just to clarify, do I run the command in stock OOS or once I've installed the ROM?
rodri_rebag5 said:
That makes a lot of sense. I was wondering how the same issues presented with every ROM I installed. Thanks for the reply, I will wait for the new builds to start rolling out and then test them again.
Click to expand...
Click to collapse
It's binder issues
rodri_rebag5 said:
Then it's a miracle, I genuinely thought this was unfixable. Thanks a lot.
Just to clarify, do I run the command in stock OOS or once I've installed the ROM?
Click to expand...
Click to collapse
After you've installed build.
rodri_rebag5 said:
Then it's a miracle, I genuinely thought this was unfixable. Thanks a lot.
Just to clarify, do I run the command in stock OOS or once I've installed the ROM?
Click to expand...
Click to collapse
You can use Developer Options of the custom ROM.
Thanks for all the answers, I will flash a ROM probably later tonight and try the cached_apps_freezer fix.