Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4.2 - SD
Due to numerous requests, I ported my NAND build to be used also with SD, booting it via MAGDLR or WindowsMobile (Haret)
...: FEATURES :...
1.84 base Deodexed and Zipaligned
RMNET/PPP Selectable via config.txt (boot via WMO only PPP)
Multilanguage and full chinese handwriting support.
Rooted (SU app + SU binaries)
AdFree
AutoAPNs
5mpx camera with face recognition + 800*400 camcorder
HSDPA, GPS, Bluethoot, WiFi all working
% battery icon and status bar icons changed (use original framework-res.apk to go back to stock attached in 2nd post)
fonts changed (use original fonts to go back to stock attached in 2nd post)
[*]Enhanced Shutdown Menu
[*]WiFi MAC Fixed
Working HTC-SENSE.COM, HTC-HUB, HTC-LIKES
Working HTC Headsets using my kernel
Working notification LEDs
[*]Working Streaming Video
[*]Working Flash Player, No more browser crash
Support config.txt to tweak boot options
Modified shutdown android process to cleanly unmount data partition and avoid data corruption.
EXT3 Filesystems to improve data safety and speed.
Personal tweaks to I/O to have the most fast full hd build you ever seen
Fast, Fast, FAST!....... FAST!
Tweaked to be stable, battery efficient and good for daily use.
.
REMOVED APPS (you can install them from market or use the package in second post):
AdobeReader.apk
Facebook.apk
GoogleMaps.apk
Quickoffice.apk
SoundHound_freemium.apk
Street.apk
Talk.apk
Twitter.apk
VoiceCommander.apk
YouTube.apk
Click to expand...
Click to collapse
...: WHAT IS NOT WORKING :...
HTC E-Reader (removed)
Weather could be buggy for someone. If its so for you, try the fix in second post
Click to expand...
Click to collapse
...: CHANGELOG :...
Code:
4.2 - 21 MAR 11
- Fixed Flash player in websites via modified app to not let the market to update it (credits: cmyxlgo)
- Fixed Camera, now no more FC in sharing (credit: aread22, pyrorob)
- Updated ad-free
- Improved data stability
- Improved ppp
- Cleaned system from unuseful stuff
- Optimized and zipaligned again
- Updated to Rafpigna 1.9 OC Kernel, with EB support
4.1 - 12 MAR 11
New base TELUS 1.84.661.1
new kernel rafpigna 1.8 OC
updated gmail
updated market
updated flash player so you will have no more erros (dont let the market to update it!)
updated busybox to 1.18 stable
modified init and init.log to have better debug informations
zip align of all apps on boot to improve speed, ram, and battery drain
updated some driver and libs for better stability
updated all languages including Serbian and handwriting languages
MMS sizes 300kb, 600kb, 1024kb (default 300kb, choose size in the sms settings)
reduced freeze a bit when installing apps from the market
some other small fixes and tweaks I forgot
Reverted to radio drivers from 3.2 for better data stability
Fixed a typo in init causing some issues with data and booting
Fixed some drivers dependencies
Some fixes on some parts of the system to improve stability and speed.
Some other small fixes
3.2.2 - 02 MAR 11
Fixed path issues
3.2.1 - 02 MAR 11
Tweaked booting process to be more compatible
added possibility to change wifi mac address
added another method to boot from a different folder
fixed update installations
3.2 -> first release
Click to expand...
Click to collapse
...: REQUIREMENTS :...
MAGDLR 1.13 or WINDOWS MOBILE
FAT partition as first partition and PRIMARY on sd card, otherwise will not boot
A little bit of brain to read the instructions and dont post questions until you did at least a search in the thread
Click to expand...
Click to collapse
Quadrant @ stock speed ---- Quadrant @ 1,5ghz
(click on the images for bigger size)
...: INSTRUCTIONS :...
Apart from the below instruction you can see also the COLOSSUS_R tutorial HERE
Download the build 7z file
Extract the whole "Android" folder in the root of your sd card. This means you have to extract not only the files inside the folder, but the folder itself!
If you are coming from a previous version and you want to keep your data and settings, dont overwrite the userdata.img file and keep your old one.
Create, inside the folder, a config.txt file based on your needs (see below for instructions). If you dont create one, the default values will be used. Anyway you can create it also on second or any next boot. Some users experienced boot issues with config.txt created with windows notepad. Try to use Notepad++ and select "Conver end line character" to UNIX in the "Edit" menu, before save.
When creating txt files, make sure your Windows is setted up to show extensions also for known files. Otherwise will happen that you will create files like "something.txt.txt" because you dont see the last .txt
If it will not boot after you follow the instructions, read post 3
FOR WINDOWS MOBILE BOOT:
First of all modify the config.txt file in your build folder, with wince=1 or you will be stuck at bootscreen.
Boot Windows Mobile, open file exploer, browse to your sd card and the android folder, tap on CLRCAD.exe (nothing will happen) then on HARET.EXE and wait the boot
First boot will take about 5-10 minutes depending on your sd card speed.
If you hear the bootsound more than one time, you have boot-loop.. something has gone wrong. Read again the instructions, check the md5/sha1 of downloaded file, start all again from scratch.
Once you see the unlock screen, dont touch your phone for 5 minutes.
After the 5 minutes, unlock the screen, do your setup.
When on the sense home screen, wait again 5 minutes without touching anything.
long press on the power button and shutdown the phone
Boot again
Again wait 5 minutes on the lock screen, then unlock it.
Go in settings -> audio -> and disable audible touch tones to avoid robo voice or phone freezes.
Enjoy.
If you want to change the build folder from "Android" to "Anythingelse" just open the startup.txt and add this line: set cmdline "rel_path=YourFolderName"
Folder name must not contains special charactes like . , ! | and so on...
FOR MAGDLR BOOT
Please note: If you want to change the build folder from "Android" to anything else just create a "rafdroid.txt" file on your sd root with the following text inside it: rel_path=YourFolderName
Folder name must not contains special charactes like . , ! | and so on...
Boot in MAGDLR powering on your phone while you press the power button until MAGDLR appears.
Select "SERVICES"
Select "BOOT SETTINGS"
Select "AD SD Dir"
Select the "ANDROID" folder or the folder where you dropped the rom.
Now select "BOOT AD SD" and wait boot
If you hear the bootsound more than one time, you have boot-loop.. something has gone wrong. Read again the instructions, check the md5/sha1 of downloaded file, start all again from scratch.
Once you see the unlock screen, dont touch your phone for 5 minutes.
After the 5 minutes, unlock the screen, do your setup.
When on the sense home screen, wait again 5 minutes without touching anything.
long press on the power button and shutdown the phone
Boot again
Again wait 5 minutes on the lock screen, then unlock it.
Go in settings -> audio -> and disable audible touch tones to avoid robo voice or phone freezes.
Enjoy.
Click to expand...
Click to collapse
...: CONFIG.TXT :...
A config.txt is included in the build folder. It has currently only the "wince=0" option, so you have to change it according to your needs.
Some users experienced boot issues if they create/modify the config.txt file using Windows Notepad. If you have the build not booting, try to use Notepad++ (google for it) and, before saving the file, goes in "Edit" menu, then select "Convert end-line carachter" and select "UNIX"
Also check the you are displaying file extensions. This because if you file extensions are hidden, you will create a config.txt.txt file that will not be read by the system and you will be stuck at boot.
Those are the options you can specify in the file:
gps_zone=[your country]
check http://www.pool.ntp.org/zone/@ for country codes (example: it for italy, us for usa.. and so on...)
wince=[1 or 0]
1 to boot the build via windows mobile
0 to boot the build via magdlr
default is 0
if you try to boot via winmo or magdlr without setting properly this parameter, the build will not boot.
ppp_mode=[1 or 0]
1 to enable PPP
0 to enable RMNET.
Default is 0
If wince=1 default ppp_mode will be 1
old_light_driver=[1 or 0]
0 to use the new light driver (working notification leds, button backlight control)
1 to use the old light driver (no notifications leds, buttons will go off after 10 seconds)
default is 0
auto_btn_backlight=[1 or 0]
1 to have the buttons backlight going off/on with the screen
0 to have the buttons backlight going off after 10 seconds from when the last button is pressed
default is 1
this work only if old_light_driver=0
wifi_mac_change=[1 or 0]
1 tells the system that you will need to change the wifi mac address to a custom one
0 tells the system that you will use the wifi mac address based on device hardware
custom_wifi_mac=yy:yy:yy:yy:yy:yy
here you have to write the wifi mac address you want.
This is needed, and will work, only if you specify wifi_mac_change=1
If you not write any mac address here, the default 00:11:22:33:44:55 will be used
Just an example on how a file could look:
Code:
gps_zone=it
ppp_mode=0
wince=0
old_light_driver=0
auto_btn_backlight=1
Click to expand...
Click to collapse
...: TIPS :...
Robot voice - known issue - disable audible touch tones and no more robot voice.
On every boot an "init.log" is created under your Android folder. Post this file if you have boot loops or booting issues, this will help debug and to solve the issue.
I modified the whole android shutdown process to avoid any data corruption. Please always choose SHUTDOWN instead of REBOOT!!! In this way you wil never have data loss or corruption!!!! Also if in my instructions or somewhere you read "reboot your phone" always SHUTDOWN then power it up again!
Click to expand...
Click to collapse
...: DOWNLOADS :...
Please, if you respect my work, dont upload this file on any other mirror or host, always put the original link in any forum or web page where you are going to post it.
Since the new base, a fresh install is suggested (means dont use the old userdata.img)
You can try to install on old userdata.img just copying all files from the zip except the userdata.img but you can have bugs, issues and loose some functionalities of the new update.
To keep al the bugfixing a FRESH installation is suggested. If you experience any bug not reported in the first post, try a fresh install (new userdata.img) and see if it happens again.
RAFDROID HD 4.2 SD -> DOWNLOAD HERE
MD5: D55FB4F671A79842B9D2618462526BE9
SHA1: 2F38F6F44F91AB54B9F6CA61A2987DF6405AE256
CRC32: 33021A3E
Old versions:
RAFDROID HD 4.1 SD -> DOWNLOAD HERE
MD5: CBDF69DF2382401E0EFFD6031B00D563
SHA1: B879A08475A32CAFB4C392E4B9EEE676FCC93E17
CRC32: 414635DA
RAFDROID HD 3r2f2 SD -> http://www.multiupload.com/HA3TRFQD9S
MD5: BE39664A7F6B4FD40DD614F0EA4FD2B3
SHA1: F508BB2D72ECDDFAF94A379601D964E62917DFFF
CRC32: FF766DAA
Click to expand...
Click to collapse
...: CREDITS THANKS :...
Cotulla and DFT for making all this possible
Darkstone - Special thanks to him for his big help
Rajko,atoore,ocm,Cass,Markinus, LeTama, cedesmith, domineus, imilka, crawlingcity, Sergio76, cmylxgo, dandiest, tytung
rmk40 for the modded su app/bin
All the testers of my NAND build and the themers kurniawan77 and dandsta34
Everyone else I forgot and a lot of other people on #htc-linux-chat
Click to expand...
Click to collapse
...: DONATIONS :...
I'm putting a lot of time in this, nights without sleeping, downloading, flashing, reflashing..So, if you like my work and appreciate it, and you want to buy me a coffe or a beer for chilling out, I will appreciate it you can do this here DONATE otherwise a click on the "thanks" button is still a good idea
Click to expand...
Click to collapse
...: KERNEL :...
My kernel is capable of Overclock up to 1.5Ghz. Anyway overlcock at you risk. I'm not responsible if you will blow your phone
You are free to use any kernel you want. Just make sure to put all the relevant system files (like modules) in the "root" folder structure under Android folder (look following post for instructions)
This build is tested to work properly with my kernel. I will not reply to any issue using other kernels.
You can find my kernel thread here: http://forum.xda-developers.com/showthread.php?t=940823
Click to expand...
Click to collapse
...: AndroidApps installation instruction and filesystem installation instructions :...
If you want to automatically install any app during boot, you can create a folder "AndroidApps" under the Android folder and put the apk there. The apps will be installed during next boot. Please dont do this on first boot because some times can give issues. The folder will be automatically deleted after the apps are installed
If you want to change any system files, you can create a "root" folder under your Android folder. In this "root" folder you have to replicate the structure of the system folders. Example: you want to change the gps.conf file that is in the following path: /system/etc/gps.conf you have to create this folder structure: "root -> system -> etc" and in the last folder (etc) you have to put your modified gps.conf file.Durin boot it will be copied and the folder deleted. Use this method if you want to change kernel and you need to push the new modules.. in that case the folder structure will be "root -> system -> lib -> modules" and here all the modules files.
Click to expand...
Click to collapse
...: Updates :...
Download the zip update that you want to apply
extract the whole "update" and "root" folders in the "Android" folder. This means looking in the Android folder you will have two subfolders "root" and "update" (in some cases the "update" folder is not present in the zip... no needed)
boot the build
FOR 4.X Version ONLY!
Standard Font: -> http://www.multiupload.com/A2V1QT48DI
RafDroid Font -> http://www.multiupload.com/VWNIIH9P2X
Standard Framework (taskbar icons) -> http://www.multiupload.com/YZALGSEPS6http://hotfile.com/dl/109974758/9fa3c11/SD_update_stock_4rX_framework.7z.html
Rafdroid Framwork (taskbar icons) -> http://www.multiupload.com/OOYO7UZKXE
Removed Apps: extract the whole folder in your Android folder and boot-> http://www.multiupload.com/GUS146P63W
Weather fix (if your weather doesn't update or it's buggy) -> http://www.multiupload.com/IF5FD2784R
FOR 3.X Version ONLY!
Standard Font: -> http://www.multiupload.com/A2V1QT48DI
RafDroid Font -> http://www.multiupload.com/VWNIIH9P2X
Standard Framework (taskbar icons) -> http://www.multiupload.com/JAA3K6VLJM
Rafdroid Framwork (taskbar icons) -> http://www.multiupload.com/77TLLYZEHD
Removed Apps: extract the whole folder in your Android folder and boot http://www.multiupload.com/LWIZC71LPJ
Click to expand...
Click to collapse
To do list (all those things will be uploaded on sunday night CET )
Provide zips for stock font and stock framework/status bar
Provide zips for themes like in the screenshots
Provide zip of removed apps
Check if this works with WP7 partitioned sd card
Do you have problems in booting?
check that your first partition is fat32
check that your fat partition and all other partitions (example the ones created by wp7) are primary partitions.
follow this tips, thanks to zarathustrax -> http://forum.xda-developers.com/showpost.php?p=11688635&postcount=52
if nothing above works, consider to format your sd card with panasonic sd formatter, using "full erase" method. You can find the tool as attachment in the bottom of this post.
check that you have config.txt inside your build folder
check that you are editing/creating the config.txt with a unix compatible text editor like notepad++ (read the config.txt instruction in post 1 to understand how to use)
if you changed the build folder name (example: from Android to RafdroidSomething) make sure you have a "rafdroid.txt" file in your sd card root and in it you have a line rel_path="RafdroidSomething"
if still no luck, try to post your problem but dont forget to post:
- are you using wmo or magldr?
- how is your config.txt?
- did you keep the enclosed userdata.img or changed with your own?
- are you using the included kernel (zimage)?
- a "init.log" file inside the android folder is created? If yes, post it!
- did you copy the "whole" android folder, including the folder itself, on the root of sd card?
- did you changed the folder name?
More info you will provide, more possibility you have that i or someone else can give you the solution to your issues.
Click to expand...
Click to collapse
...: FAQ :...
q) Can you provide a mirror for the downloads
a) I'm sorry but the answer is "no". I pay hotfile every month and the downloads give me the possibility to pay it. I dont do this for money, but I also dont want to waste my money
q) My phone sometimes freeze and I have to reboot.
a) Go in Settings -> Audio -> disable audible touch tones. this will solve the issue in most of the cases.
q) During/after boot a window appears with "System process not respoding". What I have to do?
a) This is caused from the new audio driver I used. The new audio driver has better phone stability and no robo voice. You have two choices: 1) Click on "wait" and all will be fine OR 2) download the "old_acdb_file.zip" and flash it via recovery. In this way you will not have the error anymore but you will start having robo voice on first call (you can avoid this disabling audible touch tones) and could happen that your phone freezes when receiving a call. It's your choiche. I preferred the "window error" one because for me is more important to have a working phone than an error window appearing at boot.
q) I have robo voice when I make a call
a) To avoid this, disable "audible touch tones" from the "settings -> audio" menu. You will have no-more robo voice also if you reboot.
a) During the robo-voice call, enable the speaker, then disable it. You will have no more robo-voice until next reboot.
q) I have very low audio during calls
a) During the call, enable the speaker, then disable it. You will have loud volume until next reboot.
q) after boot I see only a white screen with a green htc logo
a) just wait. It can take fro 5 up to 20 minutes depending on your sd card. There are no issue. The build booted fine, it's just copying all the files to SD. This will happen only on first installation.
q) I'm having high battery drain
a) Try reboot. Try disabling gps in location. As you can see from the screenshot I have 4mA with WIFI active! Also be careful. If during google account setup you choose to backup/restore all your data, the sync process will be dramatic heavy because it has to reinstall all your apps. It could need a couple of hours to settle. Also high battery drain could be caused by SD. try another one.
q) It's really laggy!!!!
a) as all Desire HD builds this is BIG! This needs at least 10-15 minutes after boot to be usable. Then try to use it for 5-6 hours.. and do a couple of reboots.. you will see that the speed will improve. After 24 hours of use and 4-5 rebots this will be really fast.
q) It lags when I'll install apps?
a) yes a little. Just to say: I have a desire hd... it lags also in the same case.. very few.. but the lag is there.. so it's an issue form desire hd base.
q) I have no GPS or the fix is really slow
a) Firs fixt can take up to 5 minutes. just wait.You can edit the config.txt gps_zone= to your country. See here for the right strings http://www.pool.ntp.org/zone/@ if this not solves, try use QuickGps from the market to download a-gps data.
q) Can I unmount the SD while in use or connect the phone as mass storage to my pc while in use?
a) No. Is dangerous for your files
q) It not boots
a) partition again and format again your sd card. follow the guide linked in the first post. post your init.log file for help
q) I have no data/3G/HSDPA
a) probably you have to set your apn manually. google it for tips on how to do and what settings are need for your carrier
q) How do I remove BOOTSOUND / How do I change bootanim
a) bootsound and bootanim are located in /system/customize/resource
Just delete android_audio.mp3 if you dont want sound
q) I have wake up lag
a) It's an issue that devs are trying to solve. It's not related to the build itself. In the Q&A Forum there is a thread about this problem. HERE, HERE,....
q) I have issues in flash during web brosing, the browser force closes
a) If you have issues with flash videos on website, you need an older flash version. Check this post. Thanks to Jayedamina http://forum.xda-developers.com/show...&postcount=280
Click to expand...
Click to collapse
...............
--- last one for me... just in case... ---
Wow, this is awesome.. thanks for showing the SD crowd a little love! downloading now
Really nice to see your HD build on SD.
Thanks!
rafpigna, your hd builds are maybe the best desire hd based builds for hd2
i'm very glad that you've ported it for running from magldr, thanks
Thank's !
Downloaded it,setting up right now
booted just fine .
Data working fine,arows are not working. EDIT:fine after restart !)
Thank's for the SD build !
finally see you here in SD builds, one of my favorite chief. Thank Raf.
Oh my God if i can only send a beer through package! You rock my HD2
Thanks Raf, how to restore stock font?
Master chief ! many thanks from sd lovers !
Thanks for the ROM mate..
I have read alot about its NAND version and about its wonderful performance..
Just tried it now ( SD/WinMo/No MAGLDR ), it ran well on me test card ( 8GB ), but when I tried it on me main 16 GB card, it just stucks on the first boot screen.. looks like it has something to do with SD partitionning..
P.S. both cards were unpartitionned...
Cheers...
jaguaralani said:
Thanks for the ROM mate..
I have read alot about its NAND version and about its wonderful performance..
Just tried it now ( SD/WinMo/No MAGLDR ), it ran well on me test card ( 8GB ), but when I tried it on me main 16 GB card, it just stucks on the first boot screen.. looks like it has something to do with SD partitionning..
P.S. both cards were unpartitionned...
Cheers...
Click to expand...
Click to collapse
Your init.log of unsuccessful boot would help me to find if there is an issue
Sent from my Desire HD using XDA App
Unfortunately,on WinMo boot, no fires hangs on the screenshot RAFDROID and nothing else for over 20 minutes.
What can I do?
init.log:
Code:
e2fsck on loop0
/dev/block/loop0: clean, 1492/25600 files, 95127/102400 blocks
e2fsck on loop1
/dev/block/loop1: clean, 11/65536 files, 12644/262144 blocks
Available space on partitions:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk0p1 7774208 3071040 4703168 40% /bootsdcard
/dev/block/loop0 403144 374052 8612 98% /system
/dev/block/loop1 1032088 34088 945572 3% /data
Mounted partitions:
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,relatime)
none on /dbgfs type debugfs (rw,relatime)
/dev/block/mmcblk0p1 on /bootsdcard type vfat (rw,noatime,nodiratime,fmask=0111,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/loop0 on /system type ext3 (rw,noatime,nodiratime,errors=continue,data=writeback)
/dev/block/loop1 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc)
checking loop0
tune2fs 1.41.3 (12-Oct-2008)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 4e17b557-ed30-42e8-9160-b39a0a76896e
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 25600
Block count: 102400
Reserved block count: 5120
Free blocks: 7273
Free inodes: 24108
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 24
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 6400
Inode blocks per group: 400
Filesystem created: Sat Feb 26 07:02:59 2011
Last mount time: Sat Feb 26 17:51:04 2011
Last write time: Sat Feb 26 17:51:04 2011
Mount count: 2
Maximum mount count: 21
Last checked: Sat Feb 26 07:02:59 2011
Check interval: 15552000 (6 months)
Next check after: Thu Aug 25 07:02:59 2011
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: d4b9346e-8363-420c-ab55-c2296936941e
Journal backup: inode blocks
checking loop1
tune2fs 1.41.3 (12-Oct-2008)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: deefdaf7-4c6e-4e21-bc36-a6b0e4c4300f
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 65536
Block count: 262144
Reserved block count: 13107
Free blocks: 249500
Free inodes: 65525
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 63
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Filesystem created: Sat Feb 26 02:55:15 2011
Last mount time: Sat Feb 26 17:51:06 2011
Last write time: Sat Feb 26 17:51:06 2011
Mount count: 1
Maximum mount count: 34
Last checked: Sat Feb 26 02:55:15 2011
Check interval: 15552000 (6 months)
Next check after: Thu Aug 25 02:55:15 2011
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 5b971090-c3f1-4206-8a0d-392e2f5fe4c1
Journal backup: inode blocks
gps_zone
pl
ppp_mode
0
sd_boost
wince
0
old_light_driver
0
auto_btn_backlight
0
+++++++ GPS ZONE CHANGED +++++++
+++++++ MAGLDR MODE ACTIVATED +++++++
+++++++ RMNET MODE ACTIVATED +++++++
+++++++ BTN BACKLIGHT AUTO-OFF ACTIVATED (echo 1) +++++++
rafpigna said:
Your init.log of unsuccessful boot would help me to find if there is an issue
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
My Pleasure !
Thanks....
but it did not initiate any init.log !!!
and this was me config.txt
gps_zone=uk
ppp_mode=1
wince=1
old_light_driver=0
auto_btn_backl
Have realy been waiting for this - so thanks rafpigna.
Just wating for "Provide zips for stock font" ;-)
jaguaralani said:
My Pleasure !
Thanks....
but it did not initiate any init.log !!!
and this was me config.txt
gps_zone=uk
ppp_mode=1
wince=1
old_light_driver=0
auto_btn_backl
Click to expand...
Click to collapse
If there is no log means SD card is not mounted. Are you using wp7 or wm?
Sent from my Desire HD using XDA App
rafpigna said:
If there is no log means SD card is not mounted. Are you using wp7 or wm?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
WM 6.5>>>>>>>>>>>
Hi all,
Is it normal for wifi to drain 1% every 5-10 mins on standby? Where as when I'm on 2g mobile data I get 40-45mins for every 1%. I've investigated this for 6 hours and it consistently shows the same result.
My setup:
Same Apps and setup. Wifi Cisco E3000 and 20 feet away from my room.
I also placed my phone 6feet away and still get the same batt drain.
I get a 120-190mah as per batterymonitor app on wifi and only 20-30mah on 2g
Thouhts?
My battery consumption on a 2.3.4 XXKG3 rooted S2, without Samsung crap:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Check your running services, you will know rightaway what is killing your battery.
Yes, that is possible. It all depends on your situation. For some people mobile data drains more battery then wifi. And for some wifi drains more then mobile data.
Nothing to worry about.
yqed said:
My battery consumption on a 2.3.4 XXKG3 rooted S2, without Samsung crap:
Check your running services, you will know rightaway what is killing your battery.
Click to expand...
Click to collapse
How the heck can your battery last that long? I barely touched my phone and its down to 50 in hours. Does it matter if I'm on KH3? I live in Nz but imported my phone I think from Taiwan or hk. Will I be able to use KG3?
WiFi drains battery if it is continually searching for a signal when non is present i find .
jje
I prefer to use wifi when possible just because the battery consumption is less than 3G.. i remember one time I forgot the phone at night with wifi turned on and connected, after 7-8 hours i had lost only 2%
I leave wifi and data both turned on, all the time. That way it just uses whatever's available and I don't have to worry about it. With very minimal use (only a few calls and a handful of SMS) I can get 4 days out of my phone. I have a tablet and am usually in front of a PC, so the phone rarely gets used as anything more than a phone!
Anyway, wifi is not your issue. Have you looked into freezing the wifi sharing app? (You don't have to actually be sharing wifi for this to be a relevant thing to do!)
JJEgan said:
WiFi drains battery if it is continually searching for a signal when non is present i find .
jje
Click to expand...
Click to collapse
this is correct, if you have a good Wi-Fi signal the battery drain should be les than 3G but if not then it's gonna be worse.
thanks for the rep guys. I notice that my wifi scans continuously eventhough its using my home network. It's like scanning every 20 secs or so. Ss that normal?
With regards to Apps, and I've frozen everything I can think of that might cause a drain like beautiful widget, setting all my snyc to manual except my google account. I don't receive too much push email. I've frozen the usual culprits like wifi sharing/manager, all samsung Apps, disable fast dormancy, disable auto backup by google.
3 hours ago I frozen juicedefender and when I checked batt still drained 1% 5-15mins.!!! I'm now trying viber frozen.
I'm running out of Apps to freeze!
Is it possible that my phone drains more batt by using wifi N? Btw, as my first post says I already tried to put my phone closer to my router and I still get the same drain. Damn!!!
---------- Post added at 11:40 PM ---------- Previous post was at 11:35 PM ----------
Does having kh3 have anything to do with it? If I change modems will I benefit from it? Could it be rom related - I remember when I first rooted I was on lp and I think the batt was better. I'm now on cog1. 5.1. But I'd imagine it's more of the kernel
Edit: I forgot to mention that I'm getting 60-80% Android OS
Kepster said:
thanks for the rep guys. I notice that my wifi scans continuously eventhough its using my home network. It's like scanning every 20 secs or so. Ss that normal?
With regards to Apps, and I've frozen everything I can think of that might cause a drain like beautiful widget, setting all my snyc to manual except my google account. I don't receive too much push email. I've frozen the usual culprits like wifi sharing/manager, all samsung Apps, disable fast dormancy, disable auto backup by google.
3 hours ago I frozen juicedefender and when I checked batt still drained 1% 5-15mins.!!! I'm now trying viber frozen.
I'm running out of Apps to freeze!
Is it possible that my phone drains more batt by using wifi N? Btw, as my first post says I already tried to put my phone closer to my router and I still get the same drain. Damn!!!
---------- Post added at 11:40 PM ---------- Previous post was at 11:35 PM ----------
Does having kh3 have anything to do with it? If I change modems will I benefit from it? Could it be rom related - I remember when I first rooted I was on lp and I think the batt was better. I'm now on cog1. 5.1. But I'd imagine it's more of the kernel
Edit: I forgot to mention that I'm getting 60-80% Android OS
Click to expand...
Click to collapse
Personally, I kept it short and simple. I flashed the XXKG3 generic ROM that is compatible with my Bell distributor then I installed CF-Root and started to uninstall the apps, not "freezing" them (no idea why is called freeze, as the command is "# pm disable PACKAGE").
I use Wifi N with a Cisco E4200 DD-WRT (phone at 20") as well Beautiful Widgets and I never disabled any of the system services you mentioned in your post, you should NOT play with them. You are trying blindly to see if you improve your battery when in fact you are hurting it by killing processes that are needed by system apps (there is your drain). And Juice Defender saves you a bit of battery than use it on its app... not a big advantage. Just start from fresh with a stock ROM and clean your way up, the right way... don't just disable/uninstall what you "think" it might help. And stop installing "optimization" apps, how do you know they actually help if you do not monitor them? Get your system cleaned first, then start installing one app at the time while checking the stats available in your OS, not some fancy app. DocRambone posted a very good list, related to safe applications to be removed. Did you looked at that list? Personally, I uninstalled only half of them.
These are my running services:
Code:
PID USER VSZ STAT COMMAND
1 root 508 S /init
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
4 root 0 SW [migration/0]
5 root 0 SW [watchdog/0]
9 root 0 SW [events/0]
11 root 0 SW [khelper]
15 root 0 SW [async/mgr]
16 root 0 SW [pm]
19 root 0 SW [suspend]
20 root 0 SW [sync_system_wor]
151 root 0 SW [s5p-tmu]
337 root 0 SW [sync_supers]
339 root 0 SW [bdi-default]
341 root 0 SW [kblockd/0]
356 root 0 SW [khubd]
359 root 0 SW [kseriod]
394 root 0 SW [irq/331-max8997]
434 root 0 SW [kmmcd]
527 root 0 SW [kondemand/0]
540 root 0 SW [pet_watchdog/0]
549 root 0 SW [khungtaskd]
550 root 0 SW [kswapd0]
599 root 0 SW [aio/0]
612 root 0 SW [crypto/0]
1237 root 0 SW [sec_jack_wq]
1240 root 0 SW [irq/350-sec_hea]
1245 root 0 SW [spi_gpio.3]
1262 root 0 SW [svnet_txq]
1274 root 0 SW [file-storage]
1300 root 0 SW [irq/328-mxt224_]
1306 root 0 SW [irq/325-k3g]
1312 root 0 SW [irq/326-proximi]
1315 root 0 SW [cm3663_light_wq]
1316 root 0 SW [cm3663_prox_wq]
1366 root 0 SW [mali_dvfs]
1369 root 0 SW [mali-pmm-wq]
1378 root 0 SW [sii9234_wq]
1379 root 0 SW [irq/481-mhl_int]
1380 root 0 SW [irq/496-mhl_wak]
1383 root 0 SW [irq/343-max1704]
1394 root 0 SW [kstriped]
1396 root 0 SW [kmpathd/0]
1398 root 0 SW [kmpath_handlerd]
1399 root 0 SW [ksnapd]
1400 root 0 SW [kconservative/0]
1414 root 0 SW [ktflash_requlat]
1429 root 0 SW [usbhid_resumer]
1432 root 0 SW [binder]
1441 root 0 SW [irq/333-IPC_HOS]
1452 root 0 SW [mmcqd]
1481 root 0 SW [l2cap]
1482 root 0 SW< [krfcommd]
1488 root 0 SW [dynamic hotplug]
1501 root 0 SW [melfas_touchkey]
1506 root 0 SW [fimc0_iqr_wq_na]
1509 root 0 SW [fimc1_iqr_wq_na]
1512 root 0 SW [fimc2_iqr_wq_na]
1515 root 0 SW [fimc3_iqr_wq_na]
1518 root 0 SW [hdcp work]
1529 root 0 SW [tvout resume wo]
1535 root 0 SW [sec-battery]
1538 root 384 S /sbin/ueventd
1761 root 0 SW [Si4709_wq]
1782 root 0 SW [jbd2/mmcblk0p9-]
1784 root 0 SW [ext4-dio-unwrit]
2563 root 0 SW [jbd2/mmcblk0p7-]
2564 root 0 SW [ext4-dio-unwrit]
2566 root 0 SW [jbd2/mmcblk0p1-]
2567 root 0 SW [ext4-dio-unwrit]
2570 root 0 SW [jbd2/mmcblk0p10]
2571 root 0 SW [ext4-dio-unwrit]
2579 system 868 S /system/bin/servicemanager
2580 root 6616 S /system/bin/vold
2581 system 1972 S /system/bin/notified_event
2583 root 732 S /system/bin/debuggerd
2584 radio 9512 S /system/bin/rild
2585 system 4624 S /system/bin/npsmobex
2586 system 8476 S /system/bin/drexe
2590 bluetoot 1372 S /system/bin/dbus-daemon --system --nofork
2591 root 932 S /system/bin/installd
2592 keystore 1804 S /system/bin/keystore /data/misc/keystore
2594 system 14192 S /system/bin/tvoutserver
2595 shell 800 S /system/bin/sh /system/bin/rtc_log.sh
2612 shell 780 S /system/bin/immvibed
2907 wifi 2644 S /system/bin/wpa_supplicant -Dwext -ieth0 -c/data/wifi/bcm_su
3374 media 56536 S < /system/bin/mediaserver
3375 root 15472 S /system/bin/netd
3376 root 126m S zygote /bin/app_process -Xzygote /system/bin --zygote --star
3391 system 276m S system_server
3496 root 0 SW [iscan_sysioc]
3497 root 0 SW [dhd_watchdog]
3498 root 0 SW [dhd_dpc]
3499 root 0 SW [dhd_sysioc]
3502 system 152m S com.android.systemui
3511 app_99 168m S com.sec.android.inputmethod.axt9
3521 radio 155m S com.android.phone
3522 app_66 148m S android.process.media
3528 app_53 134m S com.sec.pcw.device
3532 system 134m S com.samsung.bt.avrcp
3536 bluetoot 134m S com.broadcom.bt.app.system
3544 app_12 176m S com.sec.android.app.twlauncher
3604 app_54 173m S com.google.process.gapps
3631 app_12 148m S android.process.acore
3688 app_84 135m S com.sec.android.app.FileTransferManager
3777 app_36 137m S com.sec.android.widgetapp.weatherclock
3927 app_38 136m S com.sec.android.widgetapp.apnews
4193 app_91 137m S com.sec.android.app.clockpackage
4220 app_16 137m S com.android.providers.calendar
4234 app_100 134m S com.sec.android.daemonapp.accuweather
4255 app_78 159m S com.google.android.gm
4333 app_81 174m S com.cooliris.media
4366 app_119 144m S com.google.android.apps.reader
4376 app_103 170m S com.levelup.beautifulwidgets
4435 app_37 138m S com.sec.android.widgetapp.stockclock
4453 app_16 138m S com.android.calendar
4476 system 156m S com.android.settings
4486 app_112 177m S com.google.android.music
4633 app_82 137m S com.sec.android.app.fm
4752 app_40 135m S com.sec.android.app.samsungapps.una
6623 app_68 185m S < com.google.android.apps.maps
9014 dhcp 916 S /system/bin/dhcpcd -ABK eth0
10732 graphics 139m S com.sec.android.app.screencapture
11958 system 138m S com.wssyncmldm
11989 system 135m S com.sec.android.providers.drm
11997 app_1 139m S com.smlds
12037 app_102 139m S com.skype.raider
13094 app_5 141m S jackpal.androidterm
13136 app_115 135m S com.noshufou.android.su
13170 app_68 149m S com.google.android.apps.maps:NetworkLocationService
13180 app_68 144m S com.google.android.apps.maps:FriendService
13503 app_83 141m S com.sec.android.app.FileTransferServer
13579 root 0 SW [flush-179:0]
13646 shell 1684 S /sbin/ext/busybox sh /sbin/sleep 3600
13651 shell 1676 S /sbin/ext/busybox /sbin/sleep 3600
13707 app_68 154m S com.google.android.apps.maps:HotpotService
13788 system 135m S com.android.MtpApplication
13825 app_5 796 S /system/bin/sh -
13858 root 796 S sh -
13966 root 1684 S /sbin/ext/busybox sh /sbin/ps
13971 root 1716 R /sbin/ext/busybox /sbin/ps
Compare it with yours and see what is running extra. Here are the visual running services and my battery after 29hrs (just for reference, the proper way is to look into a terminal):
I will do what you said bro and start from scratch! Never thought I'm actually causing more drain by disabling some Apps! One more question bro. Which Apps did you remove from the list?
Thanks again!
Certain routers are known to drain battery life on our SGS2s. I'm fairly certain some D-Link routers are known offenders in this regard. I can't be certain about you're router, but if you have access to different wifi connections, you should do a little testing.
Fiddling about in your router settings and upgrading your router firmware may help.
I'd link the threads where I came across the info, but I can't seem to find them atm.
Kepster said:
I will do what you said bro and start from scratch! Never thought I'm actually causing more drain by disabling some Apps! One more question bro. Which Apps did you remove from the list?
Thanks again!
Click to expand...
Click to collapse
DocRambone's list is very helpful. Technically, you can remove all that list and it won't cause any issues to your phone. However, I wanted to keep some of the apps like the NDLA, Analog Clock (for alarms), Memo, etc. Just go with your usage and uninstall what you think you will never use. Is always easier to remove it later, instead of putting it back. I don't remember exactly which apps I uninstalled (not disabled), I did it the hard way through terminal.
Many people recommended Titanium but I feel much more comfortable to see what is going on. SystemApp Remover is very good alternative to Terminal, IMO.
Here it is a list of the package manager commands:
Code:
# pm
usage: pm [list|path|install|uninstall]
pm list packages [-f] [-d] [-e] [-u] [FILTER]
pm list permission-groups
pm list permissions [-g] [-f] [-d] [-u] [GROUP]
pm list instrumentation [-f] [TARGET-PACKAGE]
pm list features
pm list libraries
pm path PACKAGE
pm install [-l] [-r] [-t] [-i INSTALLER_PACKAGE_NAME] [-s] [-f] PATH
pm uninstall [-k] PACKAGE
pm clear PACKAGE
pm enable PACKAGE_OR_COMPONENT
pm disable PACKAGE_OR_COMPONENT
pm setInstallLocation [0/auto] [1/internal] [2/external]
The list packages command prints all packages, optionally only
those whose package name contains the text in FILTER. Options:
-f: see their associated file.
-d: filter to include disbled packages.
-e: filter to include enabled packages.
-u: also include uninstalled packages.
The list permission-groups command prints all known
permission groups.
The list permissions command prints all known
permissions, optionally only those in GROUP. Options:
-g: organize by group.
-f: print all information.
-s: short summary.
-d: only list dangerous permissions.
-u: list only the permissions users will see.
The list instrumentation command prints all instrumentations,
or only those that target a specified package. Options:
-f: see their associated file.
The list features command prints all features of the system.
The path command prints the path to the .apk of a package.
The install command installs a package to the system. Options:
-l: install the package with FORWARD_LOCK.
-r: reinstall an exisiting app, keeping its data.
-t: allow test .apks to be installed.
-i: specify the installer package name.
-s: install package on sdcard.
-f: install package on internal flash.
The uninstall command removes a package from the system. Options:
-k: keep the data and cache directories around.
after the package removal.
The clear command deletes all data associated with a package.
The enable and disable commands change the enabled state of
a given package or component (written as "package/class").
The getInstallLocation command gets the current install location
0 [auto]: Let system decide the best location
1 [internal]: Install on internal device storage
2 [external]: Install on external media
The setInstallLocation command changes the default install location
0 [auto]: Let system decide the best location
1 [internal]: Install on internal device storage
2 [external]: Install on external media
For some reason I couldn't upload screen capture photos of my usage our lack thereof but basically with minimal apps installed I still get a drain from 100 to 76% in 6 hours over wifi-with 2 signal bars. Android os 91%, display 8%, cell standby 5%, idle 3%.
Checked running apps and saw fotaclient, fb, drm, Settings, maps, viber, setcpu, go launcher, syncimds, google services, voice command. I'm assuming this are normal background apps. I've got a strong feeling that my router doesn't like my phone. I will try to keep my pyotr idle but this time on data connection
Sent from my GT-I9100 using XDA App
Problem solved! It was indeed my e3000 that's causing the excessive drain! I just separated my 2.4 and 5ghz signal and voila! After 8 hours out only drained 8%! Woohoo!
Sent from my GT-I9100 using XDA App
Some users had reported wifi drain for KH3 radio. When i was on stock 2.3.3, freezing wifi sharing, wifi sharing manager and switching to KG5 modem did the trick. KH3 also caused higher battery temp when compared to Kg5...
Kepster said:
Problem solved! It was indeed my e3000 that's causing the excessive drain! I just separated my 2.4 and 5ghz signal and voila! After 8 hours out only drained 8%! Woohoo!
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Just to add, I see you are on 2Degrees, I get higher drain on my 2Degrees than my Vodafone...whilst I suspect that 2Degrees have weak reception in my area, and usually runs on 2G, I presume the phone is still searching for 3G network...hence uses more power. Just out of curiousity did you buy your SGS2 from Vodafone or Telecom? Chur.
droidphile said:
Some users had reported wifi drain for KH3 radio. When i was on stock 2.3.3, freezing wifi sharing, wifi sharing manager and switching to KG5 modem did the trick. KH3 also caused higher battery temp when compared to Kg5...
Click to expand...
Click to collapse
I confirm that XXKH3 drains faster the battery compared to XXKG3, but look at the GPS gains... whoaaa, pinpoint location in less than 3 seconds with a 5meters accuracy. Really happy to finally use my GPS properly, it is worth the increased battery drain. From my tests, the new firmware decreased the battery life by about 4 hours... I can live with that, in exchange of a great GPS.
Yeah GPS locking was brilliant in KH3... But i use wifi and data connection more, than GPS. KH3 drained more battery on standby also. May be it's causing more wakelocks...
This kernel is based on TeamCanjica/3.0.101 branch and much credit goes to them for doing this
However not everything from TC kernel is there. I'm not happy with the new liveopp algorithm. Also there's no ddr oc as one can get hurt with this now (/data fs corruption). When @ChronoMonochrome improves the implementation, maybe I'll merge it.
Compatibility:
I suspect it should work fine for any CM-11.0 based rom. If someone tests it, I'll add info here
- Stock
- Vanir
- Carbon
- CM11
- CM10.1
- CM10.2
- CM12.1 until I get a proper ramdisk, I don't support this config, besides reboot/poweroff doesnt work on it.
For version r6 you don't need to flash extra ramdisk - it contains all previously gathered ramdisks and uses the right one based on /system/build.prop file - checks ro.build.version.sdk (https://github.com/mkaluza/Samsung_STE_Kernel/blob/master/usr/u8500_initramfs_files/init#L22)
Changes:
Kernel (https://github.com/mkaluza/Samsung_STE_Kernel/commits/3.0.101)
[r5] Full changelog
WARNING - if you have some custom uv/oc, disable it first, as now you'll be using different Vbbx by default (original one). Test your oc/uv again for stability and correct if necessary, or restore Vbbx from your uv script first:
Code:
for f in /sys/kernel/liveopp/arm_step0*; do echo vbbx=0xcc > $f; done
btw novathor settings interfere with mali UV, so I removed them completely from my phone (can't be disabled - unfortunately for them )
Download:
MediaFire all releases
A bonus - a modified torch with high power option - I was always pissed with having to use novathor settings for this...
Install:
Flash update.zip with CWM
Loading modules
There are a few ways to load modules depending on how important those modules are:
1. add module name to /system/etc/modules file (create it if it doesn't exist). Add a name without extension (like cpufreq_lionheart or logger)
(TODO: handle /data/etc/modules as well)
Those modules will be loaded just after /system is mounted
2. use KoControl app (or similar) - those modules will be loaded when system starts up, so use it only for unimportant modules
3. copy it to one of initramfs overlay/modules directory: /efs/common/overlay/modules, /efs/boot/overlay/modules, /efs/recovery/overlay/modules - these modules will be loaded before init even starts - it's useful for filesystem modules like f2fs
Dynamic governor documentation
Since it has many params that depend on each other, some doc is needed:
Dynamic governor documentation
It's a work in progress, so it'll be gradually improved. You can improve the improvement process by letting me know that you use it and whether you like it or not If "not" - then tell me why, maybe something can be done about it. Although it's unlikely that I'll accept feature requests unless I find it useful for myself, feel free to fork the kernel and modify it
LVM
Before anything else, read those and all the stuff those posts tell you to read:
https://www.howtoforge.com/linux_lvm
http://forum.xda-developers.com/nexus-s/general/howto-combined-emulated-storage-nexus-s-t2848752
http://forum.xda-developers.com/nexus-s/general/howto-partitioning-nexus-s-using-lvm-t1656794
http://www.xda-developers.com/android/bypass-nexus-s-storage-restrictions/
If you don't understand something, keep reading. If you still don't understand, leave it for now - It's for your safety.
Later I'll add SGA specific stuff how to make use of our empty /preload partition and get more free space on /data
NFC
The kernel has nfc modules available, so in theory it should work - you just need to load them as described in section on modules.
Load pn544 and/or pn547. You also need nfc-enabled rom (If it doesn't work, then I don't know what else... don't have nfc to test it)
Upgradeable ramdisk
See this file, it tells all the story
https://github.com/mkaluza/Samsung_STE_Kernel/blob/master/usr/u8500_initramfs_files/init
I'll add some comment later
Troubleshooting:
- my wifi isn't working
- TODO: how to report errors to make the difference
XDA:DevDB Information
MK Kernel [3.0.101], Kernel for the Samsung Galaxy S Advance I9070
Contributors
mkaluza
Source Code: https://github.com/mkaluza/Samsung_STE_Kernel
Kernel Special Features: LVM, new dynamic governor, automatic voltage calculation, 630 MB ram
Version Information
Status: Stable
Current Stable Version: r6.0.0.
Stable Release Date: 2015-06-05
Created 2014-12-19
Last Updated 2015-06-05
Thanks to @Reinkaos for beta testing
His report:
Reinkaos said:
OK so here's a report, I use min 200mhz max 1000mhz, continuous usage with wifi on all the time from 100%-4%.
liveopp:
200 = 0x0c
300 = 0x0d
400 = 0x0e
500 = 0x1d
600 = 0x1f
700 = 0x20
800 = 0x21
900 = 0x28
1000 = 0x2c
mali (I use idx 1 and 5)
250mhz = 0x17
400mhz = 0x1b
From BBS dump:
Deep Sleep (): 2 h 15 m 16 s 43.3%
Awake (): 2 h 57 m 4 s 56.7%
Screen On (): 2 h 56 m 28 s 56.5%
Phone On (): 27 s 0.1%
Wifi On (): 2 h 54 m 2 s 55.7%
Wifi Running (): 2 h 54 m 55.7%
No Data Connection (): 5 h 12 m 21 s 100.0%
No or Unknown Signal (): 5 h 12 m 21 s 100.0%
Screen dimmed (): 2 h 56 m 28 s 56.5%
1 GHz (): 36 m 44 s 11.8%
900 MHz (): 8 m 18 s 2.7%
800 MHz (): 9 m 51 s 3.2%
700 MHz (): 11 m 17 s 3.6%
600 MHz (): 12 m 47 s 4.1%
500 MHz (): 14 m 30 s 4.6%
400 MHz (): 16 m 24 s 5.3%
300 MHz (): 5 m 37 s 1.8%
200 MHz (): 1 h 1 m 33 s 19.7%
Deep Sleep (): 2 h 15 m 16 s 43.3%
Just to compare, here are the last 2 test that I did on previous kernel, with the same usage pattern, on interactive:
1
Deep Sleep (): 3 h 52 m 51 s 57.9%
Awake (): 2 h 49 m 36 s 42.1%
Screen On (): 2 h 47 m 57 s 41.7%
Wifi On (): 2 h 43 m 41 s 40.7%
Wifi Running (): 2 h 43 m 39 s 40.7%
No Data Connection (): 6 h 42 m 28 s 100.0%
No or Unknown Signal (): 6 h 42 m 28 s 100.0%
Screen dark (): 2 h 47 m 57 s 41.7%
1 GHz (): 45 m 25 s 11.3%
800 MHz (): 8 m 23 s 2.1%
600 MHz (): 46 m 31 s 11.6%
400 MHz (): 9 m 22 s 2.3%
200 MHz (): 59 m 54 s 14.9%
Deep Sleep (): 3 h 52 m 51 s 57.9%
2
Deep Sleep (): 3 h 58 m 48 s 60.6%
Awake (): 2 h 35 m 12 s 39.4%
Screen On (): 2 h 34 m 32 s 39.2%
Wifi On (): 2 h 32 m 1 s 38.6%
Wifi Running (): 2 h 32 m 38.6%
No Data Connection (): 6 h 34 m 1 s 100.0%
No or Unknown Signal (): 6 h 34 m 1 s 100.0%
Screen dark (): 2 h 34 m 32 s 39.2%
1 GHz (): 33 m 4 s 8.4%
800 MHz (): 9 m 27 s 2.4%
600 MHz (): 49 m 48 s 12.6%
400 MHz (): 9 m 42 s 2.5%
200 MHz (): 53 m 9 s 13.5%
Deep Sleep (): 3 h 58 m 48 s 60.6%
No random reboots. I'm not sure about how fast screen turned on when receiving a call though, since I never pay attention to it in the previous kernel, so can't really compare.
And mtp doesn't work, not sure if that's on my side.
Anyway those dynamic tunables, is there any doc or explanation of each? Will definitely play around with it. Gonna test it again today to see if I ran into problems. Haven't had any problems yet, so far so good :good:
Click to expand...
Click to collapse
mkaluza said:
Thanks to @Reinkaos for beta testing
Click to expand...
Click to collapse
No problem, glad I could help
mkaluza said:
This kernel is based on TeamCanjica/3.0.101 branch and much credit goes to them for doing this
Compatibility:
I use it with Vanir ROM and I don't know how/if it'll work on other roms, but I suspect it's fine for any CM-11.0 based rom. If someone tests it, I'll add info here
Changes:
Ramdisk (https://github.com/mkaluza/ste-ramdisk-vanir/commits/master):
- don't turn zram swap by default (can be turned on via init.d) - it just eats cpu and rarely gives
- removed cm performance profiles - they interfere with init.d/setcpu
- run adb as root by default - it annoyed me to constantly type su, esp. that this su version is a bit lame and su -c "command" doesnt work
Kernel (https://github.com/mkaluza/Samsung_STE_Kernel/commits/3.0.101)
- more liveopp freqs 100-1000 with 100 MHz step
- improved liveopp and mali_boost algorithms (compared to original Vanir Kernel, which is by Team-Exhibit)
- Dynamic cpufreq governor (my design) - brings good performance and battery life together. It's a part of Project Zen (GitHub)
- LiveOPP automatic voltage calculation based on AVS data - It should reduce probability of random reboots, but beware - if you have some custom uv/oc, disable it first, as now you'll be using different vbbs by default (original one). Test your oc/uv again for stability and correct if necessary
- killed u8500 hotplug - it caused problems with audio and didn't bring any more battery time
- disabled highmem - it's not needed with only 768 MB RAM
- added Joel RCU
As a bonus - a modified torch with high power option - I was always pissed with having to use novathor settings for this...
btw novathor settings interfere with mali UV, so I removed them completely from my phone (can't be disabled - unfortunately for them )
However not everything from TC kernel is there - I didn't like the new liveopp algorithm. Also there's no ddr oc as one can get hurt with this when used badly...
Download:
MediaFire
Install:
No update zip for now (if somebody want's to create it then by all means do)
Flash zImage with either Universal Kernel Flasher or just dd:
Code:
dd if=zImage of=/dev/block/mmcblk0p15
unpack modules.zip to /system/lib/modules/
Source:
GitHub
XDA:DevDB Information
MK Kernel [3.0.101], Kernel for the Samsung Galaxy S Advance I9070
Contributors
mkaluza
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: r1
Stable Release Date: 2014-12-19
Created 2014-12-19
Last Updated 2014-12-19
Click to expand...
Click to collapse
Wi-fi isn`t working properly. After 1 or two reboots, I can`t switch wi-fi to on . ( commonly problem seen before on other builds )
pictorul20 said:
Wi-fi isn`t working properly. After 1 or two reboots, I can`t switch wi-fi to on . ( commonly problem seen before on other builds )
Click to expand...
Click to collapse
It happens when there's kernel-module mismatch - have you extracted modules.zip into right place? check this again... It works fine for me and @Reinkaos. What does dmesg say just after you try to enable wifi?
There might be some subtle problem with this kernel that is causing random reboots from time to time. For now set your deepest sleep state to 4 (it defaults to 5 now), as I suspect this might be the cause (I removed all oc/uv and mali stuff and it still happens, now testing deepsleep=4).
If a reboot happens, save /proc/last_kmsg somewhere and look for "Unhandled fault: imprecise external abort (0x1c06)". Actually every time a crash happens, save last_kmsg You can use this init.d script to collect it at every system startup (saves them to /data/local/log/last_kmsg
mkaluza said:
There might be some subtle problem with this kernel that is causing random reboots from time to time. For now set your deepest sleep state to 4 (it defaults to 5 now), as I suspect this might be the cause (I removed all oc/uv and mali stuff and it still happens, now testing deepsleep=4).
If a reboot happens, save /proc/last_kmsg somewhere and look for "Unhandled fault: imprecise external abort (0x1c06)". Actually every time a crash happens, save last_kmsg You can use this init.d script to collect it at every system startup (saves them to /data/local/log/last_kmsg
Click to expand...
Click to collapse
sorry, I might said that wrong. I wanted to say that I don-t have wi-fi network at all. I can-t switch it on at all from settings menu. any help would be more than welcome. Ohh, and one last thing. U seem to always do a great job when it comes to " under the hood" customisation and enhanced features . Good work .
pictorul20 said:
sorry, I might said that wrong. I wanted to say that I don-t have wi-fi network at all. I can-t switch it on at all from settings menu. any help would be more than welcome.
Click to expand...
Click to collapse
You said it right and my response is probably correct - you try to tap the wifi button or turn it on in settings and either it turns on for a very brief moment or not at all. That's a sign of module-kernel mismatch. Check again if you extracted those modules (or even better, just do it) - your old modules from vanir won't work with this kernel, there are too many changes.
I'll try to make update.zip later to make install easier.
pictorul20 said:
Ohh, and one last thing. U seem to always do a great job when it comes to " under the hood" customisation and enhanced features . Good work .
Click to expand...
Click to collapse
Thank you
mkaluza said:
You said it right and my response is probably correct - you try to tap the wifi button or turn it on in settings and either it turns on for a very brief moment or not at all. That's a sign of module-kernel mismatch. Check again if you extracted those modules (or even better, just do it) - your old modules from vanir won't work with this kernel, there are too many changes.
I'll try to make update.zip later to make install easier.
Thank you
Click to expand...
Click to collapse
U`re welcome., and yess that-s exactly the problem I`m facing. It`s not quite a hazardous problem but it-`s just a bug somewhere in the kernel probably. It happens. And one last question, first time I had overwrited the modules to the sistem folder ( that-s when i saw 4 the 1st time that my wi-fi isn-t responding at all ) , then ........ I thought I might delete all the modules from lib/modules to prevent any incompatibility with the copyed ones. Now my question is : Everytime i-m installing cm 11 roms or vanir rom , Do I have to copy/paste modules and overwrite them to lib/modules folder, or do I have to wipe all content inside of that folder and only after that paste the modified modules that you posted in this thread?
L.E :. I can-t switch from internal to external also usb connection doesn-t work in windows ( can-t access my internal / external storage from usb cable )even with proper usb drivers installed )
pictorul20 said:
U`re welcome., and yess that-s exactly the problem I`m facing. It`s not quite a hazardous problem but it-`s just a bug somewhere in the kernel probably. It happens. And one last question, first time I had overwrited the modules to the sistem folder ( that-s when i saw 4 the 1st time that my wi-fi isn-t responding at all ) , then ........ I thought I might delete all the modules from lib/modules to prevent any incompatibility with the copyed ones.
Click to expand...
Click to collapse
That shouldn't matter. What "lsmod" says? what happens when you do "modprobe dhd". If it shows some error, do "modprobe dhd; dmesg | tail -n 50" and pm me the output.
pictorul20 said:
Now my question is : Everytime i-m installing cm 11 roms or vanir rom , Do I have to copy/paste modules and overwrite them to lib/modules folder, or do I have to wipe all content inside of that folder and only after that paste the modified modules that you posted in this thread?
Click to expand...
Click to collapse
Overwrite should be enough and yes, you have to do it every time you reinstall rom
pictorul20 said:
L.E :. I can-t switch from internal to external
Click to expand...
Click to collapse
I don't understand...
pictorul20 said:
also usb connection doesn-t work in windows ( can-t access my internal / external storage from usb cable )even with proper usb drivers installed )
Click to expand...
Click to collapse
Ok, than MTP is screwed. I never use it so I didn't see it, and @Reinkaos wasn't sure if it's the kernel or his phone, but now we know it's the kernel.
@mkaluza it would be great if you make a stock kernel too, since cocafe has almost stopped to support our device
Most of us are on stock JB but it would be really nice if you implement a stock kernel that can enhance the performance of our phone
Hoping you'll do it
@pictorul20 I just remembered something - apart from modules mismatch there was some problem with I think firmware paths, but I haven't got slightest idea what was it... @Reinkaos any thoughts?
The funny thing is - I flashed boot.img from original vanir nightly (and copied modules) and wifi ISN'T WORKING After flashing my kernel (not my particular source - just any one build on my machine) it works
I can remember having once the reverse problem (it wasn't working on my kernel) - I know I fixed it somehow and never had it again. I haven't noticed that wifi stopped working on dist kernel because I never again used one...
DAMN... I know it was something simple to do, but hard to find... Anyone? @cocafe maybe you can remember?
Guys, what does command find /system -iname "*bcm*" show?
For me it's this:
Code:
/system/bin/bcm4330.hcd
/system/etc/wifi/bcmdhd_apsta.bin
/system/etc/wifi/bcmdhd_mfg.bin
/system/etc/wifi/bcmdhd_p2p.bin
/system/etc/wifi/bcmdhd_sta.bin
/system/vendor/firmware/fw_bcmdhd.bin
/system/vendor/firmware/fw_bcmdhd_apsta.bin
jadega said:
@mkaluza it would be great if you make a stock kernel too, since cocafe has almost stopped to support our device
Most of us are on stock JB but it would be really nice if you implement a stock kernel that can enhance the performance of our phone
Hoping you'll do it
Click to expand...
Click to collapse
But there's actually not much more to be done Cocafe's kernel is very good. It's actually very similar to 3.0.101 kernel in terms of features. As for power/performance, when dynamic gov is field tested a bit more, I'll merge it and send a pull request to Cocafe. There's no point in keepeng two kernels...
Another thing is, for all of you still on JB - install Vanir. It's ****in awesome. Stable, fast and doesn't drain batt. And when issues with wifi are solved, it'll be even better I'm happy with the speed even on JIT, and on ART it's even faster (I don't use it not because it's unstable, but because while developing performance features I want to be able to see any improvements, and it's hard below some threshold )
mkaluza said:
@pictorul20 I just remembered something - apart from modules mismatch there was some problem with I think firmware paths, but I haven't got slightest idea what was it... @Reinkaos any thoughts?
The funny thing is - I flashed boot.img from original vanir nightly (and copied modules) and wifi ISN'T WORKING After flashing my kernel (not my particular source - just any one build on my machine) it works
I can remember having once the reverse problem (it wasn't working on my kernel) - I know I fixed it somehow and never had it again. I haven't noticed that wifi stopped working on dist kernel because I never again used one...
DAMN... I know it was something simple to do, but hard to find... Anyone? @cocafe maybe you can remember?
Guys, what does command find /system -iname "*bcm*" show?
For me it's this:
Code:
/system/bin/bcm4330.hcd
/system/etc/wifi/bcmdhd_apsta.bin
/system/etc/wifi/bcmdhd_mfg.bin
/system/etc/wifi/bcmdhd_p2p.bin
/system/etc/wifi/bcmdhd_sta.bin
/system/vendor/firmware/fw_bcmdhd.bin
/system/vendor/firmware/fw_bcmdhd_apsta.bin
Click to expand...
Click to collapse
I have no idea, does different firmware had anything to do with it?
Anyway, here's mine
Code:
/system/bin/bcm4330.hcd
/system/etc/wifi/bcmdhd_apsta.bin
/system/etc/wifi/bcmdhd_mfg.bin
/system/etc/wifi/bcmdhd_p2p.bin
/system/etc/wifi/bcmdhd_sta.bin
/system/vendor/firmware/fw_bcmdhd.bin
/system/vendor/firmware/fw_bcmdhd_apsta.bin
@pictorul20 one more thing - can you make sure permissions on modules are 644? because that's what caused wifi not to work (I extracted modules from zip file with total commander to sd card, where default perms are 770), and when I copied them to /system/lib/modules, they remained that way and that was the problem.
mkaluza said:
@pictorul20 one more thing - can you make sure permissions on modules are 644? because that's what caused wifi not to work (I extracted modules from zip file with total commander to sd card, where default perms are 770), and when I copied them to /system/lib/modules, they remained that way and that was the problem.
Click to expand...
Click to collapse
So, I need each module file to set with 644 permission, right? I`ll try and report back if that solved the problem. Thanks
pictorul20 said:
So, I need each module file to set with 644 permission, right? I`ll try and report back if that solved the problem. Thanks
Click to expand...
Click to collapse
Maybe just flash the update.zip from post #1 - it should fix everything and if not, I'll give you instructions how to debug that stuff.
mkaluza said:
Maybe just flash the update.zip from post #1 - it should fix everything and if not, I'll give you instructions how to debug that stuff.
Click to expand...
Click to collapse
I flashed this kernel on my slimsaber and wifi doesn't work.
If can help log just says WifiStateMachine E: Failed to load driver
Wifi problem debugging
hastalafiesta said:
I flashed this kernel on my slimsaber and wifi doesn't work.
If can help log just says WifiStateMachine E: Failed to load driver
Click to expand...
Click to collapse
Yes it does. Logcat is important - it's good you checked there. We'll try to make it compatible with other roms, but you must help me debug it, ok?
@pictorul20 - can you do those steps too?
(all the stuff below has to be done via adb as root). copy/paste all commands, because all the quotes there are important and it's easy to make a mistake
Code:
cd /system/lib/modules
ls -l
check that all modules have 644 permissions (rw-r--r--)
Code:
lsmod
It should say something (for me it's). If nothing is shown, continue anyway (but tell me about it).
bthid 4267 0 - Live 0x00000000
param 10593 0 - Live 0x00000000 (P)
j4fs 66945 1 - Live 0x00000000 (P)
Click to expand...
Click to collapse
Code:
insmod /system/lib/modules/dhd.ko
lsmod
It should not return an error and lsmod should then contain a line similar to this
dhd 430856 0 - Live 0x00000000
Click to expand...
Click to collapse
if however it return some error, do this and send me the output and the error
Code:
insmod /system/lib/modules/dhd.ko; dmesg | tail -n 20
If so far everything is fine, it's time for hacky stuff now
Code:
rmmod dhd
mkdir /tmp/strace
cd /proc/`pidof system_server`/task
for p in `grep -i wifi */comm | cut -f 1 -d '/'`; do n=`cat $p/comm`; strace -tt -p $p -o/tmp/strace/${n}.strace& done
then tap wifi button in quick settings at least twice (not too fast - wait at least 1 sec) and then
Code:
killall strace
zip -r /mnt/sdcard/wifi.strace1.zip /tmp/strace
if you want to look for an error, do
Code:
cd /tmp/strace
grep "= -" *.strace
this will show all failed syscals with (hopefully) some useful info. If it helps you solve the problem, than ok (share it here), if not, continue
Code:
mkdir /tmp/strace2
strace -ff -tt -p `pidof system_server` -o /tmp/strace2/system_server
tap the wifi button as before and press Ctrl-C to kill the command above
Code:
zip -r /mnt/sdcard/wifi.strace2.zip /tmp/strace2
Mail me (mk at flex.pm) both wifi.strace*.zip files from the root of your internal memory.
@mkaluza
EDIT: I messed up with modules for various tests, i restored the original modules, followed your guide and all went fine.
WIFI works with this! Thanks for your work, till now kernel works pretty well.
Just tried the r3 (630mb) and all is good and very smooth.
Hello everyone!
Does anybody know please, if it's somehow possible to dump/extract messages from the Facebook messenger application which have been already deleted by the user (read correctly as a 'cheating girlfriend') and which maybe left stored somewhere on device within the internal messenger's CACHE memory?
I am pretty sure that they still must have be stored somewhere secretly in the phone, because within the Apps -> Messenger -> Storage -> It still shows that some space is used as following: Application - 100MB, Data -325 MB, Cache - 60.14 MB Total - 486 MB. -> That's a clear evidence that application is using some internal cache storage somewhere...
I've already read many articles found on internet about how to 'very simply' recover deleted messages from the phone saying that you just need to check for subfolder "fb_temp" within the "com.facebook.orca" and WOALA - That's it!
But in fact, it's not so easy at all, because that folder always displays as empty, no matter whether I check it with windows explorer (when the phone is plugged to PC via USB) or using ADB shell.....the subfolder "fb_temp" always appears as an empty folder. Maybe it's because the phone is not yet rooted? I don't know.
Code:
hero2lte:/storage/self/primary/[COLOR="Blue"]com.facebook.katana/fb_temp[/COLOR] $ ls -la
total 8
[COLOR="DarkOrange"]drwxrwx--x 2 root sdcard_rw 4096 2019-02-02 22:51 .
drwxrwx--x 3 root sdcard_rw 4096 2018-08-08 20:03 ..[/COLOR]
-rw-rw---- 1 root sdcard_rw 0 2018-08-08 20:03 .nomedia
hero2lte:/storage/self/primary/com.facebook.katana/fb_temp $
hero2lte:/storage/self/primary/com.facebook.katana/fb_temp $
hero2lte:/storage/self/primary/com.facebook.katana/fb_temp $ cd ../../com.facebook.orca/fb_temp/
hero2lte:/storage/self/primary/[COLOR="Blue"]com.facebook.orca/fb_temp[/COLOR] $ ls -la
total 8
[COLOR="DarkOrange"]drwxrwx--x 2 root sdcard_rw 4096 2019-07-18 23:14 .
drwxrwx--x 3 root sdcard_rw 4096 2017-11-27 00:29 ..[/COLOR]
-rw-rw---- 1 root sdcard_rw 0 2017-11-27 00:29 .nomedia
hero2lte:/storage/self/primary/com.facebook.orca/fb_temp $
hero2lte:/storage/self/primary/com.facebook.orca/fb_temp $
Does anybody have any experience with similar problem ? Maybe it's more for Interpol to ask instead of here ...but ... you never know :laugh:
I've also read several articles about how to correctly root the phone in different fashions, what are the pros and cons... but, if possible, I'd prefer rather to avoid of rooting the phone at all, because it always carries a a high risk of loosing the data / because during the rooting process (for example with combination of latest TWRP and Magisk) it is necessary to wipe all the data - Obviously really I cannot afford go ahead with that option. But anyway, the rooting method does not guarantee me the results which I need to achieve (extract the deleted messages).....OR? Please feel free to correct me if I was wrong.
Any ideas how to figure this issue out?
Some technical facts:
Is phone already rooted?: No.
Phone model: Samsung Galaxy S7 Edge (SM-935F)
Android version: 8.0.0
KNOX version: 3.1 , api level 25 , TIMA 3.3.0
FB messenger version: 224.1.0.18.117
has no SD card, only phone's internal memory is used
Your any feedbacks / hints or advices will be highly appreciated! :good:
PS: any advices like: "find a new girlfriend" are not accepted! :laugh: ...
Hi Everyone,
I have been experiencing excessive battery drain from past few days, so today I decided to observe the process running on my device
Bash:
abd shell top -m 5
and found out that a process named teei_switch_thr was consuming over 20%-50% of CPU continuously and I believe this is the process causing the battery drain
Bash:
abd shell ps | grep "tee"
Code:
USER PID PPID VSIZE RSS WCHAN PC NAME
root 130 2 0 0 kthread_wo 00000000 S teei_switch_thr
root 224 1 16636 1404 tz_vfs_rea 00000000 S /vendor/bin/teei_daemon
What exactly is this process doing?
Is there a way I can kill this process without rooting my device?
Device: Moto E4 Plus
Android Version: 7.1.1
Kernel Version: 3.18.35+
Thanks in advance.
P.S I have also disabled Gboard app recently because a process called com.google.android.inputmethod.latin was also causing battery drain.