Develop Bugs

[FROYO] [WIFI] Firmware version

UPDATE:
I've put up a post with update.zip can that change your wifi firmware version. DXJPA's wifi firmware seems to use less power than XXJPY's.
http://forum.xda-developers.com/showpost.php?p=10056736&postcount=6706
----------
Hi guys,
I'd like your help to find out which Wifi firmware versions are included with which PDA firmware package.
This is what you can do to help:
1. Find out your Wifi firmware. Turn on your Wifi, then do:
adb shell "dmesg | grep Firmware"
You should see output with the Firmware version of your Wifi.
2. If your firmware is different from what other people have already found, then if you can, please package it and attach it to your post. You can do this by:
adb shell
su
cd /system/etc/wifi
tar cvzf /sdcard/wifi-(your PDA firmware version)-firmware.tar.gz *
exit
exit
(Back in DOS)
adb pull /sdcard/wifi-(your PDA firmware version)-firmware.tar.gz
Then upload the tar.gz file.
Please use the full 5-letter version of your firmware name, for example XXJPY, and not just JPY, or DXJPA, and not just JPA.
This is what I've found so far:
DXJPA: Firmware version = wl0: Jun 4 2010 14:21:21 version 4.218.214.3
XXJPY: Firmware version = wl0: Nov 16 2010 08:56:21 version 4.218.250.38

adb shell "dmesg | grep Firmware" doesnt return anything hardcore .. on JPY with JPY modem.

ashwinds said:
adb shell "dmesg | grep Firmware" doesnt return anything hardcore .. on JPY with JPY modem.
Click to expand...
Click to collapse
You have to turn off and on your Wifi first. The driver will print the firmware version in dmesg everytime you turn on wifi.

ashwinds said:
adb shell "dmesg | grep Firmware" doesnt return anything hardcore .. on JPY with JPY modem.
Click to expand...
Click to collapse
need to turn on your wifi

hardcore said:
You have to turn off and on your Wifi first. The driver will print the firmware version in dmesg everytime you turn on wifi.
Click to expand...
Click to collapse
I have the same as yours:
XXJPY: Firmware version = wl0: Nov 16 2010 08:56:21 version 4.218.250.38
I must say that the situation is improving after about 12 hours on JPY.
I have an outlandish suspicion - dO you know if they have started to use Google Backup to store Apps and settings? Maybe it syncs with Google/Samsung when the phone is Idle? And maybe it happens only on Wifi.

I've put up a post with update.zip can that change your wifi firmware version.
http://forum.xda-developers.com/showpost.php?p=10056736&postcount=6706
DXJPA's wifi firmware seems to use less power than XXJPY's.

hardcore said:
I've put up a post with update.zip can that change your wifi firmware version.
http://forum.xda-developers.com/showpost.php?p=10056736&postcount=6706
DXJPA's wifi firmware seems to use less power than XXJPY's.
Click to expand...
Click to collapse
well... i meant to do it later tonight - but heck - let me try it for a couple of hours now
PS: flashed and it now says DXJPA: Firmware version = wl0: Jun 4 2010 14:21:21 version 4.218.214.3 - will report how it works in about couple of hours. If its any better than 8% - its good.

Italian (ITV) RSJP5 has same DXJPA wifi firmware (4.218.214.3)

hardcore said:
I've put up a post with update.zip can that change your wifi firmware version.
http://forum.xda-developers.com/showpost.php?p=10056736&postcount=6706
DXJPA's wifi firmware seems to use less power than XXJPY's.
Click to expand...
Click to collapse
How did you measure power usage and is the signal strength affected ??

EarlZ said:
How did you measure power usage and is the signal strength affected ??
Click to expand...
Click to collapse
I don't know yet, thats why I'm asking people to try it. But so far DXJPA has worked well for us in the past, so it should work well now too.
If we can identify the wifi firmware of XXJPY being the cause of higher battery usage, then we have a ready solution - use the older wifi firmware.

1 hr mark - mostly idle - looks very good - 1% drain... which is close to normal (with JPA firmware). And no big %age in "Running" - its 8% - which again sounds normal compared to the 40-50% earlier.
Update:
2 hrs - and the drain is 4% - not the best ever - but looking close to normal. Running is 10%, Wifi usage though is still 25% - but given that its just 2 hrs, that seems ok.

hardcore said:
XXJPY: Firmware version = wl0: Nov 16 2010 08:56:21 version 4.218.250.38
Click to expand...
Click to collapse
Firmware version = wl0: Nov 16 2010 08:56:21 version 4.218.250.38
I can confirm that.

XXJPU (docv4) same as XXJPY.

Okay so far it looks like there are 2 versions of the wifi firmware:
- one for 2.2 roms (e.g. dxjpa)
- one for 2.2.1 roms (e.g. xxjpy)
And the DXJPA one is working well on XXJPY. Might be too early to say for sure, but I'm getting quite good battery life with it.

I think you need to mention [MOD] on the Title.

ragin said:
I think you need to mention [MOD] on the Title.
Click to expand...
Click to collapse
theres no modding being done here.

having drain with jpy here.. just applied jpa wifi firmware will let you know how it goes.
side comments..i have the wifi upstairs two walls and a floor away with external antenna.
with jpa or my old jh2 (similiar) wifi firmware signal was marginal in the bathroom down in master bedroom (extra wall)
and about 3 out of 3 squigles curve power ranking in bedroom.. with jpy firmware it was always full.
it looks like they may have upped something that improved reception or sendng power.. .and that is one reason why
the battery went quicker.. with older even though signal strength seems lower i could still get about 2 meg or 16 megabit per
sec. sustained transfers.. (max is 24 megabit down here as benchmark from my laptop)...

Hey on JPY Darky's rom...just flashed this......will report back !!
Thanks

lgkahn said:
. with older even though signal strength seems lower i could still get about 2 meg or 16 megabit per
sec. sustained transfers.. (max is 24 megabit down here as benchmark from my laptop)...
Click to expand...
Click to collapse
What kind of Wi-Fi are you using? N or G? I never achieved more than 1MB/s with any firmware from my laptop to my phone using a G router. And if G than what program do you use to transfer? Normal FTP?
Sent from my GT-I9000 using XDA App

Hi guys,
two things:
I wrote a little bash script that extracts the wifi firmware from the tar files you use for flashing with odin (all-in-one and .tar.md5) and parses the fw version.
h t t p://pastebin.com/cnZmSfLc
EDIT:
woops forgot to add a small fix ^^;
Just extract the firmwares and run the script (as root since it needs to access losetup and mount) from there
eg
Code:
~/odin/firmware/2.2.1/ $ ls
I9000XXJPX I9000XXJPY
~/odin/firmware/2.2.1/ $ ~/findfw.sh
It'll create a directory /root/wififw and puts the firmwares in there (with tarballs) and it'll dump the version and stores it in FIRMWAREVERSION.version.txt
Turns out that sometimes only one of those files gets updated....
I'll look into it in greater detail once i got more firmwares
Code:
I9000DXJPA.version.txt:bcm4329_aps.bin: May 27 2010 4.218.233.0
I9000DXJPA.version.txt:bcm4329_mfg.bin: Apr 24 2010 4.218.214.0
I9000DXJPA.version.txt:bcm4329_sta.bin: Jun 4 2010 4.218.214.3
I9000XXJM1.version.txt:bcm4329_aps.bin: Jun 4 2010 4.218.214.3
I9000XXJM1.version.txt:bcm4329_mfg.bin: Apr 24 2010 4.218.214.0
I9000XXJM1.version.txt:bcm4329_sta.bin: Jun 4 2010 4.218.214.3
I9000XXJPK.version.txt:bcm4329_aps.bin: May 27 2010 4.218.233.0
I9000XXJPK.version.txt:bcm4329_mfg.bin: Apr 24 2010 4.218.214.0
I9000XXJPK.version.txt:bcm4329_sta.bin: Jun 4 2010 4.218.214.3
I9000XXJPM.version.txt:bcm4329_aps.bin: May 27 2010 4.218.233.0
I9000XXJPM.version.txt:bcm4329_mfg.bin: Apr 24 2010 4.218.214.0
I9000XXJPM.version.txt:bcm4329_sta.bin: Jun 4 2010 4.218.214.3
I9000XXJPO.version.txt:bcm4329_aps.bin: May 27 2010 4.218.233.0
I9000XXJPO.version.txt:bcm4329_mfg.bin: Apr 24 2010 4.218.214.0
I9000XXJPO.version.txt:bcm4329_sta.bin: Jun 4 2010 4.218.214.3
I9000XXJPU.version.txt:bcm4329_aps.bin: Jun 4 2010 4.218.214.3
I9000XXJPU.version.txt:bcm4329_mfg.bin: Apr 24 2010 4.218.214.0
I9000XXJPU.version.txt:bcm4329_sta.bin: Nov 16 2010 4.218.250.38
I9000XXJPX.version.txt:bcm4329_aps.bin: Jun 4 2010 4.218.214.3
I9000XXJPX.version.txt:bcm4329_mfg.bin: Apr 24 2010 4.218.214.0
I9000XXJPX.version.txt:bcm4329_sta.bin: Nov 16 2010 4.218.250.38
I9000XXJPY.version.txt:bcm4329_aps.bin: Jun 4 2010 4.218.214.3
I9000XXJPY.version.txt:bcm4329_mfg.bin: Apr 24 2010 4.218.214.0
I9000XXJPY.version.txt:bcm4329_sta.bin: Nov 16 2010 4.218.250.38
EDIT2: added more firmwares
Appearently the same firmware has been used from JPU to JPY so it'd be interesting to see if the drain occurs on the older firmwares as well. If it does we "just" need to revert it back to JPO fw

[DRIVER] Latest BCM4329 (WiFi) driver for Gingerbread - test needed.

I recompiled latest driver for broadcomm wifi on gingerbread, this may fix the battery drain issues, but i need testers.
File attached, place it under /System/Modules
before that copy a backup of bcm4329.ko in the same dir to a safe place and put one from zip.
Please put your comments here, this is first attempt
File that were posted with Gingerbread has version: 4.218.248.18
Latest builds of gingerbread (TEN region) has version: 4.218.248.6
this one is : 4.218.248.23
Changelist:
wireless: bcm4329: Reduce listen interval to 10 (from 20)
wireless: bcm4329: Add new and default wifi locale support
wireless: bcm4329: Prevent working thread to run during suspend path
wireless: bcm4329: Clean ARP offload table on IP update
Thanks!
EDIT: Added recovery zip, flash it using recovery menu. (hopefully it will work)
EDIT: Fixed recovery image (if you got error 6 then download it again and flash)
EDIT: Phone will reboot right after applying patch using recovery for these who are scared or something

how do i aply this

pixiejoe said:
how do i aply this
Click to expand...
Click to collapse
Copy it on rooted phone to proper dirs, i will create recovery package and attach it

pixiejoe said:
how do i aply this
Click to expand...
Click to collapse
With root explorer, I think.

wifi working like usual. no improvement(s) at all.

Will check it out... Thanks!

Wifi on this module doesn't work for me. I'm on miui.

This is to test the battery drain issue on stock ginger JV* not on custom mods. Post your review here and could someone make a recovery flash with it? i cant do it now.

Recovery zip added, you may simply flash it using recovery. It will also create backup of existing driver.

Anyway, I'm testing on kitchen jvh rom 3
Sent no matter where from. Concentrate on the topic...

Working fine on JPH (goatrip) . Too early to tell if it improves wifi drain, but I'm a compulsive flasher, always gotta have the newest rom/driver lols.

Any way to tell if the update worked?
I renamed the old driver file and rebooted (without copying the new one) but wifi still worked - is that normal behaviour?

Reboot the phone after replacing the file.

http://forum.xda-developers.com/showpost.php?p=13434007&postcount=2024

and jvo or jvh whatever you call it have
Firmware version = wl0: Apr 9 2011 23:33:08 version 4.218.248.184
Click to expand...
Click to collapse

JV* directly from module file: version 4.218.248.18
Mine is compiled at: Compiled on May 14 2011
And its higher version
Also, please be aware that i supply only new kernel module not firmware for chipset (your version is firmware version)

Grooby while you are it, can you check if the Bluetooth a2dp implementation is using the highest bit pool possible?
Sent from my GT-I9000 using XDA App

sure, let me look at teh sources

correct jvh has *.6 version - my mistake
still files posted by me have *.18 that is said to be fixing the issue
gut dżab

Tank ju to moj first attempt i hope it will bedzie dzialac ;P heheheh
And it including last 6 days fixes fresh and good

How can you tell which kernel you are currently running?

A forum search turned up nothing, so I'm asking here:
On most Android phones, you usually go to Settings->About Phone and look under the "Kernel Version" section to see the name and version of the kernel you are running.
With my Galaxy Nexus, I don't see kernel names. Instead, I see something like:
Code:
3.0.31-g6fb96c9
[email protected])
#1 SMP PREEMPTY Thu Jun 28 11:02:39 PDT
2012
No matter which kernel I flash, it always seems like the same type of info but no names or version numbers.
I was okay with that as long as I remembered what I flashed last. However, I recently reverted to stock but the kernel looks like it stayed the same. Is there anyway to check if I'm back on stock kernel or still running the last kernel flashed (franco, in my case)?

I'm running leankernel 4.3.0 it says the version
Sent from my Galaxy Nexus

drdoombot said:
A forum search turned up nothing, so I'm asking here:
On most Android phones, you usually go to Settings->About Phone and look under the "Kernel Version" section to see the name and version of the kernel you are running.
With my Galaxy Nexus, I don't see kernel names. Instead, I see something like:
Code:
3.0.31-g6fb96c9
[email protected])
#1 SMP PREEMPTY Thu Jun 28 11:02:39 PDT
2012
No matter which kernel I flash, it always seems like the same type of info but no names or version numbers.
I was okay with that as long as I remembered what I flashed last. However, I recently reverted to stock but the kernel looks like it stayed the same. Is there anyway to check if I'm back on stock kernel or still running the last kernel flashed (franco, in my case)?
Click to expand...
Click to collapse
Most (if not all) kernels have a name similar to stock. But there is usually something amongst the numbers and letters which point to what kernel your running.
For instance my phone running trinity.
I know its trinity because it says dirtymorfic, morfic being the xda name of the trinity kernel developer. I only use stock kernel and trinity so can't comment on the others, but it will always look similar but also always have something pointing to the kernel your using. Hope this helps
Sent from my Galaxy Nexus using Tapatalk 2

Also typing code below in terminal will give you some more bits of info.
Code:
cat /proc/version
good day.

question
sir i want to ask 2 questions :
my phone specifications after flashing jelly blast v2 are:
android version:4.1.1
baseband version :S5360DDLC2
KERNEL VERSION : 2.6.35.7 [email protected]#1
BUILD NUMBER :NXT2ICSv2:jelly blast
1.i want to install jelly blast v3 what i have to do?
2. installing a custom rom change a kernel version or not ?

sunil332011 said:
sir i want to ask 2 questions :
my phone specifications after flashing jelly blast v2 are:
android version:4.1.1
baseband version :S5360DDLC2
KERNEL VERSION : 2.6.35.7 [email protected]#1
BUILD NUMBER :NXT2ICSv2:jelly blast
1.i want to install jelly blast v3 what i have to do?
2. installing a custom rom change a kernel version or not ?
Click to expand...
Click to collapse
Why did you bump a thread that's months old, and you don't even have our device?
Sent from my Nexus

a small doubt about sony xperia z ultra
there is a date under the kernel.
but that is not the same as the date of purchase
date of purchase is june 12 2015 at 12pm
date in the kernel is june 12 2014 at 2pm
am i being cheated with an old or used phone?
also the video clarity is very bad for a FHD screen
help me please

mnanoop said:
there is a date under the kernel.
but that is not the same as the date of purchase
date of purchase is june 12 2015 at 12pm
date in the kernel is june 12 2014 at 2pm
am i being cheated with an old or used phone?
also the video clarity is very bad for a FHD screen
help me please
Click to expand...
Click to collapse
1. Kernel and rom are developed much earlier, you weren't cheated.
2. Video clarity? Do you mean the video recording quality or the screen quality?

im running cm12 (android 5.1.) on my lg d855 right now, and it shows my kernel version in the "about phone" category.

Grom V-line

Hi All.
I am new to XDA so please be gentle and I need some help.
I have a GROM V-Line system installed and it has been giving me hell these last 11 months and I am unable to get a refund from the buyer. It is android powered and uses a custom rom etc. I was wondering if anyone out there has any knowledge of these units and can guide me through a way to maybe update the system to remove custom ROMs so I can use it as a normal android type device.
The current set up is running on Android 5.1.1
Kernel version: 3.10.0 [email protected] #11
Build number: Lite_VL1.6.0.0
Not sure if there is anything I could, I am ready for throwing this out of my motor now.
Please help.
Ta

Kanjar2020 said:
Hi All.
I am new to XDA so please be gentle and I need some help.
I have a GROM V-Line system installed and it has been giving me hell these last 11 months and I am unable to get a refund from the buyer. It is android powered and uses a custom rom etc. I was wondering if anyone out there has any knowledge of these units and can guide me through a way to maybe update the system to remove custom ROMs so I can use it as a normal android type device.
The current set up is running on Android 5.1.1
Kernel version: 3.10.0 [email protected] #11
Build number: Lite_VL1.6.0.0
Not sure if there is anything I could, I am ready for throwing this out of my motor now.
Please help.
Ta
Click to expand...
Click to collapse
Hi Ta,
I installed the Vline VL2 in my Lexus two weeks ago and initially had issues.
Here's my versions out of the box.
System update is Android 8.1 with last security patch dated Jan 5, 2019 and won't update further.
Kernel: (gcc version 6.3.q 20170404 (Linaro GCC 6.3-2017.05))
[email protected] #3
Fri Mar 19 05:27:15 PDT 2021
Vline shows VCore: V20VL3.37.0.0
VBase: 32.38 (L22)
No further updates available.
DashLinq version: 5.5.2.5
Knob Helper version: 1.0
WebView Shell version: 1.0
---
I was initially pissed too but after several resets my system is pretty stable.
One item that remains an issue is crashing when I have any SD card installed...As long as no SD card installed then system runs pretty good.
Several issues via launch controller were fixed with a $1.99 replacement launcher named AGAMA by altercars.ru. https://altercars.ru/#about

[UNOFFICIAL] LineageOS 14.1 | Celox [July 9, 2022]

BEFORE YOU decide to try this rom, please read all of post 1, 2 and 3.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this ROM.
BACKUP YOUR DATA AND OLD ROM BEFORE trying this rom.
I'm simply offering this rom for those who cannot build it themselves.
What works.
1. audio over bluetooth
2. wifi
3. brightness
4. external audio
5. GPS - a bit slow to get a fix/lock
6. audio through headphone jack
7. camera
FAQ.
Q1. How did you build this? Where can I find the source code and kernel source code?
A1. This is a continuation of bryan2894's 14.1 code found on github. His last rom was built Nov 19, 2017. His github repo shows the last changes on Nov 24, 2017. So you will get the following changes as seen at
Commits · thewizrd/android_kernel_samsung_msm8660-common
Contribute to thewizrd/android_kernel_samsung_msm8660-common development by creating an account on GitHub.
github.com
You will also get whatever LineageOS 14.1 changed in the last 3.25 years including the latest March 2021 security patches.
Thanks to @bryan2894 for his repos so I can build this rom. I have added no value, changes or edits to this rom other than compiling it for 2021.
Q2. Can you fix this GSM/LTE/voice/call/text bug?
A2. No. I recently bought the SGH-I727 (code named skyrocket), but I have no SIM card and I do not plan to get one. So I cannot fix any GSM/LTE/voice/call/text bugs that exist in this rom. Any questions regarding lost, dropped, poor quality calls, low or high volume, poor sound quality, bad microphone, can't recognize sim, etc will go completely unanswered. Do not report these bugs as they will not be fixed by me. If you want to fix them, you can look at the code repositories in post #1.
In addition, there are proprietary voice/radio Samsung blobs where there is no source code so changes are virtually impossible to make.
Q3. What version of TWRP should I use?
A3. You must follow the instructions in post #2 as written by bryan2894 exactly. I followed them and was able to flash my build successfully. If you can't flash the rom, it's likely you are not following the instructions provided. Do not ask TWRP questions in this thread, they will go unanswered.
Q4. How long does the first boot take?
A4. Booting the initial LineageOS 14.1 takes about 7.5 to 8 minutes. Be patient. After it boots, let it sit untouched for 5 minutes and then reboot the phone again. After it boots, let it sit untouched for 5 minutes again before proceeding. This will let the phone do all its stuff and get itself ready.
Q5. Does it run gapps?
A5. This phone was released in Nov 2011 so it's almost 10 years old. It only has 1GB DRAM so I would suggest that you DO NOT install gapps for best performance. There are many alternatives to gapps including Aurora Store and/or installing apks directly onto the phone. Similarly, if you watch youtube videos, I suggest newpipe which is an open source viewer and can skip ads. I use the Brave browser because it has an adblocker and anti tracking features and it works well with this 10 year old phone.
Obviously, it's going to be slower than a new phone, but it's useable as a second phone or some young person's first phone.
I use all the software below.
Aurora Store | F-Droid - Free and Open Source Android App Repository
A Google Playstore Client
f-droid.org
Releases · TeamNewPipe/NewPipe
A libre lightweight streaming front-end for Android. - TeamNewPipe/NewPipe
github.com
Secure, Fast, & Private Web Browser with Adblocker | Brave Browser
The Brave browser is a fast, private and secure web browser for PC, Mac and mobile. Download now to enjoy a faster ad-free browsing experience that saves data and battery life by blocking tracking software.
brave.com
If you must install gapps, choose pico as it's the smallest one.
Q6. Will there be monthly security patches?
A6. Yes as long as I have high speed Internet, I will try to release the rom monthly to incorporate the security patches around mid month (10th to 20th). At some point, LineageOS will discontinue back porting security patches to the 14.1 code and that's when I will stop releasing roms. Google does not provide security patches for Android 7.1 anymore (aka LineageOS 14.1).
Q7. Will there be a 15.1, 16.0, 17.1 or 18.1 release?
A7. I compiled 15.1 and while it compiled without errors, it does not boot. I get no boot animation and there is no adb output which makes debugging very difficult. I suspect a kernel problem. If someone can assist, maybe a team of people can get 15.1 running?
Q8. Can you provide step by step instructions?
A8. You can do your own research on how to install a rom and you must read bryan2894's TWRP post #2. There's lots of written FAQ or videos that show you how. In addition, I don't run Windows so I cannot answer any questions regarding drivers, odin, etc. Questions regarding how to install roms, TWRP and Windows will go unanswered.
Q9. Why is my question not answered?
A9. It's likely because it's in the FAQ or it's off topic or you are asking something that I cannot answer for the reasons stated in this FAQ.
Q10. Can I build this rom myself?
A10. Yes, I have provided the roomservice.xml file that I used to build the rom. With it, you can follow any LineageOS build guide/template like
Build for chagallwifi | LineageOS Wiki
wiki.lineageos.org
That's how I built my first rom.
If you are running a newer version of Linux, you may need this additional command to compile the rom.
Code:
export LC_ALL=C
For the June 2021 security patch, there were problems building with 4GB with Jack server which worked before. I had to increase to 6GB using
Code:
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx6G"
Q11. Does this rom run on Hercules?
A11. I have no idea. I only have SGH-I727 and that's what I tested it on. Celox is supposed to be the unification of Hercules and skyrocket, but I can't verify if it runs on Hercules. Having said that, member squircular in post #4 says it works on his/her Hercules device. There's no guarantee that with each monthly security update/patch that this will be true going forward.
Q12. I don't like this rom, can you help me revert back to stock or my old rom?
A12. No. If you want to try this rom, you must backup your data and know how to revert back yourself. Questions of this nature will go unanswered.
Q13. I bricked my phone trying to install this rom. Can you help me?
A13. You assume all responsibilty for trying this rom including a possibly bricked device, lost data, security vulnerabilities, etc. If you are not comfortable flashing roms and don't know how to revert back to stock or older rom, do not install this rom.
Q14. Okay, I accept all the risks and know what I'm getting into, now where can I download this rom?
A14. You can get it at
retiredtab - Browse /SGH-I727/14.1 at SourceForge.net
sourceforge.net

NOTE OS will show June 5th, 2021 security patches due to hold up of
https://review.lineageos.org/c/LineageOS/android_build/+/313397
Release notes for July 9, 2022
1. UNOFFICIAL July 5th, 2022 security patches as per
https://review.lineageos.org/q/topic:n-asb-2022-07
2. Whatever LineageOS changed since June 5th security patches (about 2,100 files had to be recompiled).
3. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
Release notes for June 10, 2022
1. UNOFFICIAL March, April, May and June 5th, 2022 security patches as per
https://review.lineageos.org/q/topic:n-asb-2022-03
https://review.lineageos.org/q/topic:n-asb-2022-04
https://review.lineageos.org/q/topic:n-asb-2022-05
https://review.lineageos.org/q/topic:n-asb-2022-06
2. Whatever LineageOS changed since Feb 5th security patches (about 2,000 files had to be recompiled).
3. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
Release notes for Feb 24, 2022
1. UNOFFICIAL Feb 5th security patches as per ttps://review.lineageos.org/q/topic:n-asb-2022-02
2. Whatever LineageOS changed since Jan 5th security patches.
3. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
Release notes for Jan 28, 2022
1. Jan 5th security patches as per https://review.lineageos.org/q/topic:n-asb-2022-01
2. Whatever LineageOS changed since Dec 5th security patches.
3. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
Release notes for Dec 8, 2021
1. Nov 5th and Dec 5th, 2021 security patches as per https://review.lineageos.org/q/topic:n-asb-2021-11 and https://review.lineageos.org/q/topic:n-asb-2021-12 (about 2,100 files had to be recompiled).
2. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
Release notes for Oct 11, 2021
1. July 5 + August + September + October, 2021 security patches as per
https://review.lineageos.org/q/topic:"n-asb-2021-07"+(status:eek:pen OR status:merged)https://review.lineageos.org/q/topic:"n-asb-2021-08"+(status:eek:pen OR status:merged)https://review.lineageos.org/q/topic:"n-asb-2021-09"+(status:eek:pen OR status:merged)https://review.lineageos.org/q/topic:"n-asb-2021-10"+(status:eek:pen OR status:merged)
2. A reboot after flashing the October build will take about 6 minutes. Be patient.
Release notes for July 9, 2021
1. July 5, 2021 security patches as per https://review.lineageos.org/q/topic:"n-asb-2021-07"+(statuspen OR status:merged)
2. A reboot after flashing the new build will take about 6 minutes. Be patient.
Release notes for June 9, 2021
1. May 5 + June 5, 2021 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309293 and https://review.lineageos.org/q/topic:"n-asb-2021-06"+(statuspen OR status:merged)
2. A reboot after flashing the June build will take about 6 minutes. Be patient.
3. For builders, there were problems building with 4GB with Jack server which worked before. I had to increase to 6GB using
Code:
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx6G"
Release notes for April 15, 2021
1. April 5, 2021 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307154
2. A reboot after flashing the April build will take about 6 minutes. Be patient.
Release notes for March 8, 2021
1. Initial build for Celox.
2. March 5, 2021 security patches
3. Built from bryan2894 repos with no changes or edits.
4. Please be patient on first bootup. It can take up to 8 minutes. If you installed gapps, then it will take even longer.

Reserved

I can verify that this ROM works on Hercules (SGH-T989D). Thanks very much for your effort.

squircular said:
I can verify that this ROM works on Hercules (SGH-T989D).
Click to expand...
Click to collapse
Thanks for information. Does GPS work on hercules? If yes, how long does it take to get a lock?

retiredtab said:
Thanks for information. Does GPS work on hercules? If yes, how long does it take to get a lock?
Click to expand...
Click to collapse
Yes, GPS works. It took about 2 minutes to get the first fix (cold start) and about 15 seconds to get subsequent fixes (warm start). Both of these measurements were taken inside near a window so it might be faster outside.

squircular said:
Yes, GPS works. It took about 2 minutes to get the first fix (cold start) and about 15 seconds to get subsequent fixes (warm start).
Click to expand...
Click to collapse
Thanks for the feedback. I appreciate it.
Since I bought my phone used, I'm not sure if my GPS is working 100% due to hardware. It shows the satellites, but never gets a fix. If it does work, it takes about 10 minutes to get a fix. It's completely useless for a car GPS.
There are some error messages in the adb logcat which might be related to why I can't get a fix, but I will have to investigate.

I'm going to give this a try - this will be my first modded phone and so I'm taking it very slow. I've got a Rogers Samsung Galaxy S II Skyrocket SGH-I727R which I'm ok with making a mistake on. I don't want Gapps. I've currently got TWRP 3.1.1 and I'm reading through everything multiple times.
My current task is to do my best to understand bryan2894's notes on repartitioning.

Hello retiredtab (or anyone else),
I just want to clarify one little thing. In step 4 of the ROM Installation Instructions as follows:
4. In TWRP, go to Wipe -> Advanced Wipe -> check Internal Storage -> press on "Repair or Change File System" -> press on "Change File System" -> press on "EXT4", and then swipe to start formatting the internal SD card. This can take up to a minute.
As can be seen by the picture of my screen, there is no partition called 'Internal Storage'. Instead I'm wondering if it should be 'SDCard'.
Is this correct?
Many thanks for anyone who can confirm this.

JMSchneider said:
Hello retiredtab (or anyone else),
I just want to clarify one little thing. In step 4 of the ROM Installation Instructions as follows:
4. In TWRP, go to Wipe -> Advanced Wipe -> check Internal Storage -> press on "Repair or Change File System" -> press on "Change File System" -> press on "EXT4", and then swipe to start formatting the internal SD card. This can take up to a minute.
As can be seen by the picture of my screen, there is no partition called 'Internal Storage'. Instead I'm wondering if it should be 'SDCard'.
Is this correct?
Many thanks for anyone who can confirm this.
Click to expand...
Click to collapse
I think your assumption is correct. I followed the instructions back in February 2021, but honestly can't remember if I ran into the same thing or not with the naming.

retiredtab said:
I think your assumption is correct. I followed the instructions back in February 2021, but honestly can't remember if I ran into the same thing or not with the naming.
Click to expand...
Click to collapse
Thank you for the reply retiredtab - your input is greatly appreciated!

I think I found an article on TWRP that explains the partition name change.

Because the 'Internal Storage' seems to have changed spots (as indicated in the last post), I came up with a workaround for a problem that I encountered.
Initially, I was using the twrp-3.0.0-0-skyrocket.tar.md5 and reasoned it would be the "latest OFFICIAL TWRP" file for the ROM Installation instructions but in step #9 I ran into a problem - a red-highlighted section of the log read "Updater process ended with ERROR: 7". I later discovered this has something to do with version compatibility mismatching. So I decided to regress to the older Official TWRP (v2.8.6-0) recovery and go at the whole process with the exact files in the links. Then, when I went to flash the ROM I had no problems.

bryan2894 and others did all the initial work on TWRP and building this rom. I'm only updating his work + others so I don't know why specific versions of TWRP are required. All I know is that I followed his instructions exactly so that I could build a 2021 rom. As I stated, I'm adding NO VALUE other than compiling a 2021 version.
Once the 14.1 April security patches get merged in LineageOS, I will compile a new version, test it and then share with others who are interested. It looks like there are 5 patches for April as per https://review.lineageos.org/c/LineageOS/android_build/+/307154
A number of people says it compiles, builds and boots with no problems, but I prefer to wait until it's officially merged before I start the compile process.

New build called lineage-14.1-20210415-UNOFFICIAL-celox.zip (had to try 3 or 4 times before upload succeeded).
Release notes for April 15, 2021
1. April 5, 2021 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307154
2. A reboot after flashing the April build will take about 6 minutes. Be patient.

The May security patches still aren't merged yet into LineageOS as per
https://review.lineageos.org/c/LineageOS/android_build/+/309293
It's waiting approval since May 6. There are 3 CVEs for May.
At this rate, I'll probably skip making the May security patches and wait for June 5th as it's May 26 as I write this.

The May 5th security patches finally got merged today, June 7, as per
https://review.lineageos.org/c/LineageOS/android_build/+/309293
However, seeing how the June 5th patches should be announced shortly on LineageOS, I will wait until those are announced and then make a June build. No sense making a May build, testing and uploading it if June patches will be out in a few days.

New build called lineage-14.1-20210609-UNOFFICIAL-celox.zip.
Release notes for June 9, 2021
1. May 5 + June 5, 2021 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309293 and https://review.lineageos.org/q/topic:"n-asb-2021-06"+(statuspen OR status:merged)
2. A reboot after flashing the June build will take about 6 minutes. Be patient.
3. For builders, there were problems building with 4GB with Jack server which worked before. I had to increase to 6GB using
Code:
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx6G"

New build called lineage-14.1-20210709-UNOFFICIAL-celox.zip
Release notes for July 9, 2021
1. July 5, 2021 security patches as per https://review.lineageos.org/q/topic:"n-asb-2021-07"+(status:open OR status:merged)
2. A reboot after flashing the July build will take about 6 minutes. Be patient.

New build called lineage-14.1-20211011-UNOFFICIAL-celox.zip
I have not forgotten about this device, but there's a holdup with the security monthly patches starting with the July 5 patch not being merged due to a problem as per https://review.lineageos.org/c/LineageOS/android_build/+/313397
However, the August patches are officially merged while the September and October ones are pending approval. Rather than wait any longer, I decided to merge September and October security patches into this build.
So while the OS may report that it's on the June 5th security patch, that not true in this case. It has all the October 5th 2021 patches included.
Release notes for Oct 11, 2021
1. July 5 + August + September + October, 2021 security patches as per
https://review.lineageos.org/q/topic:"n-asb-2021-07"+(status:open OR status:merged)
https://review.lineageos.org/q/topic:"n-asb-2021-08"+(status:open OR status:merged)
https://review.lineageos.org/q/topic:"n-asb-2021-09"+(status:open OR status:merged)
https://review.lineageos.org/q/topic:"n-asb-2021-10"+(status:open OR status:merged)
2. A reboot after flashing the October build will take about 6 minutes. Be patient.