Hello everyone. I have install NeatRom 5.3.1 and Dorimanx 8.43. How fix freezing phone in deep sleep ? My Device did not wake up this morning, had to reboot via Power button pressed for 10 secs, and battery was drained form 90 to 20 ....
In debug log i have :
dmesg-Error:
<4>GPT: Use GNU Parted to correct GPT errors.
<6>EXT4-fs (mmcblk0p10): mounted filesystem with writeback data mode. Opts: noauto_da_alloc,journal_async_commit,errors=panic
<3>PM: Device alarm failed to suspend: error -16
<6>sii9234_process_msc_work(): msc_req_locked error -2
<3>PM: Device power.0 failed to suspend noirq: error -11
<3>PM: Device alarm failed to suspend: error -16
<3>PM: Device alarm failed to suspend: error -16
----------------------------
dmesg-Warning:
<4>WARNING: CPU: 1 PID: 1 at fs/sysfs/dir.c:526 sysfs_add_one+0x98/0xa8()
<3>Warning: unable to open an initial console.
<4>WARNING: CPU: 0 PID: 1 at mm/page_alloc.c:2503 __alloc_pages_nodemask+0x290/0x6e0()
<11>fs_mgr: Warning: unknown flag spo_check
<11>fs_mgr: Warning: unknown flag spo_check
<11>fs_mgr: Warning: unknown flag spo_check
<6>warning: `cbd' uses 32-bit capabilities (legacy support in use)
----------------------------
dmesg-Fail:
<3>PM: Device alarm failed to suspend: error -16
<3>PM: Some devices failed to suspend, or early wake event detected
<3>PM: Device power.0 failed to suspend noirq: error -11
<3>PM: Some devices failed to power down
<3>PM: Device alarm failed to suspend: error -16
<3>PM: Some devices failed to suspend, or early wake event detected
<3>PM: Device alarm failed to suspend: error -16
<3>PM: Some devices failed to suspend, or early wake event detected
----------------------------
Click to expand...
Click to collapse
How fix this freezing ?
pheonix1 said:
Hello everyone. I have install NeatRom 5.3.1 and Dorimanx 8.43. How fix freezing phone in deep sleep ? My Device did not wake up this morning, had to reboot via Power button pressed for 10 secs, and battery was drained form 90 to 20 ....
In debug log i have :
How fix this freezing ?
Click to expand...
Click to collapse
wipe cache/dalvik reflash neatrom - had to do this on my wifes phone the other night because she was having issues with the stock dialer - her phone is fine now - oh wait, come to think of it I have left her on philz kernel that comes with neat.
Failing that GS2RomNuke @hawkerpaul and start again.
Hope this helps
Jimsilver73 said:
wipe cache/dalvik reflash neatrom - had to do this on my wifes phone the other night because she was having issues with the stock dialer - her phone is fine now - oh wait, come to think of it I have left her on philz kernel that comes with neat.
Failing that GS2RomNuke @hawkerpaul and start again.
Hope this helps
Click to expand...
Click to collapse
Hello. I reinstall rom with kernel 3 times (first in recovery: wipe data, wipe cache, wipe dalvik) and nothing. If anybody don't help i try kernel apollo. I dont use philz kernel because they do not have bln....
Waiting for help.....
pheonix1 said:
Hello. I reinstall rom with kernel 3 times (first in recovery: wipe data, wipe cache, wipe dalvik) and nothing. If anybody don't help i try kernel apollo. I dont use philz kernel because they do not have bln....
Waiting for help.....
Click to expand...
Click to collapse
Did you try gs2romnuke yet? @hawkerpaul also has a very good kernel wipe, much better than just wiping manually from recovery. You could also try formatting data/cache and dalvik in advanced settings in cwm.
Ok i try this script. Choose nuke?
Wysłane z mojego GT-I9100 przy użyciu Tapatalka
pheonix1 said:
Ok i try this script. Choose nuke?
Wysłane z mojego GT-I9100 przy użyciu Tapatalka
Click to expand...
Click to collapse
yes - from @hawkerpauls thread :good::good::good:
Related
Hi,
I've followed the instructions and installed the F15C Eagle patch / kernel for the Touchpad and all it working nice and fast.
Saying that I'm getting some issues with apps hanging but that may be my wifi.
Is there a documented way to reverse the changes that the F15C Eagle makes and un-install it and put back to the original state?
Thanks
Lee
Go into preware-> installed-> kernels. Select remove at the bottom.
Hi, if you want to uninstall the kernel. Simply go to preware, allow it to load. Then click on all application --> Kernel ---> Recovery kernel ---> Install that and will reset it to the original kernel. Then you can install other kernels as you please. Good luck, I found that the uberkernel is the best.
Thanks all. Thought I'd check first - didn't want to turn it into £115 paperweight!
lsainsbury said:
Thanks all. Thought I'd check first - didn't want to turn it into £115 paperweight!
Click to expand...
Click to collapse
dont worry, its very hard to brick ;p
[Q] Removing F15c Eagle after Reset
I searched for this but couldnt find anything, I seen the instructions to remove F15c Eagle but they don't work for me.
Basically I had F15c Eagle on the machine and did a factory reset, now I've reinstalled preware/govnah added all the feeds etc.. but it doesn't show that F15c is installed (when it actually is, even when I did the factory reset, when the machine rebooted I got the F15c boot loader screen and I am able to use Govnah to overclock)
Also the F15C Eagle Touchpad Icon is showing in my Downloads, when I click on it I just get a black minimized screen, if I tap into it, it goes full screen but nothing happens, and I can't click on the Dropdown arrow at the top left like other apps.
How can I uninstall F15c? I tried "installing it" but it gives me this error after it downloads and tries to install
begin
Nothing Interesting.
download
% Total % Received % Xferd Average Speed Time Time Time Current
86 4844k 86 4169k 0 0 482k 0 0:00:10 0:00:08 0:00:02 702k
100 4844k 100 4844k 0 0 533k 0 0:00:09 0:00:09 --:--:-- 866k
identify
org.webosinternals.kernels.psycho-f15c-kernel-touchpad
install
{"returnValue":true , "ticket":1, "subscribed":true}
{ "ticket":1 , "status":"STARTING" }
{ "ticket":1 , "status":"CREATE_TMP" }
{ "ticket":1 , "status":"VERIFYING" }
{ "ticket":1 , "status":"IPKG_INSTALL" }
{ "ticket":1 , "status":"SUCCESS" }
mkdir-prerm
Nothing Interesting.
install-prerm
Nothing Interesting.
postinst
-1: Unable to run command: IPKG_OFFLINE_ROOT=/media/cryptofs/apps /bin/sh /media/cryptofs/apps/usr/lib/ipkg/info/org.webosinternals.kernels.psycho-f15c-kernel-touchpad.postinst 2>&1
Kernel confirmed to be compatible with this webOS version
Verifying no existing modifications to target files ...
Verification failed on /boot/System.map-2.6.35-palm-tenderloin
Verification failed on /boot/config-2.6.35-palm-tenderloin
Verification failed on /boot/uImage-2.6.35-palm-tenderloin
Verification failed on /lib/modules/2.6.35-palm-tenderloin/kernel/arch/arm/common/cpaccess.ko
Verification failed on /lib/modules/2.6.35-palm-tenderloin/kernel/arch/arm/mach-msm/dma_test.ko
Verification failed on /lib/modules/2.6.35-palm-tenderloin/kernel/crypto/ansi_cprng.ko
Verification failed on /lib/modules/2.6.35-palm-tenderloin/kernel/drivers/media/video/gspca/gspca_main.ko
Verification failed on /lib/modules/2.6.35-palm-tenderloin/kernel/drivers/net/wireless/libra/librasdioif.ko
Verification failed on /lib/modules/2.6.35-palm-tenderloin/kernel/drivers/scsi/scsi_wait_scan.ko
Verification failed on /lib/modules/2.6.35-palm-tenderloin/kernel/drivers/video/backlight/lcd.ko
Verification failed on /lib/modules/2.6.35-palm-tenderloin/kernel/net/ipv4/tcp_bic.ko
Device kernel is not in factory condition, refusing to install replacement
remove
Removing package org.webosinternals.kernels.psycho-f15c-kernel-touchpad from root...
(offline root mode: not running org.webosinternals.kernels.psycho-f15c-kernel-touchpad.prerm)
delete
Nothing Interesting.
failed
Nothing Interesting.
dsenart said:
I searched for this but couldnt find anything, I seen the instructions to remove F15c Eagle but they don't work for me.
Basically I had F15c Eagle on the machine and did a factory reset, now I've reinstalled preware/govnah added all the feeds etc.. but it doesn't show that F15c is installed (when it actually is, even when I did the factory reset, when the machine rebooted I got the F15c boot loader screen and I am able to use Govnah to overclock)
Also the F15C Eagle Touchpad Icon is showing in my Downloads, when I click on it I just get a black minimized screen, if I tap into it, it goes full screen but nothing happens, and I can't click on the Dropdown arrow at the top left like other apps.
How can I uninstall F15c? I tried "installing it" but it gives me this error after it downloads and tries to install
begin
Nothing Interesting.
download
% Total % Received % Xferd Average Speed Time Time Time Current
86 4844k 86 4169k 0 0 482k 0 0:00:10 0:00:08 0:00:02 702k
100 4844k 100 4844k 0 0 533k 0 0:00:09 0:00:09 --:--:-- 866k
identify
org.webosinternals.kernels.psycho-f15c-kernel-touchpad
install
{"returnValue":true , "ticket":1, "subscribed":true}
{ "ticket":1 , "status":"STARTING" }
{ "ticket":1 , "status":"CREATE_TMP" }
{ "ticket":1 , "status":"VERIFYING" }
{ "ticket":1 , "status":"IPKG_INSTALL" }
{ "ticket":1 , "status":"SUCCESS" }
mkdir-prerm
Nothing Interesting.
install-prerm
Nothing Interesting.
postinst
-1: Unable to run command: IPKG_OFFLINE_ROOT=/media/cryptofs/apps /bin/sh /media/cryptofs/apps/usr/lib/ipkg/info/org.webosinternals.kernels.psycho-f15c-kernel-touchpad.postinst 2>&1
Kernel confirmed to be compatible with this webOS version
Verifying no existing modifications to target files ...
Verification failed on /boot/System.map-2.6.35-palm-tenderloin
Verification failed on /boot/config-2.6.35-palm-tenderloin
Verification failed on /boot/uImage-2.6.35-palm-tenderloin
Verification failed on /lib/modules/2.6.35-palm-tenderloin/kernel/arch/arm/common/cpaccess.ko
Verification failed on /lib/modules/2.6.35-palm-tenderloin/kernel/arch/arm/mach-msm/dma_test.ko
Verification failed on /lib/modules/2.6.35-palm-tenderloin/kernel/crypto/ansi_cprng.ko
Verification failed on /lib/modules/2.6.35-palm-tenderloin/kernel/drivers/media/video/gspca/gspca_main.ko
Verification failed on /lib/modules/2.6.35-palm-tenderloin/kernel/drivers/net/wireless/libra/librasdioif.ko
Verification failed on /lib/modules/2.6.35-palm-tenderloin/kernel/drivers/scsi/scsi_wait_scan.ko
Verification failed on /lib/modules/2.6.35-palm-tenderloin/kernel/drivers/video/backlight/lcd.ko
Verification failed on /lib/modules/2.6.35-palm-tenderloin/kernel/net/ipv4/tcp_bic.ko
Device kernel is not in factory condition, refusing to install replacement
remove
Removing package org.webosinternals.kernels.psycho-f15c-kernel-touchpad from root...
(offline root mode: not running org.webosinternals.kernels.psycho-f15c-kernel-touchpad.prerm)
delete
Nothing Interesting.
failed
Nothing Interesting.
Click to expand...
Click to collapse
I am having same issue
I need to send touchpad to HP for repair
I did full reset before removing kernel from Preware....
Can't install or remove F15C right now..
I'm going to try webOS doctor...
importpsycho said:
I am having same issue
I need to send touchpad to HP for repair
I did full reset before removing kernel from Preware....
Can't install or remove F15C right now..
I'm going to try webOS doctor...
Click to expand...
Click to collapse
Hmm. I seem to have the same issue. Any luck using webos doctor?
I always figured Webos Doctor was kind of a last gasp solution. What I did to fix the F15C inability to install, uninstall, was go to Preware and I installed the "Palm Kernal (Touchpad)" stock kernal first. Crossed my finger as I system rebooted. Seemed like the longest reboot ever. Double checked with Govnah that I was indeed back to crappy, stock, 1.2Ghz, then went back into Preware and installed the latest version of F15C. Reboot, rinse, lather, repeat. Now I'm back to the OC'd state and F15C is back to normal. I hope this helped. If you guys did Webos Doctor, please post your result. I'd like to know for future instance when I might need it .
mojojokho said:
Hmm. I seem to have the same issue. Any luck using webos doctor?
Click to expand...
Click to collapse
1. open preware
2. install the recovery kernel
3. reinstall the kernel which you want to install
I just got my GSIV today and rooted it using the stickied root method. I have installed setcpu. The rom crashes the second I set the governor to MSM-DCVS. Any ideas?
PelPix said:
I just got my GSIV today and rooted it using the stickied root method. I have installed setcpu. The rom crashes the second I set the governor to MSM-DCVS. Any ideas?
Click to expand...
Click to collapse
My S4 GT-i9505 crash too...
PelPix said:
I just got my GSIV today and rooted it using the stickied root method. I have installed setcpu. The rom crashes the second I set the governor to MSM-DCVS. Any ideas?
Click to expand...
Click to collapse
Same here.... i searched and really have not found an answer.
Stacktrace from enabling msm-dcvs
Here's the relevant stack trace from the kernel panic when enabling the msm-dcvs governor.
Code:
[ 2811.452880] MSM_DCVS: msm_dcvs_freq_sink_start: msm_dcvs_freq_sink_start invalid dcvs_core_id = 0 returning -EINVAL
[ 2811.462585] ------------[ cut here ]------------
[ 2811.466979] kernel BUG at /opt/jenkins/android/workspace/android/jellybean/kernel/samsung/jf/drivers/cpufreq/cpufreq_gov_msm.c:206!
[ 2811.478790] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
[ 2811.484557] Modules linked in: dhd vpnclient
[ 2811.488799] CPU: 0 Not tainted (3.4.0-cyanogenmod-gfbaa5c7 #1)
I've done a little cursory exploring and noticed that the CPU_OFFSET parameter starts at 1 on this kernel module, but it is being told to enable this governor on core 0, hence the message above. Not sure at the moment if it's the module's fault, or just some misconfiguration from settings activity when enabling this module.
I plan to look into this in a bit more depth sometime in the next few weeks(hopefully).
Follow up to stepheno's message
stephenopdx said:
Here's the relevant stack trace from the kernel panic when enabling the msm-dcvs governor.
Code:
[ 2811.452880] MSM_DCVS: msm_dcvs_freq_sink_start: msm_dcvs_freq_sink_start invalid dcvs_core_id = 0 returning -EINVAL
[ 2811.462585] ------------[ cut here ]------------
[ 2811.466979] kernel BUG at /opt/jenkins/android/workspace/android/jellybean/kernel/samsung/jf/drivers/cpufreq/cpufreq_gov_msm.c:206!
[ 2811.478790] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
[ 2811.484557] Modules linked in: dhd vpnclient
[ 2811.488799] CPU: 0 Not tainted (3.4.0-cyanogenmod-gfbaa5c7 #1)
I've done a little cursory exploring and noticed that the CPU_OFFSET parameter starts at 1 on this kernel module, but it is being told to enable this governor on core 0, hence the message above. Not sure at the moment if it's the module's fault, or just some misconfiguration from settings activity when enabling this module.
I plan to look into this in a bit more depth sometime in the next few weeks(hopefully).
Click to expand...
Click to collapse
Hi, stephenopdx and I are working together on this issue in our free time. As a follow up, we've found that the call to msm_dcvs_scm_init is returning a non-zero value (specifically 4). This function is calling the command DCVD_CMD_INIT (command ID 5) in the SCM_SVC_DCVS service. The continues down to an ARM instruction call to move the processor into "secure mode" (aka TrustZone). I'd like to emphasize at this point that both stephenopdx are complete noobs when it comes to kernel development.
We are wondering:
1) Why, if the scm_call to DCVS_CMD_INIT fails, does the kernel continue on its merry way?
2) What does that return code of 4 mean?
3) What preconditions are necessary to initialize DCVS?
4) Is there a place where we can find reference materials (things like return codes and their meanings) for the Qualcomm MSM 8960 SoC? Googling for return code 4 was fairly futile.
5) Is there some sort of kernel debugger so that we can stop using terrible pr_err messages?
We can also produce stack traces or kernel panic logs (heavily augmented with demented pr_err messages to help us figure out what's going on) if anyone is interested.
Thanks!
Hello everyone
I've managed to unlock and root my SGP312 (pollux_windy). Because I always liked AOKP, I tried to install this custom ROM. Here's what I did:
1) Flashed Little Kernel into /boot while in Sony's Fastboot Mode
2) Flashed extracted boot.img of AOKP into "boot" and newest TWRP recovery (v2.6.3) into "recovery" while in LK's Fastboot Mode
3) Rebooted into TWRP recovery, wiped data, cache and dalvik cache
4) Flashed newest AOKP version (jb-mr2 milestone #1 for pollux_windy)
5) Flashed gapps (gapps-jb-20130813-signed.zip)
And tada, the custom ROM booted and everything was fine... No force closes / crashes, no problems, everything worked like a charm.. except the god damn Play Store! Whenever I open the Play Store, it only says "No connection". Pressing retry doesn't help at all. Ofcourse I always search through some forums before posting an issue, so here's what I've already tried:
- Other custom ROM (CM 10.2 stable for pollux_windy)
- Other gapps package (pa_gapps-full-4.3-20131102-signed.zip)
- Force Google Play Store and Google Play Services to stop and delete their data
- Wiped cache and dalvik cache
- Tried a connection without native IPv6 (WLAN hotspot of my HTC One, going over mobile internet which is clearly IPv4 only)
- Checked /etc/hosts (only contains 127.0.0.1 localhost)
- Executed Shark for Root -> There is clearly some data activity going on, my tablet seems to send some data to the google servers but they return an empty response as it seems (see logcat down below)? Unfortunately I am not able to analyze the packets, thanks to SSL/HTTPS...
- Changed some build.prop settings to match an original installation (model=SGP312, device=SGP312 and so on...)
And none of these methods worked. I am totally clueless what else I could try? Here's a logcat snippet:
Code:
D/Finsky ( 4435): [1] 12.onClick: b/5160617: Reinitialize account [00Z7aRpoYHPCeSI-XHfBz1uwqFI] on retry button click
D/Volley ( 4435): [221] DiskBasedCache.clear: Cache cleared.
D/Volley ( 4435): [225] DiskBasedCache.clear: Cache cleared.
I/qtaguid ( 4435): Failed write_ctrl(u 52) res=-1 errno=22
I/qtaguid ( 4435): Untagging socket 52 failed errno=-22
W/NetworkManagementSocketTagger( 4435): untagSocket(52) failed with errno -22
E/DfeApi ( 4435): [1] DfeRequest.deliverResponse: Null wrapper parsed for request=[[ ] https://android.clients.google.com/fdfe/toc 0xe8d195d1 NORMAL 21]
D/Finsky ( 4435): [1] ErrorStrings.get: No specific error message for: com.android.volley.ParseError: java.lang.RuntimeException: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.protos.Response$Payload, but got null
W/NFC-LLC ( 1165): LLC length mis-match
My build.prop is now reverted to the original AOKP build.prop, which can be found here: dl.snapserv.net/build.prop.txt (Sorry, I am not allowed to post links yet...) Have you guys any idea? XDA is basically my last hope, otherwise it seems like I am doomed to use the stock ROM :/ Or did I do something wrong?
Thanks for reading and have a nice day!
Regards
NeoXiD
Code:
D/Finsky ( 4435): [1] 12.onClick: b/5160617: Reinitialize account [00Z7aRpoYHPCeSI-XHfBz1uwqFI] on retry button click
D/Volley ( 4435): [221] DiskBasedCache.clear: Cache cleared.
D/Volley ( 4435): [225] DiskBasedCache.clear: Cache cleared.
I/qtaguid ( 4435): Failed write_ctrl(u 52) res=-1 errno=22
I/qtaguid ( 4435): Untagging socket 52 failed errno=-22
W/NetworkManagementSocketTagger( 4435): untagSocket(52) failed with errno -22
E/DfeApi ( 4435): [1] DfeRequest.deliverResponse: Null wrapper parsed for request=[[ ] https://android.clients.google.com/fdfe/toc 0xe8d195d1 NORMAL 21]
D/Finsky ( 4435): [1] ErrorStrings.get: No specific error message for: com.android.volley.ParseError: java.lang.RuntimeException: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.protos.Response$Payload, but got null
W/NFC-LLC ( 1165): LLC length mis-match
[/QUOTE]
Same error on my Acer A500 TegraOwners Rom 4.3 MR2 v8t6. Cant find solution.
bondcheg said:
Code:
D/Finsky ( 4435): [1] 12.onClick: b/5160617: Reinitialize account [00Z7aRpoYHPCeSI-XHfBz1uwqFI] on retry button click
D/Volley ( 4435): [221] DiskBasedCache.clear: Cache cleared.
D/Volley ( 4435): [225] DiskBasedCache.clear: Cache cleared.
I/qtaguid ( 4435): Failed write_ctrl(u 52) res=-1 errno=22
I/qtaguid ( 4435): Untagging socket 52 failed errno=-22
W/NetworkManagementSocketTagger( 4435): untagSocket(52) failed with errno -22
E/DfeApi ( 4435): [1] DfeRequest.deliverResponse: Null wrapper parsed for request=[[ ] https://android.clients.google.com/fdfe/toc 0xe8d195d1 NORMAL 21]
D/Finsky ( 4435): [1] ErrorStrings.get: No specific error message for: com.android.volley.ParseError: java.lang.RuntimeException: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.protos.Response$Payload, but got null
W/NFC-LLC ( 1165): LLC length mis-match
Same error on my Acer A500 TegraOwners Rom 4.3 MR2 v8t6. Cant find solution.
Click to expand...
Click to collapse
In my case it was Little Kernel's fault. Little Kernel messed up the serial number, to the Google servers received "X-Device-ID: 0" instead of my serial number. (How I found that problem? I just went so far that I've intercepted the traffic to the google servers with a fake root certificate and Fiddler...) Such requests will just get an empty answer, which triggers these logcat errors. If you connect your device with adb, do you see the correct serial or just some messed up unicode characters like yyyyyyy...?
Regards
NeoXiD
NeoXiD said:
Same error on my Acer A500 TegraOwners Rom 4.3 MR2 v8t6. Cant find solution.
Click to expand...
Click to collapse
In my case it was Little Kernel's fault. Little Kernel messed up the serial number, to the Google servers received "X-Device-ID: 0" instead of my serial number. Such requests will just get an empty answer, which triggers these logcat errors. If you connect your device with adb, do you see the correct serial or just some messed up unicode characters like yyyyyyy...?
Regards
NeoXiD[/QUOTE]
I`m novice user and never conneced my device with adb and dont know how to do it.
bondcheg said:
In my case it was Little Kernel's fault. Little Kernel messed up the serial number, to the Google servers received "X-Device-ID: 0" instead of my serial number. Such requests will just get an empty answer, which triggers these logcat errors. If you connect your device with adb, do you see the correct serial or just some messed up unicode characters like yyyyyyy...?
Regards
NeoXiD
I`m novice user and never conneced my device with adb and dont know how to do it.
Click to expand...
Click to collapse
Okay.. Then follow this guide here: http://forum.xda-developers.com/showthread.php?t=2141817 for installing ADB and execute the command "adb devices". Although, if you do not even know what adb is, you haven't probably flashed Little Kernel, so my solution might not be the right one. Have you tested any of my tries I've listened at the thread start?
Regards
NeoXiD
NeoXiD said:
Okay.. Then follow this guide here: http://forum.xda-developers.com/showthread.php?t=2141817 for installing ADB and execute the command "adb devices". Although, if you do not even know what adb is, you haven't probably flashed Little Kernel, so my solution might not be the right one. Have you tested any of my tries I've listened at the thread start?
Regards
NeoXiD
Click to expand...
Click to collapse
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
---------- Post added at 06:51 PM ---------- Previous post was at 06:46 PM ----------
NeoXiD said:
Okay.. Then follow this guide here: http://forum.xda-developers.com/showthread.php?t=2141817 for installing ADB and execute the command "adb devices". Although, if you do not even know what adb is, you haven't probably flashed Little Kernel, so my solution might not be the right one. Have you tested any of my tries I've listened at the thread start?
Regards
NeoXiD
Click to expand...
Click to collapse
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
Emm i done mostly all you listened at the thread start but nothing helps.
Only other ROMs works fine. In any other ROMs play market have no errors. But in case i done all as guides says why other people a500 with this ROM works fine but not mine?
Sry for my english.
bondcheg said:
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
---------- Post added at 06:51 PM ---------- Previous post was at 06:46 PM ----------
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
Emm i done mostly all you listened at the thread start but nothing helps.
Only other ROMs works fine. In any other ROMs play market have no errors. But in case i done all as guides says why other people a500 with this ROM works fine but not mine?
Sry for my english.
Click to expand...
Click to collapse
That might be the fault then, because it might get interpreted as serial number '0', which might get rejected by Google. Did you flash any custom bootloader? Normally this should not occur... You can also drop me a PM so we do not spam this thread with a 4-eye-conversation.
Regards
NeoXiD
Hello there,
My Samsusng Galaxy S2 (i9100) has recently stopped working as it is supposed to. While I tried debugging the issue in any way I could, I figured out I might get some help over here.
At any time that the device itself isn't connected to a power source (USB cable [adb] or the charger), it randomly crashes (the screen turns black and I have to turn the phone on again). I also must say that this problem doesn't happen while on the recovery screen (CWM based recovery).
At first I thought this may happen because I've installed a pretty old version of Cyanogenmod (the cm11 installer version), so I installed the recent monthly build, but the issue still persists. I've tried debugging the device wirelessly (because when it was connected to a power source it never crashed), so I played a game which makes the CPU work abit, and I thought I'll get a crash log - which I didn't get. The last radio signal I got from the phone was this:
I/LibraryLoader( 2817): Expected native library version number "",actual native
library version number ""
I/chromium( 2817): [INFO:library_loader_hooks.cc(116)] Chromium logging enabled:
level = 0, default verbosity = 0
I/BrowserStartupController( 2817): Initializing chromium process, renderers=0
D/TinyALSA-Audio Hardware( 1855): audio_hw_get_mic_mute(0x4003e938, 0x4126daeb)
D/BluetoothManagerService( 2205): Message: 20
D/BluetoothManagerService( 2205): Added callback: android.bluetooth.IBluetoothMa
[email protected]:true
D/BluetoothAdapter( 2817): 1112752792: getState() : mService = null. Returning
STATE_OFF
D/libEGL ( 2817): loaded /system/lib/egl/libEGL_mali.so
D/libEGL ( 2817): loaded /system/lib/egl/libGLESv1_CM_mali.so
D/libEGL ( 2817): loaded /system/lib/egl/libGLESv2_mali.so
E/ ( 2817): Device driver API match
E/ ( 2817): Device driver API version: 23
E/ ( 2817): User space API version: 23
E/ ( 2817): mali: REVISION=Linux-r3p2-01rel3 BUILD_DATE=Wed Oct 9 21:05:
57 KST 2013
W/chromium( 2817): [WARNINGroxy_service.cc(890)] PAC support disabled because
there is no system implementation
I/chromium( 2817): [INFO:CONSOLE(0)] "Document was loaded from Application Cache
with manifest {URL}
k-core-v40.appcache", source: {URL}
d/sdk/native/sdk-core-v40.html (0)
I/chromium( 2817): [INFO:CONSOLE(0)] "Application Cache Checking event", source:
{URL}
l (0)
I/chromium( 2817): [INFO:CONSOLE(0)] "Application Cache NoUpdate event", source:
{URL}
l (0)
W/chromium( 6284): [WARNINGroxy_service.cc(890)] PAC support disabled because
there is no system implementation
I/chromium( 6284): [INFO:simple_index_file.cc(437)] Simple Cache Index is being
restored from disk.
D/Yamaha-MC1N2-Audio( 1855): yamaha_mc1n2_audio_output_stop()
D/Yamaha-MC1N2-Audio( 1855): yamaha_mc1n2_audio_route_start()
Click to expand...
Click to collapse
I've tried tracing the log files the system automatically creates in the ./system folder, but I couldn't find any useful information except from some deamon crash logs.
I tried resetting the dalvik cache, reinstalling my ROM manually (adb sideload), preforming a complete factory reset and wiping cache partition, and yet it didn't work.
I'm quite sure the issue relates to my phone's battery (which overheated a bit when I used it for a long time), but I'm still not completely sure this is the issue, so I would like to hear your suggestions.
Thanks in advance,
Eden
Eden Campo said:
Hello there,
....
I've tried tracing the log files the system automatically creates in the ./system folder, but I couldn't find any useful information except from some deamon crash logs.
I tried resetting the dalvik cache, reinstalling my ROM manually (adb sideload), preforming a complete factory reset and wiping cache partition, and yet it didn't work.
I'm quite sure the issue relates to my phone's battery (which overheated a bit when I used it for a long time), but I'm still not completely sure this is the issue, so I would like to hear your suggestions.
Thanks in advance,
Eden
Click to expand...
Click to collapse
I also read your logcat or yeah the part of it and it seems all to be fine, normal lines.
I don't own the S2 anymore and I didn't had the issue. But I suggest to try somethings first before buying a new battery.
Try another rom instead of cyanogenmod, Cyanogenmod is supporting Alot of devices and it's not really good specific for devices so I suggest to try one of the roms from the development forums.(Cyanogenmod always have bugs.)
Try to flash back to stock with odin
Try to borrow a battery from a friend and see or you still have the same problem
Remove the battery out of the phone and leave your phone without a battery for like 1-5 minutes.
It could be maybe the battery that it got issues cause the S2 is not the newest phone anymore and hardware also has a lifetime sadly. But your screen goes black and your device goes off right?
1. Unlocking Bootloader taken from here (Success)
2. Installing SuperSU, BusyBox Installer
3. Downloading the CM12 from here
4. boot to recovery mode to install the Custom ROM. first I do wipe data, then install the ROM. when Installing, there are no error code or notifications so I assumed it's installed. I try to install the Gapps, but failed, so I skipped it. when I reboot my phone, suddenly I got messages on the left top of screen says :
[840] fastboot_init()
[840] Error: allocating memory for ssd buffer
[860] USB init ept @ 0x7ad0000
[860] udc_start()
------------------------------------------------
DOWNLOAD MODE
------------------------------------------------
Loading ......
Press the Volume Up key until you see the download screen
[530] fastboot_init()
[530] Error: allocating memory for ssd buffer
[550] USB init ept @ 0x7ad0000
[570] udc_start()
[680] -- reset --
[680] -- portchange --
[720] -- reset --
[720] --portchange --
I've tried so many ways to restore it. from Laf Multi Tools, using fastboot device (my device won't detect in PC, even in my friend's laptop), etc and still no luck. can someone please help me?