Related
*** PLEASE READ CAREFULLY BEFORE INSTALLING OR FLASHING ANY SOFTWARE POSTED IN THIS THREAD ***
The software posted here is for TESTING purposes only, The Polaris Android Linux development team or any of the posters of software or links to software on this thread, take absolutely no responsibility or liability for damage caused by the result of installing or flashing software or links to software found on this thread - correctly or otherwise, you do so on the sole understanding that you do so at your own risk.
Previous thread was closed because too big you can find lot of information into it with the search button : http://forum.xda-developers.com/showthread.php?t=555000
Hello to all of you, Android user.
This thread is the right place to talk about non-kernel related discussions, questions and requests.
Please, remember that the thread is public, so don't use bad word
So...have fun
-------------------------------------------------------------------------------------------------------------------------------
01-09-09 - new link to files for working wifi
http://www.4shared.com/dir/19593527/...a/sharing.html
From Google Code Vogue-Android:
01-09-09 - Initrd - works with unpartitioned cards, otherwise no changes.
01-09-09 - Rootfs - works with unpartitioned cards, otherwise no changes.
Reserved for future use
Reserved for future use.
Reserved for future use,
Reserved for future use-
what packages do i have to dload? everything?
nicandris said:
what packages do i have to dload? everything?
Click to expand...
Click to collapse
From the first link (4share), you took all but rootfs and initrd, these one you could download it from the other links
You should put name Android in the title to know about what is this thread
whitealien said:
You should put name Android in the title to know about what is this thread
Click to expand...
Click to collapse
Thanks for the suggestion
@Mormy
Could you give us your startup/default haret script? With script whitch you uploaded to 4shared, graphics don't work properly.
Good thing to open a clean thread to speak about testing
I'm currently testing the SquashFs version, latest on http://code.google.com/p/vogue-android/downloads/list
With this system.sqsh : http://vogue-android.googlecode.com/files/hero.zip
And this base files : http://vogue-android.googlecode.com/files/squashfsbasefiles.zip
It's very stable. With this build I haven't got anymore the 'reload UI' problem when I go back to home screen.
But it's very slow. It takes more time to launch application, wake up the phone, open settings... But the scrolling is normally fast.
Wifi doesn't work for me with it.
Maybe I'll try this one tonight : system-090109r1.img on http://code.google.com/p/vogue-hero/downloads/list
I didn't understood how works the last one with 'userinit.sh' system, so I think I will not try it
Averne said:
@Mormy
Could you give us your startup/default haret script? With script which you uploaded to 4shared, graphics don't work properly.
Click to expand...
Click to collapse
I've tried Neocore and won't start either with the 4share startup and with mine.
By the way, this the one I usually have:
Code:
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz
#
# The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing
# ppp.password - The password used to connect to the network when dialing
# ppp.apn - Set apn of your provider
# ppp.nostart - Set ppp.nostart=1 to disable starting the ppp connection on boot
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 1, use 1 for best power savings
# board-htcpolaris.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
# lcd.density - Defaults to 160, 128 shows more on screen
#
set cmdline "board-htcpolaris.panel_type=3 ppp.apn=tre.it ppp.username=none ppp.password=none pm.sleep_mode=1 mddi.width=324 mddi.height=432 no_console_suspend board-htcpolaris-battery.battery_capacity=1350 clock-7x00.mddi=0xa51 mddi_client_vogue.vsync=0"
boot
Averne said:
@Mormy
Could you give us your startup/default haret script? With script whitch you uploaded to 4shared, graphics don't work properly.
Click to expand...
Click to collapse
Try with '1' instead of '3' for "board-htcpolaris.panel_type" property.
Averne said:
@Mormy
Could you give us your startup/default haret script? With script whitch you uploaded to 4shared, graphics don't work properly.
Click to expand...
Click to collapse
if you mean neocore then yes that is broken in this kernel.
if you are having display issues, then try changing the panel type or try to be more specific on what you mean by "graphics dont work properly".
Ok, this is my default.txt file:
Code:
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz
set cmdline "board-htcpolaris.panel_type=0 ppp.apn=orange ppp.username=orange ppp.password=orange pm.sleep_mode=1 mddi.width=336 mddi.height=448 lcd.density=160 no_console_suspend board-htcpolaris-battery.battery_capacity=1350 mddi_client_vogue.vsync=0"
boot
With this settings display works fine, but you must disconnect usb cable before press [Run] button in haret.
Hi ,
with the last files taken from bally site I have wifi working but data connection li ke previous release taken from vogue-android sometime starts sometimes no.
And with this files I can't start calling it creashes.
No Gps..
Why start up logo is changed? and button mapping?
Averne said:
Ok, this is my default.txt file:
Code:
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz
set cmdline "board-htcpolaris.panel_type=0 ppp.apn=orange ppp.username=orange ppp.password=orange pm.sleep_mode=1 mddi.width=336 mddi.height=448 lcd.density=160 no_console_suspend board-htcpolaris-battery.battery_capacity=1350 mddi_client_vogue.vsync=0"
boot
With this settings display works fine, but you must disconnect usb cable before press [Run] button in haret.
Click to expand...
Click to collapse
why have you got lcd density set at 160 and width and height at 336x448?
this is not my startup file. you should try that first.
Does somebody know what are the benefits of using 'squash FS' system instead of old standard system.img?
Kiiv said:
Does somebody know what are the benefits of using 'squash FS' system instead of old standard system.img?
Click to expand...
Click to collapse
if you are really interested: (from http://groups.google.com/group/andr...ad/e4ce4f06f982d51b/30fa2b5deb6533b2?lnk=raot)
I think it would be a good idea to compress /system/bin and /system/
lib at least with squashfs, I have done this on a couple ubuntu and
gentoo systems and it actually increased performance and space
significantly!
Reasons (short version): decompressing data is faster than reading it
from the hard drive, in most current computers, especially when you
have multiple programs reading from the disk, causing thrashing, and/
or when the data on the disk is fragmented. You can read more details
about what was done and the results on http://forums.gentoo.org/viewtopic-p-4732709.html#4732709
Squashfs is intended for general read-only file system use and in
constrained block device/memory system, it can also be combined with a
union mount system like unionfs and aufs for read/write access.
We will be able to improve android boot time, app launch time, and
increase space, what more could we ask for? Maybe a little bit more
ram? Whats up with compcache too?
So now we just need to compile squashfs-tools for android and
experiment, im pretty damn excited to try this!
Also ubifs has lzo compression, not sure how that would work either,
it seems ubifs is favored over jffs2 and yaffs2
Well right now it looks squashfs+lzma wont be in the kernel until
2.6.30 found this via:
http://www.squashfs-lzma.org/
So I think we are left with UbiFS with lza compression but I have no
idea on how to add it to the kernel, and test this out, im really
interested in seeing some results and doing some benchmarks, if
someone more knowledgeable than me can help out that would be awesome
defcon
found a nice pdf comparing the filesystems:
http://free-electrons.com/doc/flash-filesystems.pdf
Benchmarks Of Yaffs2, JFFS2, SquashFS, & UBIFS:
http://free-electrons.com/pub/conferences/2008/elce/flash-filesystems...
Seems like people are already using ubifs on android:
http://groups.google.com/group/android-porting/browse_thread/thread/a...
Reference:
http://forums.gentoo.org/viewtopic-p-4732709.html#4732709
http://jt0.org/news/squashing_usr_and_the_2629_kernel
Hum, thank you for the link
So I don't understand why it's slower with squash FS on my phone... I will try to find other discussions on the subject.
[STOPPED][ROM ICS 15 Jul] slim rom for Desire [based on Sandvold .15 & K900 build 40]
These are a simple slim version of the original ICS ported rom for htc desire (aka bravo) provided by Sandvold and K900
Of course all credits must go to Sandvold & K900, I'm not a developer, simply I needed a lighter rom and due to many requests I decided to share my (small) work and dedicate to it a thread
They work just as original rom, I haven't changed a single bit, just removed all stuffs that can be downloaded later from google play (aka PhoneSky.apk). This thread is intended for "advanced users" but none can't stop you to make experiments
These rom are intended to work with cm7r2 hboot table & without the need of any ext3-4 partition (this means max 120-130 app)
IMPORTANT: as a2sd script we use as default for both roms 69a2sd script, more info here
CHANGELOG (15 Jul) :
- updated 98mydesireI script (modded minfree memory management)
- updated default Apex Launcher (anyway you can use whatever you prefer)
- updated OS fonts, I choose a ligther & smoother one
- Download here or Mirror here
CHANGELOG (06 Jul) :
- updated 98mydesireI script (reduced boot pause, it will stay only upon a fresh installation)
- updated MultiLing keyboard
- updated Music apk with JB release (moved backup to /system)
- moved LauncherApex from /system to /data (make an apex setting/icon backup before flash, you have to replace widget too)
CHANGELOG (04 Jul) :
- upgraded Sandolvd based ics rom (.15)
Some notes before starting:
before start I strongly suggest, if you are under MS Windows environment, to download the mini-sdk-android-windows.zip (look at 2nd post for details) from repository (aka known as diaduit), unzip the entire folder, without renaming it, where you prefer under your C: drive, this little zip contains some utilities and batch scripts to automate some recurrent actions useful to easily manage your device, such as for example radio flash, hboot flash, script injection, etc...
these slim rom will fit on cm7r2 partition table, if you don't know what is it you can start from alpharev.nl website, or simply download your .img copy from repository
I strongly suggest to use a modern and full functionally recovery, personally I use 4EXT: download from repository and flash trough _flash_recovery.bat batch script (from mini-sdk-android-windows.zip)
always in repository you can find a copy of the slim rom (named as rom-slim-etc...zip)
editing directly rom-slim-desireics-xyz_x.y.zip requires winrar (search in google)
this rom can work without any ext3-4 additional partition, I just move into sd-card ALL the games and not fundamental apps using default android behavior: Settings => Applications => Sd-card (tap correspondent app to move)
as a2sd script we use as default for both roms 69a2sd script, more info here
and now rom modded content:
removed all google applications (*) downloadable from google-play except QuickSearch and Vending (google-play app)
removed all tts lang (except for the service), they can be downloaded later from google-play because I suppose that own language should be enough for most of us
removed almost all sounds except one for alarm, one for ring and six for notifications, anyway you can create your own sounds repository in your sd-card, so you wont loose them never more: make a folder in your sd-card named /media/audio, then create under audio other 3 folders named: alarms, notifications, ringtones , then put your personal sounds under correspondent folders
removed default ics keyboard, the 1st reason because it's heavy and fat, the 2nd because has ton of languages when we really need just one... our own (I included as default MultiLing free keyboard, a light and highly configurable keyboard with downloadable single dictionary)
removed all customization and stock kernel is provided (eventually Tiamat kernel can be flashed separately), of course customization are included with best options/balance about my experience/opinion
default launcher is Apex Launcher
added 98mydesireI script (present under extra folder of mini-sdk-android-windows.zip), you can edit it as you prefer (use for this purpose pspad editor due to its ability to manipulate unix txt files), as default its primary goal is to manage cpu freq between sleep and awake states (245-245 when sleep, 960-1075when awake)
auto-adjust swap tuning (swappiness= 20 if zRam enabled, 0 if not)
installation instructions, starting from the beginning:
make a full backup before start, personally I don't use titanium due to its restoring issues probabilities, I prefer a full backup from recovery, for this purpose 4EXT is just perfect (from repository), it will backup eventually your ext3-4 partition too
download and copy rom-slim-desireics-xyz_x.y.zip file in your sd-card
if you don't have cm7r2 hboot you should upgrade to cm7r2, download the .img file from repository and use _flash_hboot.bat batch script (from mini-sdk-android-windows.zip) to easily flash the new hboot
reboot your device into recovery, pay attention that if you changed hboot table, for example from data+ to cm7r2, you have to force a full wipe (do it from recovery itself)
after rom flash & upon complete boot SetupWizard wont start (I removed it) so as 1st step I suggest you to configure a working wlan, then launch google-play and start registering your existing account...
download & configure all apps you intend to use (hint: search google inc to find all google stuffs such as maps, gmail, youtube, etc...)
post installation guide, another important step:
if you come from an upgrade/reflash remember that installer will format only /system folder, some previous related system app will still be under /data/app such as for example LatinIME.apk, so if you keep MultiLing keyboard (or whatever) remove from /app/data the LatinIME.apk (edit and use _remove batch script)
go under Settings => Evervol Toolbox => Performance => Memory management and activate "kernel samepage merging" (do not activate zRam, our device has enough ram and also because I noticed random FC under heavy usage)
as you know some video from gallery (using internal libs) are rendered badly, install instead MXPlayer (from google-play) and force it to use SW rendering (from MXPlayer settings)
removed almost all sounds except one for alarm, one for ring and six for notifications, anyway you can create your own sounds repository in your sd-card, so you wont loose them never more: make a folder in your sd-card named /media/audio, then create under audio other 3 folders named: alarms, notifications, ringtones , then put your personal sounds under correspondent folders
added 98mydesireI script, you can edit it as you prefer (use for this purpose pspad editor), as default its primary goal is to manage cpu freq between sleep and awake states (245-245 when sleep, 960-1075 when awake)
Other tips (I'll add step by step as I remember):
prevent unnecessary battery drainage by disabling auto-time update... device keeps date/time sync with connected cell tower every minute! (disable from Settings => Date & Time) and install instead ClockSync from google-play (setup auto-update every 3 days)
move ALL games or spare used app from nand to sd-card (Settings => Application => SD-card => tap on move able app)
to speed-up open/close phase disable animation from Settings => Developer options => Scale from 1x to 0,5x (or none)
(*) App list installed as default on /system:
Code:
ApplicationsProvider.apk
BackupRestoreConfirmation.apk
Bluetooth.apk
Browser.apk
Calendar.apk
CalendarProvider.apk
Camera.apk
CertInstaller.apk
Contacts.apk
ContactsProvider.apk
DefaultContainerService.apk
DeskClock.apk
DownloadProvider.apk
DownloadProviderUi.apk
DrmProvider.apk
EVToolbox.apk
EVWidgets.apk
Email.apk
Exchange.apk
Gallery2.apk
GenieWidget.apk
GoogleBackupTransport.apk
GoogleCalendarSyncAdapter.apk
GoogleContactsSyncAdapter.apk
GoogleLoginService.apk
GooglePackageVerifier.apk
GooglePackageVerifierUpdater.apk
GoogleQuickSearchBox.apk
GoogleServicesFramework.apk
GoogleTTS.apk
HTMLViewer.apk
KeyChain.apk
LauncherApex.apk
MarketUpdater.apk
MediaProvider.apk
MediaUploader.apk
Mms.apk
Music.apk
MusicFX.apk
NetworkLocation.apk
PackageInstaller.apk
Phone.apk
PicoTts.apk
Provision.apk
Settings.apk
SettingsProvider.apk
SharedStorageBackup.apk
SoundRecorder.apk
Stk.apk
Superuser.apk
SystemUI.apk
Talk.apk
TelephonyProvider.apk
UserDictionaryProvider.apk
Vending.apk
VoiceCommand.apk
VoiceSearch.apk
WAPPushManager.apk
df output on fresh installation:
Code:
Filesystem Size Used Free
/dev 202M 32K 202M
/mnt/asec 202M 0K 202M
/mnt/obb 202M 0K 202M
/system 145M 141M 3M
/data 287M 1M 285M
/cache 5M 784K 4M
screenshots below plus videos here 1/3 (installing) - 2/3 (average usage test) - 3/3 (game test)
mini-android-sdk-windows dedicated post
As explained few lines above this small zip downloadable from repository contains some batch scripts useful to automatize frequent operations, such as flashing radio, hboot, inject scripts, splash screen, etc...
simply unzip it on your physical hard drive ( C: ) in the folder you prefer, rename adb.ba_ as adb.bat, then move adb.bat under c:\windows folder, this to help you in recalling adb environment* (Start > adb > Run and it will open the folder plus a ready cmd shell)
*tested under Vista and 7, remember also if you intend to use adbWireless to edit IP.bat batch file and change IP (up 3) addresses matching the one of your device (useful for adbWireless)
let's take a tour on its content:
IP.bat => simple IP file configuration, write here your device IP list for connecting trough adbWireless (of course if you use it)
_flash_hboot.bat => this will flash hboot table, simply connect your device (without reboot in anything, just attach it) and provide in the same folder the hboot .img file named hboot.img (remember if you change hboot table to wipe before flash anything else)
_flash_radio.bat => as above but for radio, provide radio.img in the same folder, pay attention that radio flashing is really dangerous because in case of fault you'll probably brick your device, anyway latest radio provided for our device (on XDA or repository) is perfect so you shouldn't need to change it
_flash_recovery.bat => as above but for recovery, personally I use 4EXT (version 2.1.3 is faultless, download a copy from repository)
_flash_splash.bat => this is intended for flashing .bmp as splash screen (different from boot-animation, this is the 1st thing you see upon turn-on), provide splash1.bmp in the same folder ([email protected])
_push_98* => init script for control cpu freq (pay attention different version for different hardware, latest version already included in the slim rom)
_push_build.prop.bat => this will inject your personalized build.prop in your device (provide the file under extra folder)
_push_gps.conf.bat => as above, anyway the modded version is yet included in the slim rom
_push_hosts.bat => as above
_push_to_sdcard.abt => this batch script will copy under sd-card your drag'n dropped file (I use in conjunction with adbWireless)
_remove_stuff.bat => use this batch script with care, edit it to add removing actions
note: all .img file go under current folder, while all "extra" such as hosts, build.prop and init script go under extra folder
98mydesireI script dedicated post
1st part are just personal mods, you can keep, mod or remove, but the core of the script is the 2nd part, where the script itself creates a mini script named mycpu under /etc and will detach it in background (nohup /system/bin/sh /system/etc/mycpu&)
so in few words:
98mydesireI init script will be executed after complete boot (90 sec)
98mydesireI init script will write under /etc another script named mycpu (for managing cpu freq)
98mydesireI init script before exiting will launch mycpu control script
mycpu control script will stay in background looking for device state (sleep or wake) and applying relative properties
the annoying problem having a high cpu freq jump, for example from 245 to 1113 also with interactive/smartass governors, is that when your device wake up or when you don't put your fingers on it becomes a bit sluggish for a while
instead forcing freq matching display on/off states gives better results also if using conservative governor, in fact we don't need a "speedy" device when its screen is turned off... who use it in that state? while instead we want a speedy device when we actively use it, when its screen is turned on
so the most balanced setup is to have a really sleepy device when screen is off (99% of times not actively in use by user) and on the opposite a really speedy device when screen is on (99% of times in use by user)
the script will control also certain pid priority differently between sleep & wake states, during sleep state it will also recovery ram if under a critic level (right now fixed at 59Mb) by flushing caches
anyway is possible to specify min-max freq by editing 98mydesireI init script, look at these lines below they speak themselves :
Code:
echo 'MinFreqWake=960000;'>>/system/etc/mycpu
echo 'MaxFreqWake=1075200;'>>/system/etc/mycpu
echo 'MinFreqSleep=128000;'>>/system/etc/mycpu
echo 'MaxFreqSleep=384000;'>>/system/etc/mycpu
change values upon your needs, here below freq steps:
128000 245000 384000 422400 460800 499200 537600 576000 614400 652800 691200 729600 768000 806400 844800 883200 921600 960000 998400 1036800 1075200 1113600
to check correct behavior connect your device and open a shell (adb shell) then put commands:
cd /sys/devices/system/cpu/cpu0/cpufreq
turn off display (without detach of course)
cat scal*
last two numbers are current min-max frequencies, your freq min-max should be the lowest possible
turn on display and repeat step 3, your freq min-max should jump
if you turn off again your freq min-max should be lowered
downloading.. will report my experience after flashing
ill give this a go
good Idea Suiller ! - a comprehensive project !
I need to do a little home-work before I dip into this project....
Your repository is very familiar.
Ive taken things from there before
rraaka said:
good Idea Suiller ! - a comprehensive project !
I need to do a little home-work before I dip into this project....
Your repository is very familiar.
Ive taken things from there before
Click to expand...
Click to collapse
thank you friend... probably you used the repository during "diamond" era
added 98mydesireI script, you can edit it as you prefer (use for this purpose pspad editor), as default its primary goal is to manage cpu freq between sleep and awake states (245-245 when sleep, 900-1113 when awake)
This is not good idea.
k3lcior said:
added 98mydesireI script, you can edit it as you prefer (use for this purpose pspad editor), as default its primary goal is to manage cpu freq between sleep and awake states (245-245 when sleep, 900-1113 when awake)
This is not good idea.
Click to expand...
Click to collapse
why not? I use this setup from about 2 years... (from froyo/ginger) I prefer a really responsive device when I actively use it (screen on)
anyway it's easy to lower freqs, is enough to edit the script:
Code:
'MinFreqWake=960000;'>>/system/etc/mycpu
'MaxFreqWake=1113600;'>>/system/etc/mycpu
I'll put freq list on 3rd post
uploaded latest tested version at 12.00 (UTC/GMT time) - 14.00 (CET)
ps: no need to wipe again, just take a look of old apk still under /data/app such as LatinIME.apk (if you don't want default ics keyboard of course)
Does int boot also with stock hboot?? Or only with cm7r2??
gastrella said:
Does int boot also with stock hboot?? Or only with cm7r2??
Click to expand...
Click to collapse
sure, but you'll wast a lot of space... /system will take less than 140Mb
In one word: GREAT!!
I'll give it a try ASAP
P.S. already started to address your initiative onto ... Well, you know where!!
trinity1 said:
I'll give it a try ASAP
P.S. already started to address your initiative onto ... Well, you know where!!
Click to expand...
Click to collapse
thank you friend
tested latest slim version, I wiped everything to be sure & to simulate a complete new installation, all worked as expected so I'm going to publish (it will take few minutes), of course always in repository
ps: keep an eye on rom file date & time (on repository) to be sure you get the updated version
Hi..... Can I make a port request.....?
Sent from my HTC Desire using XDA
Miui ics v4 being developed for n1..... I hope its easy.... There is also a detailed porting guide on miui us. I tried many times but failed...:banghead:
Sent from my HTC Desire using XDA
no sorry, I don't have much time
I'll seek only this thread without beginning any new adventure
Yasir Javed Ansari said:
Miui ics v4 being developed for n1..... I hope its easy.... There is also a detailed porting guide on miui us. I tried many times but failed...:banghead:
Sent from my HTC Desire using XDA
Click to expand...
Click to collapse
I will try to port before end of May but I need people to test.
Sent from my HTC One V using XDA
Thanks
shubhamchamaria said:
I will try to port before end of May but I need people to test.
Sent from my HTC One V using XDA
Click to expand...
Click to collapse
Hi, thanks for response..... as i mentioned in your runny thread, i'm back on wmjan rom, but using ur framework files for swipe to clear, (thanks again), but im waiting for miui ics for desire as lenny has abandoned the project.... untill then, ill stay put at wmjan sense.
Could someone help me identify my new tablet, so that I can flash the correct CM ROM. It's branded as a Tursion.
Model number: F721
Android version: 4.0.4
Baseband version: 1.4rc3
Kernel version: 3.0.8 [email protected] #2
Build number: 20120821-F721
Any help is appreciated.
Thanks in adavance.
Didn't find out if it has a ROM or not but did find:
Diag/Setup Menu - recovery mode?
Up+Power+home on touchscreen (four little boxes)
1- Autotest
2- Tools Menu (see below)
3- Vibration
4- Screen Color Adjust
5- Camera
6-7- missing
8- Keyboard
9- Speaker
10- Audio and Router/ing (?)
11-12- missing
13- Battery
14- Touch Screen
15-16- missing
17- Gravity Sensor
18- missing
19- T-Card (? older name for microSD)
20- WIFI
21- EFUSE
The 2- Tools Menu leads to:
(read left to right, top to bottom. No numbers)
1- Clear Test Results
2- IMEI
3- Coupling Test
4- Clear Data (did a factory reset, lost apps)
5- Off
It appears to have root already. I installed superuser and sshdroid and am able to ssh [email protected] to it.
I was able to remove the unwanted apps (so my daughter could use it) from /system/app.
Unfortunately the /oem directory w/ facebook and youtube (just what I want my daughter surfing) is not removeable. It appears to be mounted in the /init program (binary file) since grep'ing that file returns the line /oem. I tried adding a line to /init.rc to "umount /oem" but that didnt work. Any ideas?
(before anyone screams...she's young, when she gets older she'll get more access)
Thank you so much I needed to factory reset a tablet with this chinnese service menu and thanks to your information I was able to do it may the force be with you
bsaunder2002 said:
Didn't find out if it has a ROM or not but did find:
Diag/Setup Menu - recovery mode?
Up+Power+home on touchscreen (four little boxes)
1- Autotest
2- Tools Menu (see below)
3- Vibration
4- Screen Color Adjust
5- Camera
6-7- missing
8- Keyboard
9- Speaker
10- Audio and Router/ing (?)
11-12- missing
13- Battery
14- Touch Screen
15-16- missing
17- Gravity Sensor
18- missing
19- T-Card (? older name for microSD)
20- WIFI
21- EFUSE
The 2- Tools Menu leads to:
(read left to right, top to bottom. No numbers)
1- Clear Test Results
2- IMEI
3- Coupling Test
4- Clear Data (did a factory reset, lost apps)
5- Off
It appears to have root already. I installed superuser and sshdroid and am able to ssh [email protected] to it.
I was able to remove the unwanted apps (so my daughter could use it) from /system/app.
Unfortunately the /oem directory w/ facebook and youtube (just what I want my daughter surfing) is not removeable. It appears to be mounted in the /init program (binary file) since grep'ing that file returns the line /oem. I tried adding a line to /init.rc to "umount /oem" but that didnt work. Any ideas?
(before anyone screams...she's young, when she gets older she'll get more access)
Click to expand...
Click to collapse
[HUAWEI WATCH 2 (LTE/4G-Sawshark) & (Bluetooth/BT-Sawfish)-OWDE.180926.001.A1]INTERNATIONAL VERSION
Please read the instructions and notes before flashing anything. Don't ask me if you don't read the instructions.
Code:
###Disclaimer###
[COLOR="Red"][B]WARNING:
IMPROPER FLASHING MAY POTENTIALLY BRICK YOUR DEVICE. SO PLEASE PROCEED AT YOUR OWN RISK. ME OR ANY OTHER DEVELOPER MENTIONED IN THIS POST WILL ASSUME NO RESPONSIBILITY FOR THIS.[/B][/COLOR]
DONATE ME HERE
DONATE-ME
##############################
REQUIREMENT
##############################
- An Unlock bootloader
- Working adb/fastboot and driver - Download from Here
- A custom recovery (twrp) See my twrp thread for custom twrp recovery
TWRP-RECOVERY
##############################
HOW TO FLASH KERNEL/BOOT IMAGE
##############################
- Steps via adb/fastboot
- Unzip the folder and move the boot image into your adb/fastboot folder and apply the following commands
Code:
- adb devices
- adb reboot bootloader
- fastboot flash boot boot.img
- fastboot reboot
##############################
HOW TO FLASH THE ROM AND ROOT
##############################
1- Move the build/ROM and Busybox and Magisk to your watch
2- Make a backup - there's always 1% chance something goes wrong.
3- Full wipe is recommended....Wipe data/Factory reset
4- Flash the ROM, then flash Busybox and Magisk (Please flash in this order, ROM, then Busybox and Magisk)
5- Reboot and complete your initial setting
6- Open Magisk Manager and go to settings and set Automatic Response to Grant
7- Done. Don't forget to donate if you like my work, Thanks.
##############################
ROM AND KERNEL FEATURES [22-Jan-2020]
##############################
[Changelog]-Huawei Watch 2 LTE(Sawshark)+Huawei Watch 2 BT(Sawfish)-[22/Jan/2019]
- Based on latest kernel source (-Source 3.18.24) android-wear with latest security patch
- Linux version 3.18.24 (gcc version 4.9.3 20141215 (prerelease) (UBER-SaberMod-4.9.3_arm-graphite)) #1 SMP PREEMPT Wed Jan 22 9:45:39 CET 2020
- Forced-encryption disabled
- dm-verity removed/disabled
- Auto memory killer set to default
- Sepolicy is patched
- Fix the CPU idle latency unvote timeout. It should reduce the wasting power and CPU go to deep idle states immediately after a request
- Add and use a timer frequency of 100 Hz. It should improve power consumption.
- Add and update/Hide verifiedbootstate from /proc/cmdline in order to fix the failed SafetyNet CTS check(It can still fail through other means)-GOOGLE PAY SHOULD WORK. USE MAGISK TO HIDE ROOT. U may need Gpay enabler
- Remove verifiedbootstate flag from /proc/cmdline - Disable CRC check
- Scheduler optimize/support for heterogeneous multi-core
- Scheduler support for heterogeneous multi-processor systems
- Enable all core with scaling_available_frequencies (200000 400000 533333 800000 1094400 1267200 MHz)- scaling down the frequency of the CPUs to 200 MHz during idl mode and rise the freq. to 1.26Ghz during high pressure.
- Set swappiness to 60
- Change zswap max pool % to 20%. It will reduce CPU usage a lot
- Enable zram & zswap and add 256MB virtual memory default. It will speed up the device a lot
- Removed nolog usage, remove rtb logging from the kernel
- Remove selinux auditing from kernel for lower overhead
- Remove IPC logging from the kernel
- Disabled some kernel parameter to speed up the performance- at the cost of battery/ power consumption
- Remove some logging from several drivers
- Improve memory allocations -Should improve the device a lot
- Add some tweaks to improve the overall speed, apps startup are too faster
- Set zswap compressor to lz4 by default
- APM driver updated again to reduce battery usage during sleeping
- Several other patches to reduce battery usage
- Multi-core scheduler enable/optimized
- APM driver updated reduce battery usage during sleeping
- Fix the wake up time. The screen should wake up more quickly when pressing the button.
- Tweaked the scheduler to reduce/save power by scaling down the frequency of the CPUs or idling them,
- A lot subsystems converted to use power efficient workqueue
- The watch goes to sleep during no action in order to save battery
- Remove debug event logging-Kill the useless logging to reduce overhead
- Remove sync debug entirely to cut down CPU waste in the frame render hot path
- Remove 10 ms CPU idle latency unvote timeout- Doesn't force the CPU to stay out of deep idle states for far longer than necessary, which wastes power
- Disable audit support, usually comes with a measurably significant amount of overhead
- Remove audit dependency
NOTE: THERE IS NO NEED TO FLASH THE LATEST KERNEL IF YOU FLASH THE LATEST ROM.
##############################
DOWNLOAD
##############################
[Huawei Watch 2 4G/LTE]+[Huawei Watch BT][22-Jan]
[DECRYPTION KEY]
WO0FVexxQnrtcODYdmNvnQ
##############################
MAGISK/BUSYBOX/APP-KERNEL-CONTROL
##############################
DOWNLOAD LATEST MAGISK FROM HERE
DOWNLOAD LATEST BUSYBOX FROM HERE
KERNEL CONTROL APP WEAR OS
##############################
How to get the Gpay back...
##############################
1-https://pastebin.com/HKV7cj7H
2-https://forum.xda-developers.com/smartwatch/other-smartwatches/rom-kernel-t3821013/page172
3-https://www.youtube.com/watch?v=UKxGfNxRjo4&t=320s
4-https://forum.xda-developers.com/showpost.php?p=79637148&postcount=1720
##############################
HOW TO FLASH THE STOCK IMAGES-(BACK TO STOCK)
##############################
1- Download and unzip the system image below
2- Attach the watch charger to the watch and plug the USB cord (from the charger) into your computer
3- Use the following adb command to start the watch in fastboot mode: adb reboot bootloader
4- On your computer, navigate to the directory where you unzipped the system image in Step 1. At the top level of that directory, execute the flash-all script:
- On Linux or MacOS, type ./flash-all.sh
- On Windows, type flash-all.bat
5 -DONE. Don't forget to donate if you like my work, Thanks.
STOCK-IMAGES-HUAWEI-WATCH-2-LTE-LEO-DLXX-OWDE.180215.017-SAWSHARK-(13/Oct/2018)
STOCK-IMAGES-HUAWEI-WATCH-2-BT-LEO-BX9-OWDD.180215.018-SAWFISH-(22/7/2018)
##############################
Source/GitHub
##############################
-Source
IF YOU LIKE MY WORK AND WANT ME TO CONTINUE, THEN BUY ME A SHOT OF WHISKY
DONATE ME HERE
DONATE-HERE
Special thanks to:
If you can, donate and respect all the devs and enjoy
@Chainfire for great work in android
@Maxr1998 Big thanks for giving me knowledge and your great work for Asus Zenwatch_3 and your great github guide. Please thank and donate him for all his efforts
@topjohnwu for his great effort (Magisk)Thank you so much
@SuperR.R for the great kitchen
@Xmaster24 for system-less root-
@moneytoo for his great app. Please appreciate and donate him
Pay Enabler
@SuperThomasLab for great tools
Please always support devs and others (soon).
ROM download asking for decryption key?Can fix the link?
Hello All,
Is it possible to install this latest ROM on model without LTE?
Thank you for reply :good:
arthos7 said:
ROM download asking for decryption key?Can fix the link?
Click to expand...
Click to collapse
Hoffmanns said:
Hello All,
Is it possible to install this latest ROM on model without LTE?
Thank you for reply :good:
Click to expand...
Click to collapse
Link are fixed now. It will properly not gonna work on non-lte. I can build a new for non-lte version if some one send me the latest system image and boot image. (I can extract from your watch via teamviewer, in case you can't) But you need to flash the latest firmware without root.
IF YOU LIKE MY WORK AND WANT ME TO CONTINUE, THEN BUY ME A SHOT OF WHISKY
DONATE ME HERE
I will upload a complete latest stock images N7176C (lte) incase anyone wanna go back to latest stock again.
The only thing you have to do is boot into bootloader mod and then run the script by double click on it. After some reboots you will be back on latest stock.
I will combine both Linux and Windows together, use one you prefer.
IF YOU LIKE MY WORK AND WANT ME TO CONTINUE, THEN BUY ME A SHOT OF WHISKY
DONATE ME HERE
Just received my Huawei SW 4G this weekend and after installing Huawei wear I got the alert message that the watch was rooted.
How can I confirm is it's rooted or not.
Thanks
Sent from my ONEPLUS A3003 using Tapatalk
Can anyone who's used this verify that it's notably faster or has improved battery life compared to stock? Or is the difference negligible?
How to build boot.img
Hi Janjan,
I am trying to build a custom kernel for my Huawei Watch 2 (non LTE) and I was wondering if you could share a little of your development work.
How do you actually put the boot image together? I am able to compile the kernel from android-msm-sawshark-3.18-nougat-mr1-wear-release,
which gives me a zImage. I also have the original images. So I tried to unmkbootimg the original boot image and replace the kernel. However, this doesn't seem to work. when I compare the sizes of the supposedly original zImage and the one created from the repository above, their size differs by roughly a factor of 100. So there must be something seriously wrong
What steps do you use to create the kernel and the boot image?
I also checked your github code and tried to use it but it seems to depend on other stuff that is not in your repos. Where did you find the code you have in your repos?
Best regards,
Mogli
janjan said:
I can build a new for non-lte version if some one send me the latest system image and boot image. (I can extract from your watch via teamviewer, in case you can't) But you need to flash the latest firmware without root.
Click to expand...
Click to collapse
Does that offer still stand? If yes I am willing to let my watch be used as a test subject.
mogli19 said:
Hi Janjan,
I am trying to build a custom kernel for my Huawei Watch 2 (non LTE) and I was wondering if you could share a little of your development work.
How do you actually put the boot image together? I am able to compile the kernel from android-msm-sawshark-3.18-nougat-mr1-wear-release,
which gives me a zImage. I also have the original images. So I tried to unmkbootimg the original boot image and replace the kernel. However, this doesn't seem to work. when I compare the sizes of the supposedly original zImage and the one created from the repository above, their size differs by roughly a factor of 100. So there must be something seriously wrong
What steps do you use to create the kernel and the boot image?
I also checked your github code and tried to use it but it seems to depend on other stuff that is not in your repos. Where did you find the code you have in your repos?
Best regards,
Mogli
Click to expand...
Click to collapse
Sure, tell me what you did and your steps for building zImage + modul. I am away from my office for a while.
janjan, have you had success with making a non-lte version?
cdkg said:
janjan, have you had success with making a non-lte version?
Click to expand...
Click to collapse
If you send me the latest boot.img, system.img and vendor.img then I will definitely make.
janjan said:
If you send me the latest boot.img, system.img and vendor.img then I will definitely make.
Click to expand...
Click to collapse
I have the boot.img and system.img. Is there a tutorial or any instructions you could give on how to get the vendor.img?
janjan said:
Sure, tell me what you did and your steps for building zImage + modul. I am away from my office for a while.
Click to expand...
Click to collapse
Hi Janjan,
(Apparently I am not allowed to post links yet, so I am trying my best to explain without them)
1. I got the source code for the Sawshark watch from github (mr1-wear-release). I guess there is no dedicated Seafish kernel source. Short question: There is a choice of 3 different kernel codes. Which one shall I take?
2. I tried to compile this source code without changes (to rule out errors before I make modifications). This works and I get as zImage. What do you mean by modul though? I thought zImage was the only product.
3. Using unmkbootimg, I un-packed an stock boot.img. The unmkbootimg tool says that the boot.img has been compiled with a non-standard mkbootimg program. However the offsets and other values (I am supposed to tune when I use mkbootimg) are contradicting. Eventually, the "non-custom" values recommended by unmkbootimg caused errors in mkbootimg and I ended up using the default values. This worked.
4. When I flash the resulting boot.img my watch gets stuck during boot with the Huawei logo on all the time.
To verify my tools, I tried step 3. in two more ways:
3.1. re-pack the un-packed boot.img, flash it (no errors and boot works)
3.2 pack a boot.img using a zImage obtained from a sawshark boot.img (instead of the seafish). This also worked and boot was successful
I have also looked at the boot.img and zImage files in a hex editor. I can locate the beginning of the kernel but not the end. Also if I did, I wouldn't know how to replace the kernel in hex mode But from what I have understood about mkbootimg, this script does not much more than concatenate zImage and ramdisk and add a header. Is this somewhat correct?
Eventually, I need to turn on some currently disabled kernel features (which is why I am doing all of this ). So I am still trying to figure out the right tools and components. And therefore the question: How do you usually build the kernel and how do you pack it into the boot.img. Do you modify the ramdisk when you replace the kernel?
Best,
Mogli
Instructions to modify ramdisk
Hi Janjan,
How do you disassemble and re-assemble the ramdisk?
Wanted to make a few modifications to the ramdisk.cpio.gz. Again, I wanted to try the tools first. So I unpacked and re-packaged the ramdisk without modifications. After flashing the regenerated boot image, my watch goes into recovery mode...
I found these instructions in a tutorial (again, I can't post links yet... sorry):
For disassembly:
Code:
$ mkdir ramdisk_dir
$ cd ramdisk_dir
$ gunzip -c ../ramdisk.cpio.gz | cpio -i
for re-assembly
Code:
$ find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
Update to my previous post:
I found my mistake in building the kernel:
Instead of using
Code:
make ARCH=arm CROSS_COMPILE=arm-linux-androidkernel-
I was using
Code:
make ARCH=arm CROSS_COMPILE=arm-linux-androideabi-
mogli19 said:
Hi Janjan,
How do you disassemble and re-assemble the ramdisk?
Wanted to make a few modifications to the ramdisk.cpio.gz. Again, I wanted to try the tools first. So I unpacked and re-packaged the ramdisk without modifications. After flashing the regenerated boot image, my watch goes into recovery mode...
I found these instructions in a tutorial (again, I can't post links yet... sorry):
For disassembly:
for re-assembly
Update to my previous post:
I found my mistake in building the kernel:
Instead of using
I was using
Click to expand...
Click to collapse
It seems much better now. Are you in Windows or Linux? I will post my script and tools once I reach my PC. I am away from my PC right now. It means you destroy something during generating or packaging the boot image. Does you kernel /boot.img work without or before editing the ramdisk?
Update:- seems you are in Linux.
janjan said:
It seems much better now. Are you in Windows or Linux? I will post my script and tools once I reach my PC. I am away from my PC right now. It means you destroy something during generating or packaging the boot image. Does you kernel /boot.img work without or before editing the ramdisk?
Update:- seems you are in Linux.
Click to expand...
Click to collapse
Yes, I am on linux. I found a different approach that works for me now:
Code:
Extract the ramdisk.
$ mkdir ramdisk
$ cd ramdisk
$ gzip -dc ../ramdisk.cpio.gz | cpio -i
# Make any changes necessary (e.g., set ro.secure=0 in default.prop).
# Recreate the cpio archive using the mkbootfs binary produced from building the Android source code
$ cd ..
$ mkbootfs ./ramdisk | gzip > ramdisk-new.gz
You said you were able to turn on all the cores. Can this be done by modifying the ramdisk or how do you do this?
mogli19 said:
Yes, I am on linux. I found a different approach that works for me now:
You said you were able to turn on all the cores. Can this be done by modifying the ramdisk or how do you do this?
Click to expand...
Click to collapse
Did I said? But It can't be done by editing the ramdisk only. You need to add and edit alot (add driver edit cores etc) in kernel sources.
Okay, before anyone flames, I did look everywhere in this thread and cannot find it. Does anyone have the link to the flashing instructions for this rom?
janjan said:
Did I said? But It can't be done by editing the ramdisk only. You need to add and edit alot (add driver edit cores etc) in kernel sources.
Click to expand...
Click to collapse
Oh sorry, I thought I had read this on your feature list I actually looked at this and asked myself if there was a way to make the cpu settings permanent:
https://stackoverflow.com/questions/20221680/android-how-to-force-cpu-core-offlineshut-down-cores
As most of you guys know Magisk will not work for us on the international snapdragon S9, S9+, and N9
So, I have made a custom kernel that will allow us to have root on stock pie firmware..
Files needed:
N9600:
klabit kernel V6.5
FK Manager n9600 kernel download configuration link
FK Manager n9600 GSI kernel download configuration link
Copy the n9600_q_vx.zip to your external sd card.
Make sure you have TWRP installed with instructions found in this thread.
Flash the n9600_q_vx.zip
Flash Magisk (only necessary if you have not flashed Magisk previously or if coming from a clean install from stock)
Reboot to system.
If you currently do not have a working lockscreen/pin/fingerprint setup, you will need to restore your stock boot.img either via backup or extract your boot.img from the official firmware and flash the img then flash my kernel.
Changelog:
Code:
V6.5
[LIST]
Merge OSRC: N9600ZHU5FTK1
[/LIST]
V6.4
[LIST]
Merge OSRC: G9650ZHS6DTG2
Merge OSRC: G9650ZHS7ETH1
Remove additinal SafetyNet flags from /proc/cmdline
Proc: Fake CMDline
Merge OSRC: G9650ZHU7ETI3
Merge OSRC: G9650ZHU7ETJ2
Expanded GSI kernel compatibility for Android 11 support
[/LIST]
V6.3
[LIST]
Merge OSRC: G9650ZHS6DTF1
Merge OSRC: G9650ZCU6ETF6
[/LIST]
V6.2
[LIST]
Merge OSRC: G9650ZCS6DTD5
[/LIST]
V6.1
[LIST]
Add powersave governor
Add conservative governor
Add ondemand governor
[/LIST]
V6.0
[LIST]
[*]7e123dad108c Import crownqlte && starqlte defconfigs
[*]824f70f8d070 Add .gitignore
[*]7d3612a88cbf Import G9600 and N9600 defconfig && initialize
[*]c1e7a35e59a7 Import G9600 and N9600 dts with verity removed
[*]0a587fae1745 Add option for gsi mtp driver
[*]10b851dfaa03 star2qlte: Initialize defconfig
[*]5f38f4cc0d99 Remove verity
[*]101dedaf7aec scripts: remove localversion + from kernel version strings
[*]c1b726584344 selinux: enable selinux faking
[*]70ed91e9c15a star2qltechn: Enable Samsung MTP driver
[*]9c88019d96fd drivers: usb: add separated Samsung MTP option
[*]6c54f88a648b star2qltechn: Update defconfig
[*]13a223ea3ed9 dts: disable avb,verify
[*]5c36fed8d37b Regen configs
[*]9a37c1921037 (osrc) OSRC: G9650ZCU6DTA9
[/LIST]
V5.9
- Small version bump to 5.9.
- Integrate auto patch of security patch date since Samsung slow af. (Credit to [user=4280397]@djb77[/user])
- Better GSI compatibility.
- Better OneUI compatibility for recent/most up-to-date firmwares.
V5.8
- Fix compilation issue for n9600
- Version update to V5.8
- Add changelog
- Update crownqlte defconfig
- OSRC: G9650ZCU6CSJ2
- Merge SM-N9600 defconfig and dts
V5.7
- Merge G9650ZHU5CSH6 source which includes fix for the recent zero day on android binder driver
- Prevents potential wake-lock while on wireless charger
- Merge G9650ZCU5CSI3 source which includes some Note9 camera integrations
- Adds support for wireless adapters based on Broadcom 43436 chipset
- Increased wifi security
- Increased wifi hotspot security
- DHD 100.13.36.1 - 2019.07.31
Security Patch
- CS8424803(By Choi Hyeonu) SI-14869: Moved the length check routine for the nlioc variable before accessing it in the wl_cfgvendor_priv_string_handler() function
DHD 100.13.36 - 2019.05.24
New Feature
- CS5350346(By Jung Junyeop) Fake AP - Fixed to provide correct channel information for beacon receive result
- Enable to support Fake AP
(This patch should be sync up with FW 13.38.60(4361B0), FW 13.50.10(4361B2) or higher version)
- WIPS attack warning reporting
(This patch should be sync up with FW 13.38.60(4361B0), FW 13.50.10(4361B2) or higher version)
Security Patch
- CS8069399(By Kang Hyung Wook) SI-13926 Fixed use-after-free in the wl_cfg80211_set_mgmt_vndr_ies function
Others
- CS7939107(By Kim Tae-Yong) Included memdump value prints in the dump information
- Added missing options into the Kconfig file
DHD 100.13.32 - 2019.04.26
Kernel Panic
- CS7696936(By Min SungBin) Fix misspelling of CUSTOMER_HW4_DEBUG definition
- CS7706946(By Min SungBin) Fixed to avoid kernel panic due to race condition of cfg->scan_request
Security Patch
- CS7860687(By Kang Hyung Wook) SI-12455: Fixed use-after-free write in dhd_set_monitor() function
- CS7949699(By Choi Hyeonu) SI-14074: Fixed Security issue, Potential stack-based buffer overflow in dhd_pktfilter_offload_set
- CS7956197(By Choi Hyeonu) SI-14130: Fixed the multiple NULL pointer dereference in wl_cfgvendor.c
Others
- CS6844193(By MinSoo Kim) Changed log level of LQCM report
- CS7099653(By Nitesh Suthar) Enabled frameburst to enhance throughput for BCM43436 projects
- CS7362375(By Gu Ja Heon) Added Private command in order to receive every beacon in Suspend
- CS7526157(By Suthar Nitesh) Fixed DualBandConcurrency field in .softap.info
- CS7765577(By Park Heebae) Wifi-on time reduction by reading necessary CIS information
- CS7827257(By Choi Hyeonu) Fixed kernel panic caused by invalid memory access
- CS7834653(By Kang MinHo) Removed redundant TX error prints during suspend in SDIO
- CS7884436(By Beom Jip Kim) Fixed to cancel p2p listen offloading by framework scan request
- CS7892037(By Sun Yinghan) Fixed to support W2018/KELLY Android P OS upgrade
DHD 100.13.31.1 - 2019.04.19
Others
- CS4726130(By Min Hyun-Ki) Added User priority to AC mapping in case of various DSCP types that may not compatible with RFC8325
- CS6951980(By Min Hyun-Ki) Changed the UP to AC mapping of CS6 based on the RFC8325
DHD 100.13.31 - 2019.02.15
Others
- CS7241767(By LEE EONJI) Added more logs for the DPC schedule error debugging
- CS7299641(By Kim MinSoo) Enabled LB_TXP for MSM8998 Platform
- CS7323375(By kwon Jaecheol) Enabled the softap.info file support in BCM4359 platform
- CS7362527(By Hyeonu Choi) Cancel P2P listen offloading operation when SoftAP brings up
- CS7363197(By Junhak Lim) Fixed prevent issues
- CS7386068(By Lee Gibum) Disabled frameburst for "2.4Ghz + SoftAP" (Drame & Great projects)
- Fixed the scan failure when p2p listen offload is triggered
- Fixed to abort scan when connection/disconnection requested
- Prevented the bus suspend by the PCIe Runtime PM from abnormal ISR status
V5.5
- Merge G9650ZHU5CSG8 source which includes some stock Samsung debugging sanity checks and increase of stability
- Prevent possible IO/wake-locks when accessing sdcard
V5.4
- Merge G9650ZCU5CSFB source which includes additional ethernet support and additional battery stats support
- Removed more verity from the appended dtb
- Finally fixed FK Manager compatibility!! (ie no longer need to reflash Magisk)
V5.3
- Added Conservative gov for G9600 (sorry I could have sworn I included this in V5.2)
- Fix stability issues
- Remove Interactive governor
V5
- Removed Defex
- Removed Samsung rooting protections
- Removed RKP (Realtime Kernel Protection)
- Added Conservative cpu governor
- Sanity checks for video drivers and the power share feature
- Added support for broadcom 43456 wireless cards
- Added ddhd random mac scanning
- Added more security to wifi hotspot to protect from ARP attacks,
- CS7111512(By LEE EONJI) Detect turn on failure in factory binary
- CS7299329(By Kim Yu-Kyoung) Fixed SoftAP CTS fail due to interface creation failure
- Blocked WLC_E_ROAM event to fix wakes-up frequently under weak signal AP
- Changed error results of GETSTAINFO private command to BCME_UNSUPPORTED if the BIGDATA_SOFTAP is not supported
- Fixed kernel panic during mfg mode interface creation
- CS7091164(By Kang Hyung Wook) SI-13561: Fixed kernel heap overflow security issue at dhdpcie_downloadvars
- CS7091371(By Kang Hyung Wook) SI-13584: Fixed kernel panic due to access to not allocated memory
- CS6785460(By Jeong Min Cheol) Send HANG event to the framework for the sequential private command failure
- CS7003600(By Kang MinHo) Support android private command for restoring roam/scan parameters
- CS7094302(By Yoon YeJi) Fixed connect failure caused by connection information not initialized
- CS7103552(By LEE EONJI) Fixed the recovery routine to fix the D3_ACK timeout issue
- CS7119174(By Kim Seong Hwan) Avoid HANG event indication due to sequential private command failures in case of unsupported error
- CS7137399(By Yoon YeJi) Fixed connect failure caused by connection information not initialized
- CS7141596(By Suthar Nitesh) Fixed MHS operates with STA mac address
- Control HANG report for consecutive Android private command failure by sysfs
- Increased the NUMBER_SEQUENTIAL_PRIVCMD_ERRORS from 4 to 7
- Taking a SOCRAM dump in the sequential private command error case
- CS6935603(By Hong Min Whoa) SI-13638: Fixed Kernel warning message by restructuring the DMA_LOCK and DMA_UNLOCK
- CS7091347(By Kang Hyung Wook) SI-13585: Fixed kernel panic due to write buffer exceeds the size
- CS6650676(YeJi Yoon) Fixed mismatch connect status between framework and DHD
- CS6678972(By Hwang MinSik) Fixed TIS/TRP test failure and high current issue from sysfs change
- CS6715508(By Choi Hyeonu) Exported sysfs for ADPS bad AP list
- CS6744438(By Yoon Jae Ho) Fixed duplicated roaming notification to WPA supplicant during FT roaming
- CS6769798(By Kim Beom Jip) Fixed for GraceR/4359c0 P OS P2P connection failure issue
- CS6856753(By kwon Jaecheol) Added the dual interface capability filed in the SoftAP info file (.softap.info)
- CS6870793(By Tae-Yong Kim) Fixed prevent issues
- CS6871138(By Lee Gibum) Configure AER registers to debug PCIE ERROR ATTN issues
- CS6880409(By Sung-gi Choi) Fixed prevent issues
- CS6887298(By Min Whoa Hong) Fixed prevent issues
- CS6928243(By Sung-gi Choi) Fixed prevent issues
- CS6935678(By Hwang MinSik) Fixed array out of bound issue from sysfs mac address
- CS6984743(By Min SungBin) Print DPC schedule request timestamp for ROT issue
- CS6985032(By LEE EONJI) Enabled DHD_RECOVER_TIMEOUT for D3_ACK missing case on 4359C0 and 4361B0
- CS6993967(By Jeong Min Cheol) Added last_d3_inform_timestamp to check root cause of ROT
- CS7042030(By Min SungBin) Implemented the new API to sync up the status between RC and EP to avoid unwanted L1ss configuration
- Changed the DHD_COMMON_DUMP_PATH for non-BCM4375 Android P OS projects
- DHD driven random mac enable by default for 4361B0
- Enable frameburst for standalone 2.4GHz SoftAP on Dream and Great project
- Wi-Fi Sharing-Lite feature support for Android P OS
- CS6461136(By Min SungBin) Fixed for kernel panic due to stack overflow at get_roamscan_channel_list()
- CS6302259(By Kang Hyung Wook) Supported DHD driven Random MAC feature
- CS6324532(By Choi Hyeonu) Port files under /data/vendor/conn to sysfs after Android P OS
- CS6396705(By Min SungBin) Added additional timestamp log to debug resumed on timeout issue
- CS6398346(By Hyeonu Choi) Fixed prevent issues
- CS6516071(By Choi Hyeonu) Fixed for corner case of schedule_timeout() API at dhd_timeout_expired()
- CS6536174(By Choi Hyeonu) CS6433018(By Choi Hyeonu) Fixed prevent issues
- CS6594869(By Min SungBin) Triggering Kernel panic for the scheduling problem only if the memdump mode is enabled
- CS6600348(By LEE EONJI) Implemented 4359c0/GraceR P OS Wi-Fi sharing feature
- CS6658253(By Choi Hyeonu) Fixed random mac setting issue instead of otp mac
- CS6678972(By Hwang MinSik) Fixed TIS/TRP test failure and high current issue from sysfs change
- CS6713692(By Kim MinSoo) Fixed NET_RX delay issue
- CS6769798(By Kim Beom Jip) Fixed for GraceR/4359c0 P OS P2P connection failure issue
- CS6791516(By Lee Gibum) Fixed the unexpected frameburst enable on standalone SoftAP in 2GHz
- CS6791556(By Hwang MinSik) Removed CR/LF character at .cid.info including sysfs
- CS6809444(By Hwang MinSik) Unified DHD_COMMON_DUMP_PATH for the Android P OS project of all chips
- Changed the timestamp value to Kernel local time to debug resumed on timeout and scan timeout issues
- Defer RxBuf post size based on the rxbufpost_sz iovar return value for monitor mode
- Disabled DHD_LB_IRQSET for Exynos8890 platform
- Dump AER HeaderLog registers in configuration space for PCIe debugging
- Dumping PCIe registers for PCIe debugging enhancement
- Fixed VHT features enable issue from GraceR project
- Fixed unexpected RSDB mode configuration for legacy RSDB chip
- Implemented the debug code to check if the scan timeout or resumed on timeout happens due to the DPC scheduling problem
- Refined TDLS initialization code
Kernel source: https://github.com/klabit87/android_kernel_samsung_sdm845
Thanks to @tylerhole and the @stang5litre test group for testing anything I throw at them!
As well as @hibuk , @Lavachita , and @HakandSack for testing the Note9 specific kernel.
Thanks to @djb77 for the ramdisk patches
You guys are the best!
Reserved
I've had it working for a while using your instructions.. something I'm missing here ?
Sent from my SM-N9600 using Tapatalk
mentathf said:
I've had it working for a while using your instructions.. something I'm missing here ?
Sent from my SM-N9600 using Tapatalk
Click to expand...
Click to collapse
I don't understand what you mean.
This is an updated pie kernel.
I haven't made anything for pie on the note9 before.
Sent from my Pixel 2 XL using Tapatalk
It feels so good to be rocking pie rooted on the n96000. Kinda hilarious because i went and purchased an n960fds last month to get pie/root. I no longer have to live without google camera as it doesnt work on eynos .Thanks alot!
Thank you so much @klabit87 for your continued support of this amazing phone
@klabit87 Thanks a lot for the kernel. I just wonder if after flash, something get lost.. for example encryption.. Samsung health.. or any knox crap dependencies.. Thanks!
andrew.mackew said:
@klabit87 Thanks a lot for the kernel. I just wonder if after flash, something get lost.. for example encryption.. Samsung health.. or any knox crap dependencies.. Thanks!
Click to expand...
Click to collapse
Anytime you trip Knox when you unlock your bootloader you will loose something. Encryption is an option and a choice.
Health and whatnot can be fixed but the kernel is not responsible for it.
Sent from my Pixel 2 XL using Tapatalk
Kernel source: https://github.com/klabit87/android_kernel_samsung_sdm845
Thanks to @tylerhole and the @stang5litre test group for testing anything I throw at them!
As well as @hibuk , @Lavachita , and @HakandSack for testing the Note9 specific kernel.
You guys are the best![/QUOTE]
I successfully compiled kernel with my needed modules, however when using "anykernel" to flash to device, all good except NO WIFI.
I also used the "tar-Tool_Odin3-v3.10.7_by_mkh.mourad" used pulled boot.img from phone to test if tar-tool worked for me and wifi worked, then replaced my compiled Image.gz-dtb , everything works but no wifi.
I pulled proc/config.gz from my working wifi device
then renamed to config_defconfig
then compiled
ran thru tar-tool ,converted to md5.tar
flashed with odin
Works as before NO WIFi
EDIT: Is it possible Magisk has something to do with the kitchen not repacking everthing into new boot.img?
Going to try to repack using magisk tools..
Any sugestions would be helpfull
Homefix said:
Kernel source: https://github.com/klabit87/android_kernel_samsung_sdm845
Thanks to @tylerhole and the @stang5litre test group for testing anything I throw at them!
As well as @hibuk , @Lavachita , and @HakandSack for testing the Note9 specific kernel.
You guys are the best!
Click to expand...
Click to collapse
I successfully compiled kernel with my needed modules, however when using "anykernel" to flash to device, all good except NO WIFI.
I also used the "tar-Tool_Odin3-v3.10.7_by_mkh.mourad" used pulled boot.img from phone to test if tar-tool worked for me and wifi worked, then replaced my compiled Image.gz-dtb , everything works but no wifi.
I pulled proc/config.gz from my working wifi device
then renamed to config_defconfig
then compiled
ran thru tar-tool ,converted to md5.tar
flashed with odin
Works as before NO WIFi
EDIT: Is it possible Magisk has something to do with the kitchen not repacking everthing into new boot.img?
Going to try to repack using magisk tools..
Any sugestions would be helpfull[/QUOTE]
I meant to respond to this earlier but no magisk isn't breaking wifi. You need to export a couple of variables before compiling.
Code:
export ANDROID_MAJOR_VERSION=p
export PLATFORM_VERSION=9.0.0
add those to your build script or just run them manually before running your build script and the wifi drivers will be included properly.
klabit87 said:
I successfully compiled kernel with my needed modules, however when using "anykernel" to flash to device, all good except NO WIFI.
I also used the "tar-Tool_Odin3-v3.10.7_by_mkh.mourad" used pulled boot.img from phone to test if tar-tool worked for me and wifi worked, then replaced my compiled Image.gz-dtb , everything works but no wifi.
I pulled proc/config.gz from my working wifi device
then renamed to config_defconfig
then compiled
ran thru tar-tool ,converted to md5.tar
flashed with odin
Works as before NO WIFi
EDIT: Is it possible Magisk has something to do with the kitchen not repacking everthing into new boot.img?
Going to try to repack using magisk tools..
Any sugestions would be helpfull
Click to expand...
Click to collapse
I meant to respond to this earlier but no magisk isn't breaking wifi. You need to export a couple of variables before compiling.
Code:
export ANDROID_MAJOR_VERSION=p
export PLATFORM_VERSION=9.0.0
add those to your build script or just run them manually before running your build script and the wifi drivers will be included properly.[/QUOTE]
OMG I have been googelin for 2 days ,Not a mention of that. Going to try now.
Homefix said:
I meant to respond to this earlier but no magisk isn't breaking wifi. You need to export a couple of variables before compiling.
Code:
export ANDROID_MAJOR_VERSION=p
export PLATFORM_VERSION=9.0.0
add those to your build script or just run them manually before running your build script and the wifi drivers will be included properly.
Click to expand...
Click to collapse
OMG I have been googelin for 2 days ,Not a mention of that. Going to try now.[/QUOTE]It was mentioned in the official kernel source release notes which should be included in the osrc branch.
Sent from my Pixel 2 XL using Tapatalk
How did the test build go @Homefix ?
Sent from my Pixel 2 XL using Tapatalk
In light of the most recent update to FK Manager see here for details ------->> https://twitter.com/franciscof_1990/status/1215673739435704320?s=20
I have added support for the kernel download configuration which will allow you to update directly within the app. It will also notify you when an update is ready.
Check the OP for the links to the configuration.
Just copy the link address and paste into the "Import a kernel download configuration" box and done.
You can remove and add different ones if you want as well.
Also wanted to note that I will still post the updates in the OP. I am not going to make the updates only available through the app.
With that said, V5.8 will drop today
New minor update to v5.9.
This will make using gsi and most up to date/latest firmware versions much easier and more compatible.
Sent from my Pixel 2 XL using Tapatalk
klabit87 said:
New minor update to v5.9.
This will make using gsi and most up to date/latest firmware versions much easier and more compatible.
Click to expand...
Click to collapse
Awesome, thanks man! Flashing through FKM worked perfectly as well. Everything seems to be running great.
klabit87 said:
How did the test build go @Homefix ?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Sorry I was away,
Yes it went perfect. Thank you.
However since android 4.4 I have compiled kernels and modules with ease.
I really don't have the time to commit to my hobby(Debian on Android) like I used to, so my reading and experience has slipped a bit.
Now I read Android 8.0 and up have "Modular Kernel splitting the device kernel into a system-on-chip (SoC), device, and board-specific deliverables ".
For reasons "ensure a workable booting system remains on the disk during an over-the-air (OTA) update. This approach reduces the likelihood of an inactive device after an update, which means fewer device replacements and device reflashes at repair and warranty centers" as explained here: https://source.android.com/devices/tech/ota/ab_updates.
Well that's all fine but I still cannot figure out how to tell the system upon bootup to load a specific module. How would I load the module from adb or terminal. The older way ,depmod -a , insmod , modprobe, seems to have no effect with android 8 and up.
I have successfully built modules with:
CONFIG_MODULES=y (and not with...CONFIG_MODULES=m)
CONFIG_MODULE_UNLOAD=y
CONFIG_MODVERSIONS=y
After flashing kernel, I can see the module folders under /sys/module and within that folder is another, "parameters" and an empty "uevent" file. Within the "parameters" folder is a file "oom_pages" the content is "256"
So how would I load say "virtio"
The old way would work:
1st: depmod -a
2nd: modprobe virtio
Not working with android 8
By the way Im using ubuntu 16.04 image mounted here: mount -t ext4 -o rw,noatime /dev/block/mmcblk0p2 $mnt
$mnt=/data/local/Linux
As a side note: I like to play around with qemu , virt-manager, (windows-xp runs fast enough to be usable with this snapdragon)
and I can run full Minecraft , haha.
Homefix said:
Sorry I was away,
Yes it went perfect. Thank you.
However since android 4.4 I have compiled kernels and modules with ease.
I really don't have the time to commit to my hobby(Debian on Android) like I used to, so my reading and experience has slipped a bit.
Now I read Android 8.0 and up have "Modular Kernel splitting the device kernel into a system-on-chip (SoC), device, and board-specific deliverables ".
For reasons "ensure a workable booting system remains on the disk during an over-the-air (OTA) update. This approach reduces the likelihood of an inactive device after an update, which means fewer device replacements and device reflashes at repair and warranty centers" as explained here: https://source.android.com/devices/tech/ota/ab_updates.
Well that's all fine but I still cannot figure out how to tell the system upon bootup to load a specific module. How would I load the module from adb or terminal. The older way ,depmod -a , insmod , modprobe, seems to have no effect with android 8 and up.
I have successfully built modules with:
CONFIG_MODULES=y (and not with...CONFIG_MODULES=m)
CONFIG_MODULE_UNLOAD=y
CONFIG_MODVERSIONS=y
After flashing kernel, I can see the module folders under /sys/module and within that folder is another, "parameters" and an empty "uevent" file. Within the "parameters" folder is a file "oom_pages" the content is "256"
So how would I load say "virtio"
The old way would work:
1st: depmod -a
2nd: modprobe virtio
Not working with android 8
By the way Im using ubuntu 16.04 image mounted here: mount -t ext4 -o rw,noatime /dev/block/mmcblk0p2 $mnt
$mnt=/data/local/Linux
As a side note: I like to play around with qemu , virt-manager, (windows-xp runs fast enough to be usable with this snapdragon)
and I can run full Minecraft , haha.
Click to expand...
Click to collapse
I haven't messed with modules in a long time. I just include what I want in the kernel instead of building modules lol.
I would have to do a little investigating to find the answer you're looking for tbh.
But that's awesome that you can run such different software on your device, mainly the qemu stuff.
If I recall correctly, you need to allow unsigned modules to be loaded as well as remove lkmauth from the kernel.
Sent from my Pixel 2 XL using Tapatalk
Kernels are updated and live for Android 10!