This is a question about the CSC when upgrading the firmware. Basically I have a problem with the P1000XWJMI firmware. The problem is simple, after upgrading from my stock SGT firmware P1000XXJK2, I have a wake lock problem that prevents the device from going to sleep.
Code:
[email protected]:~/sgtfirmware/P1000XWJMI$ adb shell dumpsys power
...
mLocks.size=2:
FULL_WAKE_LOCK 'CscReceiver'ACQUIRE_CAUSES_WAKEUP activated (minState=7, uid=1001, pid=2509)
FULL_WAKE_LOCK 'CscReceiver'ACQUIRE_CAUSES_WAKEUP activated (minState=7, uid=1001, pid=2509)
These two wake locks prevent the screen from turning off and the device from going to sleep. It has something to do with the CscReceiver service so I suspect it is CSC related. Basically the service is invoked three times during boot, but only the first time does it release the wake locks. I can see this in the logcat output.
I've tried keeping my old CSC and MODEM from JK2 and only flashing the zImage, factoryfs.rfs and param.lfs from JMI using Heimdall but after rebooting the CSC and MODEM are gone and the problem is back.
Does anyone else have this problem? You can check it easily using the 'adb shell dumpsys power' command after restarting the device.
The wake locks usually go away after a while, but it can be 30 minutes later and there will be a message about a wake lock timeout and serious failure the log. It's annoying because it drains the battery for a long time after you turn off the screen.
Which firmware would be recommended for central Europe (NL), preferably newer that JK2 (which has a horribly slow browser) and one with a working CSC?
I am about to give up with JMI
Just an update if other people from Europe have the same problem with P1000XWJMI. Just use P1000XWJMG instead. It does not have the problem. Flash it with Heimdall, of course without the two boot loaders. This firmware correctly installs the CSC which fixes the wake lock problem.
Now.. To EXT4 and beyond!
EDIT: Ugh! The problem with P1000XWJMG is that the /system partition is 100% full. Does anyone know what i can remove?
Related
Hi guys,
Well I've flashed my Tab up to JM6, but now I have a rather odd issue.
when I go to *#1234# it shows like this....
PDA: Blank
Phone *****JM6
Modem: Blank
I've tried reflashing back to JJ4, and everytime it is failing on boot.bin. This is with both the P1_Blank and P1_EU PIT files.....
I'm now a little lost on what has happened. The device is working fine (From what I can see) on JM6, but the fact those two options are blank and I seem unable to revert to JJ4 are concerning me.
If anyone else has flashed to JM6, does yours display the same?
Have you tried clearing caches and erasing data to factory default before flashing ?
pda p1000xxjm6
phone p1000xxjm6
csc p1000xxjm6
I'm pretty sure that this is fine. I get the same (PDA and CSC blank) on JM6 and everything works fine as far as I can tell.
My guess is that the Samsung-specific *#1234# menu is just there to keep track of carrier-specific customizations (CSC). On the internal flash storage, there is no such distinction; rather, the CSC overwrite part of the base system. In particular, you get a 100% functional device if you don't apply the CSC.
This was my first tab which had a fault and was replaced. Now working fine.
Old post, forgot to update it.
Sent from my GT-P1000 using XDA App
How did you fix this problem? I got the same? I have no way of replacing my tab since there is no service center near by.
HELP
Heyy guys. I am facing a lil problem at the moment.
After upgrading to 4.2.2 (Downloaded the Malaysia firmware from Sammobile and flashed it with Odin),
My 'remembered' WiFi has been cleared and it has been my fourth time.
My lock screen seems to have a 1-second lag as well. Sometimes, the lock screen is a little messed up - after a longer call (say 2 mins +), it shows my lock screen but couldn't unlock it.
Could it possibly be my CSC and such?
Any idea how to solve this issue?
Attached are my phone details.
Thanks!
Hello everyone,
Here's my situation. Today i updated my phone had a chinese 5.0.1 android and flashed UAE 5.0.1 (using the adonis pit since i believe i had used another for the chinese). Started the phone everything ok. As soon as the screen went of (screen timed out) i couldnt get it to work using the power and main button im not sure if theres is just long delay or i need to click the buttons multiple time or its the fault of the screen not reacting fast enough. All i know is that when i start the phone keys work good i can start in download or cwm with no problem.
Please help. Its very frustrating. Any advise is welcomed. Please give me even the most basic advices cause i got no idea what to do.
FIXED ! it fixed after i flashed ap, bl, cp and csc. idk why...
DNS resolving fails when switching between Wifi & data connections (i9505 LineageOS)
I am having a long standing issue with my Galaxy S4. First noticed on CyanogenMod 12 but persists after a wipe and fresh install of LineageOS 14.1 and baseband update (I forget which baseband I was on with CyanogenMod)
My phone will frequently, but not consistently not be able to resolve hosts when I switch between WiFi networks and Data Network (3g). When on CyanogenMod I was able to toggle flight mode and this would "fix" the issue temporarily. However with LineageOS I must reboot the phone to get resolving working again. When this happens I will get an x in the status bar icon for either wifi or data connection.
It has also been noted to happen when I have data turned off but am connected to Wifi. If I leave the Wifi area for a bit and return the DNS issues persist.
Has anyone else come across this problem. Any help greatly appreciated as rebooting my phone several times a day is a PITA
Details:
Galaxy S4 (GT-I9505)
Android 7.1.2 (LineageOS 14.1-20170524)
Baseband: I9505XXUHOJ2
Have you tried updating to the latest baseband (I9505XXUHPK2)?
Strephon Alkhalikoi said:
Have you tried updating to the latest baseband (I9505XXUHPK2)?
Click to expand...
Click to collapse
I have not yet, I was working under the assumption that DNS resolving failures (I can connect via IP address) was going to be in the OS. Updated to the latest weekly and problem persists so I guess baseband is a good next step
I am embarrassed to say I am not sure where the best place to get a version of I9505XXUHPK2 that will with heimdal cli*and does it matter my phone provider or location (europe).
Is flashing the baseband modem requiring a wipe of the phone?
* heimdall flash --MDM modem.bin
Phone location nor carrier matter. In General there is a basebands thread where you can get that baseband file from. You should then be able to flash it using Heimdall. If you have issues, downloading the full ROM from Sammobile and flashing it should reset everything. But flashing the full ROM is the last resort because it wipes everything, whereas flashing just the baseband won't.
baseband updated to I9505XXUHPK and LineageOS to 2017-06-07. Early days but so far no errors.
For anyone following along, I did the following to update the baseband
I went to this thread which gives you a nice small download of just the files needed compared to the websites that offer them up which are 1.4GB downloads!
Scrolled down to the section "I9505 Download links for Lollipop and up ". Clicked "Click to show content.
Under XXUHPK2 I "Clicked to show content"
Downloaded "GSM and NON-HLOS"
From ubuntu extracted "XXUHPK2_COMBINED.tar"
Fired up terminal
Put phone into download mode (from off, hold down volume and power. pressing up when prompted)
In terminal checked heimdall could see phone running
Code:
heimdall detect
Then flashed the files
Code:
sudo heimdall flash --MDM modem.bin --APNHLOS NON-HLOS.bin
Waited for flashing to complete
Phone rebooted, all done
Latest updated: Updating baseband did not work. The problem still exists.
If my phone switched from wifi to mobile data or vice versa there is a high chance that while it will connect to the relevant network, DNS does not work and I can not connect to anything by hostname, only by IP address.
If anyone has any other suggestions on how to potentially fix this or even manually get DNS working again via terminal or an app or anything. Having to reboot a couple of times a day is driving me loopy
Morning Guys,
Ive had all sorts of fun and games with this damn G950F every time i root it it throws up a problem.
It had just gotten to unlock time for the third time, but started throwing up 'SystemUI has stopped working' errors when i hit the 'app list' button. Didnt think much of it, and went to root. SuperSU took and was granting root permissions but would not update the binary. I fell asleep at some stage and didnt go back to it until this morning.
Went to use the phone this morning and its reset itself and thrown up a big red message about only having stock binaries installed. Queue about 7 hours of not being able to resurrect a phone that had spat out TWRP and now appeared to have a locked down bootloader again. Finally realised i could flash the stock XSA rom without the bootloader and resurrected the phone.
Fired it up, and its no longer detecting the SIM card, and *all* of the Mobile Network settings are missing. Cant find an answer to this anywhere. Im hoping like hell its a software issue (another non answered question i have is that i get weird ass settings options with strange labels and duplicate entries and options that crash the settings app after some re-flashes.
Anyway.. wat do plez?
Have tried - Factory resets and cache wipes both in UI and recovery. Reflashing AP, CP, CSC and/or CSC_HOME. Cant flash BL as its currently 'prenormal'. Keep reading the 'download mode, start odin, quickly hit buttons' trick but have never gotten it to work, and ill try it again right now to triple check but im 99.9999% sure it wont let me re-flash Nougat on it for the same reason.
Cheers in advance.
UPDATE - So it looks like something has accidentally'd the IMEI. Now looking for non root non bootloader methods to bring it back. Looks like thats my problem.