Should I bother updating?
Does Chrome finally work as it should?
Yes after one day testing ...
Sent from my SHIELD Tablet using XDA Free mobile app
So far so good after 3 hours.
Sent from my SHIELD Tablet using XDA Free mobile app
There has been a marked increase in stability and responsiveness for me.
And battery life in standby seems better as well (so far)!
Sent from my SHIELD Tablet using XDA Free mobile app
allright. So I'll pull the plunge on this one.
TWRP and the regular update process don't seem to work. So square one from what it seems
sQeetz said:
allright. So I'll pull the plunge on this one.
TWRP and the regular update process don't seem to work. So square one from what it seems
Click to expand...
Click to collapse
I updated with theOTA from this post http://forum.xda-developers.com/shield-tablet/general/android-5-1-t3115536 just download the ota and supersu from that link and flash the OTA first then supersu and your done. I didnt even lose recovery after i flashed these!
Oh yeah and I used google sheets and docs for 4 hours this morning without a single freeze or crash normally i would've had at least 10 during that time. So yes its def. worth it.
So far.... I installed about 3 hours after release, it's much much smoother. Only once have I gotten the "what the frig is this thing doing" hang and sputter, while installing busy box. Colors are great. It's like flashing a new screen. Xposed super alpha for 5.1 working. Gravity box works, flat style colored bars works.
Now just waiting for custom kernels....
Depends. Update 3.0 has these issues:
1- Apps optimization on every reboot. (rebooting takes 5 or more minutes)
2- USB OTG not working (tried usb flash drives and nothing)
3- Controller not turning off when button pressed (by design)
I was on 5.0.1 rooted, I wiped everything, flashed 5.1 and rooted again, if you are wondering.
NaminatoR1254jaime.sier said:
Depends. Update 3.0 has these issues:
1- Apps optimization on every reboot. (rebooting takes 5 or more minutes)
2- USB OTG not working (tried usb flash drives and nothing)
3- Controller not turning off when button pressed (by design)
I was on 5.0.1 rooted, I wiped everything, flashed 5.1 and rooted again, if you are wondering.
Click to expand...
Click to collapse
Something may have gone wrong. I've only had the optimization come up if I clear cache or install apps via recovery so far... And I've been trying to get it to crash at reboot....
Judging from the responses in this thread, it looks like it's finally time for me to unlock my bootloader and update from 4.4. Wish me luck, guys!
Pariahnoble said:
Something may have gone wrong. I've only had the optimization come up if I clear cache or install apps via recovery so far... And I've been trying to get it to crash at reboot....
Click to expand...
Click to collapse
I've had it come up on several reboots. Many people report it too on the official Nvidia forums.
But the USB OTG thing did it, Im staying on 2.2.1 until a hotfix is released.
I stand corrected, =x I have 2 apps optimizing at boot.
No problems here
I installed ota 3.0 from twrp after wiping everything including internal memory and I have no problems....
No app optimizations after every reboot or havent encountered any lags or sound glitches + wifi performance is much better and no issues with hdmi or usb otg either, played half life 2 for like 2.5 hours straight and had no issues even for a second...
Don't now what happened with the people who are having problems with this update. I have 32gb lte version and the tab performance is perfect now, for me atleast.
So i would suggest wiping everything except external sdcard and flashing full rom + latest supersu
USB OTG is working for me. I can use my 8GB drive.
I also have the Apps optimizing at every boot bug. 189 of them nonetheless... So the wait is huge.
Full OTA dirty flash over previous 2.2.1, dalvik/cache wipe. I hope for a fix soon.
Wipe everything then install full rom, i am pretty sure u wont get apps optimizing every boot. For me after the update the boot cycles are the fastest yet and I also do have around 180 apps...
Sarge29490 said:
Wipe everything then install full rom, i am pretty sure u wont get apps optimizing every boot. For me after the update the boot cycles are the fastest yet and I also do have around 180 apps...
Click to expand...
Click to collapse
I wiped everything except internal and external storage, I rooted and I still had the optimizing apps every reboot. And not just 2 or 3 apps, all of them.
NaminatoR1254jaime.sier said:
I wiped everything except internal and external storage, I rooted and I still had the optimizing apps every reboot. And not just 2 or 3 apps, all of them.
Click to expand...
Click to collapse
Well the only difference now is i wiped internal storage too and i have no idea if this helps but i have selinux mode set to permissive, if this doesnt work then i guess i am one of the lucky ones...
I also found that the speakers has a screeching irritating sounds when playing media on my wifi version.
Anybody else having the same problem?
Related
Just like the title, i have been experiencing some random rebooting in the past 9 days... at first i thought that i somehow held the on/off button inside my pocket and rebooted itself. my theory changed when i was charging it on that same night... i knew something was wrong few days after it would reboot itself from time to time.
also sometimes after rebooting (mostly when it is charging..) wifi connections start to goof off. i checked the wifi setting and it would say "error" under the "turn on/off wifi" area where you usually see the "connected/connecting/disconnected" letters, along with that some apps start to force close mostly the ones that needs the net get fc's.....
only yesterday it got worse. on the morning it had started to reboot. when i unlocked the lockscreen some apps started to FC. i usually get fc's in booting are the juice plotter, Google partner setup, and something with "wifi". now i manually rebooted it myself when it boots, it still shows those fc's. if it tried pressing some apps it tried to fc as well. manual reboot again, now messages fc's along with the three....
so i went to recovery and restored my safest backup. after restoring no more fc's in my boot. i thought it was all fine now but after a while it would randomly reboot!!!!
Styles of random reboots ive gotten:
1. on screen-off while charging after a while BOOM! reboot.
2. on screen-off not charging, after a while BOOM! reboot.
3. pressing the on/off button on the side when it was on screen-off, BOOM! reboot.
4. pressing the on/off button on the side when it was on screen-off, shows the lockscreen, shows "SD card unexpectedly removed" on status bar, BOOM! reboot.
*it wont reboot when you're using it unless it goes to screen-off for a while (like when using music player... when it goes to screen-off for a while it would reboot...)
--- i will add more of the reboots styles if i remember the others.---
i really need help. i cannot reflash to stock because my laptop got stolen since February. i would be receiving my new laptop in five days.... but i am worried that something worse would happen before even getting my laptop in five days.
Stats:
Samsung galaxy S i9003 (rooted)
currently unrooted
Firmware Version - 2.3.6
kernel - 2.6.35.7-CL709629 [email protected] #6
Baseband - I9003XXKPQ
Build # - GINGERBREADXXKPQ
*ics theme by Tarunagg update 18-
*restored phone to update 14 but same stats
SOMEONE PLEASE SHED SOME LIGHT INTO THIS. PLEASE!
normally when i experience random reboots, i just wipe cache and dalvik cache
if that dont work out then i flash back to stock kernel
its might me rom problem and one thing try to flash ur phone again but u said u don't have laptop but its only sol. according to me . if u want to be on 2.3.6 then acc to me don't install kernel and brother flashing again is the only sol
but for the mean while wipe everything and then deodex again it might help u .
after wipe all and formatting deodex it again
bcz sometime app FC and for that deodex again is necessary
sandeepsivia said:
its might me rom problem and one thing try to flash ur phone again but u said u don't have laptop but its only sol. according to me . if u want to be on 2.3.6 then acc to me don't install kernel and brother flashing again is the only sol
but for the mean while wipe everything and then deodex again it might help u .
after wipe all and formatting deodex it again
bcz sometime app FC and for that deodex again is necessary
Click to expand...
Click to collapse
Thanks sandeep. I am no longer flashing anythingbjust like you said...but what do you mean wipe all? dalvik, cache, battery stats and format? but wont that remove root and cwm? Give me step to step procedure so i can try what you are saying about wiping all..
also about your first paragraph, i will reflash fw to 2.3.6 and no longer flash diff kernel?
noypi_ako said:
normally when i experience random reboots, i just wipe cache and dalvik cache
if that dont work out then i flash back to stock kernel
Click to expand...
Click to collapse
Actually i have been clearing dalvik cache and cache.... but it does not work that much.. i want to flash to stock but i dont have comp. or stock kernel.
Wahaha123 said:
Thanks sandeep. I am no longer flashing anythingbjust like you said...but what do you mean wipe all? dalvik, cache, battery stats and format? but wont that remove root and cwm? Give me step to step procedure so i can try what you are saying about wiping all..
also about your first paragraph, i will reflash fw to 2.3.6 and no longer flash diff kernel?
Click to expand...
Click to collapse
so one thin i forot to tell u tha once along time ago like 6 or moths is installed theme and i did deodex 1st too but the process was aboard bcz of some prlm with deodex file then i installed theme without looking and i my did same rebooting and FC so u can wipe cache and dalvik and battery too then wipe data/ factory reset in recovery only then again deodex it and see the problem solved or not
Just set you min cpu feq back to stock.300mhz - 1.0ghz.
Remove any tweek.
Sent from my GT-i9003 DXKP9(UC-kernel 10) using Tapatalk 2
chongns said:
Just set you min cpu feq back to stock.300mhz - 1.0ghz.
Remove any tweek.
Sent from my GT-i9003 DXKP9(UC-kernel 10) using Tapatalk 2
Click to expand...
Click to collapse
Cpu in my is set to 300-1100. Thanks... hope it'll hold the phone till i get my comp.
Wahaha123 said:
Cpu in my is set to 300-1100. Thanks... hope it'll hold the phone till i get my comp.
Click to expand...
Click to collapse
Dont u think so that u are using too old kernel...use v10 version of UC kernel.
vishal24387 said:
Dont u think so that u are using too old kernel...use v10 version of UC kernel.
Click to expand...
Click to collapse
Yes I know . The latest uc kernel is v10. But my laptop was stolen since the first week of february. That time the best kernel suited for poseidon rom was the v6. So till now I am stuck with v16 since the time my laptop was gone until I get my new on in 4 days at least...
sandeepsivia said:
so one thin i forot to tell u tha once along time ago like 6 or moths is installed theme and i did deodex 1st too but the process was aboard bcz of some prlm with deodex file then i installed theme without looking and i my did same rebooting and FC so u can wipe cache and dalvik and battery too then wipe data/ factory reset in recovery only then again deodex it and see the problem solved or not
Click to expand...
Click to collapse
Sorry, I didnt see your post earlier. But I am wiping every thing now while im replying you. I will tell you the results when it is finished.
Edit: phone seems to work normally. But some apps get fc's... But i think i know why. Its because i forgot to move back apps which were moved to the sd card back to phone memory.(using app2sd).. I know so because i remember having 7 apps moved to sd which had taken alot of space due to its size.
Anyway, thanks bro! I guess i owe you my phone but i will still be monitoring the phone and see if it'll reboot randomly again... Till i get my laptop ill reflash my phone. Again, thanks alot sandeep!and good luck with your exams again!
RE-EDIT: it not kinda fixed yet... When i woke up and checked my phone it seemed to be normal but when i opened the lockscreen fc's starts flooding me... About 6 or 7 fc's they are google goggles, superuser,titanium backup, google play music, google setup sumthing (it was in the first post..) Emai and.messages... I also get fc on yahoo mail but it doesnt fc the same time as the others. I tries uninstalling rthem and other apps as well but some time while i uninstall it starts to freeze and reboot... But the reboot is different. I doesnt reboot the "samsung galaxy s 19003 " thing. Justs stars from the glowing samsing logo. When it boots, the uninstalled apps seems to come back. So i thought of removing mg sd card and then restart... Fc's lessened to superuser, email tbackup and email. And i can uninstall now without it rebooting. Now i know ext sd cards are somewhat along with the problem. My phones antivirus does not see any viruses in it tho.
... Oh im using my SE W8.. Kinda small, hard to type...
it sounds like a kernel problem to me just update your kernel if you cant because you dont have a laptop just use mobile odin
http://forum.xda-developers.com/showthread.php?t=1347899
Good luck
mR_ said:
it sounds like a kernel problem to me just update your kernel if you cant because you dont have a laptop just use mobile odin
http://forum.xda-developers.com/showthread.php?t=1347899
Good luck
Click to expand...
Click to collapse
Hmm.. I also thought if it could be the kernel as well. I researched last night on my arc and some say that it is the kernel that was doing this.i am downloading the kernel and odin on my new xperia arc as im making this post. Thanks.
Sounds like a hardware problem forme. I have this problem 4 months ago. I have random reboots. I have tried everything from flashing new roms and kernels and nothing seems to fix it. Have you tried clean flashing(xxkpe-xxkpq)? If that still doesnt work then you really have a hardware problem. The only thing you can do is to send it back to samsung service center for repair or replacement(I just hope you are still in warranty period)
earldroid said:
Sounds like a hardware problem forme. I have this problem 4 months ago. I have random reboots. I have tried everything from flashing new roms and kernels and nothing seems to fix it. Have you tried clean flashing(xxkpe-xxkpq)? If that still doesnt work then you really have a hardware problem. The only thing you can do is to send it back to samsung service center for repair or replacement(I just hope you are still in warranty period)
Click to expand...
Click to collapse
Like i said i dont have a laptop yet to reflash phone to stock and check. If it'll not work, im pretty sure they'll change the motherboard.. My warranty expires on july so there is still time. pretty sure my dad will get pissed and buy an s2 instead. This phone already went to the service center twice. And the service center is far from where i live. Though i am enjoying improving the capabilities of this phone :\
Anyway what i did now was flashed uc kernel v10 via odin mobile (thanks mR_ ). Then i wiped everyting again. So far there was no fc's yet and one reboot only when i was installing dolphin browser... And thats it. Nothing else suspicious happened yet.
This problem has happened to my bro before. I helped him change his rom to clean kpu and it was fixed.
Cheers
Sent from my GT-i9003 powered by Smooth and no lag vurrutRom
Looks like the infamous pseudo reset bug again! Well looks like it with some symptoms missing, the i9003 had a faulty board with faulty internal memory card, so when it goes to sleep the int card sometimes doesn't wake up again. I faced this problem personally myself, no amount of flashing can help you (though i suspect excessive flashing might have caused/triggered it, dunno) so make sammy change the board on this bad boy, hey! you might get 16gb inbuilt memory as a bonus!
Wahaha123 said:
Like i said i dont have a laptop yet to reflash phone to stock and check. If it'll not work, im pretty sure they'll change the motherboard.. My warranty expires on july so there is still time. pretty sure my dad will get pissed and buy an s2 instead. This phone already went to the service center twice. And the service center is far from where i live. Though i am enjoying improving the capabilities of this phone :\
Anyway what i did now was flashed uc kernel v10 via odin mobile (thanks mR_ ). Then i wiped everyting again. So far there was no fc's yet and one reboot only when i was installing dolphin browser... And thats it. Nothing else suspicious happened yet.
Click to expand...
Click to collapse
if dad is buying you an s2 then i wont fix it until i get the s2
swerte mo pre ... im so jealous
noypi_ako said:
if dad is buying you an s2 then i wont fix it until i get the s2
swerte mo pre ... im so jealous
Click to expand...
Click to collapse
Di naman. He will pay half for the s2 and ill pay the other half... And prices of s2 here are expensive still. About 27-35 k. I dont have that much money yet.
mzone1510 said:
Looks like the infamous pseudo reset bug again! Well looks like it with some symptoms missing, the i9003 had a faulty board with faulty internal memory card, so when it goes to sleep the int card sometimes doesn't wake up again. I faced this problem personally myself, no amount of flashing can help you (though i suspect excessive flashing might have caused/triggered it, dunno) so make sammy change the board on this bad boy, hey! you might get 16gb inbuilt memory as a bonus!
Click to expand...
Click to collapse
hmm... i hope not. also i dont really flash anything unless updates are available on the ics theme. well now that you mentioned it, while i was at the beach like last week, i put my phone on my pocket without screening of (which i always and should do..) and then when i checked back the all my messages and files in the internal sd card were gone.... though the apps are still there and were still on go launcher ex home..... i hope it was just am accidental reset. i want to bring it to the service center im going to get my laptop in at least 2 days! and i want to spend my summer with both of them.
anyway. is wifi working well on poseidon rom with the uc kernel v10? thats the only problem here. my wifi keeps going on and off. crashing the apps that needs wifi whenever i press it. its the same problem with amit cf root kernel when you use poseidon.
Its real nice to have ICS finally for Galaxy R, But we have found some issues.
List of Issues:
1. MMC_CAP_ERASE is enabled by default (eMMC brick bug).
2. Only Tegra optimized Games are working fine, Other Games are lagging a lot (eg: Temple Run).
3. Pinch to zoom in gallery is lagging.
Hold and drag simply doesn't work. First I thought it was a bug in the TW-launcher, but tried with Apex and the same issue is present. I'm trying to solve this with my kernel.
Adam77Root said:
Hold and drag simply doesn't work. First I thought it was a bug in the TW-launcher, but tried with Apex and the same issue is present. I'm trying to solve this with my kernel.
Click to expand...
Click to collapse
Isn't that related to android framework only? How can it be related to the kernel?
Adam77Root said:
Hold and drag simply doesn't work. First I thought it was a bug in the TW-launcher, but tried with Apex and the same issue is present. I'm trying to solve this with my kernel.
Click to expand...
Click to collapse
Wow great news buddy, so you have started working on custom kernel :good:....
All the best man....
i have no issues till now
everything going smooth
battery even holding more longer much more
mj.vikram said:
2. ICS RAM hungry, so battery drain is bit fast compared to GB.....
Click to expand...
Click to collapse
Yes its RAM usage causes bit more battery drain. But jus wan to iterate the importance of Factory reset for ICS update. Without a Factory reset, the upgrade may FC of some of apps. Apart it wil cause a lot of battery drain too. So always do a factory reset before this upgrade from GB to ICS (It will clear the older battery stats file). Also, at the initial stages, there will be some battery issues as the system will be building the battery stats file. With few days, the battery will be back to normal.
When pushing the screen 2 seconds in xda app (just to reply or say thanks) the screen gets black and unresponsive.
And my baseband is I9103NELA1,is it ok?
mj.vikram said:
Its real nice finally to ICS on my phone, But i have found some issues.
So we will use this thread to discuss the Issues related to ICS, i will update the OP ....
1. When mobile is charging Time and Battery % are not updating on the Lock screen.
2. ICS RAM hungry, so battery drain is bit fast compared to GB.....
Click to expand...
Click to collapse
Hey Vikram,
On my device the Time & Battery is changing fine & still by the time not much battery had drain mine currently rooted with RootRecovery_v4.
mj.vikram said:
Wow great news buddy, so you have started working on custom kernel :good:....
All the best man....
Click to expand...
Click to collapse
I tried with my kernel that I created approx. a week ago for JB. It doesn't work (as I expected) because of the framebuffer changes. This is just a beta build and Sam releases src's after official release so we've to wait.
Indha Lezzio said:
When pushing the screen 2 seconds in xda app (just to reply or say thanks) the screen gets black and unresponsive.
And my baseband is I9103NELA1,is it ok?
Click to expand...
Click to collapse
NELA1 is the baseband that came with austrian XWLA4. According to Machram's post it should be XXLQ3. That's because you just restored a nandroid backup and not did a regular installation process which is required to change modem (basedand/radio). (you can flash the modem via cwm or Odin separately) Restoring backups doesn't affect modem, bootloader (this can be crucial sometimes) .. not sure about sales code.
I'm happy to share that I encountered the first SOD. That could be because of too much of install uninstallation while charging. Yes, it is eating RAM but battery backup is good as gb.
Sent from my GT-I9103
vrajan said:
I'm happy to share that I encountered the first SOD. That could be because of too much of install uninstallation while charging. Yes, it is eating RAM but battery backup is good as gb.
Sent from my GT-I9103
Click to expand...
Click to collapse
man from morning i had thrice but its because of high usage i think , i am trying all the apps and thing which i am seeing on XDA.....
Okay, so I noticed that if you enable the motion feature (Samsung's one), then drag&drop works. It's very smooth with TW UX!!! (Will post a CWM-flashable zip in some moments)
Adam77Root said:
Okay, so I noticed that if you enable the motion feature (Samsung's one), then drag&drop works. It's very smooth with TW UX!!! (Will post a CWM-flashable zip in some moments)
Click to expand...
Click to collapse
waiting for your release....
m.kochan10 said:
NELA1 is the baseband that came with austrian XWLA4. According to Machram's post it should be XXLQ3. That's because you just restored a nandroid backup and not did a regular installation process which is required to change modem (basedand/radio). (you can flash the modem via cwm or Odin separately) Restoring backups doesn't affect modem, bootloader (this can be crucial sometimes) .. not sure about sales code.
Click to expand...
Click to collapse
How to restore baseband only buddy..
Sent from my GT-I9103 using xda premium
Sorry for reposting it here again but I really need to know ... I leave for a weekend trip tonight and want to be carrying a stable build. These are the issues I am facing.
1. Lockscreen doesn't work at all.
2. The music kept pausing frequency on my way to office (AUX cable). Will try earphones soon.
3. A 2 sec press on power just restarts the phone and doesn't give the option to set the phone on vibrate (maybe a feature)
4. I am still getting the wrong baseband in About phone ( did anyone flash modem.bin. where is it?)
Maybe I was half asleep when I flashed it. Will flash it again once I reach home. But i did wipe dat and cache
Is hardware accelerated video decoding working confirmed in ics ..?
Anyone tested ..?
How to confirm ..?
In mx player i am not able to play 1080p video..
It is saying hw not possible..
Sent from my GT-I9103 using xda premium
parajsinghal said:
Sorry for reposting it here again but I really need to know ... I leave for a weekend trip tonight and want to be carrying a stable build. These are the issues I am facing.
1. Lockscreen doesn't work at all.
2. The music kept pausing frequency on my way to office (AUX cable). Will try earphones soon.
3. A 2 sec press on power just restarts the phone and doesn't give the option to set the phone on vibrate (maybe a feature)
4. I am still getting the wrong baseband in About phone ( did anyone flash modem.bin. where is it?)
Maybe I was half asleep when I flashed it. Will flash it again once I reach home. But i did wipe dat and cache
Click to expand...
Click to collapse
Hey Buddy you can try with factory reset option before restore the ICS ....
1. ScreenShot for me is not working with Power+Home Combination. Although @Mj.Vikram Confirmed its working fro him.
2. I cannot Mount Phone as USB Storage with/without USB Debugging On. Only MTP mode is connected every time
maheepmaurya said:
1. ScreenShot for me is not working with Power+Home Combination. Although @Mj.Vikram Confirmed its working fro him.
2. I cannot Mount Phone as USB Storage with/without USB Debugging On. Only MTP mode is connected every time
Click to expand...
Click to collapse
Navigate to 'Settings -> Wireless and Networks -> USB utilities' to use it as a USB storage.
Bout damn time I made a thread
Sent from my SGH-T699 using Tapatalk
It IS about time.
ok so the cm wiki page says to use cwm. any reason i can't use twrp?
Gibson99 said:
ok so the cm wiki page says to use cwm. any reason i can't use twrp?
Click to expand...
Click to collapse
Shouldn't be any reason you couldn't use TWRP. I'm pretty sure nard himself uses it. The CWM was a CM project for a long time, and still the recovery built within it. Everyone pushes their stuff.
been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.
Gibson99 said:
been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.
Click to expand...
Click to collapse
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.
orange808 said:
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.
Click to expand...
Click to collapse
doh, you're right. my point still stands about messaging not matching the rest of cm's theming. i guess they expect people to just use chomp, go, handcent or whatever other app... i like the standard one in cm tho. except for how light it is.
What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?
Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
which build are you on? i'm running cm11-20140608-Snapshot-M7 (which is 4.4.2, not 4.3.3) and have no issues to report so far. i haven't given it a full shakedown yet - still haven't tried BT or GPS but so far so good. watched netflix on the bus this morning and never had an issue. my wife and i text a lot and haven't had issues w/ that either. this evening i'm going to try out BT with my elm327 obd-ii adapter and if i have time, test audio over an avantree cara adapter. i started google maps a couple times and it found me quickly and accurately but i haven't run gps for more than a minute or so at a time so i don't know how it'll do. maybe i'll turn it on while on the bus this afternoon and see if it works well for the whole ride home.
robuser007 said:
What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?
Click to expand...
Click to collapse
I updated ****. we're benefiting vicariously from the d2 kit-kat release
Sent from my Nexus 7 using Tapatalk
After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help
Balthasar85 said:
After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help
Click to expand...
Click to collapse
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk
reaper000 said:
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i second this. my steps were:
1- boot to download mode, install twrp
2- boot to recovery, flash CM
3- while still in recovery, flash gapps if you want them (make sure you have the correct version of gapps from the CM site)
4- still in recovery, wipe cache and dalvik
5- still in recovery, do factory reset
6- reboot normally (it's called 'system' in twrp) and start using phone
note that there is no need to copy/flash SU at any time because CM is already rooted.
using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).
robuser007 said:
using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).
Click to expand...
Click to collapse
Ok. Now, find out what version of cpu you have and get some logs to help them track down your problems.
There's a search box in the corner.
I don't have any of the problems you are describing and I am betting the developers do not, either.
orange808 said:
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?
Click to expand...
Click to collapse
I am on T-Mo, I get this via the default android messaging app as well as hangouts, but I also have times where mobile data refuses to work as well.
Right now, I'm having this issue on 11-20140608-Snapshot-M7-apexqtmo. I did wipe data and cache before I flashed. I'm not sure what is causing my issue.
I am tempted to reflash it back to factory, and take it back under my total care and get it replaced for a S5, but I really like my keyboard. :crying:
did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).
Gibson99 said:
did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).
Click to expand...
Click to collapse
I even tried that too. My phone's about a year and a half old now. I've noticed recently if the keyboard is out, or i'm holding the phone sideways, and I get a call, the phone app crashes over and over till i rotate it upward so the display is vertical, then it stops crashing(all while the phone is still ringing so I can still answer it.)
Hi,
I'm having trouble with my OpO since I rootet it. Here is the history:
-Day One: Just stock 25R, installed all Apps via google play, no problems whatsoever.
-Update 30O still no problems.
-Then I rootet the phone and flashed TWRP recovery to install the Titanium Backups of my old Nexus 4. Thats when I had the first random reboots. Some while Browsing in Chrome, Some on Youtube, Some while listening Music on Hedphones.
Since I have no Sim-Pincode activated a reboot just means, that I'm Offline for about 20 seconds but having that about 5 times a day just isn't acceptable.
-Then I got the 33R OTA update, which made my root and TWRP recovery disappear because I forgot to make a check in the developper settings, but that did not make the reboots disappear
-Today I flashed the 25R stock Image of the Firmware via Fastboot to set my One to real Factory status. I only installed apps via google play and recovered the app data of 2-3 apps via helium backup without root. I got the two OTA updates, and another reboot.
-Then I rootet the thing again, to use a logcat app, and now I have two logcats ending with a reboot.
I really hope that you can help me since I allready sold my old phone and expect that it will take really long until I get a new OpO here in Germany.
The next thing I will do is flash the 25R Image again and install the apps without using helium at all and leave out the goolors icon pack that I used before. But after that I'm absolutely out of ideas.
UPDATE: Yeah so it's definitely a HW defekt or something I cannot solve. I just wiped everything via TWRP, then flashed the factory image 25R without root and just installed some apps via google play. But after one hour I read an email and it rebooted....
Unfortunately I cant post the links to the logcats due to my low post count.
Logcats don't help you when it comes to finding out what is causing your phone to reboot. It is last_kmsg that is responsible for debugging reboots.
A hardware defect would not be causing your phone to reboot, its something to do with the way your phone is configured / set up.
I would highly recommend you to start from scratch completely and do the following,
- Flash XNPH33R http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip from scratch. Make sure you do wipe.
(OR.. flash a custom ROM after wiping)
- List all of the apps that you currently have installed.
- Are you using Xposed?
- Whats your set up? ROM/Kernel/Gapps/etc.
I am not using any custom Rom, root, custom kernel or xposed module.
I just wiped everything in TWRP and flashed the 25R factory image. After about one hour of installing apps in Google play and loging into account i got the first reboot.
I can try flashing the image that you postet tomorrow but thats the same Rom that Im using now
Ord3r66 said:
I am not using any custom Rom, root, custom kernel or xposed module.
I just wiped everything in TWRP and flashed the 25R factory image. After about one hour of installing apps in Google play and loging into account i got the first reboot.
I can try flashing the image that you postet tomorrow but thats the same Rom that Im using now
Click to expand...
Click to collapse
I meant, you can try a custom ROM and see if you can reproduce the problem. Custom ROMs are running on code that is much newer than CM11S.
Ensure you're on XNPH33R when it comes to OTAs.
I just wanted to add my frightful experience. I've had the OPO for two weeks now without problems and no random reboots. Had my first reboot today and just now my phone powered off and wouldn't turn back on. I plugged it back into the wall charger and it turned itself back on but was stuck on the boot logo. I tried holding down the power button to turn it off but nothing. Pressing the power button only turned the display on and off but still stuck on boot logo. Eventually I held down the power button and volume down and the phone buzzed and went to recovery. I'm on stock 33R and Franco's kernel. Haven't tweaked anything. Now I'm afraid my phone is going to brick itself.
Sent from my A0001
Yeah so this is definitely getting worse. At first I had 1-2 reboots a day but today after unplugging I already had 3 reboots in one hour.
I think I am definitely going to send it back when I'm back home next Week.
I already flashed stock Firmware 3 times and did what feels like 10 full wipes in one Week.
This cant be normal. Apps that I installed that arent in the top 50 in the play store are: Dailyme, yatse for xbmc, line, Wolfram aplha and ogyoutube.
That really sucks. I already sold my nexus 4 and have no other phone left
Btw: I'm on 33R for the third time this Werk. Everytime via OTA
Try a different Rom like crDroid + AK Kernel. Running this 2 things since 2 weeks and i only got one reboot just because my camera stopped working because in undervolted my phone ^^
THX but I just want a functioning phone. And since I have errors that nobody else has I think that it is a Hardware issue. At the Moment I am waiting for a answer from one plus so i can send it back
Ord3r66 said:
THX but I just want a functioning phone. And since I have errors that nobody else has I think that it is a Hardware issue. At the Moment I am waiting for a answer from one plus so i can send it back
Click to expand...
Click to collapse
ok I understand your frustration but to fully test your phone you will need to run stock and stock only with no outside apps loaded. Try and do this for a day or half a day or so and see what your results may be. Its your phone and of course do what you like but testing your phone and doing the same thing every time as in reloading your apps is not a good way of fully testing.
also did you do a last_kmsg report as recommended.
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Ord3r66 said:
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Click to expand...
Click to collapse
Yes you need root. After a reboot just pull the last_kmsg file from /proc/ using adb, file Explorer of your choice, etc.
Sent from my One A0001 using Tapatalk
Ord3r66 said:
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Click to expand...
Click to collapse
of course there is a tutorial there is a tutorial for everything.... Got to utilize google my friend.
OKay it's me again. Meanwhile the Oneplus support answered my mails and told me to flash custom Kernels to resolve the issue.
Since Yesterday I tried three Kernels (Franco, Heeroluca and AK) and nothing changed, so now I start to gather some Last_kmsg files name it after the APP where the reboot occured and upload it here. Ofcourse I'm also sending those files to the Oneplus Support
Here is the first one:
https://dl.dropboxusercontent.com/u/43103242/1_Line_Messenger_last_kmsg
https://dl.dropboxusercontent.com/u/43103242/2_standby_screenoff_last_kmsg
Have the same problem. Using wi-fi -> reboot. Don't know how to fix this defect. I hope a solution will be found
Had a random reboot while browsing chrome. I was scrolling down the page and received a text at the same time when my screen froze. After freezing for a few seconds, it rebooted itself. I tried getting the last_kmsg but it tells me that it isn't found. The code I used was: "su" followed with "cat /proc/last_kmsg > /sdcard/last_kmsg.txt" in terminal emulator. Let me know if there is anything else I can do. Thanks!
I have also problems with chome beta browser. I get freezes. Is this issus only with chrome or with all browers?
Gesendet von meinem A0001 mit Tapatalk
A bit of history, I was running KK Cloudy 1.2 for a while with xposed and I'd get a 1 or 2 auto reboots from apps/system crashing. I figured this was probably because KK was old and runnign xposed modules.
Recently I clean flash upgraded to 'D850 20f Stock ROM Debloated' Lollipop ROM by cmulk.
I'm still getting one or two auto reboots a day from system crashing. Is this normal?
Even on other ROMs as a more general question how often does your guys system auto reboot from a crash? How often do you reboot manually?
Just so everyone knows how clean of flash I did...
I went through the process of restoring the factory image using LG Flash Tool and TOT file. Then I immediately stump rooted, flashified TWRP, updated TWRP to latest twrp-2.8.5.1_d850-bumped.zip, wipe in TWRP, installed D850_20F_2.0.1.c1.13-00050_Modem.zip and then Debloated_Stock_20f.zip. Then let PS reinstall apps and configured everything manually. Didn't even do a TB restore.
So is this normal behavior for android? Or just the LG G3? Or just me? Thanks!!!
Too early for me to tell. Installed yesterday morning, clean install. So far in the 24 hours, no rebooting. Only thing thus far is my LED is not signaling as designed.
The clean ROM install is 5K faster with Antutu than KK, and 17K faster than a dirty install of the same 5.01 ROM This was repeated x3 to make sure it was the clean install which made the difference for me... yup.
JeffDC said:
Too early for me to tell. Installed yesterday morning, clean instal. So far in the 24 hours, no rebooting. Only thing thus far is my LED is not signaling as designed.
The clean ROM install is 5K faster with Antutu than KK, and 17K faster than a dirty install of the same 5.01 ROM This was repeated x3 to make sure it was the clean install which made the difference for me... yup.
Click to expand...
Click to collapse
Thanks for the reply. Let me know how it goes. I heard about the led issue some folks are trying to get some logs to debug it.
I went through the process again and this time I installed a lot less apps. I'm going to see if that helps.
I didn't have any random reboots until I installed Trickster.. which was stupid of me since there's no BusyBox on the 20f release by AutoPrime
As soon as I uninstalled it after 1 reboot it hasn't happened again.
So if you've got Trickster or any other Kernel Tweak apps installed.. try uninstalling
Two days, no reboots.
I've been running autoprime's stock 20f with Xposed for a week and a half with not a single random reboot. I'm actually amazed by the performance and stability. Wiped system, cache, and data, flashed ROM, and reinstalled all apps with TB (without app data). Froze all AT&T and some LG apps with TB, and removed CarrierIQ.
Activated Xposed Modules:
AcDisplay
All Notifications Expanded
Amplify
G3 TweaksBox (1.4 beta 2)
GravityBox [LP]
Intelli3G
NotifyClean
Pandora Patcher
Play Store Changelog
Screen Filter
YouTube AdAway
EDIT: Forgot to mention that I wiped system and cache also.
cameronkelley28 said:
I've been running autoprime's stock 20f with Xposed for a week and a half with not a single random reboot. I'm actually amazed by the performance and stability. Wiped data, flashed ROM, and reinstalled all apps with TB (without app data). Froze all AT&T and some LG apps with TB, and removed CarrierIQ.
Activated Xposed Modules:
AcDisplay
All Notifications Expanded
Amplify
G3 TweaksBox (1.4 beta 2)
GravityBox [LP]
Intelli3G
NotifyClean
Pandora Patcher
Play Store Changelog
Screen Filter
YouTube AdAway
Click to expand...
Click to collapse
Similar to you, but also wiped system. Titanium installed apps and data. Only two days old at this point. Is stable so far. Very unlike my past trials with LP ROMs. Glad I waited.
JeffDC said:
Similar to you, but also wiped system. Titanium installed apps and data. Only two days old at this point. Is stable so far. Very unlike my past trials with LP ROMs. Glad I waited.
Click to expand...
Click to collapse
Forgot to include that I wiped system and cache also. So glad I waited as well. It is mind blowing how stable it is, especially with an alpha version of Xposed and so many alpha/beta modules. Just installed the beta versions of Greenify and AppSettings also, so we'll see if that introduces any instability.
After restoring apps with their data, were there any apps that you had to clear data for due to issues? Or have they all been solid?
I had all sorts of random reboots with this phone. It started while I was still running stock kitkat . Things got much better after I reformatted my ext SD card to what ever these devices prefer. I think it's fat 32?
Sent from my LG-D850 using Tapatalk
Thanks for the all replies guys.
So far I'm still averaging about a reboot or two a day since I uninstalled a bunch of apps. I don't have any apps that run regularly besides some gapps and soundcloud. I also uninstalled greenify to see if that helped. I don't have any kernel mods and not running xposed either. Probably the most non-stock thing I'm running is the XCam app. But the phone hasn't crashed while using that app.
It's interesting to hear that some of you haven't had any reboots. Makes me wonder if I have faulty hardware. I guess the only way to find out is to go back to complete stock, take the lollipop OTA update and see if it still crashes. I assume if it did I could get another warranty replacement. I also might as mention this G3 is actually a warranty replacement due to my original phone having a LCD defect.
Also I did wipe system and cache before installing lollipop modem and zip update but thanks for the ideas. Maybe I should try autoprime's stock 20f load but I can't see how that'd be any better/different than cmulks debloated 20f?
Any of you guys know a way to use logcat to capture logs just before the crash? I see there is an app to write logcat out to external SD but the crashes are intermittent so it seems I'd probably fill up my SD card before getting a good trace.
slojam said:
I had all sorts of random reboots with this phone. It started while I was still running stock kitkat . Things got much better after I reformatted my ext SD card to what ever these devices prefer. I think it's fat 32?
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
Thanks slojam I will give this a try tonight.
running cloudy 2.2 without any crashes. Thanks cloudyfa
illusivenick said:
Thanks for the all replies guys.
So far I'm still averaging about a reboot or two a day since I uninstalled a bunch of apps. I don't have any apps that run regularly besides some gapps and soundcloud. I also uninstalled greenify to see if that helped. I don't have any kernel mods and not running xposed either. Probably the most non-stock thing I'm running is the XCam app. But the phone hasn't crashed while using that app.
It's interesting to hear that some of you haven't had any reboots. Makes me wonder if I have faulty hardware. I guess the only way to find out is to go back to complete stock, take the lollipop OTA update and see if it still crashes. I assume if it did I could get another warranty replacement. I also might as mention this G3 is actually a warranty replacement due to my original phone having a LCD defect.
Also I did wipe system and cache before installing lollipop modem and zip update but thanks for the ideas. Maybe I should try autoprime's stock 20f load but I can't see how that'd be any better/different than cmulks debloated 20f?
Any of you guys know a way to use logcat to capture logs just before the crash? I see there is an app to write logcat out to external SD but the crashes are intermittent so it seems I'd probably fill up my SD card before getting a good trace.
Thanks slojam I will give this a try tonight.
Click to expand...
Click to collapse
This is from skeevydude @ http://forum.xda-developers.com/att-lg-g3/development/rom-20f-stock-rom-debloated-t3059610/page13
I'm sure someone will come along who can provide more detail. It does not take long for a log to fill. I did my first few today and an 800K file was about 28 pages long. That is a lot to look through unless you know what to search for.
********************
skeevydude
Anyways, as far as the logs go, the easiest way is by using adb logcat on a PC. Look for guides on how to set all that up....then again, your rooted on LP so that should be done already
The first command to run is "adb logcat *:W >> C:\bootwarn.txt". Enable ADB, power off your phone, plug your phone in to your computer, and let it boot up to the home screen and let it sit there for a minute or two. End the command by using "control+c".
Next, run the command "adb logcat *:W >> C:\notificationwarn.txt" while intentionally doing things that should make your notification light blink -- email yourself, have someone text you a few times, call you, etc. End the command the same way. We need to catch the warnings and errors that are being thrown, so hopefully doing that will help find it.
To help you out on the commands "*:W" tells logcat to only display warnings and up and ">>" tells it to append to a file located where you tell it to be....">" all alone will overwrite a file if it's there.
Anyways, on both those commands, do them twice only changing out the ":W" for ":E" so it'll filter out errors and up.
******************
What worked for me in the first part of his instructions, was to have the command ready/typed into the command prompt on the PC but don't hit the return yet. Then, with the phone off, plug into the computer, wait for the computer to register the phone/acknowledge it, just turn on the phone, and once it starts up press the return key on the PC keyboard to launch the commend. The log will catch things as the phone starts to boot. I tried with the specific directions, but for some reason the PC could not find the device, other than how I detailed here. Just for that first command where the phone is off.
Good luck