Related
Well guys, it's a sad thing to have to say, but I've finally made the decision to move on from the Hero. Currently, I now own an EVO 3D and loving it to pieces. The Hero has been a ridiculously resilient phone. What's been done with it is nothing short of incredible. It's gone through and will probably continue to go through every version of Android that we've thrown at it.
It's been a great deal of fun being at this section of XDA, but now I must take my leave. Thank you to everyone who made my phone experience what it was.
The links in this thread should remain accurate with no need to change them, but I will not be updating it when major versions come out or if RCs come out.
Click to expand...
Click to collapse
** These CyanogenMod builds are highly experimental and unsupported. [/FONT]
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
Links
ROM: http://mirror.teamdouche.net/?device=heroc
Gapps: Universal GApps Package
Changelog: cm-nightlies by appspot
F.A.Q.
What is this?
CyanogenMod is an aftermarket firmware for a number of cell phones based on the open-source Android operating system. It offers features not found in the official Android based firmwares of vendors of these cell phones. It is community built, and open source, the heart of what Android stands for. The current version of Android that CyanogenMod is built on is 2.3 (Also known as Gingerbread)
DISCLAIMER: This is not my work. I did not help build CyanogenMod in any way, shape or form. Do NOT donate me or thank me with the assumption that I had any part in dev'ing this. I simply created this thread to help you keep track of the nightlies.
Any accidental donations given to me because of this thread will be promptly returned.
The real people you should be donating to is jaybob (if you can help us convince him to add a donate link for his hard work), Decad3nce, and of course, Darchstar himself.
Darchstar!? and Deca? and jaybob? and possibly some asop on the side?
oh man, these CM7 nightlies are gonna kick ass.
MrDowntown12 said:
Darchstar!? and Deca? and jaybob? and possibly some asop on the side?
oh man, these CM7 nightlies are gonna kick ass.
Click to expand...
Click to collapse
I know, I can't wait to see what comes out of it
LiquidSolstice said:
I know, I can't wait to see what comes out of it
Click to expand...
Click to collapse
thanks for this and for what is to come. is this going to be the thread we need to follow for 2.3 gb for now on.
so I don't have to weed through a million pages, how functional are the current builds (even non CM) at the moment? i.e. will I be on my 6.1 for a while yet? I can't imagine we can push these phones much further. Much faster and better than stock for sure, but still laggy for what I do.
danibri82 said:
so I don't have to weed through a million pages, how functional are the current builds (even non CM) at the moment? i.e. will I be on my 6.1 for a while yet? I can't imagine we can push these phones much further. Much faster and better than stock for sure, but still laggy for what I do.
Click to expand...
Click to collapse
Nightly builds of CM7 for the heroc have not been released yet, this page is more of an anticipation/preparation thread for when they do.
I just want to say "thanks" in advance to those of you who are working to make my phone better. This has been a fun ride so far...
Pete
danibri82 said:
so I don't have to weed through a million pages, how functional are the current builds (even non CM) at the moment? i.e. will I be on my 6.1 for a while yet? I can't imagine we can push these phones much further. Much faster and better than stock for sure, but still laggy for what I do.
Click to expand...
Click to collapse
From my experience the 2.3.2 rom posted by aosp has everything working save the camera (this can be fixed by using a third party camera such as camera 360) and there is a small issue with streaming videos that only allows one to watch a few videos before a reboot is needed.
damiandarkwater said:
From my experience the 2.3.2 rom posted by aosp has everything working save the camera (this can be fixed by using a third party camera such as camera 360) and there is a small issue with streaming videos that only allows one to watch a few videos before a reboot is needed.
Click to expand...
Click to collapse
The camera works, refer to:http://romrepo.info/wiki/index.php?title=Main_Page for the most recent releases to date among a wealth of other information.
silberj said:
The camera works, refer to:http://romrepo.info/wiki/index.php?title=Main_Page for the most recent releases to date among a wealth of other information.
Click to expand...
Click to collapse
Camera 360 improves the picture quality but the stock camera works fine too.
Glad to see CM7 coming, I'll have to watch for the official thread and see how it goes. I'm loving the aospCMod version right now though, smooth as butter and absolutely no issues at all so I'll stick with it for now.
Sent from my sexy aospgingermod Heroc
LiquidSolstice said:
If you're having issues with the other Gingerbread build here, or are just interested in a pure CyanogenMOD ROM straight from the source, I'd figure I'd reassure everyone that the official CM7 builds are coming soon, and darchstar will maintain them. I've opened up this thread in anticipation of his first nightly.
For those who need proof that darchstar is indeed coming back, I quote this post from the CM Forums, by Moderator ciwrl:
Source for the above post is located here.
Here are the links listed. NO NIGHTLIES ARE UP AS OF 2/17/11. They are here for when the nightlies do go up, so you can check them.
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
Download: http://mirror.teamdouche.net/?device=heroc
Gapps: http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110120-signed.zip
Changelog: http://twitter.com/cmsrc
I will be checking the CM7 forums every day for updates from Darchstar and will update this post as soon as I know more.
DISCLAIMER: This is not my work. I did not help build CyanogenMod in any way, shape or form. Do NOT donate me or thank me with the assumption that I had any part in dev'ing this. If you'd like to thank me for keeping you upadted, that's your choice, either way, it does not bother me.
Any accidental donations given to me because of this thread will be promptly returned.
Click to expand...
Click to collapse
Darch is coming back! This is huge news!
since i can't (and no one else) seems to be able to figure out how to get data2ext to work on a sense rom........i'm going to switch to gingerbread once the default camera has just as good as quality or better quality than the sense camera i'll be making my switch then. but until then i'm with the setup in my signature
Can't wait. Just came back to nightly #188 thi king we'd have more love here.
I'll be looking for an official thread posted by Darchstar.
Mmm... I knew that we would eventually get cm gingerbread. I can hardly wait!
Sent from my HERO200 using Tapatalk
It looks like the first nightly is up: http://mirror.teamdouche.net/?device=heroc
BlaqkAudio said:
It looks like the first nightly is up: http://mirror.teamdouche.net/?device=heroc
Click to expand...
Click to collapse
Yup, dl'ing now.
Thread updated.
So, what will be the difference between this and aospCMod? Will it take a while for darchstar to get to where aosp is now? I just want some distinction between the two.
c00ller said:
So, what will be the difference between this and aospCMod? Will it take a while for darchstar to get to where aosp is now? I just want some distinction between the two.
Click to expand...
Click to collapse
From what I know, the dev is totally independent, but darch had the kickstart of help from Deca and jaybob, both extremely talented devs themselves, so we'll see where it goes.
EDIT: Flashing the first build now, we'll see how it goes
So, this thread is not about when the Thunderbolt will get Cyanogenmod support, because I can search and find that.
This thread is about how "official" CM support works. When I go to the Cyanogenmod site, I see a list of officially supported devices, which if I guess, are made, maintained and released by their team? I've been following along Android forums for almost a year now and see a lot of phone users trying to give their respective phones a CM port or CM rom to use. I presume these are "unofficial" and are being put together "aftermarket" by outside developers.
How and will the Thunderbolt get adopted by the Cyanogemod team and be one of those official phones listed on their site?
I'd take the root plunge for a rom like CM, which seems to be heavily updated and maintened and has the updater which would make updates for me very easy.
The thunderbolt will eventually.. I believe the reason it's not "supported' right now is because it's still in alpha. They don't state official support until they have a solid build.
My location is in montevideo urugauy according to CM7 lol.. On the map it shows me my location but somehow it thinks im in uruguay.. Any fix for this?
marc314 said:
My location is in montevideo urugauy according to CM7 lol.. On the map it shows me my location but somehow it thinks im in uruguay.. Any fix for this?
Click to expand...
Click to collapse
Clearly you must move to Uruguay.
Sent from my ThunderBolt using Tapatalk
At this point CM7 support is mostly anecdotal experiences by users to assist other users.
necosino said:
Clearly you must move to Uruguay.
Sent from my ThunderBolt using Tapatalk
Click to expand...
Click to collapse
Mine had me in Paris somewhere. Get GPS Status from the market. From the app hit menu, tools, manage a-gps state. Hit reset. Then go through those again but hit download data this time. After that and a refresh, it should all be well.
Sent from my ADR6400L using XDA Premium App
obeygiant said:
Mine had me in Paris somewhere. Get GPS Status from the market. From the app hit menu, tools, manage a-gps state. Hit reset. Then go through those again but hit download data this time. After that and a refresh, it should all be well.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Thanks man.. Let me try this out..
macewank said:
The thunderbolt will eventually.. I believe the reason it's not "supported' right now is because it's still in alpha. They don't state official support until they have a solid build.
Click to expand...
Click to collapse
Where is it even listed in alpha?
http://wiki.cyanogenmod.com/index.php?title=Latest_Version#HTC_Thunderbolt
All I see are messages in the Wiki that the Thunderbolt is not yet supported. I am not talking about the port(s) that are here in XDA... I'm referring to a release by the CM team.
I am not rooted, and haven't played around with Rom Manager, but is an alpha "official" version of CM listed in there for the Thunderbolt?
Bwangster12 said:
Where is it even listed in alpha?
http://wiki.cyanogenmod.com/index.php?title=Latest_Version#HTC_Thunderbolt
All I see are messages in the Wiki that the Thunderbolt is not yet supported. I am not talking about the port(s) that are here in XDA... I'm referring to a release by the CM team.
I am not rooted, and haven't played around with Rom Manager, but is an alpha "official" version of CM listed in there for the Thunderbolt?
Click to expand...
Click to collapse
slayher is part of the CM team and the thunderbolt CM7 he's building is the "official" version. it's not listed under the officially supported devices because the code isn't anywhere near stable enough to be considered a daily driver. it's buggy, things don't work like they should. it's not release quality software yet.
all CM builds are technically ports. the base CM code doesn't just magically work on all phones by itself. there are specific people assigned as vendor maintainers that are generally responsible for making sure that CM works on their individually assigned device. see http://wiki.cyanogenmod.com/index.php?title=Community_Members for a list.
edit: i'm sure I did a poor job of explaining it and there's way more to it than what I described, but that's the gist. hope it makes sense
The CM7 alpha for the Thunderbolt is awesome. I have yet to find anything that it does not do well... except wireless tether..
4g, wifi for some people, battery life, soft buttons lighting up, call volume, getting settings to stick.
Just some of the bugs still plagueing CM7 for the thunderbolt.
Sent from my ThunderBolt using XDA App
It seems to be coming along nicely from my end user perspective. I'm running the pre-alpha pre-release on my TB from http://forum.xda-developers.com/showthread.php?t=1049542
I've been using it as a daily driver because of its Netflix support. One of the users in that thread posted a kernel and wifi fix which seem to greatly improve wifi and data connectivity, at least for me. I can deal with some minor bugs and annoyances. I'm just happy to have Netflix.
So once it becomes more stable, is considered a daily driver and presumably added to their support page....it will show up in rim manager and have the cyanogenmod updater support?
Right now for updates, you havta just keeping flashing the time from ur flash card right?
Bwangster12 said:
So once it becomes more stable, is considered a daily driver and presumably added to their support page....it will show up in rim manager and have the cyanogenmod updater support?
Right now for updates, you havta just keeping flashing the time from ur flash card right?
Click to expand...
Click to collapse
yep! i don't suspect it will be too much longer before we've got official support. exciting times
It's the only LTE phone. That's why it will take a while to get all bugs cleaned to be in the supported list.
Sent from my thunderbolt
Thats fine... didn't mean this to sound like a pushy thread. I thought the description given in this thread was fantastic, thanks. I was unclear as to what exactly happens when CM releases a rom.
I haven't rooted yet, but am sort of waiting for CM. From what I've read, it seems to be one of the most stable and maintained roms available and one of my main concerns is "quality" and maintaince/updates. Some of the roms available now sound good, but I don't wanna deal with having to be flashing left and right when new updates get released by Verizon.
My assumption with CM is that I can put install it with Rom manager and worry about updates using their Updater, right? Any GPS issues, battery concerns, whatever would be dealt with by CM?
This thread can be in violation of the XDA rules, but those were not clear in this regard I have therefore still opened this thread and I would like to ask the MODs to close this thread if it does appear to be in violation of the rules. I also would like to mention that this thread does not have the intention to disrespect any developers and that I appreciate the work every dev has done for the Note 3.
What I would like to be discussed in this thread is the stability of the different Android Lollipop roms. Since most of the devs have not made a seperate thread for their (at this stage alpha) builds of Lollipop. I would like to collect the experiences of the users from these alpha's.
At this stage there are 3 builds of Lollipop that I know of in alphabetical order:
Slayer (it is said to be a port, but since the original rom was for the HLTETMO. I think that it is mostly only a change in the 'device checking' file. The dev has himself stated that he does not intend to make any more builds in the near future it was more a proof of concept. The unofficial thread for Slayer's rom: http://forum.xda-developers.com/gal...m-cyanogenmod-12-lollipop-build-1-16-t2942687
Temasek: this is just an experimental build this dev has posted. I do not have any statement regarding support. Now on preview 2: http://forum.xda-developers.com/showpost.php?p=56934897&postcount=6046
Zion: also just an initial build (I think). Also no statements regarding support. The build from ZION: http://forum.xda-developers.com/showpost.php?p=56900235&postcount=542
I would like the structure of the posts in this thread to be:
Device: hlte/hltespr/hltetmo/hltevzw/hlteatt/hltexx/hlteusc/hltevan
ROM: Slayer/Temasek/Zion
What works: WIFI/Calling/etc.
What does not work/bugs: Random reboots, no network
Other remarks:
Again, if I have offended anyone in anyway I would like to apologise and I didn't intend to do so. Mod's could you then remove this thread.
And most importantly I would like to thank the devs for releasing these builds.
I can't even get temasek's build to boot.
speedyjay said:
I can't even get temasek's build to boot.
Click to expand...
Click to collapse
Booted and with LTE.
temasek said:
Booted and with LTE.
Click to expand...
Click to collapse
Share and share alike my good friend?? Lol
I've been using android 5.0 from slayer por as daily driver, I have HLTE and I have wifi, LTE, bluetooth and all works so nice and beautiful. The main problems are the camera and there are a lot of apps that not work
Today I will to try Temasek's port
Miniprepumen said:
I've been using android 5.0 from slayer por as daily driver, I have HLTE and I have wifi, LTE, bluetooth and all works so nice and beautiful. The main problems are the camera and there are a lot of apps that not work
Today I will to try Temasek's port
Click to expand...
Click to collapse
Port? It's built from source and not a port.
PREVIEW 2 is up.
temasek said:
Port? It's built from source and not a port.
PREVIEW 2 is up.
Click to expand...
Click to collapse
Sorry mistake
Downloading !!
Miniprepumen said:
Sorry mistake
Downloading !!
Click to expand...
Click to collapse
It's a preview so don't get so excited.
temasek said:
It's a preview so don't get so excited.
Click to expand...
Click to collapse
Works very well, LTE works normal, wifi too, I can do calls without any problem, and very very smooth and fast.
Problems for now: There are apps that not work, but very very good job. Thanks really
Edit: camera not works.
Wait where is zion's build? How's google now on all these builds? On Slayer's it's broken / causes reboots
My two cents on the port and on temaseks build.
The port is quite stable and random reboots usually come from incompatible apps or missing libs (as i read). I have managed to rest a lot of apps causing me trouble, but a lot of them are not yet optimized for L. The rom also has anomalies, strange stuff like closing all apps will close system ui (which is a bug not a feature, just in case i confused you). Weird stuff crash, such as Documents, which seems to be the mother of all other apps since it uses it to pick files for attach and e.t.c..
where as temaseks is very fragile. Not sure why but i barely made it to the homescreen, it kept on crashing a lot and rebooting prior to the homescreen.
Both are sort of proof of concepts, the port however is quite damn stable for an initial preview build, and yea, both surprised me with their early appearance
PlutoDelic said:
My two cents on the port and on temaseks build.
The port is quite stable and random reboots usually come from incompatible apps or missing libs (as i read). I have managed to rest a lot of apps causing me trouble, but a lot of them are not yet optimized for L. The rom also has anomalies, strange stuff like closing all apps will close system ui (which is a bug not a feature, just in case i confused you). Weird stuff crash, such as Documents, which seems to be the mother of all other apps since it uses it to pick files for attach and e.t.c..
where as temaseks is very fragile. Not sure why but i barely made it to the homescreen, it kept on crashing a lot and rebooting prior to the homescreen.
Both are sort of proof of concepts, the port however is quite damn stable for an initial preview build, and yea, both surprised me with their early appearance
Click to expand...
Click to collapse
Preview 2?
Tema prev 2 fixes the touch button wake for me. But WiFi + Google now still cases reboot. Google now hotword doesn't seem to work which it does on slayer. All camera apps fc. And the home button still doesn't wake the device. Aside from those it seems near perfect. Thanks a ton!
Sent from my SM-N9005 using XDA Premium HD app
temasek said:
Preview 2?
Click to expand...
Click to collapse
Actually no my friend, i just read it 10 minutes ago and am downloading as i write.
I did not want to spam around and used this thread exactly for expressing opinions, as i know both roms are early stage builds and none of the devs should be bombarded with requests anyway.
Will report back.
I just need spotify working them I'm happy as Larry lol
temasek said:
Preview 2?
Click to expand...
Click to collapse
One hell of a ROM at the moment, havent had a single crash and loaded loads of apps that used to crash in nearly all Lollipop builds. Too bad your ROM doesnt have the flashlight in the notification drawer, was very useful.
Right I must be blind. I can only find the ROM thread that is a cyanogenmod 12 PORT.
Can't even find any other Lollipop ROM!
can someone share the links please?
Hope their compatible with the international Note 3
Suggestion
hom.hom said:
This thread can be in violation of the XDA rules, but those were not clear in this regard I have therefore still opened this thread and I would like to ask the MODs to close this thread if it does appear to be in violation of the rules. I also would like to mention that this thread does not have the intention to disrespect any developers and that I appreciate the work every dev has done for the Note 3......
At this stage there are 3 builds of Lollipop that I know of in alphabetical order:
Slayer (it is said to be a port, but since the original rom was for the HLTETMO. I think that it is mostly only a change in the 'device checking' file. The dev has himself stated that he does not intend to make any more builds in the near future it was more a proof of concept.
Temasek: this is just an experimental build this dev has posted. I do not have any statement regarding support.
Zion: also just an initial build (I think). Also no statements regarding support.
I would like the structure of the posts in this thread to be:
ROM: Slayer/Temasek/Zion
What works: WIFI/Calling/etc.
What does not work/bugs: Random reboots, no network
Other remarks:
Again, if I have offended anyone in anyway I would like to apologise and I didn't intend to do so. Mod's could you then remove this thread.
And most importantly I would like to thank the devs for releasing these builds.
Click to expand...
Click to collapse
We can assume there will be a ton of reports here of what is working and what isn't (probably duplicates or even 5 times the same report as we saw in Unnofficial CM12 Port from Jamal's thread...). I would advise everyone to post phone info after every report. Because there is a confusion of what is working on which model.... You might wanna add this to OP so people can actually see since my post will be long forgotten after pages and pages of comments.
Plus you might add link to Jamal's thread and download links for Zion and Temasek's ROM... Not everyone has those since they are buried in an ocean of posts over at Jamall's thread. @AndroidInsanity here they are:
1. @jamal2367 thread
http://forum.xda-developers.com/gal...m-cyanogenmod-12-lollipop-build-1-16-t2942687
2. @ZION959 cm 12 unofficial
https://s.basketbuild.com/devs/Zion959/L/HLTE/
3. @temasek Build
http://d-h.st/users/temasek/?fld_id=41330#files
SM-N9005 (would be an example, so people know what phone is about. I know some have details listed in signature but not everyone).
and as always noone cares about exynos note 3...
ereneren564 said:
and as always noone cares about exynos note 3...
Click to expand...
Click to collapse
And rightfully so, if you buy an exynos device you should know that developers do not support these devices. Because the documentation of exynos chips is practically non existent. I am sorry, but with regard to custom aosp roms and devices with exynos chip consider this an expensive lesson. For support for these devices complain to Samsung.
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/
X86 Atom Android tablet BLISS ROM. Kernel source & HALS, is tha enough to get going?
I have a TX201LA tablet runs Android 4.2. Its a dual device 2 systems in 1. The tablet half is what i am focusing on. NOT the dock as I have windows 10 running fine on that half. The tablet is nearly useless as it is on android 4.2. I've been exploring a few options for getting an android update. My tablet runs an atom x86 cpu with 2GB of ram and is quad core cloevertrail CPU x2560. Plenty of power to run a newer android or even chromeOS, cloudready, or remixOS. I've explored those options but Bliss is the most straight forward as there are already x86 builds of Bliss. I think support should be relatively easy to add for my device.
There are a few caveats however I know ways to overcome them if I can get a rom to load.
1. I dont have a unlocked bootloader but I maybe able to unlock using zenfone 5 unlock method. Still no custom rom has ever been made for my tablet, only for similar devices like zenfone 5, galaxy tab 3 10.1, & dell venue 7.
2. Once I get it unlocked, I can load CWM or use flashfire. My tablet boots with Droidboot, which I can replace with CWN via again a zenfone 5 exploit that I have confirmed works with my tablet.
3. Would bliss load things like my LCD driver, touch screen etc? That is possibly the biggest issue. I have the kernel code here, UPDATED: http://support.asus.com.cn/Download....1LAF&p=3&s=587 OR here original: http://support.asus.com.cn/Download....01LA&p=3&s=587
3A. If the kernel code has all the HALS isnt it possible to build a Bliss rom that would be loaded via CWM/Flashfire and then boot-able?
3B. Could the Bliss team build a rom with the kernel code listed above, that I could then test? Or would the bliss team need to the device (I would think not, i hope). If a rom could be created I would GLADLY donate to BLISS.
Love to find out if this is possible. THANKS
madhits45 said:
I have a TX201LA tablet runs Android 4.2. Its a dual device 2 systems in 1. The tablet half is what i am focusing on. NOT the dock as I have windows 10 running fine on that half. The tablet is nearly useless as it is on android 4.2. I've been exploring a few options for getting an android update. My tablet runs an atom x86 cpu with 2GB of ram and is quad core cloevertrail CPU x2560. Plenty of power to run a newer android or even chromeOS, cloudready, or remixOS. I've explored those options but Bliss is the most straight forward as there are already x86 builds of Bliss. I think support should be relatively easy to add for my device.
There are a few caveats however I know ways to overcome them if I can get a rom to load.
1. I dont have a unlocked bootloader but I maybe able to unlock using zenfone 5 unlock method. Still no custom rom has ever been made for my tablet, only for similar devices like zenfone 5, galaxy tab 3 10.1, & dell venue 7.
2. Once I get it unlocked, I can load CWM or use flashfire. My tablet boots with Droidboot, which I can replace with CWN via again a zenfone 5 exploit that I have confirmed works with my tablet.
3. Would bliss load things like my LCD driver, touch screen etc? That is possibly the biggest issue. I have the kernel code here, UPDATED: http://support.asus.com.cn/Download....1LAF&p=3&s=587 OR here original: http://support.asus.com.cn/Download....01LA&p=3&s=587
3A. If the kernel code has all the HALS isnt it possible to build a Bliss rom that would be loaded via CWM/Flashfire and then boot-able?
3B. Could the Bliss team build a rom with the kernel code listed above, that I could then test? Or would the bliss team need to the device (I would think not, i hope). If a rom could be created I would GLADLY donate to BLISS.
Love to find out if this is possible. THANKS
Click to expand...
Click to collapse
For one, you should ask Bliss OS (x86) related questions in the Bliss OS thread: https://forum.xda-developers.com/bliss-roms/bliss-roms-development/x86-bliss-x86-pc-s-t3534657
Second, I tend to only use source dumps that maintain proper commit attribution. This is our way of giving credit where it is due (the original developers) Most of the source dumps I come across are a bunch of source code, with one commit at best titled, "initial commit" or "dump", and this to me says that there is something not trustworthy about it. I would like to see all the individual commits and changes made throughout the commit history, as this allows us to easily target changes that were made for that specific device.
If others want to go through the trouble of picking out those differences and creating a pull request with the proper attribution attached, we have no issues merging into our releases after testing.
electrikjesus said:
For one, you should ask Bliss OS (x86) related questions in the Bliss OS thread: https://forum.xda-developers.com/bliss-roms/bliss-roms-development/x86-bliss-x86-pc-s-t3534657
Second, I tend to only use source dumps that maintain proper commit attribution. This is our way of giving credit where it is due (the original developers) Most of the source dumps I come across are a bunch of source code, with one commit at best titled, "initial commit" or "dump", and this to me says that there is something not trustworthy about it. I would like to see all the individual commits and changes made throughout the commit history, as this allows us to easily target changes that were made for that specific device.
If others want to go through the trouble of picking out those differences and creating a pull request with the proper attribution attached, we have no issues merging into our releases after testing.
Click to expand...
Click to collapse
Did you look at my source to see if this is a problem? I'm not exactly sure how it needs to look but is this something you have found to be the case with other asus sources in the past? I'd be surprised if it was. I'd love to get a bliss rom for my tablet but I figured this would not be so easy even with x86 support being its base.
madhits45 said:
Did you look at my source to see if this is a problem? I'm not exactly sure how it needs to look but is this something you have found to be the case with other asus sources in the past? I'd be surprised if it was. I'd love to get a bliss rom for my tablet but I figured this would not be so easy even with x86 support being its base.
Click to expand...
Click to collapse
By the time I read your post, the links didn't work. And of the Asus source dumps I've seen in the past, they haven't included any git history
electrikjesus said:
By the time I read your post, the links didn't work. And of the Asus source dumps I've seen in the past, they haven't included any git history
Click to expand...
Click to collapse
Hey Electrik jesus, Here is the new link: https://www.asus.com/2-in-1-PCs/ASUS_Transformer_Book_Trio_TX201LA/HelpDesk_Download/
I'm from Michigan to.. So hopefully you can help another Michigander lol with a bliss build. Asus recently changed up there whole support site and the source code used to only be available on the international site now it seems its also on there US site. The Tx201LA was sold more overseas then in the US. It so similar to about 50 other devices (same Soc) asus made but mostly a lot of them are phones.
madhits45 said:
Hey Electrik jesus, Here is the new link: https://www.asus.com/2-in-1-PCs/ASUS_Transformer_Book_Trio_TX201LA/HelpDesk_Download/
I'm from Michigan to.. So hopefully you can help another Michigander lol with a bliss build. Asus recently changed up there whole support site and the source code used to only be available on the international site now it seems its also on there US site. The Tx201LA was sold more overseas then in the US. It so similar to about 50 other devices (same Soc) asus made but mostly a lot of them are phones.
Click to expand...
Click to collapse
I checked it out, and it is just as I was expecting. no .git folder or anything to show what commits were made on top of the standard kernel source. I guess the only thing we can do about it though is set an example of how to do it...
Example of how a kernel commit history could look: https://github.com/BlissRoms-x86/platform_kernel_common/commits/k4.15.10-ipts
electrikjesus said:
I checked it out, and it is just as I was expecting. no .git folder or anything to show what commits were made on top of the standard kernel source. I guess the only thing we can do about it though is set an example of how to do it...
Example of how a kernel commit history could look: https://github.com/BlissRoms-x86/platform_kernel_common/commits/k4.15.10-ipts
Click to expand...
Click to collapse
So if I understand you correctly the source code needs to be gone through to be pick out the comments etc and then it can be pulled into the bliss x86 source for merging? I think this is above my skill set, what can I do if I dont have the skills to do this?
madhits45 said:
So if I understand you correctly the source code needs to be gone through to be pick out the comments etc and then it can be pulled into the bliss x86 source for merging? I think this is above my skill set, what can I do if I dont have the skills to do this?
Click to expand...
Click to collapse
It's more of a prevention on our end from not giving attribution to the original author. Let's say that someone who worked on a linux project, got the GPU to finally work right with the chipsets in your ASUS. I would like to see that one guy's additions, but even moreso, I would like to see ASUS show that they used his work. Because for all we know, there are hundreds of commits in there that were added, and some of that could be work that someone else deserves to be reimbursed for. The fact that they removed the .git folder shows that they have something to hide. Calling it "trade secrets" shouldn't be allowed when it comes to kernel code.
electrikjesus said:
It's more of a prevention on our end from not giving attribution to the original author. Let's say that someone who worked on a linux project, got the GPU to finally work right with the chipsets in your ASUS. I would like to see that one guy's additions, but even moreso, I would like to see ASUS show that they used his work. Because for all we know, there are hundreds of commits in there that were added, and some of that could be work that someone else deserves to be reimbursed for. The fact that they removed the .git folder shows that they have something to hide. Calling it "trade secrets" shouldn't be allowed when it comes to kernel code.
Click to expand...
Click to collapse
So its about credit and royalties? I understand being upset at asus because they did not or have not credited someone but what can i do about that? Am I stuck at not being able to have my device supported because asus is a bad actor? Is there any way I can get support?
madhits45 said:
So its about credit and royalties? I understand being upset at asus because they did not or have not credited someone but what can i do about that? Am I stuck at not being able to have my device supported because asus is a bad actor? Is there any way I can get support?
Click to expand...
Click to collapse
There is, you could take the route Jakeday has for the Surface line. Since we don't know the author, he created patches to add the support needed to the kernel. It's far from the easy road, but this is what helps developers far more than any source dump
https://github.com/jakeday/linux-surface
electrikjesus said:
There is, you could take the route Jakeday has for the Surface line. Since we don't know the author, he created patches to add the support needed to the kernel. It's far from the easy road, but this is what helps developers far more than any source dump
https://github.com/jakeday/linux-surface
Click to expand...
Click to collapse
What I am confused about is this.
1. Is it a protocol thing? IE asus did not give credit and thus bliss refuses to add support unless they do.
OR
2. Is it an actual road block? IE we cant use the source code as is because it needs more information or reformatting?
Or is it both with more weight on #2?
If its #1 then can we make an exception? and if it is #2 why isnt there some sort of code AI that can redo the code to make it conform to the needed edits, seems like that should be possible. I would hope that if it is #1 only that you would admit that is all it is and help more people instead of forcing people to work around the bureaucracy brought onto them by bad actors like asus.
madhits45 said:
What I am confused about is this.
1. Is it a protocol thing? IE asus did not give credit and thus bliss refuses to add support unless they do.
OR
2. Is it an actual road block? IE we cant use the source code as is because it needs more information or reformatting?
Or is it both with more weight on #2?
If its #1 then can we make an exception? and if it is #2 why isnt there some sort of code AI that can redo the code to make it conform to the needed edits, seems like that should be possible. I would hope that if it is #1 only that you would admit that is all it is and help more people instead of forcing people to work around the bureaucracy brought onto them by bad actors like asus.
Click to expand...
Click to collapse
It's the third option, I'm too busy to do the work for something that is more important to you than it is to me.
electrikjesus said:
It's the third option, I'm too busy to do the work for something that is more important to you than it is to me.
Click to expand...
Click to collapse
LOL.. Pretty PLEASE, with big traverse city cherrys on top.
I have also emailed asus to see if they will look at the source code again to properly format it, not likely but worth a shot.
Does this help: https://proandroiddev.com/ooga-chaka-git-hooks-to-enforce-code-quality-11ce8d0d23cb
Is the process of going through the code very time consuming? So even if using git hooks it will take time? Im still trying to understand why there is no AI that can go through it.
electrikjesus said:
It's the third option, I'm too busy to do the work for something that is more important to you than it is to me.
Click to expand...
Click to collapse
It is important for several people. I hope at some point you have enough time to be able to help us. please help.
I am revisiting this conversation after a few months, and for starters, I would like to say I'm sorry for being rude. Secondly, I would like to use this conversation to start change where we need it. Innovation is the key point here. and if any of us are to build off of one another, we must work together to make it all possible. The lack of commit attribution by OEMs is a blatant disregard for GPL and Open Source licensing. As a ROM team, I would love to work with any OEM to help them through the process of adding a proper commit history. As Bliss, we are open to taking on any new device work, and we have in the past with Udoo-x86 & PINE64, but one of our requirements is that we can release full source, commit history, etc. Everything anyone could need to build off our work.
Too many OEM's are using patents as a way to stab eachother in the back, or use it as a "competitive" road block to stop the sale other devices that may have a similar method or feature. We don't agree with this practice and believe it is driven by greed and the wants of a few, not the needs of the majority. We as Bliss will continue to do what we can to act as an example of what should be done to best facilitate the rapid development of mobile technology and software for all parties involved.