I been searching how to update the tzdata (aka timeinfo.dat) in Android, and so far I can't find an answer.
I live in Buenos Aires, Argentina, and have a HTC HERO and the time zone in android has been broken for more than 9 months now.
The correct timezone is GMT -3 with no summer time, but for some reason it keeps saying GMT -2 (Summer time).
I decided to find a way to change this information and I found that the timezone information is from 2007. I found this the file called zoneinfo.version in Raindroid 1.1. (A 2.1 Custom Rom)
Can anyone give me a hint on how to do this?
I'm a very technical person (I'm what could be translated as "Engineering Informatics" graduate {CS} ) and I'm not afraid on compiling source, or doing whatever it takes to fix this.
Thanks everyone so much for your time.
Update: I found an updated version from Kagudroid, but my question remains the same.
--
From here you can get the last tzdata: ftp://elsie.nci.nih.gov/pub/
Guess you can find a better response at http://source.android.com/discuss. You may check out Cyanogenmod.com for more information.
BTW, if it's in the sources at Google, report it at b.android.com as well.
Cheers.
Thanks you so much. I will see what I can do. ^_^
Zic For Windows
I present to all of you Zic for Windows.
This application will extract timezone data from IANA. So, you can used it to create tzdata or zoneinfo using zonecompactor.
Source file taken from IANA timezone data 2016j.
I'm modify that source to comply with JellyBean, KitKat and Lollipop.
I'm also modify that source to comply with Marshmallow.
With this, hopefully, the zone data for old android can be updated with the current timezone from IANA.
You can download binary file and modified source file from my attachment.
For JellyBean, KitKat and Lollipop, please download Lollipop.
If you want to compile my modified source file, please use GCC 6.x (msys or others). Remember 32-bit only.
com.force.timezonefixer
Enviado desde mi GT-S5310L mediante Tapatalk
Related
Hi all,
Can someone point out a tutorial or share some thoughts on building CM13?
Problem: it took around ~6 hours to build CyanogenMod yesterday because of the kernel compilation (i3 processor on an Asus laptop running Linux Mint Debian Edition).
I want't to be able to use specific repositories but don't want to compile the kernel everytime I "brunch bacon".
I hear it is possible to point out a specific boot.img (previsously built), include it while building, thus preventing the compilation of the kernel, which is very time consuming and doesnt make any sense, unless something changed.
But couldn't find any tutorial on this and the Cyanogenmod documentation is a bit confusing.
I bet this isn't new to some of few, so, could you please point me in the right direction here?
Regards,
- aurocha
aurocha said:
Hi all,
Can someone point out a tutorial or share some thoughts on building CM13?
Problem: it took around ~6 hours to build CyanogenMod yesterday because of the kernel compilation (i3 processor on an Asus laptop running Linux Mint Debian Edition).
I want't to be able to use specific repositories but don't want to compile the kernel everytime I "brunch bacon".
I hear it is possible to point out a specific boot.img (previsously built), include it while building, thus preventing the compilation of the kernel, which is very time consuming and doesnt make any sense, unless something changed.
But couldn't find any tutorial on this and the Cyanogenmod documentation is a bit confusing.
I bet this isn't new to some of few, so, could you please point me in the right direction here?
Regards,
- aurocha
Click to expand...
Click to collapse
just run "make bootimage" after lunching device
But that would build the kernel, right?
Enviado do meu A0001 através de Tapatalk
I was wondering how hard it would be to alter the patches in the update.zip found here to work with the leon. I know the two phones are almost identical as seen here. as of right now there is only an update for the sprint/boost/virgin g-stylo's but there is supposed to be one coming for the t-mobile/mpcs one soon. i've taken the source and started tinkering with it. I've compiled the kernel changing TARGET_PRODUCT=g4stylusds_global_com to TARGET_PRODUCT=c50_mpcs_us but leaving the config as g4stylusds_global_com_defconfig and get far enough to get the zImage, but not the ko files. I have not yet compiled the rom, and it was about this point i started thinking about the update.zip DominicGresham was kind enough to provide us and maybe it would be easier than editing the source. any input would be appreciated. I like 6.x and would like to have it on my daily driver, and help everyone else that wants it for our device. i'm going to keep tinkering away until i get something besides a bootloop, and will attach the zimage i got after this test compile again on the kernel with the mpcs gstylo defconfig. i guess i should go ahead and try to compile the rom also and see how that goes. https://www.dropbox.com/sh/04pab4lbxncd7rr/AAA_GesYl74E35ikF4weaw1ca?dl=0
natediggler said:
I was wondering how hard it would be to alter the patches in the update.zip found here to work with the leon. I know the two phones are almost identical as seen here. as of right now there is only an update for the sprint/boost/virgin g-stylo's but there is supposed to be one coming for the t-mobile/mpcs one soon. i've taken the source and started tinkering with it. I've compiled the kernel changing TARGET_PRODUCT=g4stylusds_global_com to TARGET_PRODUCT=c50_mpcs_us but leaving the config as g4stylusds_global_com_defconfig and get far enough to get the zImage, but not the ko files. I have not yet compiled the rom, and it was about this point i started thinking about the update.zip DominicGresham was kind enough to provide us and maybe it would be easier than editing the source. any input would be appreciated. I like 6.x and would like to have it on my daily driver, and help everyone else that wants it for our device. i'm going to keep tinkering away until i get something besides a bootloop, and will attach the zimage i got after this test compile again on the kernel with the mpcs gstylo defconfig. i guess i should go ahead and try to compile the rom also and see how that goes. https://www.dropbox.com/sh/04pab4lbxncd7rr/AAA_GesYl74E35ikF4weaw1ca?dl=0
Click to expand...
Click to collapse
Hey are you still working on this rom? i would like to know because i can try to help in any way if needed
Me:
"Any ETA on releasing the EMUI 5.0 kernel source for the US Honor 8 FRD-L04? If EMUI is not going to keep up with the Android security patches (Still on December and it's almost April) I'd like to switch to a custom ROM that will. However that can't happen without the kernel source."
Honor USA:
"Good morning John, thank you for your great question. could you provide me with the build number on your device so that I can check on the system to see if the update to the emui 5.0 is available or not. Thank you for choosing Huawei and I hope you have a great day."
Me:
"I already have EMUI 5.0 build FRD-L04C567B360 on my phone. What I'm looking for is the EMUI 5.0 kernel source code for my device. Honor/Huawei is required to release the kernel source if requested since you're distributing binaries built off the Linux kernel source code which is distributed under the GPLv2 license."
Honor USA:
"Hello John, Thank your for contacting us, in regard your inquiry, first we need the Model of your device, in order to take a better care of you."
Me:
"Then read the software build number I gave you. The model number is the first 6 digits FRD-L04. How can you not know that?"
Quite a disappointing answer from Honor USA
Well, or just pretending :laugh:
Try to not write some many sentences with so many potential topics.
Just ask: when will Huawei release the kernel source of Nougat as is required by the Linux GPL license.
Make it maybe even clearer: Huawei is currently violating the GPL license as the kernel sources for Nougat are not released yet. When will this violation stop?
faeArai said:
Try to not write some many sentences with so many potential topics.
Just ask: when will Huawei release the kernel source of Nougat as is required by the Linux GPL license.
Make it maybe even clearer: Huawei is currently violating the GPL license as the kernel sources for Nougat are not released yet. When will this violation stop?
Click to expand...
Click to collapse
I posted the question on the Honor 8 Google+ today.
Just a straight question.
Are you going to give us this code
I have also been posting on Thier Facebook pages.
If we all keep doing this they will release just to shut us up (i hope)
Also patches for all the bugs in EMUI5, and a potential release date for EMUI5.1
Either way, it's my last Huawei phone. They clearly don't care. Very disappointing.
SolarisSixth said:
Also patches for all the bugs in EMUI5, and a potential release date for EMUI5.1
Either way, it's my last Huawei phone. They clearly don't care. Very disappointing.
Click to expand...
Click to collapse
They are not going to release to us EMUI 5.1
They have said that they will release us an update with extra features after June but not EMUI 5.1
Why i don't know.
I got an email back from Honors Facebook page.
They asked me for a screenshot of the page on my phone that says that i need kernel source code !!
This shows what we are dealing with here.
The guys at Honor ain't got a clue.
I'm guessing that EMUI is just handed down to them from Hauawi and Honor have no control or say over releasing anything
My answer from Honor USA Facebook
We have limited information on the specific kernel source code based on specific countries, as different countries will have different procedures. We suggest to refer back to Honor United Kingdom customer care at 08000 886 700 or 0800 088 6900 for better assistance. Or alternatively, you may click on the below link to find out more:
http://consumer.huawei.com/uk/support/faqs/detail/index.htm?id=77412
Those guys who are dealing with Facebook and Google+ have no idea or way to help us with the kernel code
John
The Facebook groups are only there to answer stupid questions like where can I buy this phone or what colours option is this phone available in? No tech questions what so ever.... I've given up hope on Huawei long time ago.
Honor is launching a beta program for its current hardware and upcoming software.
http://www.androidcentral.com/honor-wants-few-brave-americans-beta-test-its-buggiest-software
I doubt they're clueless. If anything the facebook rep was instructed to avoid the question, because he isn't allowed to share info about it.
johnhux7 said:
They are not going to release to us EMUI 5.1
They asked me for a screenshot of the page on my phone that says that i need kernel source code !!
Click to expand...
Click to collapse
Go to Settings ->About Phone -> Legal Information -> Open Source Licenses
And you can screenshot that first section right there that say they will provide you with a copy of kernel source code if you request it.
Ok.
So that's what they are wanting.
Thank you
---------- Post added at 08:48 PM ---------- Previous post was at 08:44 PM ----------
anks329 said:
Go to Settings ->About Phone -> Legal Information -> Open Source Licenses
And you can screenshot that first section right there that say they will provide you with a copy of kernel source code if you request it.
Click to expand...
Click to collapse
I have done it.
Don't think they have a clue
You have to take into account that the kernel, as well as every other part of the operating system is built in China, specifically, in their Jenkins instance, that's why neither Honor USA nor Honor UK will (be able to) help you.
XePeleato said:
You have to take into account that the kernel, as well as every other part of the operating system is built in China, specifically, in their Jenkins instance, that's why neither Honor USA nor Honor UK will (be able to) help you.
Click to expand...
Click to collapse
I get that but what else can we do.
We need to get them listening some how and i don't speak Chinese !!!
So I finally found Huawei's instructions for requesting the Honor 8 EMUI 4.1 opensource software here.
Here's the contents of the readme.txt file within the FRD-L04_MM_EMUI4_1_opensource.zip file:
Huawei Device Co., Ltd ("Huawei")is pleased to provide you the corresponding open source code of the device. If you want the code, please contact us with an email titled "Open Source Codes Issue" to [email protected]. Please note we may charge you the cost of physically performing source distribution like sending you a CD of the Open Source Codes, if you reqest. And the code download link will be ready soon.
Click to expand...
Click to collapse
I sent an email following their instructions requesting the EMUI 5.0 source code. We'll see if I get any response.
If not, the next step is probably to involve the Free Software Foundation (www.fsf.org). There is a page at http://www.gnu.org/licenses/gpl-violation.html describing how to report GPL violations.
There is a file at /etc/NOTICE.html.gz on the Honor 8 that contains a NOTICE.html listing all? of the opensource licensed software on the device and the specific license covering each file. One possible avenue is the f2fs software that's copyright Samsung Electronics and released under the GPLv2. They might be willing to enforce their copyright on a competitor...
But what really is the issue with the kernel? Didn't they at least released the emui 4.1 source (and so the blobs needed)?
Can't this be used in a modern kernel, too?
Even if they release emui 5 kernel, what happens, let say with lineage 15 or 16 when there is no newer emui kernel?
How do other projects handle this, as there still are new versions of lineage for old devices?
faeArai said:
But what really is the issue with the kernel? Didn't they at least released the emui 4.1 source (and so the blobs needed)?
Click to expand...
Click to collapse
Yes, they released emui 4 kernel, I don't know what do you mean with 'the blobs needed'.
faeArai said:
Even if they release emui 5 kernel, what happens, let say with lineage 15 or 16 when there is no newer emui kernel?
Click to expand...
Click to collapse
We'll use the latest kernel then.
faeArai said:
How do other projects handle this, as there still are new versions of lineage for old devices?
Click to expand...
Click to collapse
Because 'other projects' OEM's do release the kernel source.
-----------
Why does this affect development? Let's make clear the kernel / userspace barrier, the kernel is (supposed to be) open source while the userspace drivers are not, so it makes sense to use the Nougat (proprietary) pre-built drivers because they'll work better with the Android framework, but those drivers are 'tied' to the kernel. It would be an option to rollback to the emui 4 kernel, but that would also mean to use the closed source userspace drivers.
TL;DR
If we want to use the newer libraries, we need the newer kernel
I doubt it that other companies release source code for devices not longer supported. There always is an end of life and still lineage comes up with new releases for those devices.
There is still new lineage for Nexus 4 or 5 or even older devices that also needed binary drivers and from my understanding those drivers are not open source, are they? With blobs i mean the binary files.
If i remember rightly, the only device with fully open source drivers is HTC HD2 since the drivers where reverse engineered back than in the good old days.
So why can't we take the binary drivers from emui 4 and use them with some adaptation to the interface in newer kernel versions as i assume is done for other devices as there are no more official updates?
Granted I'm not a developer, but I had wondered something similar -- can we cross-compile using the closed binaries from MM using a 4.1.18 kernel version.
Hello Guys,
Today I woke up with a new idea; I want to port LineageOS to the LG V20 version H990DS. I was tinkering with this idea for about one year, but never actually wanted to make the step. Until today. I used LineageOS and CyanogenMod since 2012.
The reason why I want to create the first port is because I have the time at the moment, so why not help the community? I do have four years of programming skills C/C++. Run Linux as daily driver etc... Do know how to use git, linux, autotools etc... The tricky part however is: I never compiled a Lineage OS rom from source and I don't think the compiling would be a problem, but the LG V20 H990DS isn't officially supported. My question is: Where do I start to program? How can I compile and build a working Lineage OS for the LG H990DS. Are there any good website I can read from?
I saw this:
https://www.youtube.com/watch?v=MGI3NSJFtKA&feature=youtu.be
https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484
http://www.lineageosrom.com/2017/01/how-to-build-lineageos-rom-for-any.html
https://www.reddit.com/r/LineageOS/comments/6iie9l/how_to_compile_lineage_os_141_for_unsupported/
https://www.reddit.com/r/LineageOS/comments/684qkp/help_noob_compile_lineageos/
So to make it easy: I want to program a working LineageOS for the LG H990DS, but don't have any understanding about where to start. I do have four years of programming skills, not so much, but know C and C++ well.
Thanks in advance,
Maurice
English isn't my native language, sorry for grammars.
someone help this man up.
Did you check the existing LineageOS thread?
https://forum.xda-developers.com/v20/development/dev-cm14-t3509953/post74550386#post74550386
If you want to help, I'd suggest asking him if there's anything you can do.
Thank you for your response. I do watch that thread, because I want lineageOS for the h990ds device. The problem however is that I don't want to jump right into the code. I want to know what I am doing with each line of code. At the moment I think I have to change some things in the kernel so that it can boot, but I don't know if that's true. And there is so many documentation about how to compile lineageOS, which I don't want to do. I want to program and compile lineageOS. Every tutorial skips the program parts and just compiles lineageOS.
So maybe a good programmer can give my some advice? Where to start and where can I find some documentation?
Best regards,
Maurice
Welcome!
First off, I recommend using Ubuntu 16.04 (I personally use 16.10 however). Be sure to follow the guide you linked from chef central carefully.
For the dual SIM variant, I don't believe any current source exists. Although with the similar hardware and if you have decent skills, you could get it going.
Take a look at the existing v20 trees:
V20-common: https://github.com/LineageOS/android_device_lge_v20-common
Msm8996-common: https://github.com/LineageOS/android_device_lge_msm8996-common
H918 (as a reference): https://github.com/LineageOS/android_device_lge_h918
Kernel: https://github.com/LineageOS/android_kernel_lge_msm8996
Vendor: https://github.com/TheMuppets/proprietary_vendor_lge
Those are the basics to check out. Now I did see someone converted the H918 tree to H990. Here's a link to that for reference: https://github.com/android-device-lge-h990/android_device_lge_h990
You will definitely need to make a custom defconfig in kernel sources. The device tree changes should be rather easy. You'll need to pull vendor files from stock and import the drivers and dts files from stock kernel source. If/when you get a working kernel and device trees there's a 99% chance you will need to Port other drivers and vendor files as stock files don't play nice in aosp. If I were you, I'd start looking through commit history on GitHub to see how the other devices we're brought up. That is how I learned everything.
Also, git will be your best friend when bringing up large projects, like kernel. Learn git, get comfortable with it. Cherry-picking and merging is what keeps us going.
Best of luck!
I suppose you could say there are dueling work-in-progress H990 trees since the other one is: https://github.com/x86cpu/android_device_lge_h990
The one you pointed to is mine. I was hoping for some collaboration with @x86cpu on there (in theory @x86cpu also has permissions to modify that repository, assuming I've set things up correctly). While the initial steps have been done, it is not finished! Some issues are left for getting LineageOS operational on H990 devices.
Of crucial note the modem fix in its current form is unacceptable to LineageOS (despite working). I've got two variants of one solution almost ready, but they're yet ready.
Thank you for your answer and I will look into it. I sure hope that I can help you some day, but first I want to understand the repository. After that I will help you both to code.
Really thank you and I will do my best to catch up with you.
As for the Ubuntu version. I personally use arch Linux (with plasma), because I like it more than Ubuntu. I don't think that's a problem and else I will compile the Ubuntu programs to arch. And I know my way around got. Use it for about 4 years now and now what merging/branching rebasing etc means and know how to use it.
@emdroidle I could help
Dear fellow developers and users of this great device,
I'm working on mainline support for the p4note device family, I started with the N8010 but this is usable on all the other N80XX devices as well as they are technically all the same aside from the modem.
The current status is that an initial device tree will land in 5.11 with some components still missing but its a good start. I'm working on the rest and also I'm working on Android 11 on top of that.
This post will not be updated any longer, you can find my mainline progress here.
There is also a blog which I'll probably woefully neglect as I'm way too busy with everything in life.
Cheers
An update for my mainline progress, there is kernel logs on the display now! I'm currently working on the touch screen config.
Oh Nice to see.
But i think not many people read the General forum anymore ^^
You might want to mention this in the Dev thread.
Do you have a git repository anywhere? I found a Note 10 8000 hidden in a box and wanted to get a working small working terminal up on the wall at my 3D-Printer/Soldering-workstation, I would be happy to be tinkering around som with the code.
Nevermind, found it.
fldc said:
Do you have a git repository anywhere? I found a Note 10 8000 hidden in a box and wanted to get a working small working terminal up on the wall at my 3D-Printer/Soldering-workstation, I would be happy to be tinkering around som with the code.
Nevermind, found it.
Click to expand...
Click to collapse
Hey, great to hear that you want to tinker with it. Remember that I currently work on rev 6 of the hardware, the version info can be found in the atags of the kernel log. You may run into issues with other revisions but it should be fine.
For the wifi settings, you need the correct nvram file. I'm not yet sure whether you can determine it by the version of the hardware, the current way is a macloader in the current hardware repo.
I extracted the touchscreen firmware from the sources and put them in my buildroot repo. The driver will look for a file called maxtouch.fw on boot.
I hope this helps.
Thank you very much for the pointers, I haven't t really been into kernel development since Samsung Galaxy S2 (9100), but getting a proper Linux installation on this device would fit me perfectly so I would happily try things on my side, keep us posted.