Related
India got update 2.3.4 update with software version 1.45.720.
Till now I have seen change with
1) icons clarity.Icons look very fine now.
2) 130 MB RAM free most of the time time (stock ROM)
Let me know if any one know more changes ..bcoz I don't see any surprises
I am on a Custom ROM. HTC will take ages to make their stock ROM as good as the custom ROMs available on this forum....Try one of them...you will also forget the stock ROMs.
@ mathrania but will i loose warranty ? And when i tried rooting my sensation it was not detecting my cell on 1st step only if u can help tht will be much better ..It say waiting for phone though it is connected
You loose some to gain some. Go for insert coin 2.2.5 sse with bricked kernal .5 and see results. Superfast ROM and very good battery.
Sent from my HTC Sensation Z710e using xda premium
I also observed the following:
new Facebook app (updated to latest I guess. I am using stock HTC Facebook app)
its noticeably smoother now
battery consumption is worse. I will do battery calibration again this weekend and then if it still remains as bad. Earlier I could go upto 1.5 days with moderate use and still have 20-25% juice left. Now it was like after 8-10 hours of moderate use I was at 45% level.
sidd6800 said:
India got update 2.3.4 update with software version 1.45.720.
Till now I have seen change with
1) icons clarity.Icons look very fine now.
2) 130 MB RAM free most of the time time (stock ROM)
Let me know if any one know more changes ..bcoz I don't see any surprises
Click to expand...
Click to collapse
I hvn't updated to 2.3.4 yet, I'm still on 2.3.3, but I still get around 150-200 MB free RAM. So ur 2nd point has no relation to 2.3.4 at all! Also check ur google Talk app., ur HTC Sensation might now hv the video chat feature. HTC made only subtle changes via the 2.3.4 update, it basically includes a few bug fixes & a few visual fixes. Also the sense crashes might be reduced now.
I'll update my phone in a couple of weeks, I'll be able to answer this better after updating.
can you check to see if your camera's macro function is now f'ed up?
I've almost had it up to here with that and the constant home button/screen shot issue. I almost threw my phone yesterday in frustration.
No update here in Canada yet
Sent from my HTC Sensation 4G using Tapatalk
No my camera is still working fine
Sent from my HTC Sensation Z710e using XDA App
Ya and now i have gmail video chat
Nothing special with friends stream
Scroll much smooth and battery drain like hell
Sent from my HTC Sensation Z710e using XDA App
How to take screen shot with home screen button
Sent from my HTC Sensation Z710e using XDA App
power + Home = screen shot
It's been eleven days since Android Police published this story detailing the discovery by Trevor Eckhart of some serious security issues within HTC's more recent software. Three days after that HTC responded, and now, a further week or so later, we are seeing reports of an "important security update" being pushed to HTC Sensations throughout Europe.
Now this update is available in India from 29th Oct 2011. While HTC does not specify exactly what the ~9 MB update addresses, the timing seems right to relate to the preceding story. Besides alluding to some positive-sounding "performance improvements and new features", the update description does not mention any further details, and HTC certainly doesn't dwell on the nature of the security update itself.
Quick Update - After you install the ~ 9 MB file. Check for update again you will get a ~400 KB update as well not sure what that is for...
Has somebody in India done this??
Will check any improvements and post the same....
It's been eleven days since Android Police published this story detailing the discovery by Trevor Eckhart of some serious security issues within HTC's more recent software. Three days after that HTC responded, and now, a further week or so later, we are seeing reports of an "important security update" being pushed to HTC Sensations throughout Europe.
Now this update is available in India from 29th Oct 2011. While HTC does not specify exactly what the ~9 MB update addresses, the timing seems right to relate to the preceding story. Besides alluding to some positive-sounding "performance improvements and new features", the update description does not mention any further details, and HTC certainly doesn't dwell on the nature of the security update itself.
Quick Update - After you install the ~ 9 MB file. Check for update again you will get a ~400 KB update as well not sure what that is for...
Has somebody in India done this??
Will check any improvements and post the same....
The next update was probably an application update. I had noticed that the "make more space" under "SD & phone storage" in the settings showed an error (something in the lines of "no action attached"). After the application update, its working fine.
Sent from my HTC Sensation Z710e using XDA App
What does "nightly" mean? I also have ROM tool box pro installed on my i605 when trying to get the most out of my battery what's the best settings on CPU controlled and why.
Thanks.
every software development goes under various phases before a stable version is released to the end users . I think the order goes as
Alpha
Beta
Weekly
Nightly - means each 15 days
Monthly
Release Candidates
and final version
Sent from my GT-S5670 using xda premium
webb7735 said:
What does "nightly" mean? I also have ROM tool box pro installed on my i605 when trying to get the most out of my battery what's the best settings on CPU controlled and why.
Thanks.
Click to expand...
Click to collapse
Hi,
I edited your post to add a thread title. Leaving off the title makes it much harder for people to help you.
Quoting from Wikipedia, that gives an optimal definition:
In software development, a neutral build is a software build that reflects the current state of the source code checked into the source code version control system by the developers, and done in a neutral environment (an environment not used for development).
A nightly build is a neutral build that takes place automatically. These typically take place when no one is likely to be working in the office so that there are no changes to the source code during the build. The results of the build are inspected by the arriving programmers, who generally place a priority on ensuring the recent changes to the source code have not broken the build process or functionality of the software.
Click to expand...
Click to collapse
sorry
justmpm said:
Hi,
I edited your post to add a thread title. Leaving off the title makes it much harder for people to help you.
Click to expand...
Click to collapse
Thanks
Hello,
I am using CM 10.2.1 and when I checked the "CyanogenMod Updates" on my phone lately I noticed that three CM 11 snapshots were listed even though I chose to display only stable releases (see attached pic). Are these snapshots considered stable? This is for my primary phone and don't have a toy phone to test this with. I'd appreciate your input.
Snapshot M => M = Monthly / Monthly => same principle as monthly but nightlies. Basically they take a recent nightly deemed stable enough for release under this label. Normally it is functional and relatively stable. It allows you to be "up to date" vis-à-vis the latest developments without taking too many risks
Click to expand...
Click to collapse
It's pretty clear that the road forward for CyanogenMod is a dead end at this point. While it's no huge loss for me (been running a stock Stylo 2 Plus lately, and my Relay is just a backup and occasional wireless camera controller at this point), I wouldn't mind switching out ROMs on the Relay, at least if there's something still maintained.
I was afraid something like this would happen to CM once Microsoft got its grubby little paws into the picture. Looks like Cyanogen effectively got Elop'd just like Nokia did.
A month or so back, I was getting ready to buy my wife and myself a pair of new phones to replace our Relays. I was basing my selection on CM-14.1 support. Things got confusing, and I postponed the whole matter until some time next year. Boy, and I glad I delayed.
Of course I still have to select a replacement for the Relay - one that is really supported for the long run - which may still push me into something CM-like. Now to figure out what that is.
Well if you want to be safe just go Nexus, only the Nexus one and Nexus s have lost support, galaxy Nexus and up still has developers not to mention google will support each for 2 years plus
Other safe bets are the real popular devices such as galaxies and even the OnePlus community
If you want a hardware keyboard I would suggest to learn development as you will always be limited and haven't seen one with good support since HTC g2
Hi there, why not port Ubuntu Touch? I did read that it is quite easy to port ubuntu touch to cyanogenmod supported phones...
I'm still in the process of learning how to do that... but there are no real reference on doing that and building/brewing a rom would be my first.
You certainly could but I'm not sure if that ever works too well with a HW keyboard, at that point may as well move on.
There are many of options on what to bring over but few still use phones like these, in truth i haven't touched any of my 5 hw keyboard phones in at least two/three years, i miss them but have learned to live without...
But i did just read BlackBerry has a new one soon, may not get much support though, priv was a bit of a bust...
*sigh* i know you are right. Beginning this year i started using the Nokia e7 Communicator again on custom Symbian ROM. After a few not solveable problems i imported the Relay short after as my last ray of hope. Is it that dificult as a manufacturer to build a landscape slider with 5 key rows? Just one decent powered would be enough. I don't care if i use QNX, Android, iOS or Windows Mobile, the phone is just a phone for me. I don't need 5 thousand sounboard fart apps..... god damn...
Make last Relay build available???
It appears that Cyanogenmod is offline, so nothing new is coming - ever. That said, I'd seen that things were going to go offline at the end of the year, and was rather hoping to pick up the "auto-integration" of the final AOSP merges into CM-11. I'm assuming this happens, because I don't believe any person has touched this since TDM left at the end of July.
I'm currently running a nightly I built on Dec 3 of this on my wife's and my phones, and have had no problems. I'm willing to make this build available for anyone who wants a small update for their Relay.
There's another question... How do I find out the date of the final update? I ran my build script again this morning, and got a result, but since the CM servers are dead, I suspect it just ran through its paces. I know that the Dec 3 built I'm running carries a date of 20161126 and an Android security patch level of November 1, 2016.
My last builds are very little different in file sizes, but as I sift through the build directory, I see a bunch of stuff with a Dec 15 date, so I believe I may have picked up some fixes on that build. I see that the servers actually went offline apparently on Dec 25, which also matches some of the date stamps I see in my build tree.
So - Can someone tell me a distinctive spot in my build tree where I can find out what the actual date of this stuff is? I suppose I'm going to try flashing this build one of these days, to see if there is anything better than what I've got on the phone now. If so this will be the last, best build of CM-11 for the Relay.
I will make one or both of these builds available, if there is interest. I'm not quite sure how to do that, where, etc. I have a basic Dropbox account, though I see that they will be phasing out the Public folder in April. That's a start, or I'm open to suggestions.
phred14 said:
Make last Relay build available???
It appears that Cyanogenmod is offline, so nothing new is coming - ever. That said, I'd seen that things were going to go offline at the end of the year, and was rather hoping to pick up the "auto-integration" of the final AOSP merges into CM-11. I'm assuming this happens, because I don't believe any person has touched this since TDM left at the end of July.
I'm currently running a nightly I built on Dec 3 of this on my wife's and my phones, and have had no problems. I'm willing to make this build available for anyone who wants a small update for their Relay.
There's another question... How do I find out the date of the final update? I ran my build script again this morning, and got a result, but since the CM servers are dead, I suspect it just ran through its paces. I know that the Dec 3 built I'm running carries a date of 20161126 and an Android security patch level of November 1, 2016.
My last builds are very little different in file sizes, but as I sift through the build directory, I see a bunch of stuff with a Dec 15 date, so I believe I may have picked up some fixes on that build. I see that the servers actually went offline apparently on Dec 25, which also matches some of the date stamps I see in my build tree.
So - Can someone tell me a distinctive spot in my build tree where I can find out what the actual date of this stuff is? I suppose I'm going to try flashing this build one of these days, to see if there is anything better than what I've got on the phone now. If so this will be the last, best build of CM-11 for the Relay.
I will make one or both of these builds available, if there is interest. I'm not quite sure how to do that, where, etc. I have a basic Dropbox account, though I see that they will be phasing out the Public folder in April. That's a start, or I'm open to suggestions.
Click to expand...
Click to collapse
I think we all as the last battalion of the Galaxy S Relay 4g would really appreciate if you could share your build. :fingers-crossed:
I just loaded today's build, though I haven't tested it much yet.
The Cyanogenmod version is 11-20161129-UNOFFICIAL-apexqtmo
The Android security patch level is Nov 1, 2016
The Kernel version is Sat Dec 24 15:10:38 EST 2016
So I guess I didn't get a new AOSP, nor new CM-11. But I did get a new kernel? I'd built a few times between then and now, so it looks like that's that.
I'll do a bit of testing with this one, then see if I can get it up to Dropbox Public, even if only for a quarter.
phred14 said:
I just loaded today's build, though I haven't tested it much yet.
The Cyanogenmod version is 11-20161129-UNOFFICIAL-apexqtmo
The Android security patch level is Nov 1, 2016
The Kernel version is Sat Dec 24 15:10:38 EST 2016
So I guess I didn't get a new AOSP, nor new CM-11. But I did get a new kernel? I'd built a few times between then and now, so it looks like that's that.
I'll do a bit of testing with this one, then see if I can get it up to Dropbox Public, even if only for a quarter.
Click to expand...
Click to collapse
Hi phred14, sorry to bother. Did you manage to upload that last nighly? Can you tell me if everything you test works? In the past I tried CM and was having issues with Mic, GPS and Camera, so i revert to stock.
Thanks in advance!
ninguno2 said:
Hi phred14, sorry to bother. Did you manage to upload that last nighly? Can you tell me if everything you test works? In the past I tried CM and was having issues with Mic, GPS and Camera, so i revert to stock.
Thanks in advance!
Click to expand...
Click to collapse
Yes, it's uploaded to my Google Drive with public access. I uploaded both Dec 4 and Dec 29 versions. I did a bit of specific testing with GPS and Camera on the Dec 4 version, but have not tested those functions on the Dec 29. I'm running Dec 29 now, so it does what I need - acts like a phone, texts, does wifi, and does stuff over data - and I don't know that any other functions don't work.
Do you have GPS working now? I believe that there was a specific "era" that borked the GPS in a persistent way. If you did that, which I did, you need to backflash to stock, or at least JB, then there is a procedure for flashing new. I've done this, and have working GPS.
The links to my stuff are on a separate thread under "Development", titled "Lineage OS", which is the successor to CM. We can discuss more if you're still interested. I can also take my current flash and do a bit more testing, when I have time. (Maybe not soon - we're getting work done on the house, and are in the process of moving out for a few weeks.)
phred14 said:
Yes, it's uploaded to my Google Drive with public access. I uploaded both Dec 4 and Dec 29 versions. I did a bit of specific testing with GPS and Camera on the Dec 4 version, but have not tested those functions on the Dec 29. I'm running Dec 29 now, so it does what I need - acts like a phone, texts, does wifi, and does stuff over data - and I don't know that any other functions don't work.
Do you have GPS working now? I believe that there was a specific "era" that borked the GPS in a persistent way. If you did that, which I did, you need to backflash to stock, or at least JB, then there is a procedure for flashing new. I've done this, and have working GPS.
The links to my stuff are on a separate thread under "Development", titled "Lineage OS", which is the successor to CM. We can discuss more if you're still interested. I can also take my current flash and do a bit more testing, when I have time. (Maybe not soon - we're getting work done on the house, and are in the process of moving out for a few weeks.)
Click to expand...
Click to collapse
Hi phred14, thanks for the quick answer.
Yes, my GPS is working great in JB (I'm using the last offical stock 4.1.2 T699UVBOH1_T699TMBBOH1_TMB), so I suppose i don't need a special procedure for the gps, right?
I already found the links you mention, as I understand from your answer, the camera works ok with the Dec 4 version? Can you tell me if the mic works ok with the version you're running? I remember that when using CM in the past, voice notes that i sent with whatsapp were muted (or tooo quiet) showing that the mic wasn't working. Reverting back to JB fix that too, as with the GPS.
Do you have some kind of updated guide/procedure/backup you follow before flashing CM, being I'm still at stock rom (i remember there was one on the old CM wiki)? I would really like to test your CM following the right steps.
Besides, i found another post you made about modem fixes (https://forum.xda-developers.com/showpost.php?p=63925086&postcount=20) is that still needed? As the link for RelayMC5modem.zip file is not working.
Best,
phred14 said:
A month or so back, I was getting ready to buy my wife and myself a pair of new phones to replace our Relays. I was basing my selection on CM-14.1 support. Things got confusing, and I postponed the whole matter until some time next year. Boy, and I glad I delayed.
Of course I still have to select a replacement for the Relay - one that is really supported for the long run - which may still push me into something CM-like. Now to figure out what that is.
Click to expand...
Click to collapse
Try going for something that's supported by LiquidSmooth or other custom ROMs. CM was the best, no doubt. There will always be options.
That's the beauty of Android as an OS. I'm proud of my contribution and maybe I might do more in the future. Albeit in a lesser light than FB, I see Google as a info hog.
Among devices, you should try either Nexus or older, unlocked Samsung devices.
Not very sure about the authenticity of the pic provided in this link, maybe someone could dig deep down and flush out the real news (maybe based on the kernel or baseband version) but here is the link:
MOTO G4+ SPOTTED RUNNING 8.0
It seems fake to me. Also, there is no mentioned source of that screenshot. Also, Moto probably wouldn't have released the February security patch if all the work is focused on Oreo, which shows the January patch in that screenshot.
A L S O, the screenshot doesn't include the build number. That would have helped to confirm that the screenshot is 100% fake. And I would consider it kinda stupid from Moto to release 8.0.0 when 8.1.0 has already been out for months.
corlatemanuel said:
It seems fake to me. Also, there is no mentioned source of that screenshot. Also, Moto probably wouldn't have released the February security patch if all the work is focused on Oreo, which shows the January patch in that screenshot.
A L S O, the screenshot doesn't include the build number. That would have helped to confirm that the screenshot is 100% fake. And I would consider it kinda stupid from Moto to release 8.0.0 when 8.1.0 has already been out for months.
Click to expand...
Click to collapse
That I agree with, that's why my post didn't say it's real, it happened before with the g5 Oreo, someone faked it using x4 Oreo's build number
In addition to the other comments made about this:
1)Zooming into the picture, seems the 'Moto G4 Plus' text is slightly darker than the other descriptors and the font for the baseband (beginning with MSM8952) appears to be a different font to the other descriptors.
For example, look at the capital C in the baseband (CUST) and the C in the kernel timestamp (CST) and they seem to be 2 different styles. Contrast that with an Oreo soak test screenshot from the Moto Z Play: https://forum.xda-developers.com/showpost.php?p=75395738&postcount=15 The capital Cs are more consistent in their styles.
Additionally, look at the M in 'Modelo' and the M in 'Moto G4 Plus' and the 'MSM8952'. The M in 'Modelo' has its 'tails' pointing straight down, whereas the M in 'Moto G4 Plus' is angled. Contrast that again with the Moto Z Play screenshots where the M is pointing straight down in the About Phone photos.
2)As mentioned above, seems odd they would have the Jan 2018 patch, and the Jan 2018 baseband, when the February 2018 patch has come out. Jan 2018 baseband ends in 62.01R, with the Feb 2018 baseband ending in 62.02R. In theory, this could be an early build of the Oreo beta, but Motorola in the past has appeared to focus development on soak tests and included the latest patches with them, rather than splitting development (I think with the G4 Play, Motorola continued to release security patches as they had major issues with the soak test).
3)The kernel version and build timestamps match that from the Moto Z Play Oreo soak test build. https://forum.xda-developers.com/showpost.php?p=75395738&postcount=15 As others have noted in this thread https://forum.xda-developers.com/moto-g4-plus/help/android-oreo-t3763868 our device is likely to be running kernel version 3.10 (now on extended support), which makes a kernel change to 3.18 unlikely. Especially as Google only mandated newer kernels for devices released with Oreo/built in 2017 - devices updated to Oreo, if I recall, could maintain their original kernels.
Yeah, at first glance may be convincing but now seems just to bring false hope and/or is clickbait for tech sites. Regardless, I await evidence or signs of a soak test for our devices.
EDIT: that's at least 2 articles from Techdroider I've seen where they've not verified their sources...
EDIT 2: I see that this has gotten some traction on the Techdroider website, and yes, my post has a lot of focus on the screenshot. However, that's the only screenshot of an 'Oreo build' for G4 Plus devices I've seen, and without word of a soak test, so the timing of this seems a little suspect. Couple that with previous fakes mentioned on the Moto G subreddit and thus it warranted closer inspection, if only to stop giving false hopes to users and try to keep the record straight. Else, users will keep asking on this forum and the other G5/G5S forums when Oreo is arriving. The simple answer is we don't know (yet).
As for those that are commenting about the kernel version requiring to be 3.18 or higher, Google's documentation says that if your device is being upgraded, you can stay on the base kernel if you so wish:
Kernel version
Kernel version requirements:
All SoCs productized in 2017 must launch with kernel 4.4 or newer.
All other SoCs launching new Android devices running Android 8.0 must use kernel 3.18 or newer.
Regardless of launch date, all SoCs with device launches on Android 8.0 remain subject to kernel changes required to enable Treble.
Older Android devices released prior to Android 8.0 but that will be upgraded to Android 8.0 can continue to use their original base kernel version if desired.
Click to expand...
Click to collapse
Reference: https://source.android.com/devices/architecture/kernel/modular-kernels
LOL, you're just thinking too much. When you try to prove something "Fake" and you observe each and every detail of a Screenshot.
This was also Fake right? http://bit.ly/2FWnp2z
The thing is the screenshot is too good to be true, that's the only reason you cannot accept it. Also what makes you think G4 Plus is going to stay with base version? They can update it to 3.18 if the want.
Your logic in faking a Screenshot is not sound.
Moderator edit: Please avoid quoting the entire PREVIOUS post, and your choice of words for another member has been amended.
harsinghal said:
LOL, you're just thinking too much. When you try to prove something "Fake" and you observe each and every detail of a Screenshot.
This was also Fake right? http://bit.ly/2FWnp2z
The thing is the screenshot is too good to be true, that's the only reason you cannot accept it. Also what makes you think G4 Plus is going to stay with base version? They can update it to 3.18 if the want.
Your logic in faking a Screenshot is not sound.
Click to expand...
Click to collapse
Did you get the Oreo update then? Otherwise his analysis is dope. Echo is one of the masters when it comes to fixing. Hus saying this means it's the truth.
Ayan Uchiha Choudhury said:
Did you get the Oreo update then? Otherwise his analysis is dope. Echo is one of the masters when it comes to fixing. Hus saying this means it's the truth.
Click to expand...
Click to collapse
Saying something fake on the basis of color and font of words and letters makes you think his analysis is dope. Well, great then
He might be great in fixing and development, but i think his points are no facts but too much thinking to prove the ss fake.
harsinghal said:
Saying something fake on the basis of color and font of words and letters makes you think his analysis is dope. Well, great then
He might be great in fixing and development, but i think his points are no facts but too much thinking to prove the ss fake.
Click to expand...
Click to collapse
I get the impression you see the screenshot as real, so I'd like to ask you for your view on why you see this as genuine, or at least not faked. I would be interested in evidence too, e.g. do you have the build on your device? Or at least what you see as 'stupid in faking a screenshot'?
As for the screenshot you linked, that Chinese Moto Z Play screenshot looks genuine to me.
Here I have done a closer look at the screenshot and a comparison between that screenshot and a screenshot from my build of Lineage 15.1 and found two more details:
1. If you pay close attention/have a well trained eye, you will notice that the spacing is wrong for the Baseband Version when compared to the other elements (Android version, Kernel version etc.). When compared, the spacing between the "Baseband version" and the actual baseband version looks rather like the one on my LOS 15.1 build than the one on the stock Moto ROM, with the two being closer together on LOS 15.1. Though you need to look really close to notice it.
2. When you look at it, there is a part of the baseband version that only the stock ROM (7.0) and the bootloader show. On that screenshot, that detail is next to the baseband version rather than underneath the part that would be found on custom ROMs. Look at the dotted lines.
I also think this is fake cuz of the simplest reason that a company would be actually cheating to the customers who bought the g5 family if we had a soak test before them since we are an older model. Even if the company had a soak test ready they would hold till ALL the g5 phones had a soak test out and then would release for g4 plus. I doubt Lenovo would want an uproar from the community.
harsinghal said:
LOL, you're just thinking too much. When you try to prove something "Fake" and you observe each and every detail of a Screenshot.
This was also Fake right? http://bit.ly/2FWnp2z
The thing is the screenshot is too good to be true, that's the only reason you cannot accept it. Also what makes you think G4 Plus is going to stay with base version? They can update it to 3.18 if the want.
Your logic in faking a Screenshot is pure stupid.
Click to expand...
Click to collapse
Have you ever seen a company which updated their kernel, except Google? No.
Motorola didn't even upstream the kernel. It's still .84 while there's .108
He proved that this screenshot is fake in a detailed way and you just disrespected him.
That screenshot is fake, believe or not.
LineageOS 15.1
corlatemanuel said:
Here I have done a closer look at the screenshot and a comparison between that screenshot and a screenshot from my build of Lineage 15.1 and found two more details:
1. If you pay close attention/have a well trained eye, you will notice that the spacing is wrong for the Baseband Version when compared to the other elements (Android version, Kernel version etc.). When compared, the spacing between the "Baseband version" and the actual baseband version looks rather like the one on my LOS 15.1 build than the one on the stock Moto ROM, with the two being closer together on LOS 15.1. Though you need to look really close to notice it.
2. When you look at it, there is a part of the baseband version that only the stock ROM (7.0) and the bootloader show. On that screenshot, that detail is next to the baseband version rather than underneath the part that would be found on custom ROMs. Look at the dotted lines.
Click to expand...
Click to collapse
Hi, I saw in your post that you have a catch of LineageOS 15.1 with a latest version of March.
Can you tell me or pass the link where you downloaded it?
Thank you very much
al3al3al3jandr0 said:
Hi, I saw in your post that you have a catch of LineageOS 15.1 with a latest version of March.
Can you tell me or pass the link where you downloaded it?
Thank you very much
Click to expand...
Click to collapse
About Lineage OS. Yes, it's a build of mine, I didn't make a thread about it because I'm an absolute noob when it comes to ROM building and this is my first ever ROM built. I can upload it somewhere, if you want me to.
corlatemanuel said:
About Lineage OS. Yes, it's a build of mine, I didn't make a thread about it because I'm an absolute noob when it comes to ROM building and this is my first ever ROM built. I can upload it somewhere, if you want me to.
Click to expand...
Click to collapse
Of course it would be fine, congratulations for doing it.
What bugs do you have?
corlatemanuel said:
About Lineage OS. Yes, it's a build of mine, I didn't make a thread about it because I'm an absolute noob when it comes to ROM building and this is my first ever ROM built. I can upload it somewhere, if you want me to.
Click to expand...
Click to collapse
Post edited - XDA is for public sharing, not code via PM...
LenAsh said:
Post edited - XDA is for public sharing, not code via PM...
Click to expand...
Click to collapse
It has been shared meanwhile:
https://forum.xda-developers.com/moto-g4-plus/development/lineageos-15-1-nightlies-thanks-to-nikit-t3765065
(actually, that's a different one )
jer194 said:
It has been shared meanwhile:
https://forum.xda-developers.com/mo...ageos-15-1-nightlies-thanks-to-nikit-t3765065
(actually, that's a different one )
Click to expand...
Click to collapse
Actually, It's pretty much the same thing, only that mine has very minor changes. Maybe I'll make a thread of my own if I manage to sort everything out for my builds. I didn't make a thread yet as I didn't feel like it was ready for use yet
I just a saw youtube video,in that video he told that moto is testing oreo on the g4 plus
jaxx08 said:
I just a saw youtube video,in that video he told that moto is testing oreo on the g4 plus
Click to expand...
Click to collapse
i know seen that too. sad it is. probably his own ignorance to deceitful nature
here's latest news
https://www.xda-developers.com/motorola-testers-moto-g4-plus-android-oreo/