Related
at least in Germany, i guess in other countrys (soon) to!
Source: http://www.t-mobile.de/g1/software-update
bassbox said:
at least in Germany, i guess in other countrys (soon) to!
Source: http://www.t-mobile.de/g1/software-update
Click to expand...
Click to collapse
I hope so! so i can un-root my phone, i only wanted root just to use cupcake
djdant said:
I hope so! so i can un-root my phone, i only wanted root just to use cupcake
Click to expand...
Click to collapse
Why would you want to un-root your phone? There are no adverse effects to having a rooted phone, its only positive.
As for cupcake I guess it could make sense seeing that the Magic is suppose to launch in May, with cupcake. So it only makes sense for cupcake to be released. And there have been a lot of talks about Google preping dev's for 1.5.
speoples20 said:
Why would you want to un-root your phone? There are no adverse effects to having a rooted phone, its only positive.
As for cupcake I guess it could make sense seeing that the Magic is suppose to launch in May, with cupcake. So it only makes sense for cupcake to be released. And there have been a lot of talks about Google preping dev's for 1.5.
Click to expand...
Click to collapse
I thought it'd have to be un-rooted in order to go back to the "official cupcake" when it drops.
I dont know why you wouldnt want root, I'll be continuing to watch androids development and I'll be flashing development roms as features are added and bugs are fixed
If you "update" from your phone, when it prompts, to cupcake, that will basically update to official firmware and "un-do" root, wouldn't it?
harpreet1988 said:
If you "update" from your phone, when it prompts, to cupcake, that will basically update to official firmware and "un-do" root, wouldn't it?
Click to expand...
Click to collapse
I believe it will attempt do download but won't be able to install.
Like the others said, why would you want to un-root??! Just wait a day or so after the official update and most likely there will be a JF version. That's what happened with 1.1
Who cares???
I'm rocking cupcake right now with Dudes .8 and Haykuro's H VK!
I'm so sick of the "HEY! Cupcake is coming out on (insert date of your choice here)!" that I just don't care anymore.
The devs on this site have kept me more than happy with all of their updates!
Thanks again to JF, Sterickson, Manup, Haykuro, The Dude, and all of the others I'm failing to mention! You guys rock! Google can stuff their cupcake up the opposite end.
The only benefit that cupcake will bring at this point will be to force the app devs to update all of the apps and the theme devs to make 1.5 themes.
Re the themes... Gee, I think xda-devs are already beginning to do that... imagine that!?!?
Well, I hope the cupcake for G1 is optimized for it. Because I found the Haykuro builds too buggy and laggy, and just not worth the grief.
harpreet1988 said:
If you "update" from your phone, when it prompts, to cupcake, that will basically update to official firmware and "un-do" root, wouldn't it?
Click to expand...
Click to collapse
If you have root now then you shouldn't even receive an update, will have to wait for jf version of update. As far as haykuro rom its great that everyone likes it but the REAL update from jf will work 100% with no problems.
harpreet1988 said:
If you "update" from your phone, when it prompts, to cupcake, that will basically update to official firmware and "un-do" root, wouldn't it?
Click to expand...
Click to collapse
If you have root now then you shouldn't even receive an update, will have to wait for jf version of update. As far as haykuro rom its great that everyone likes it but the REAL update from jf will work 100% with no problems. Then the 7000 post thread will hopefully go away and all 25 of its other threads throughout the forum as well.
I liked the Haykuro updates... But, I agree they were too buggy. Dudes' seems to be working very well!
But, I'll be surprised if the posts go away! The Dude build has a lot in it that may not be allowed by T-mobile. So, all I see happening is that Cupcake will officially release...
Then JF, Dude or whoever, will modify it to add all the goodies back inside.
It will just make for a more stable modified release. There are too many custom features in the Dude build for anyone to just use the stock cupcake!
For those that don't speak German ...
http://translate.google.com/transla...ww.t-mobile.de/g1/software-update&sl=de&tl=en
I'm not giving up Haykuro's H build unless the modified official G1 has all the good stuff we got with the HTC version. I like my camera, I like having a pdf reader, (I don't think the official Google version has it, but I might be wrong). I also like the H virtual keyboard.
I also doubt that the official version for the G1 will have exchange.
The only way I am going to switch is if I find some really big bug that I can't live with. (Although multitouch might make me change my mind if it's included in a JF build).
momentarylapseofreason said:
For those that don't speak German ...
http://translate.google.com/transla...ww.t-mobile.de/g1/software-update&sl=de&tl=en
Click to expand...
Click to collapse
Thanks! Now I can skip taking German classes so I can browse through this website. LOL.
I think when google drops there version of cupcake it will be like having the google's update of RC33 and when all the source codes are out the Dude build will be like having RC33 JF builds. I hope everyone understands what i mean.
I think this build is made by Tmobile. But I hope this build would be made by HTC. HTC's designer is very good.
I have the haykuro g build.. and i really dont see anything wrong.. it works just as smooth as the jf 1.42 rc 33
DAKIDD236 said:
I have the haykuro g build.. and i really dont see anything wrong.. it works just as smooth as the jf 1.42 rc 33
Click to expand...
Click to collapse
Well, I guess my phone is some special version, as I found it to be unstable, and the browser was much slower.
The Wifi was horrible, and showed a much weaker connection than in JF 1.42
And kept disconnecting. (Yes, I made sure the option for it to automatically turn off was not selected).
funbacon said:
I think this build is made by Tmobile. But I hope this build would be made by HTC. HTC's designer is very good.
Click to expand...
Click to collapse
TMo doesn't exactly cook their own builds. They just customize them to meet their needs.
So I've been looking at the video codecs issue that blocks YouTube HD and video recording on the Dream. Seems there are two underlying issues, libsgl from donut was merged into a new library, and that theres an API break in libhardware.
On the first issue, its fairly easy to build donut's libsgl.so on eclair with some minor changes to source to get it, build it, and it seems that it works properly (as far as I can tell, the OpenGL 3D interface it binds to has had a stable API). I don't have a strong test case to use it on.
The second problem is more interesting. It seems to me that the problem with the API break is that Qualcomm is using enum's in a way that is absolutely stupid, and added new numbers that broke the magic numbers copybit needs. This causes a set of copybit failures when blitting stuff to the screen. Rebuilding the proprietary libraries would fix the problem, but as we only have libraries built against 1.6, this obviously won't work, so I'm seeing if theres a better solution we can use to solve this problem. Any ideas welcome.
NCommander, you've done amazing work here before
unfortunately, based on my research and trying to merge patches from 1.6 into 2.0 source and vice versa, that this is nearly impossible.
I would expect that the only feasable way would be to make a whole new composition method for android, based loosely off the methods shown in the 1.6 source.
Unfortunately, i think that it will be best to wait for HTC to work with qualcomm, and actually release something. I've heard that the MyTouch will be getting the 2.0/2.1 update, and hope that this release will solve our problems.
Noting is impossible
jcarrz1 said:
NCommander, you've done amazing work here before
unfortunately, based on my research and trying to merge patches from 1.6 into 2.0 source and vice versa, that this is nearly impossible.
I would expect that the only feasable way would be to make a whole new composition method for android, based loosely off the methods shown in the 1.6 source.
Unfortunately, i think that it will be best to wait for HTC to work with qualcomm, and actually release something. I've heard that the MyTouch will be getting the 2.0/2.1 update, and hope that this release will solve our problems.
Click to expand...
Click to collapse
Camera didn't work but now it does. Youtube will work 100% very soon
Interesting.... could we possible encapsulate the existing libhardware and create a new interface to it to translate the new calls (enums) to existing? Just throwing the idea out there - probably too simple and I am missing something not knowing too much of the details. I guess I would think of a libWINE like approach, interface just translates the new expected calls to the old driver....
if all goes well, will this also help speed up things like live wallpapers? (sorry if this is a noob question)
smackdown85146 said:
if all goes well, will this also help speed up things like live wallpapers? (sorry if this is a noob question)
Click to expand...
Click to collapse
In theory, it would allow any opengl call to be handled on the GPU. Not only would the livewallpaper speed up, but you'd have more available CPU time for other operations.
The idea is sound, the tricky part is making them efficient enough to actually be a net benefit. It could decent stopgap until new drivers are released.
????-????
So your saying that the first eclair roms where 1.6 with 2.0 skins?
llxll0m3g4llxll said:
So your saying that the first eclair roms where 1.6 with 2.0 skins?
Click to expand...
Click to collapse
No, not entirely...when the Eclair Roms roms were first being made in the beginning Devs didnt have the drivers for the camera. But, thanks to NCommander we do now =)
Android G1 2.0 Update
T-Mobile Czech Republic officialy announced 2.0 update for G1 for end of January (1-2 weeks). Maybe is better wait for this release.
pinkolin said:
T-Mobile Czech Republic officialy announced 2.0 update for G1 for end of January (1-2 weeks). Maybe is better wait for this release.
Click to expand...
Click to collapse
Isn't january ending... tomorrow?
vincom2 said:
Isn't january ending... tomorrow?
Click to expand...
Click to collapse
yeah, my senses tell me that it is
Yes, but this is Europe, "End of January" is in T-mobile speak half of February :-D. I have Google Translate page with this info, but i'm Junior member without rights :-D.
Eh would probably be too lazy to go back to stock anyways, will just have to wait for those video drivers =)
pinkolin said:
Yes, but this is Europe, "End of January" is in T-mobile speak half of February :-D. I have Google Translate page with this info, but i'm Junior member without rights :-D.
Click to expand...
Click to collapse
This can be "helpfully" for your work on this thread. More info:
http://forum.xda-developers.com/showthread.php?t=625108
http://www.4shared.com/file/207649694/b347bfad/RUU_Sapphire_HTC_Europe_304401.html
Is a full origianl ROM 2.1 for HTC Sapphire, the problem is that it only works on 32A, and I think that this can be a problem.
shawe_ewahs said:
This can be "helpfully" for your work on this thread. More info:
http://forum.xda-developers.com/showthread.php?t=625108
http://www.4shared.com/file/207649694/b347bfad/RUU_Sapphire_HTC_Europe_304401.html
Is a full origianl ROM 2.1 for HTC Sapphire, the problem is that it only works on 32A, and I think that this can be a problem.
Click to expand...
Click to collapse
I don't see anyone in that thread indicating that it's a 2.x ROM, just that it's a potential way to root some newer 32A SPLs. Might help some Rogers people out. Am I missing something? Have you pulled the build.prop?
olearyp said:
I don't see anyone in that thread indicating that it's a 2.x ROM, just that it's a potential way to root some newer 32A SPLs. Might help some Rogers people out. Am I missing something? Have you pulled the build.prop?
Click to expand...
Click to collapse
Its probably the default rom that comes with the phone.
How close is the camera in the g1 to the camera in the Hero ? I keep seeing articles that HTC is releasing 2.1 upgrade for the hero. Will this help the g1 ?
menace said:
How close is the camera in the g1 to the camera in the Hero ? I keep seeing articles that HTC is releasing 2.1 upgrade for the hero. Will this help the g1 ?
Click to expand...
Click to collapse
yup with the 2.1 upgrade ur g1 can take 10mp pics
bakgwailo said:
Interesting.... could we possible encapsulate the existing libhardware and create a new interface to it to translate the new calls (enums) to existing? Just throwing the idea out there - probably too simple and I am missing something not knowing too much of the details. I guess I would think of a libWINE like approach, interface just translates the new expected calls to the old driver....
Click to expand...
Click to collapse
Sounds like ndiswrapper for linux
gregnotcraig said:
Sounds like ndiswrapper for linux
Click to expand...
Click to collapse
doesnt it though
I switched from Cyanogenmod 13.0 to LineageOS 14.1 when CM died in late December. Was very excited about Nougat at first, but there are a lot of bugs with mobile data, bluetooth, etc. After a couple months of flashing nightly builds hoping for things to get better, I gave up and went back to the last build of CM13 and all the bugs have disappeared and my battery life improved as well. Plus I can use Xposed which is nice.
Only problem is CM13 will never be updated so I'm stuck on December 2016 security patch level. Thus I am steadily getting more outdated. With no official Nougat ever coming to the G3, it makes me wonder if the bugs in LOS14.1 will ever be fixed since there will never be an official source to base it on. I know there are other Nougat-based roms out there but I imagine they must suffer from the same bugs as LineageOS.
I don't care about new features or anything, I just would like to have security updates because it seems like a bad idea not to.
Is this what I'm looking for? https://forum.xda-developers.com/20...nt/rom-lineageos-13-0-moto-g-3rd-gen-t3530402
Consider this - most folks with Moto G3 are on stock M. With no security updates.
With CM13 you say you are on Dec '16. That's a year and a half better than stock.
Maybe you aren't really so bad off...
Have you ever really felt any real harm having "outdated" security patch? I'm kin to hear exact cases when your phone needs a new security patch. Or maybe you are installing experimental software from deep web? There are a lot of users with devices with Android 5.0.2 or 5.1 that haven't even heard about security patches, and they feel themselves very comfortable using their daily package of normal and verified software. So I don't see any point to look for a developing MM 6.0.1 ROM, as it is already developed and bugless.
Mama Luigi said:
I switched from Cyanogenmod 13.0 to LineageOS 14.1 when CM died in late December. Was very excited about Nougat at first, but there are a lot of bugs with mobile data, bluetooth, etc. After a couple months of flashing nightly builds hoping for things to get better, I gave up and went back to the last build of CM13 and all the bugs have disappeared and my battery life improved as well. Plus I can use Xposed which is nice.
Only problem is CM13 will never be updated so I'm stuck on December 2016 security patch level. Thus I am steadily getting more outdated. With no official Nougat ever coming to the G3, it makes me wonder if the bugs in LOS14.1 will ever be fixed since there will never be an official source to base it on. I know there are other Nougat-based roms out there but I imagine they must suffer from the same bugs as LineageOS.
I don't care about new features or anything, I just would like to have security updates because it seems like a bad idea not to.
Is this what I'm looking for? https://forum.xda-developers.com/20...nt/rom-lineageos-13-0-moto-g-3rd-gen-t3530402
Click to expand...
Click to collapse
mokee is in active development
I too had this confusion....all marshmallow roms stopped development and i never wanted to try any N rom coz i thought its not stable. i tried many nougat roms and they all had many bugs...... But now I'm settled for tesla rom......its a great rom and havent found any bugs...... Its the fastest rom among N roms....... I'm using it with optimus kernel and battery backup is also very good......
https://forum.xda-developers.com/2015-moto-g/development/rom-gzroms-tesla-t3350265
KrisM22 said:
Consider this - most folks with Moto G3 are on stock M. With no security updates.
With CM13 you say you are on Dec '16. That's a year and a half better than stock.
Maybe you aren't really so bad off...
Click to expand...
Click to collapse
A January 2017 security patch for the stock 6.0 XT1540 just came out just a few weeks ago.
Mama Luigi said:
I don't care about new features or anything, I just would like to have security updates because it seems like a bad idea not to.
Click to expand...
Click to collapse
The misconception here is that those "security updates" are actually of any real world use... they are not. There are no real security exploits of any real significance to modern Android devices, all of these horrible vulnerabilities like Quadrooter, Certi-gate, Stagefright, FakeID, Towelroot, and Dirty Cow are of not really problems as outside of a controlled lab environment, there are no working exploits of any of them.
Security updates by themselves are a marketing ploy that sounds good, unless your devices is 3 or 4 years old (in which case you should just be replacing it anyway since there are no security updates).
A lot of people will disagree with me, but all these security updates are just media hype and company propaganda, there is no real worry about them because of all the other stuff we have in Android, like app sandboxing, DMverity, SElinux, and other mechanisms that even if an exploit does get past one things it has to deal with the others.
I am not an naive and I know what I am talking about, I have worked in the telecommunications and networking industry for over 25 years and deal with security in both telecom and IT daily. You have far more important things to worry about than security updates for your Android phone, unless you live on pirate apps and porn.
georgearn said:
Have you ever really felt any real harm having "outdated" security patch? I'm kin to hear exact cases when your phone needs a new security patch. Or maybe you are installing experimental software from deep web? There are a lot of users with devices with Android 5.0.2 or 5.1 that haven't even heard about security patches, and they feel themselves very comfortable using their daily package of normal and verified software. So I don't see any point to look for a developing MM 6.0.1 ROM, as it is already developed and bugless.
Click to expand...
Click to collapse
acejavelin said:
The misconception here is that those "security updates" are actually of any real world use... they are not. There are no real security exploits of any real significance to modern Android devices, all of these horrible vulnerabilities like Quadrooter, Certi-gate, Stagefright, FakeID, Towelroot, and Dirty Cow are of not really problems as outside of a controlled lab environment, there are no working exploits of any of them.
Security updates by themselves are a marketing ploy that sounds good, unless your devices is 3 or 4 years old (in which case you should just be replacing it anyway since there are no security updates).
A lot of people will disagree with me, but all these security updates are just media hype and company propaganda, there is no real worry about them because of all the other stuff we have in Android, like app sandboxing, DMverity, SElinux, and other mechanisms that even if an exploit does get past one things it has to deal with the others.
I am not an naive and I know what I am talking about, I have worked in the telecommunications and networking industry for over 25 years and deal with security in both telecom and IT daily. You have far more important things to worry about than security updates for your Android phone, unless you live on pirate apps and porn.
Click to expand...
Click to collapse
Thanks guys. No, I haven't felt "unsafe" from not being totally updated, but if you were unsafe would you even know it? Isn't that part of the problem? At any rate, I suppose the real danger isn't my phone's OS but rather my online accounts, where my personal information is stored on the servers of who knows how many companies.
Between ad blocking and just careful habits and knowledge, I'm guessing I'm also much safer than the average smartphone user.
I will keep rolling with cm13 unless/until Alberto hammers out the Bluetooth bugs in Lineage. Nougat is cool but it's not worth my headphones disconnecting multiple times per day.
Maybe this reply is off topic, but as far as my xt1550 is considered, all bugs related to data and Bluetooth have been fixed.
Regarding the "staying updated" thing, maybe you will have to jump to Nougat one day or the other if you want to increase the life of the phone.
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/
Okay, strategy question for you. I've recently purchased the U12+, and I am loving it so far. However, I am concerned about security patches / support for the next year or so. It seems to me that if you want the best experience with patching, it's Pixel, Android One, or Essential / Sony. I am not terribly concerned about major releases, though I know we'll be getting Pie at some point.
If patching can be done after google releases them, that's all good with me... but I *think* they need to go through the vendor before they come to @LeeDroid ROM's etc... Is that true?
If so, I may need to move on... or is there hope with Android One via Treble?
charlatan01 said:
Okay, strategy question for you. I've recently purchased the U12+, and I am loving it so far. However, I am concerned about security patches / support for the next year or so. It seems to me that if you want the best experience with patching, it's Pixel, Android One, or Essential / Sony. I am not terribly concerned about major releases, though I know we'll be getting Pie at some point.
If patching can be done after google releases them, that's all good with me... but I *think* they need to go through the vendor before they come to @LeeDroid ROM's etc... Is that true?
If so, I may need to move on... or is there hope with Android One via Treble?
Click to expand...
Click to collapse
One will never come to the U12+.
Security patches are not for all devices, so if it is not unsecure there is no need for a patch.
But before it is included in leedroid HTC has to release a new base with the patches included.
Except some special patches that are baken into custom Kernels.
diamond09 said:
One will never come to the U12+.
Security patches are not for all devices, so if it is not unsecure there is no need for a patch.
Click to expand...
Click to collapse
I'm sorry, but that is just not true. Every month there are android updates, and they are NOT device specific.
Security bulletin for July.
If you're not getting monthlies, you're at risk, however small that may be.
charlatan01 said:
I'm sorry, but that is just not true. Every month there are android updates, and they are NOT device specific.
Security bulletin for July.
If you're not getting monthlies, you're at risk, however small that may be.
Click to expand...
Click to collapse
HTC includes most patches from upcoming security patches in their "older" one...like in june patch, there are patches for july etc included. that's why HTC only patches and has most of the time an older date, because they only patch necessary stuff. if they would implement everything, even the bugs from google they would have the newest date, but also a lot more to do, which is stupid, wasting time and money
Also got to take into account. Google test, creates, and updates security issues with their software build. AOSP/Pixel software. HTC and Samsung for example make significant changes to Android. Some of which are the fixes that Google either told them about or the other way around.
As mentioned before and past history has shown. HTC tends to release and fix security issues before Google does. I'm not saying HTC software is perfect, but some security might not apply to manufactures that make significant changes to Android.
But generally I believe that some things would be better if security updates came straight from Google. Android already is build around a module concept. Maybe they can do something similar concerning security patches. Peace of mind etc.
Tachi91 said:
Also got to take into account. Google test, creates, and updates security issues with their software build. AOSP/Pixel software. HTC and Samsung for example make significant changes to Android. Some of which are the fixes that Google either told them about or the other way around.
As mentioned before and past history has shown. HTC tends to release and fix security issues before Google does. I'm not saying HTC software is perfect, but some security might not apply to manufactures that make significant changes to Android.
But generally I believe that some things would be better if security updates came straight from Google. Android already is build around a module concept. Maybe they can do something similar concerning security patches. Peace of mind etc.
Click to expand...
Click to collapse
android Q changes those things. each phone released with android Q will have a generic system image (GSI), so they can be used straight from google, that'S why security updates will come directly from google and the OEM can update the vendor apart from it and also maybe patch the system with "modules" so you can still have htc sense, touchwiz or whatever comes with the phone