Related
Hello,
some of us who have bought a Hero locked to Orange can't seem to get it unlocked (http://forum.xda-developers.com/showthread.php?t=555424).
For those have you who have managed to successfully unlock an Hero on Orange please can you advise on your experience- did you have to do something differently? And who you used to get the code? I have used Unlock Now (www.unlock-now.com) but the code they have supplied didn't work (they refunded me).
I have never had a problem unlocking a HTC phone until now and I find it hard to believe that Orange Heros can't be unlocked.
Please help if you can.
*********************************************************
[Update 16/10/09]
I am glad this thread has been of use to people.
I thought I would add and update to the first page so people don't have to wade through the whole thread.
If you are experiencing this issue you have two choices:
1)CID unlock your Hero (http://forum.xda-developers.com/showthread.php?t=559806).
2)Use a Rebel II Sim.
OK there are three choices.
3) Use your Hero on an Orange contract for about three months then ring up Orange and ask them for a unlock code. They will charge about £20 for it and you may have to wait up to two weeks for em to send it.
C'est tout.
*********************************************************
[Update 24/10/09]
OK, after discussions and PM's on this thread I was advised to use the code I had previously bought with a different rom (when I first got my Hero tried it I was using the Orange stock rom then Modacos 2.3).
I just tested it now, took out my rebel sim put in the code and it works! I am currently using Modaco's 2.8.
Hope this helps.
I used http://hero.unlock-now.com/sim-unlock-HTC-Hero/ and the code worked for me. I did get my Hero within a few days of release. My work collegue also did the same with no problems.
What network do you use your hero on now?
hi i bought one locked to orange uk and unlocked it here
http://www.simunlock-htchero.com/buy.html
i received the code in 2 minutes and it worked, i use now Optimus in Portugal
Got my second one (for the wife) off eBay a week or two back. Poster claimed it was days old. Unlocked through htcunlock fine. Three sim seems to work better with Orange radio than the tmobile hero I purchased earlier.
Zuber
RetroFlux: I'm now on o2 after my unlock.
i'm getting the same thing with my orange locked hero, I have even tried a foreign sim as suggested. But does not seem to unlock with the correct unlock code. Is there a cable method for unlocking?
I have the same problem.
First case:
Turn on the phone with orange SIM card - everything works fine.
Turn on the phone with any other SIM card (I actually tried 3 other SIM card from 3 different providers). It asks unlock code. Enter unlock code I bought (actually any code containing 8 digits) it says "Network unlock successful." But after that it allow only emergency calls and if I try to make a call I see "Not registered in network" message. After reboot it asks unlock code again.
Second case:
If I do "restore to factory defaults" and turn it on the first time with my (no orange) SIM card, it asks unlock code I enter correct unlock code (salesman gave me one, and after that I also bought the same code in the Internet )
it hangs with phrase "Unlocking SIM card...". (Actually "turn off menu" works, I even can make an emergency call, but that is all I can get from it)
Also I noticed that in the first case there is strange line on the bottom of the screen (of the size of the notification bar).
I have tried different ROMS (original, rooted, latest, modacos) all the same. I also tried to downgrade radio firmware. I even tried all SIM cards I can obtain, the problem is obviously doesn't caused by SIM/Network incompatibility. Btw, my SIM card works OK in another HTC Hero (which was bought with my one).
I think it is problem with unlock procedure itself, not with code correctness. If wrong code entered it must say something like "wrong code", but for any 8 digit code it says "Network unlock successful". Is is the symptom! )
I do not know what to do further
I got a (UK) Orange Hero about 3 weeks ago from dial-a-phone. Unlocked it without a problem about a week later from:
http://hero.unlock-now.com/sim-unlock-HTC-Hero/
Took about 20 mins and worked 1st time. Now running with an UK O2 sim. Sorry!
As I mentioned above, while first boot with my local SIM card it hangs with "Unlocking SIM card..." message. At this time I see the following processes running.
Code:
# ps wwwwwww
PID USER VSZ STAT COMMAND
1 0 292 S /init
2 0 0 SW< [kthreadd]
3 0 0 SW< [ksoftirqd/0]
4 0 0 SW< [watchdog/0]
5 0 0 SW< [events/0]
6 0 0 SW< [khelper]
7 0 0 SW< [suspend]
8 0 0 SW< [early_suspend]
9 0 0 SW< [kblockd/0]
10 0 0 SW< [kmmcd]
11 0 0 SW< [btaddconn]
12 0 0 SW< [btdelconn]
13 0 0 SW< [kondemand/0]
14 0 0 SW< [qmi]
15 0 0 DW< [rpcrouter]
16 0 0 SW< [detection/0]
17 0 0 SW< [krpcserversd]
18 0 0 SW [pdflush]
19 0 0 SW [pdflush]
20 0 0 SW< [kswapd0]
21 0 0 SW< [aio/0]
22 0 0 SW< [panel_on/0]
23 0 0 SW< [cabc_work_q]
24 0 0 SW< [mtdblockd]
25 0 0 SW< [kadspd]
26 0 0 SW< [USB mass_storag]
27 0 0 SW< [synaptics_wq]
29 0 0 SW< [kstriped]
30 0 0 SW< [krfcommd]
31 0 0 SW< [mmcqd]
33 0 3328 S /sbin/adbd
50 1000 808 S /system/bin/servicemanager
51 0 852 S /system/bin/vold
52 0 668 S /system/bin/debuggerd
53 1001 11064 S /system/bin/rild
54 0 73504 S zygote /bin/app_process -Xzygote /system/bin --zygote --start-system-server
55 1013 30172 S /system/bin/mediaserver
57 1002 1180 S /system/bin/dbus-daemon --system --nofork
59 0 800 S /system/bin/installd
61 1008 1196 S /system/bin/akm8973
73 0 0 DW< [snd_rpc]
77 1000 173m S system_server
140 9998 159m S android.process.acore
142 1001 132m S com.android.phone
144 1000 96660 S com.htc.android.htcsetupwizard
166 10002 111m S com.google.process.gapps
179 0 0 DW< [ksdiorqd]
180 0 0 SW< [tiwlan_wifi_wq]
186 10004 96600 S com.htc.android.worldclock
193 10005 101m S com.htc.provider
207 1010 3160 S /system/bin/wpa_supplicant -Dtiwlan0 -itiwlan0 -c/data/misc/wifi/wpa_supplicant.conf
237 10031 121m S com.htc.android.htcime
244 9999 140m S com.htc.launcher
253 10016 98640 S com.htc.android.psclient
265 10017 107m S com.android.mms
285 10019 97736 S android.process.media
296 10020 106m S com.google.android.apps.maps:FriendService
307 10022 99016 S com.esmertec.android.jbed
322 10036 97.6m S com.google.android.partnersetup
332 10042 100m S com.htc.calendar
346 1000 100m S com.android.settings
356 10029 98612 S com.htc.android.footprints
366 10013 98012 S com.android.setupwizard
430 0 740 S /system/bin/sh -
468 0 2072 R ps wwwwwww
Im having the same issue, I got a new HTC Hero on Orange today, and it wont unlock. I used Unlock-now, so I have sent them a message asking for my money back, will that suffice. Has anyone been able to get there Orange UK, branded and locked phones unlocked.
nintendolinky, what is your ROM version ? There may be a possibility you have the latest firmware build... maybe...
i'm in the same boat! bought the code but no joy. it say's unlocked but could not register my voda sim. Anyone?
I tried to contact Orange today to buy an unlock code from them directly, after been passed about I eventually got through to someone bureaucratic wench who was completely unhelpful and I ended up telling them to F off and hung up. Kind of shot myself in the foot there.
I know this doesn't help our situation but I am still looking into it.
joemax said:
nintendolinky, what is your ROM version ? There may be a possibility you have the latest firmware build... maybe...
Click to expand...
Click to collapse
So are you saying there is an issue with the new firmware? When you say firmware do you mean ROM? As I have already flashed Modacos latest ROM and my Three/Vodafone/O2 sim still won't work.
I don't have my Hero with me at the moment but will post back my firmware number later, if other people (who are having the same issue) can post theirs maybe we can find a common firmware at fault.
nintendolinky said:
I used Unlock-now, so I have sent them a message asking for my money back, will that suffice.
Click to expand...
Click to collapse
I used Unlock-Now, they did refund me after your usual basic diagnostics.
joemax said:
nintendolinky, what is your ROM version ? There may be a possibility you have the latest firmware build... maybe...
Click to expand...
Click to collapse
Ok, here are my firmware details:
Firmware version: 1.5
Baseband Version: 63.18.55.06EU_6.35.06.18
Kernel Version: 2.6.27-8dd6deee [email protected]
Build Number: 2.73.405.5 146733 CL#61267 MCR2.2c release keys
Software Version: 1.0.0.A6288
Someone out there must be able to help fix this, pros/cooks/anyone can you shed anylight on this?
I've tried oldest/newes/custom ROMs, it looks like unlocking procedure doesn't depend on ROM at all.
is there a way to unlock this via cable? what about flashing the rom?
my build number is
Build Number: 1.76.61.3 whats the difference with this and Build Number: 2.73.405.5?
Here is my info:
Firmware version: 1.5
Baseband Version: 63.18.55.06EU_6.35.06.18
Kernel Version: 2.6.27-8dd6deee [email protected]
Build Number: 2.73.405.5 146733 CL#61267 MCR2.2e release keys
Software Version: 1.0.0.A6288
My build number is different, to the one listed here.
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...
Hi, ive recently bought a phone I9301 (the one with 1.5gb RAM and 4.4.2 kitkat from 12th August)
but the main problem is that the phone happens to restart itself
it does it very often when (i think) something wakes it up from the Deep Sleep (after about 10minutes of doing nothing) like:
- unlocking the phone
- setting the alarm
- receiving a call
sometimes it restarts automatically when i'm not using it
ive checked the android there are no Kernel panic logs left, no crash logs at all
tried to crash the phone while having it connected to the Catlog via USB, but it doesnt go Deep Sleep while charging (so the alarm and calls worked) but managed to crash it once
thats what the CatLog left me with
Code:
10-04 13:31:30.145: E/SMD(225): DCD ON
10-04 13:31:30.345: E/adsprpc(254): vendor/qcom/proprietary/adsprpc/src/listener_android.c:124:listener protocol failure -1
10-04 13:31:30.355: E/adsprpc(254): vendor/qcom/proprietary/adsprpc/src/listener_android.c:128::error: -1: 0 == (nErr = __QAIC_HEADER(adsp_listener_next_invoke)( ctx, nErr, 0, 0, &ctx, &handle, &sc, bufs->inbufs, inBufsAllocated, bufs->inbufLenReqs, MAX_BUFS, bufs->outbufLenReqs, MAX_BUFS))
10-04 13:31:30.365: E/adsprpc(254): vendor/qcom/proprietary/adsprpc/src/listener_android.c:187:listener thread exiting with code -1
10-04 13:31:30.365: E/adsprpc(254): vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:215::error: -1: 0 == (nErr = remotectl_open(name, (int*)ph, dlerrstr, sizeof(dlerrstr), &dlerr))
10-04 13:31:30.375: E/adsprpc(254): vendor/qcom/proprietary/adsprpc/src/listener_android.c:189:listener thread failed to cleanly shutdown. This is ok durring process exit.
10-04 13:31:30.375: E/adsprpc(254): vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:215::error: -1: 0 == (nErr = remotectl_open(name, (int*)ph, dlerrstr, sizeof(dlerrstr), &dlerr))
10-04 13:31:30.375: E/adsprpc(254): vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:215::error: -1: 0 == (nErr = remotectl_open(name, (int*)ph, dlerrstr, sizeof(dlerrstr), &dlerr))
10-04 13:31:30.375: E/adsprpc(254): vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:215::error: -1: 0 == (nErr = remotectl_open(name, (int*)ph, dlerrstr, sizeof(dlerrstr), &dlerr))
10-04 13:31:30.385: E/adsprpc(254): vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:215::error: -1: 0 == (nErr = remotectl_open(name, (int*)ph, dlerrstr, sizeof(dlerrstr), &dlerr))
: E/(): Device disconnected
(look at the bottom), i guess nothing special, however didnt find time to check what the remotectl_open function does in detail
its been to the Warranty 2 times, first time they 're' flashed the firmware, but the problem remained, tried disabling tons of built-in apps, hard reset, nothing works
second time they said theres nothing to do and all i have to do is just wait for the release of firmware update,
any ideas whats wrong with the phone?
I'm running stockfied ROM v.1.3.6d. Searching the net brought me no answer to my question to what are the differences regarding the sensor use and data fields between the 8 activities offered on the Pace (activitiy no should be consistent to internal database). This is what I got so fare, mistakes are possible since I'm owning the watch only a week now. If anyone has more infos, please share them:
No. English German GPS Baro. Heartr. Steps Pace Lap-Alarm
1 running Laufen 1 1 0 1 1 1
2 walking Gehen 1 1 0 0 0
3 trail run Trailauf/Wandern 1 1 1 0 0 0
4 treadmill Laufband 0 0 0 1 1
5 bike Fahrrad 1 1 0 0 0
6 indoor bike Trimmrad 0 0 1 1 0
7 eliptical Stepper 0 0 1 1 0
8 climbing Klettern 1 1 0 0 0
Edit: Above should be a table but I wasn't able to produce one here.
{
"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"
}
A custom kernel for (most) V20 variants
SwanKernel is an android kernel based on the latest Lineage OS 18.1 sources for the LG MSM8996 phones, aiming to bring those features and updates and improve them with some extra tuning, fixing and external features tailored specifically for the LG V20's performance characteristics and feature set, while trying to maximize the battery life and responsiveness of the device at the same time.
This kernel is based on Linux 3.18.140, and has become EOL with the last commit, as i don't think there's anything else that can be optimized for the V20 on this source anymore.
Which phone variants/models does this kernel support?
The kernel currently supports the following variants:
H910/H915
H918
H990
LS997
US996
VS995
Support for other special variants like the US996Santa might come at a later date if needed.
What does this kernel intend to achieve?
The main goal here is to have a kernel that not only has extra features and improvements, but is also clean and concise, having only features that are truly needed from a kernel that will run alongside a Android 11-based ROM. One example of that is Kcal display control, a feature that is unnecessary here since most, if not all Android 11 ROMs have LiveDisplay for that exact same purpose and without the need to root. This helps the kernel have a smaller file size and lower processing overhead, as well as promote better maintainability.
This kernel does have a battery life bias, but will still scale up to maximum performance when needed. No Overclocking is done for now.
Does it have any features over stock?
Yes, a lot. The kernel is divided into two variants, here are the features both variants have over stock:
AdrenoBoost for improved GPU performance.
GPU and CPU/Cache Undervolt for better power efficiency on load.
CPU governors tuned for better battery life and thermal stability without impacting performance all that much.
Almost no unnecessary debug flags on the kernel for better kernel performance.
Westwood TCP Congestion Algorithm set as default in order to have better network performance and consistency.
AutoSMP CPU Hotplug to shutdown the big cores when their stronger performance isn't needed, slightly improving battery life on light loads and idle.
Disabled CPU Boost when a finger is detected on screen, preventing unnecessary frequency boosts when no meaningful action is done other than tapping on screen and slightly scrolling around. We have Schedutil to keep it smooth anyways.
USB Fast Charge.
Multiple cherry-picks from different msm8996 sources with fixes and improvements to the kernel.
Configurable wakelock blocker (boeffla) for roms that have some "unneeded" wakelocks enabled by default and/or users that know which wakelocks can be blocked for better battery life.
Anxiety IO Scheduler enabled by default, offering a read bias and lower latency in IO operations.
Kernel updated to Linux 3.18.140 with some extra patches from Googlesource.
Wireguard support, improving VPN performance.
Cryptographic functions optimizations, slightly improving the phone's performance when calculating hashes and so on.
The Extreme variant has some extra features over the Stable one, those being:
Stronger Undervolts (i'm talking about borderline unstable undervolts here, so i really recommend that you flash the Stable one first).
CPU Voltage Control if you need to setup a custom undervolt to keep it more stable and have no need to compile the kernel from source just to change the values... and that's assuming your phone even boots with this variant of the kernel.
Disabled Battery BCL which eliminates the power throttling caused by the battery, just be careful when running demanding tasks while having almost no battery left.
Are there any bugs?
Right now, there's the dreaded Infrared Blaster, and it... kinda works? The IR is able to send the very first command i give to my LG TV without any problems after every reboot, but refuses to send anything else after that first command. The IR Blaster's light still works all the time though despite having some big delays between on/off states.
Download & Installation
The folders containing each kernel variant can be found here:
Stable Version
Extreme Version
To install the kernel, it's the standard procedure:
Download the kernel you want for your device
Place it into the phone
Boot into recovery, select it and then flash
Wipe Dalvik Cache (optional, you only need to wipe it if you face random Force Closes, but it is a good practice anyway)
Reboot.
Open any app that can check the device info and look for "kernel", where it will show "... 3.18.xxx-Swan" if it installed correctly. I personally use SmartPack for that, but it requires root.
Enjoy the experience!
Performance and Battery metrics
Spoiler: outdated (done in v1.00), performance has improved since then:
And now to the kernel's real world performance. But before delving in, keep in mind that my refurbished H910 is apparently a Snapdragon 821 prototype, that's why you will see higher than normal performance and clock values on cpu matters even with the LITTLE cores underclocked to 1785MHz instead of 2188MHz, the snapdragon 820 ones should not have any underclock applied and will reach the max of 1593MHz on them. I also took the liberty of testing those on the Extreme variant as BCL often interferes with the performance results and the extra undervolt doesn't increase performance in any substantial way, 5-7% at most on Geekbench.
Battery life:
Screen SOT test (Youtube looping through a massive playlist of songs with some scrolling to change between them):
Not very impressive, until you consider the battery currently powering it:
CPU/GPU Performance:
CPU performance according to Geekbench 5.4.1 (there is some minor variance of about 15-21 points in multithread):
CPU sustained performance on CPU Throttling Test(running it for 15+ minutes barely changes the curve, as it stabilizes at around 80-82 Celsius, i suppose a Snap 820 will fare better here due to the lower clocks):
GPU general performance on GFXBench 5:
No copper shim replacement or thermal pad change was made, the phone's internal structure is still the same from when i bought it.
Storage Performance:
General IO performance in Androbench 5(Not very accurate, but welp, if anyone has a more in-depth one feel free to share):
And there we go, everything i could benchmark so far. This will not be the best kernel on every front so the stock kernel on Lineage 18.1, Lighthouse's kernel or mk2000 might suit you better depending on your needs.
Changelog
Spoiler: Changes done in recent versions:
*********** Swankernel V1.09+ [Maintenance release] ***********
CPU/Cache/GPU Voltages have basically reached the optimum point on both stable and extreme.
Some performance commits were cherry-picked from newer kernels for other devices
Dynamic FSync was disabled since it could cause data loss on some edge cases involving reboots.
Improved some string routines and memory access functions, about 4% or so improvement on geekbench.
*********** Swankernel V1.09 [Last 3.18 version, i think] ***********
Minor performance and power-saving optimizations throughout the kernel
CPU M4M cache undervolting (not really a big difference, but nice to have anyway).
A few cherry-picked fixes for the 3.18 msm8996 kernel tree.
Crypto function optimizations and HW acceleration for CRC32 Enabled.
Not actually a kernel change but: Can now be flashed on android versions lower than 11.
*********** Swankernel V1.08 ***********
Small performance optimizations related to the voltage curves, especially in the GPU.
PC USB Charging has been fixed and the phone can now be charged over it again.
*********** Swankernel V1.06 ***********
Upstreamed kernel to 3.18.140 + some extra patches, with more coming later.
Added Wireguard support for better VPN performance compared to IPSec.
Smaller fixes to the kernel zip files, improving compatibility with some models.
Minor performance optimizations, shouldn't be noticeable to the end user.
Now stable enough (at least the Stable version is) to be used as a daily driver.
*********** Swankernel V1.00 ***********Initial release. Has the features from 1 to 12 on both versions, and from 1 to 3 on the Extreme version.
Closing notes
With V1.09, the kernel can now be flashed on basically any android version and should work out-of-the-box, although i didn't test it on stock roms at all and there are no reports of it working there, so it might not work on them.
From what i could gather during the multiple Pre-Beta tests, the battery life improved considerably over the kernel shipped by default with Lighthouse V20 and even more when compared to Lineage's stock kernel.
If you have any suggestion or idea that can possibly improve the kernel, do not hesitate to share, i will try to implement it when my time allows it. If there are any problems that only happen on this kernel, submit a log and i'll try to look at it.
The kernel's source code can be found here.
And last but not least, a special thanks for those that helped me even if indirectly:
@xxseva44
@npjohnson
@askermk2000
@lybxlpsv
@flar2
@osm0sis
And many, many others
The ir is most likely consumer ir related so, we'll have to tweak it until it starts working
xxseva44 said:
The ir is most likely consumer ir related so, we'll have to tweak it until it starts working
Click to expand...
Click to collapse
I was discussing the same thing with @askermk2000 a while ago and that seems to be the case, as not even gamma kernel had a working IR on the branch he tested, and neither the IR files or the git log of it shows any relevant difference on the IR when compared to Lineage's sources. I will keep the disclaimer about it for now because it makes things clearer as there is some confusion about the IR being a kernel problem, so the less convoluted it is to the user for the time being, the better.
Edit: Also, if you need any logs about the infrared while testing it, i can help (i even have some older ones describing the behaviour). Just hit me up when needed since my device will be mostly used as a development phone for the time being.
AShiningRay said:
I was discussing the same thing with @askermk2000 a while ago and that seems to be the case, as not even gamma kernel had a working IR on the branch he tested, and neither the IR files or the git log of it shows any relevant difference on the IR when compared to Lineage's sources. I will keep the disclaimer about it for now because it makes things clearer as there is some confusion about the IR being a kernel problem, so the less convoluted it is to the user for the time being, the better.
Edit: Also, if you need any logs about the infrared while testing it, i can help (i even have some older ones describing the behaviour). Just hit me up when needed since my device will be mostly used as a development phone for the time being.
Click to expand...
Click to collapse
It's more likely an issue with the implementation of the ir drivers not playing well with consumerIR or vise versa. Atm ir only works on the older versions of gamma as they weren't upstreamed like los 18
Hello when I try to flash Swan-H918-Stable.zip on an h918 I get "Unsupported device. Aborting..."
Aethera said:
Hello when I try to flash Swan-H918-Stable.zip on an h918 I get "Unsupported device. Aborting..."
Click to expand...
Click to collapse
Huh... that's strange. I must have messed something up during the anykernel zipping procedure on that model. I'm almost pushing an update to the kernel, so i'll be back in a while with a fix for that.
Edit: Yeah, it was something in the script file, i forgot to change the H910 to H918 on that specific variant flashable. Sorry for that.
I just pushed the file with the fixed script for all the models i checked. If you could test that, i would appreciate it.
AShiningRay said:
Huh... that's strange. I must have messed something up during the anykernel zipping procedure on that model. I'm almost pushing an update to the kernel, so i'll be back in a while with a fix for that.
Edit: Yeah, it was something in the script file, i forgot to change the H910 to H918 on that specific variant flashable. Sorry for that.
I just pushed the file with the fixed script for all the models i checked. If you could test that, i would appreciate it.
Click to expand...
Click to collapse
Just successfully flashed the new Swan-H918-Stable.zip thank you!
Code:
$ uname -a
Linux localhost 3.18.113-Swan-g24ffa95cf1b3-dirty #1 SMP PREEMPT Wed Oct 20 00:18:37 -03 2021 aarch64
Aethera said:
Just successfully flashed the new Swan-H918-Stable.zip thank you!
Click to expand...
Click to collapse
No worries, glad to help.
Here is some output from 'logcat *:E' in case it is of interest:
10-31 16:19:38.753 5926 5926 E ActivityThread: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
10-31 16:19:40.586 905 937 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-31 16:19:41.778 959 1031 E QC-time-services: Lib:time_genoff_operation: Connection failed !!
10-31 16:19:41.783 959 1031 E QC-time-services: Lib:time_genoff_operation: Connection failed !!
10-31 16:19:42.002 10005 10005 E receiver.modul: Not starting debugger since process cannot load the jdwp agent.
10-31 16:19:42.143 455 455 E lowmemorykiller: Error writing /proc/7941/oom_score_adj; errno=22
10-31 16:19:43.218 10025 10025 E hbox:interacto: Not starting debugger since process cannot load the jdwp agent.
10-31 16:19:44.391 455 455 E lowmemorykiller: Error writing /proc/9412/oom_score_adj; errno=22
10-31 16:19:44.658 1144 1217 E KernelCpuSpeedReader: Failed to read cpu-freq: /sys/devices/system/cpu/cpu2/cpufreq/stats/time_in_state: open failed: ENOENT (No such file or directory)
10-31 16:19:44.675 1144 1214 E libprocessgroup: Error encountered killing process cgroup uid 99005 pid 9572: Permission denied
10-31 16:19:46.683 1144 1550 E LightsService: Light requested not available on this device. 2
10-31 16:19:47.629 0 0 E variable_rate_pll_clk_enable_hwfsm: PLL pwrcl_pll didn't lock after enabling it!
10-31 16:19:51.008 1144 4213 E WifiService: Permission violation - getScanResults not allowed for uid=10086, packageName=com.google.android.gms, reason=java.lang.SecurityException: Location mode is disabled for the device
10-31 16:19:56.216 0 0 E vote : name[BATTCHG_SUSPEND], client[BATTCHG_UNKNOWN_BATTERY_EN_VOTER,0], enabled[0], val[0]
10-31 16:19:56.216 0 0 E SMBCHG : smbchg_config_chg_battery_type: BATTERY FULL NAME : LGE_BL44E1F_LGC_3200mAh
10-31 16:20:09.541 0 0 E : LGE charging scenario : state 0 -> 0(0-0), temp=292, volt=4404, fl_volt=4400 BTM=0, charger=1, cur_set=1000/0, chg_cur = -481
10-31 16:20:09.541 0 0 E [LGE-CC] lge_monitor_batt_temp_work: (work_queue)->(work_queue)
10-31 16:20:09.541 0 0 E vote : name[BATT_FCC], client[LGE_POWER_CLASS_FCC_VOTER,1], enabled[1], val[1000]
10-31 16:20:09.541 0 0 E vote : name[BATTCHG_SUSPEND], client[LGCC_EN_VOTER,1], enabled[0], val[0]
10-31 16:20:09.541 0 0 E vote : name[BATTCHG_SUSPEND], client[STORE_MODE_EN_VOTER,2], enabled[0], val[0]
10-31 16:20:09.541 0 0 E vote : name[USB_SUSPEND], client[STORE_MODE_USB_EN_VOTER,2], enabled[0], val[0]
10-31 16:20:29.221 0 0 E variable_rate_pll_clk_enable_hwfsm: PLL pwrcl_pll didn't lock after enabling it!
Here is some more:
10-31 16:21:38.622 10126 10148 E libEGL : Driver indicates EGL 1.5 support, but does not have a critical API
10-31 16:21:38.739 905 937 E ANDR-PERF-RESOURCEQS: Failed to reset optimization [2, 1]
10-31 16:21:38.740 905 937 E ANDR-PERF-RESOURCEQS: Failed to reset optimization [2, 1]
10-31 16:21:43.557 905 937 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-31 16:21:43.558 905 937 E ANDR-PERF-RESOURCEQS: Failed to apply optimization [2, 2, 0]
10-31 16:22:09.540 0 0 E : LGE charging scenario : state 0 -> 0(0-0), temp=292, volt=4408, fl_volt=4400 BTM=0, charger=1, cur_set=1000/0, chg_cur = -358
10-31 16:22:09.541 0 0 E [LGE-CC] lge_monitor_batt_temp_work: (work_queue)->(work_queue)
10-31 16:22:22.518 0 0 E vote : name[BATTCHG_SUSPEND], client[BATTCHG_UNKNOWN_BATTERY_EN_VOTER,0], enabled[0], val[0]
10-31 16:22:22.518 0 0 E SMBCHG : smbchg_config_chg_battery_type: BATTERY FULL NAME : LGE_BL44E1F_LGC_3200mAh
10-31 16:22:37.783 0 0 E rmt_storage: INFO:rmt_storage_rw_iovec_cb: Write iovec request received for /boot/modem_fs1
10-31 16:22:37.783 0 0 E rmt_storage: INFO:rmt_storage_client_thread: Calling Write [offset=0, size=2097152]for /boot/modem_fs1!
10-31 16:22:37.814 0 0 E rmt_storage: INFO:rmt_storage_client_thread: Done Write (bytes = 2097152) for /boot/modem_fs1!
10-31 16:23:00.530 0 0 E variable_rate_pll_clk_enable_hwfsm: PLL pwrcl_pll didn't lock after enabling it!
10-31 16:23:09.540 0 0 E : LGE charging scenario : state 0 -> 0(0-0), temp=292, volt=4408, fl_volt=4400 BTM=0, charger=1, cur_set=1000/0, chg_cur = -324
10-31 16:23:09.540 0 0 E [LGE-CC] lge_monitor_batt_temp_work: (work_queue)->(work_queue)
Aethera said:
Here is some output from 'logcat *:E' in case it is of interest:
10-31 16:19:38.753 5926 5926 E ActivityThread: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
10-31 16:19:40.586 905 937 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-31 16:19:41.778 959 1031 E QC-time-services: Lib:time_genoff_operation: Connection failed !!
10-31 16:19:41.783 959 1031 E QC-time-services: Lib:time_genoff_operation: Connection failed !!
10-31 16:19:42.002 10005 10005 E receiver.modul: Not starting debugger since process cannot load the jdwp agent.
10-31 16:19:42.143 455 455 E lowmemorykiller: Error writing /proc/7941/oom_score_adj; errno=22
10-31 16:19:43.218 10025 10025 E hbox:interacto: Not starting debugger since process cannot load the jdwp agent.
10-31 16:19:44.391 455 455 E lowmemorykiller: Error writing /proc/9412/oom_score_adj; errno=22
10-31 16:19:44.658 1144 1217 E KernelCpuSpeedReader: Failed to read cpu-freq: /sys/devices/system/cpu/cpu2/cpufreq/stats/time_in_state: open failed: ENOENT (No such file or directory)
10-31 16:19:44.675 1144 1214 E libprocessgroup: Error encountered killing process cgroup uid 99005 pid 9572: Permission denied
10-31 16:19:46.683 1144 1550 E LightsService: Light requested not available on this device. 2
10-31 16:19:47.629 0 0 E variable_rate_pll_clk_enable_hwfsm: PLL pwrcl_pll didn't lock after enabling it!
10-31 16:19:51.008 1144 4213 E WifiService: Permission violation - getScanResults not allowed for uid=10086, packageName=com.google.android.gms, reason=java.lang.SecurityException: Location mode is disabled for the device
10-31 16:19:56.216 0 0 E vote : name[BATTCHG_SUSPEND], client[BATTCHG_UNKNOWN_BATTERY_EN_VOTER,0], enabled[0], val[0]
10-31 16:19:56.216 0 0 E SMBCHG : smbchg_config_chg_battery_type: BATTERY FULL NAME : LGE_BL44E1F_LGC_3200mAh
10-31 16:20:09.541 0 0 E : LGE charging scenario : state 0 -> 0(0-0), temp=292, volt=4404, fl_volt=4400 BTM=0, charger=1, cur_set=1000/0, chg_cur = -481
10-31 16:20:09.541 0 0 E [LGE-CC] lge_monitor_batt_temp_work: (work_queue)->(work_queue)
10-31 16:20:09.541 0 0 E vote : name[BATT_FCC], client[LGE_POWER_CLASS_FCC_VOTER,1], enabled[1], val[1000]
10-31 16:20:09.541 0 0 E vote : name[BATTCHG_SUSPEND], client[LGCC_EN_VOTER,1], enabled[0], val[0]
10-31 16:20:09.541 0 0 E vote : name[BATTCHG_SUSPEND], client[STORE_MODE_EN_VOTER,2], enabled[0], val[0]
10-31 16:20:09.541 0 0 E vote : name[USB_SUSPEND], client[STORE_MODE_USB_EN_VOTER,2], enabled[0], val[0]
10-31 16:20:29.221 0 0 E variable_rate_pll_clk_enable_hwfsm: PLL pwrcl_pll didn't lock after enabling it!
Here is some more:
10-31 16:21:38.622 10126 10148 E libEGL : Driver indicates EGL 1.5 support, but does not have a critical API
10-31 16:21:38.739 905 937 E ANDR-PERF-RESOURCEQS: Failed to reset optimization [2, 1]
10-31 16:21:38.740 905 937 E ANDR-PERF-RESOURCEQS: Failed to reset optimization [2, 1]
10-31 16:21:43.557 905 937 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-31 16:21:43.558 905 937 E ANDR-PERF-RESOURCEQS: Failed to apply optimization [2, 2, 0]
10-31 16:22:09.540 0 0 E : LGE charging scenario : state 0 -> 0(0-0), temp=292, volt=4408, fl_volt=4400 BTM=0, charger=1, cur_set=1000/0, chg_cur = -358
10-31 16:22:09.541 0 0 E [LGE-CC] lge_monitor_batt_temp_work: (work_queue)->(work_queue)
10-31 16:22:22.518 0 0 E vote : name[BATTCHG_SUSPEND], client[BATTCHG_UNKNOWN_BATTERY_EN_VOTER,0], enabled[0], val[0]
10-31 16:22:22.518 0 0 E SMBCHG : smbchg_config_chg_battery_type: BATTERY FULL NAME : LGE_BL44E1F_LGC_3200mAh
10-31 16:22:37.783 0 0 E rmt_storage: INFO:rmt_storage_rw_iovec_cb: Write iovec request received for /boot/modem_fs1
10-31 16:22:37.783 0 0 E rmt_storage: INFO:rmt_storage_client_thread: Calling Write [offset=0, size=2097152]for /boot/modem_fs1!
10-31 16:22:37.814 0 0 E rmt_storage: INFO:rmt_storage_client_thread: Done Write (bytes = 2097152) for /boot/modem_fs1!
10-31 16:23:00.530 0 0 E variable_rate_pll_clk_enable_hwfsm: PLL pwrcl_pll didn't lock after enabling it!
10-31 16:23:09.540 0 0 E : LGE charging scenario : state 0 -> 0(0-0), temp=292, volt=4408, fl_volt=4400 BTM=0, charger=1, cur_set=1000/0, chg_cur = -324
10-31 16:23:09.540 0 0 E [LGE-CC] lge_monitor_batt_temp_work: (work_queue)->(work_queue)
Click to expand...
Click to collapse
Some of those errors are due to the massive amount of debug flags i disabled in the kernel (it still tries to load many of them up for some reason). Are you facing any bugs on the device so far? My H910 also prints many "errors" similar to these but it works just as fine as when it used Lineage's stock kernel, but i didn't test other variants so i don't know if this kernel works fine on them as well.
AShiningRay said:
Some of those errors are due to the massive amount of debug flags i disabled in the kernel (it still tries to load many of them up for some reason). Are you facing any bugs on the device so far? My H910 also prints many "errors" similar to these but it works just as fine as when it used Lineage's stock kernel, but i didn't test other variants so i don't know if this kernel works fine on them as well.
Click to expand...
Click to collapse
One thing I'm noticing is that the adb USB connection keeps breaking. I run 'adb shell' and it connects then after a few seconds disconnects. It never did this before.
EDIT: Now it stopped doing it. For a while it kept disconnecting but now it is staying connected.
Aethera said:
One thing I'm noticing is that the adb USB connection keeps breaking.
Click to expand...
Click to collapse
That's weird, some time ago when i started taking logs to debug the IR i managed keep running the adb logcat for quite a while with no problems whatsoever. Is there a certain amount of time that it takes to happen?
Edit: Oh, ok then. Might have been some random issue with adb's connection. If any other problem arises, do tell.
Unfortunately the phone is still crashing at random intervals (was happening before using this kernel).
10-31 19:17:56.642 0 0 E : Fatal error on the modem.
10-31 19:17:56.642 0 0 E : modem subsystem failure reason: sleep_target.c:305:.
10-31 19:17:56.647 0 0 E M-Notify: General: 8
Aethera said:
Unfortunately the phone is still crashing at random intervals (was happening before using this kernel).
10-31 19:17:56.642 0 0 E : Fatal error on the modem.
10-31 19:17:56.642 0 0 E : modem subsystem failure reason: sleep_target.c:305:.
10-31 19:17:56.647 0 0 E M-Notify: General: 8
Click to expand...
Click to collapse
I see.. well, i tried searching this sleep_target.c that seems to be related in some manner to the problem in the kernel directory but there is no file with such a name. It could be something ROM-related, but i can't rule that out yet. Are there any other logs with more info about it?
AShiningRay said:
I see.. well, i tried searching this sleep_target.c that seems to be related in some manner to the problem in the kernel directory but there is no file with such a name. It could be something ROM-related, but i can't rule that out yet. Are there any other logs with more info about it?
Click to expand...
Click to collapse
I will try to do some various types of log filtering over the next day or so to see if I can get more information.
AShiningRay said:
I see.. well, i tried searching this sleep_target.c that seems to be related in some manner to the problem in the kernel directory but there is no file with such a name. It could be something ROM-related, but i can't rule that out yet. Are there any other logs with more info about it?
Click to expand...
Click to collapse
Looks like most if not all info about sleep_target.c is in Chinese. For example:
https://cloud-tencent-com.translate...auto&_x_tr_tl=en&_x_tr_hl=en-US&_x_tr_pto=nui
This one appears to have more detail: https://www-cnblogs-com.translate.g...auto&_x_tr_tl=en&_x_tr_hl=en-US&_x_tr_pto=nui
Aethera said:
Looks like most if not all info about sleep_target.c is in Chinese. For example:
https://cloud-tencent-com.translate...auto&_x_tr_tl=en&_x_tr_hl=en-US&_x_tr_pto=nui
This one appears to have more detail: https://www-cnblogs-com.translate.g...auto&_x_tr_tl=en&_x_tr_hl=en-US&_x_tr_pto=nui
Click to expand...
Click to collapse
Yeah, and the problem is... none of the files the article talks about are present in the kernel's source. tlmm_bsp for example also returns no results here. The fact that you log referenced a specific line from the file means it actually is present somewhere, but i'm not able to ascertain where exactly it is. I'll have to look at it in more details later.
AShiningRay said:
Yeah, and the problem is... none of the files the article talks about are present in the kernel's source. tlmm_bsp for example also returns no results here. The fact that you log referenced a specific line from the file means it actually is present somewhere, but i'm not able to ascertain where exactly it is. I'll have to look at it in more details later.
Click to expand...
Click to collapse
It is related to the Qualcomm MSM8996 system-on-chip. Perhaps it is embedded in the firmware. It appears there's some way to enable a debug mode for the modem and access various flags and voltage levels. This would explain why the error seems to be power-related. The device is trying to throttle the voltage to a "bottom current" which is a minimal current when the device is sleeping and for whatever reason it's crashing.
FYI here is a tool which can extract a MSM8996 modem image.
Aethera said:
Unfortunately the phone is still crashing at random intervals (was happening before using this kernel).
10-31 19:17:56.642 0 0 E : Fatal error on the modem.
10-31 19:17:56.642 0 0 E : modem subsystem failure reason: sleep_target.c:305:.
10-31 19:17:56.647 0 0 E M-Notify: General: 8
Click to expand...
Click to collapse
What variant? And did you ever crossflash?
Aethera said:
It is related to the Qualcomm MSM8996 system-on-chip. Perhaps it is embedded in the firmware. It appears there's some way to enable a debug mode for the modem and access various flags and voltage levels. This would explain why the error seems to be power-related. The device is trying to throttle the voltage to a "bottom current" which is a minimal current when the device is sleeping and for whatever reason it's crashing.
FYI here is a tool which can extract a MSM8996 modem image.
Click to expand...
Click to collapse
Ok, so it means that those files might actually be located inside the modem partition? I can see how a improper voltage can lead to kernel crashes (Undervolting the SoC's Kryo cores themselves too hard does the same thing, crashing the phone into either a black screen or a green one with some tracing info about the files that caused the problem), but how do we even go about testing if the modem is the one causing the problem? I'm not familiar with the modem images and structures at all so i doubt i would be able to fix those things, especially the voltages since we probably have no voltage table to determine which voltages are acceptable, too high, or too low.