Related
Just doing independent research
From 1:10 wonder has boot loop problem
Although you already do flashing well
No kidding, but the characteristic for the phone that possible have a boot loop are always have FORCE CLOSE app and doing RESTART itself
And in next day it restart and only showing samsung logo...
In this situation you can't get to recovery
It can fixed but only if we get stock firmware with wipe and boot loader to fix this issue
Maybe I8150ZSKI3 Android 2.3.6 (ASIA) can helped, all component to do hard reset is in this firmware
OPS– Ancora.ops.
Boot – APBOOT_I8150ZSKI3_CL613004_REV00_user_low_ship_EMM C.tar.md5.
Phone – SMD_MODEM_I8150ZSKI3_CL613004_REV00_user_low_ship_ EMMC.smd.md5.
PDA – SMD_PDA_I8150ZSKI3_CL613004_REV00_user_low_ship_EM MC.smd.md5.
CSC – SMD_CSC_GT-I8150-MULTI-CSC-OZSKI3_EMMC.smd.md5
I will try it first.. i will report latter
Reported..
Still have no change to bring that phone back to live -_-
Anyone..
Can help regarding this issue
Rio Saputro said:
Reported..
Still have no change to bring that phone back to live -_-
Anyone..
Can help regarding this issue
Click to expand...
Click to collapse
Sorry, I can't help, but in my flashing thread, it has also been reported. But I think it happens more often on phones with asian firmwares. I had one report in the german forum too, but I am not sure if it was an "asian" version.
I think if something happens while the firmware update with an asian firmware, it might end up in a bootloop. I am not sure, but I think it makes also the partitioning of the storage, isn't ?
It would be good if we could get a "gettogether" in this thread and have all the reports of the soft-/hardbricked SGWs. So we can analyse and maybe find out the reason or atleast narrow down the issue.
I would like to know:
1. Did you have a custom rom before the flash ?
2. Was your phone rooted ?
3. Did you make the internal/external swap ?
4. Did ODIN say PASS before you disconnected(before the bootloop happend) ?
5. Any other fancy modifications you have done and what we should know ;-D ?
greets
THE-E
THE-E said:
Sorry, I can't help, but in my flashing thread, it has also been reported. But I think it happens more often on phones with asian firmwares. I had one report in the german forum too, but I am not sure if it was an "asian" version.
I think if something happens while the firmware update with an asian firmware, it might end up in a bootloop. I am not sure, but I think it makes also the partitioning of the storage, isn't ?
It would be good if we could get a "gettogether" in this thread and have all the reports of the soft-/hardbricked SGWs. So we can analyse and maybe find out the reason or atleast narrow down the issue.
I would like to know:
1. Did you have a custom rom before the flash ?
2. Was your phone rooted ?
3. Did you make the internal/external swap ?
4. Did ODIN say PASS before you disconnected(before the bootloop happend) ?
5. Any other fancy modifications you have done and what we should know ;-D ?
greets
THE-E
Click to expand...
Click to collapse
My team already try for asian rom that you provide in your tread and the new version of stock rom. it didn't do full wipe just normal flash like the others
Only stock rom & rooted bro...
PASS but the phone not turn on -_-"
No swap partitions
Just regular phone for daily use
If we can found the stock rom with wipe and bootloader still can be fixed
Hopefully it can be fixed without go to samsung -_-
All of us must aware for this issue bro..
Regards
Rio Saputro said:
My team already try for asian rom that you provide in your tread and the new version of stock rom. it didn't do full wipe just normal flash like the others
Only stock rom & rooted bro...
PASS but the phone not turn on -_-"
No swap partitions
Just regular phone for daily use
If we can found the stock rom with wipe and bootloader still can be fixed
Hopefully it can be fixed without go to samsung -_-
All of us must aware for this issue bro..
Regards
Click to expand...
Click to collapse
I have edited my thread, it makes people now more alert about the risk of bricking.
Maybe it is more secure always wiping everything using ClockWorkMod:
Using this course of action:
1. Backup everything manually what you can!
2. Flash via ODIN ClockWorkMod Recovery on your device(english). Scroll down to other and select ClockWorkMod.
3. Once ClockWorkMod is flashed, go to the recovery:
a) backup and restore -> backup to external sdcard
b) backup and restore -> restore from external sdcard
This is to make sure the files aren't corrupted, if this is successful you can be sure everything is backupped. If you get a MD5 mismatch something went wrong. Try again!
c) wipe data/factory reset -> confirm
d) wipe cache partition -> confirm
e) mounts and storage -> format system -> confirm
f) mounts and storage -> format cache -> confirm
g) mounts and storage -> format data -> confirm
4. You restart your phone in Download Mode and flash a firmware using this instruction, which is provided in the thread under Firmwares.
5. Now you will have to flash again the ClockWorkMod recovery to restore your data.
Than open ClockWorkMod Recovery and:
backup and restore-> advanced restore from external sdcard -> select the backup -> Restore data -> confirm.
Now if you want the stock recovery back(needed for OTA updates) instood of ClockWorkMod, than go to the Others or Sonstiges and select the stock recovery, and flash it on your device.
6. Now you should have a fresh device like you have never flashed before!!!
Oh yeah, the reason why you have to make these complicated steps: Because you were flashing all different kinds of firmwares, you system will be a mess. To make sure your device is not a overwritten old firmware these steps are necessary.
Flashing via ODIN does not delete all old data !!!
I have to say also: I have flashed all the ROM's successfully before posting them in my thread about flashing.
greets
THE-E
Is it not important to say that the guy in original thread here:
http://forum.xda-developers.com/showthread.php?p=22560826
He had installed Rio's Black Note 2 ROM using CWM to do Nandroid Restore.....as is Rio's method to flash his ROM ???
Maybe is not important, but maybe is!!!
Sent from my GT-I8150 on Lanzarote Canary Vacation using Tapatalk
irishpancake said:
Is it not important to say that the guy in original thread here:
http://forum.xda-developers.com/showthread.php?p=22560826
He had installed Rio's Black Note 2 ROM using CWM to do Nandroid Restore.....as is Rio's method to flash his ROM ???
Maybe is not important, but maybe is!!!
Sent from my GT-I8150 on Lanzarote Canary Vacation using Tapatalk
Click to expand...
Click to collapse
Yes he already inform this...
But the question why just only him that get boot lop, this is kind a strange because another user didn't face the problem like this
His problem happened after applying V6 SC
I know that V6 SC update 9 RC6 have a change for boot lop, because for applying 100% must integrated built.prop
So many friend of my use V6 SC update 9 RC4 that more stable for our phone
Actually there is nothing different if we flash with nandroid and update.zip
The script doing same thing except for the user data
nandroid use md5 for more safety flashing
Like i wrote before..
Before this happen the phone always do restart it self
I hope there is any progress for prevent and fix this issue
The user that have this problem, now must go to Samsung to fix it before we know how to fix it
Regards
I'd like to say this sudden restart happen to me quite often while in stock rom, but after I flash custom rom this phenomenon never happen again. This phenomena only happen while I'm on stock rom.
Sent from my GT-I8150 using XDA App
Update for this..
My friend reported..
For my country, we get FULL WARRANTY for this case
and waiting this status until fixed about 2 days
For the first phase they do regular Flashing with STOCK ROM based on country
then it still cannot on (we know already -_-)
We didn't sure yet is the phone will be change with the new one or not because this had implication from hardware issue..
Come back latter..
Rio Saputro said:
Update for this..
My friend reported..
For my country, we get FULL WARRANTY for this case
and waiting this status until fixed about 2 days
For the first phase they do regular Flashing with STOCK ROM based on country
then it still cannot on (we know already -_-)
We didn't sure yet is the phone will be change with the new one or not because this had implication from hardware issue..
Come back latter..
Click to expand...
Click to collapse
same problem with my devices , after flash cwm and use GingerIce Rom my device cant boot again.
im tried Oneclick Unbrick : http://forum.xda-developers.com/showthread.php?p=15330252#post15330252
but still problem
flowish said:
same problem with my devices , after flash cwm and use GingerIce Rom my device cant boot again.
im tried Oneclick Unbrick : http://forum.xda-developers.com/showthread.php?p=15330252#post15330252
but still problem
Click to expand...
Click to collapse
Hi Bro...
We don't know yet how to fix it.
Update for this,
Samsung do spare part / hardware changes for this case. It probably cause not only by flashing but hardware also
BTW now i have 1 Wonder and 1 Wonder at Samsung center (i mean both are my friend phone ). ETA for fixing this is 3 days
And my friend want me to re write black notes chapter 3
It will come next week
Come back latter
Rio Saputro said:
Hi Bro...
We don't know yet how to fix it.
Update for this,
Samsung do spare part / hardware changes for this case. It probably cause not only by flashing but hardware also
BTW now i have 1 Wonder and 1 Wonder at Samsung center (i mean both are my friend phone ). ETA for fixing this is 3 days
And my friend want me to re write black notes chapter 3
It will come next week
Come back latter
Click to expand...
Click to collapse
yeah , my wonder goto SSC now
Update for this,
Finally SGW come out from hospital
The problem cause not from FLASHING but from HARDWARE
Samsung must change the MAINBOARD for this problem
If this problem happened to you
Don't blame yourself or the Developers
Don't try to fix or figure this out by your self
Go to Samsung to Fix it
Regards
Rio Saputro said:
Update for this,
Finally SGW come out from hospital
The problem cause not from FLASHING but from HARDWARE
Samsung must change the MAINBOARD for this problem
If this problem happened to you
Don't blame yourself or the Developers
Don't try to fix or figure this out by your self
Go to Samsung to Fix it
Regards
Click to expand...
Click to collapse
They change your Mainboard???
No questions?????
Very good result Rio!!!!
Is there a thread outlining what the symptoms of this particular Boot loop problem are.....
Maybe this post in this thread.....from THE-E....
http://forum.xda-developers.com/showthread.php?p=22744322
it should be stickied!!!!!
How to do that here, who request to???
Not enough stuff getting stickied here, peeps have to trawl thro' full forum to find answers to sometimes repeated questions??
But important stuff certainly should be "stickied".
Anyone else agree....and how to get a result on this???
Sent from my GT-I8150 on Lanzarote Canary Vacation using Tapatalk
irishpancake said:
They change your Mainboard???
No questions?????
Very good result Rio!!!!
Is there a thread outlining what the symptoms of this particular Boot loop problem are.....
Maybe this post in this thread.....from THE-E....
http://forum.xda-developers.com/showthread.php?p=22744322
it should be stickied!!!!!
How to do that here, who request to???
Not enough stuff getting stickied here, peeps have to trawl thro' full forum to find answers to sometimes repeated questions??
But important stuff certainly should be "stickied".
Anyone else agree....and how to get a result on this???
Sent from my GT-I8150 on Lanzarote Canary Vacation using Tapatalk
Click to expand...
Click to collapse
This thread and The-E thread must be stick because now the problem occur much often...
So we can inform the others Galaxy W users
Regards
thanks for your update... which mean Im having same problem too here... need to send this phone to SSC... Huh! (
same problem here, my friend sgw had bootloop from unknown reason, have try flashing with ASIA firmware but have no result (before i read this thread) thanks for op, this must be sticky..
will go to ssc now :hammer
same problem as well
stuck at samsung logo and just keep reboot reboot and reboot
already bring to SSC few days ago they say will change board
now just waiting the phone to be back
Guys, i bought one Wonder from eBay and its with thos problem now.. any change of fixing it without going to samsung assistance?
gajodafeira said:
Guys, i bought one Wonder from eBay and its with thos problem now.. any change of fixing it without going to samsung assistance?
Click to expand...
Click to collapse
A little late in reading this post but I also bought my Galaxy W from Ebay. Samsung user agreement states that the phone is guaranteed for 2 years after the date of sale and the agreement is transferable between owners. In other words it doesn't matter who originally bought it but is guaranteed for 2 years and our phone is still less than 2 years old. I know this as had to send mine back and they accepted it.
My sgw restarts automatically for 2 or 3 sec. And sometimes after restarts it shows at far down left (safe mode)... So
Whats happening? is it a hardware problem?
Sent from my GT-I8150 using xda premium
mohza said:
My sgw restarts automatically for 2 or 3 sec. And sometimes after restarts it shows at far down left (safe mode)... So
Whats happening? is it a hardware problem?
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
Stock ROM or customed ?
Stock rom , then phone works normally but restarts after 2 or 3 days for example
Sent from my GT-I8150 using xda premium
I have this problem too. This happened with black notes and cow v7. However, it is less frequent now.
If it's stock rom, you could have it check to your nearest samsung service center.
i.am from indonesia and after upgrade stock rom I8150DXLC1 in march 30th i have this isue too, what happen with this room?
we can't go to samsung because there is no proove .. this is happen any time some times 2 or 3 times rebooting still cant go to normal mode, and i must pull out battery or quicly press power button to shut down then press power again to have a normaly boot, for info i use a Apach*r sdhc 8GB class 10 any problem with that maybe ?
btw sorry for my bad english
artfelin1 said:
i.am from indonesia and after upgrade stock rom I8150DXLC1 in march 30th i have this isue too, what happen with this room?
we can't go to samsung because there is no proove .. this is happen any time some times 2 or 3 times rebooting still cant go to normal mode, and i must pull out battery or quicly press power button to shut down then press power again to have a normaly boot, for info i use a Apach*r sdhc 8GB class 10 any problem with that maybe ?
btw sorry for my bad english
Click to expand...
Click to collapse
Try to re-flash the ROM again. Use CWM to wipe data and cache then use ODIN to flash the Stock ROM again.
I too am suffering from random restarts. I am running stock rom unrooted
PDA: I8150TDULA4
PHONE: I8150TDULA2
CSC: I8150TVAULA1
I have tired wiping the cache, reformatting the external SD card, doing a factory reset, no luck to all. Depending on phone usage will depend on how many restarts I get per day.
I have even tried to capture the logs with alogrec to see if I could find the culprit, but it doesn't seem to point to anything specific, the only error I seem to get (from my review of the logs) just before the restart is:
"W/dalvikvm(17668): threadid=20: thread exiting with uncaught exception (group=0x4001e578)"
I was hoping to reflash the ROM, but can't locate the ROM anywhere, was wondering if anyone had a copy?
Any help with the ROM or suggestions would be appreciated.
Thanks
On my device, it was a ram problem, when i played with the last three switches in a ram manager (hidden, content, empty) the cycles between a reboot changed. Found the most stable settings with adjusting the switches like a staircase, every ram-switch as minimal as possible.
Delmare said:
On my device, it was a ram problem, when i played with the last three switches in a ram manager (hidden, content, empty) the cycles between a reboot changed. Found the most stable settings with adjusting the switches like a staircase, every ram-switch as minimal as possible.
Click to expand...
Click to collapse
Hmmm one shouldn't have to mess around with ram manager. I hope someone has a copy of the latest VAU firmware so I can reflash the phone to rule that out.
Try here for march 2012 Indonesian Rom
http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-I8150&r=2#regiona
andyvbrown said:
I too am suffering from random restarts. I am running stock rom unrooted
PDA: I8150TDULA4
PHONE: I8150TDULA2
CSC: I8150TVAULA1
I have tired wiping the cache, reformatting the external SD card, doing a factory reset, no luck to all. Depending on phone usage will depend on how many restarts I get per day.
I have even tried to capture the logs with alogrec to see if I could find the culprit, but it doesn't seem to point to anything specific, the only error I seem to get (from my review of the logs) just before the restart is:
"W/dalvikvm(17668): threadid=20: thread exiting with uncaught exception (group=0x4001e578)"
I was hoping to reflash the ROM, but can't locate the ROM anywhere, was wondering if anyone had a copy?
Any help with the ROM or suggestions would be appreciated.
Thanks
Click to expand...
Click to collapse
Ultimate BackUp free [from JRummy] has a fix permissions option.....
this may sort out your random re-boots.
But, you need Root to use this....have you rooted, or do you want to?
It [rooting] can be done from Stock Recovery....check THE-E posts/tutorials.
irishpancake said:
Ultimate BackUp free [from JRummy] has a fix permissions option.....
this may sort out your random re-boots.
But, you need Root to use this....have you rooted, or do you want to?
It [rooting] can be done from Stock Recovery....check THE-E posts/tutorials.
Click to expand...
Click to collapse
Phone is currently unrooted, but am considering rooting it.
I don't think this is a permissions isuue. I'm curious to understand why you think it is?
thanks
andyvbrown said:
Phone is currently unrooted, but am considering rooting it.
I don't think this is a permissions isuue. I'm curious to understand why you think it is?
thanks
Click to expand...
Click to collapse
No particular reason specific to your device...
it is just one of those routine Android fix things, which don't hurt, but are recommended to sort out FC issues, and random re-boots.....
Here is Cyanogen's little write-up on fix permissions
It may not fix your problem, but it just may!!!
And if it does, great......but if it doesn't nothing lost, and another thing done!!
In your position, I would give it a try, either from CWM or with the App I recommended, which can do lot's more, even for free, like zipalign, and full back-up and restore Apps, cache clean, etc.
Rooting guide from THE-E....recommended via Stock Recovery!!
irishpancake said:
No particular reason specific to your device...
it is just one of those routine Android fix things, which don't hurt, but are recommended to sort out FC issues, and random re-boots.....
Here is Cyanogen's little write-up on fix permissions
It may not fix your problem, but it just may!!!
And if it does, great......but if it doesn't nothing lost, and another thing done!!
In your position, I would give it a try, either from CWM or with the App I recommended, which can do lot's more, even for free, like zipalign, and full back-up and restore Apps, cache clean, etc.
Rooting guide from THE-E....recommended via Stock Recovery!!
Click to expand...
Click to collapse
Irishpancake,
Thanks for the information, I'll look into these and give them a try. Still hopeful that someone has the ROM....
Cheers
---------- Post added at 07:27 AM ---------- Previous post was at 07:22 AM ----------
Also further errors related to my restarts from the phone logs shows:
D/LockscreenWallpaperUpdater(30999): onResume()
D/LockscreenWallpaperUpdater(30999): get drawable (public)
D/LockscreenWallpaperUpdater(30999): get drawable (keygurardupdatemonitor private get)
D/LockscreenWallpaperUpdater(30999): drawable is null(keygurardupdatemonitor private get)
D/LockscreenWallpaperUpdater(30999): set drawable
D/LockscreenWallpaperUpdater(30999): wallpaper file exist
D/dalvikvm(30999): GC_EXTERNAL_ALLOC freed 89K, 34% free 9177K/13703K, external 51441K/51717K, paused 76ms
E/dalvikvm-heap(30999): 768000-byte external allocation too large for this process.
E/GraphicsJNI(30999): VM won't let us allocate 768000 bytes
D/dalvikvm(30999): GC_FOR_MALLOC freed 0K, 34% free 9177K/13703K, external 51441K/51717K, paused 68ms
D/skia (30999): --- decoder->decode returned false
W/dalvikvm(30999): threadid=21: thread exiting with uncaught exception (group=0x4001e578)
D/GLSurfaceViewGroup( 6251): Skipped drawing due to suspendDrawingUntilResume()
E/ (30999): Dumpstate > /data/log/dumpstate_sys_error
E/AndroidRuntime(30999): *** FATAL EXCEPTION IN SYSTEM PROCESS: WindowManagerPolicy
E/AndroidRuntime(30999): java.lang.OutOfMemoryError: bitmap size exceeds VM budget
andyvbrown said:
I too am suffering from random restarts. I am running stock rom unrooted
PDA: I8150TDULA4
PHONE: I8150TDULA2
CSC: I8150TVAULA1
I have tired wiping the cache, reformatting the external SD card, doing a factory reset, no luck to all. Depending on phone usage will depend on how many restarts I get per day.
I have even tried to capture the logs with alogrec to see if I could find the culprit, but it doesn't seem to point to anything specific, the only error I seem to get (from my review of the logs) just before the restart is:
"W/dalvikvm(17668): threadid=20: thread exiting with uncaught exception (group=0x4001e578)"
I was hoping to reflash the ROM, but can't locate the ROM anywhere, was wondering if anyone had a copy?
Any help with the ROM or suggestions would be appreciated.
Thanks
Click to expand...
Click to collapse
Download
I8150TDULA4 / 2.3.6 / January 2012 / I8150TVAULA1 / Australia (Vodafone)
I got the same problem! I'm in Indonesia too. Is that because the Rom?
same here
Hi ,
We have 2 of these in our family , both on 2.3.6 stock (UK latest version) updated by Kies , can restart twice a day or once a week - very puzzling have asked samsung and I am waiting a reply
cheers
Dear Users...this happened to me also after flashing Rebel Rom Milestone 2...i got random reboots after normal usage of about 120+ hours...i flashed XXLM8 with Odin in order to get rid of this problem...but no luck...finally i fixed permissions from CWM recovery...then as far as i know...it didnt reboot...i saw my running apps for about many many hours without any restarting of timer..i also switched to other xxlm8 based custom ROM (FAW Rls 2) but just didnt notice rebooting again...only now my phone stucks and reboots when i play hd games continuously.... that's because of Ram shortage...i advise to install only Roms without bugs...and make wipe of everything before flashing...and fixing permissions after switching to a new ROM...also clearing RAM once before playing games...Good Luck!
Sent from my GT-I8150
I experienced this issue too when I firstly bought the phone. Did you update it to the latest version? The problem is fixed for me after updating the update before value pack (sorry I forgot its name).
Hope it helps and sorry for my bad English
Hi guys,
I am using a Sony Ericsson Xperia Arc and am having a lot of trouble with the device constantly crashing and rebooting.
when this first happened these are the steps i took.
i completely wiped the device (factory reset, wipe dalvik cache, wipe cache partition, format system)
i then flashed Baseband 77 using flashtool
i then flashed fxp149 using flashtool
i then flashed Baseband 77 libs using CWM
i then flashed AOKP JB M1-R1 ROM using CWM
i then flashed gapps using CWM
i the reloaded all apps from the market and not applied any backups and yet it still rebooted all the time.
Since then i have tried using
Fusion 3.8
Fusion 3.9
Fusion 4.0
FXP 148
FXP 150
Stock Kernel inside ROM .zip file.
I have also tried putting it back to Baseband 72 but it made no difference.
None of these make any difference to my issue and yet before i had the issue, I had used all of these kernels except FXP 150 and they all worked fine with no issues at all.
I then decided to go all the way back to stock firmware as it is out of the box.
so I used flashtool and flashed LT18i_4.1.B.0.587_(1254-2716).ftf
I reloaded my applications and monitored the device only to see that by the next day, the problem had returned.
I am now at the end of my tether and do not know what else i can possibly do to figure out the issue.
the device has not been dropped or damaged in any way so there is no reason for a hardware fault.
i desperately NEED this device to be working as i use it on a daily basis for my business and cannot live with out it.
IF THERE IS ANYONE OUT THERE THAT COULD PLEASE PLEASE PLEASE HELP I WOULD BE FOREVER IN YOUR DEBT!!!!!!!
i also have a logcat that i was running in the background when one of the reboots happened
not sure if that can tell anyone anything but i have it if it does
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
XperienceD said:
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
Click to expand...
Click to collapse
thanks for the suggestion but my battery is not loose and i have tried your method but with the same results.
weaselmetal said:
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Click to expand...
Click to collapse
hmmm i thought if that were the case there would be others experiencing it too.
i will take your idea and post results.
thank you very much
rod555 said:
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
Click to expand...
Click to collapse
i tried this, unfortunately i had the same issues occurring.
thank you for your suggestion
Needs a trip to the Service Centre then by the sounds of it.
XperienceD said:
Needs a trip to the Service Centre then by the sounds of it.
Click to expand...
Click to collapse
yes i am starting to think that may be my next move
will i have an issue with getting it repaired since i have unlocked my bootloader, flashed different kernels and roms and rooted the device?
if so, is there any way i can get it back to official "out of the box" state?
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
tangosierra_ said:
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
Click to expand...
Click to collapse
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
plastic_prophet said:
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
Click to expand...
Click to collapse
Here:- http://forum.xda-developers.com/showthread.php?t=1324703
Sent from my LT15i using xda premium
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
plastic_prophet said:
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
Click to expand...
Click to collapse
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
lalek said:
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
Click to expand...
Click to collapse
if you open a terminal session and type:
su
cd sdcard
logcat >> logcat.txt
it will create a .txt file and put the live logcat info into it.
you need to leave the terminal running in the background to make sure it continues to update
then when you see a reboot just get the logcat.txt file from the sd card and open it in wordpad or something. (notepad doesnt display properly)
have a look at the last thing that happened before the reboot and see what it tells you
mine had info about wifi scanning and showed that it had seen ssids
next step was to turn wifi off to see if the problem stayed or resolved.
good luck!! id love to hear how it goes
I'm using Snipers PACMAN, and battery just seems to drain way to fast. It is the latest push. Being newly registered on here I hate to introduce my self this way but I need advice. What tweaks are being used by people for the SPH-D710 to help with this issue? I originally started with the CM 10.1 rom and found I had no data, flashed a different modem. Still no data, switched roms and now have data....go figure! But the battery drain is killing me, I've got it throttled back as far as I can go and it still be a daily driver. So anyone have any suggestions?
Godlys Comadose Tweak pack works great:thumbup:
Give it a shot and thank him while you're over there...here's the link
http://forum.xda-developers.com/showthread.php?p=39080082
OK....now I'm lost as to which to try and use.....reading the posts to the provided links seems to give contradictory information as to where to start this journey.....
Sent from my SPH-D710 using xda premium
Most 4.2 Roms use ICS modems. As for battery us betterbatterystats found here on xda or gsam in the play store to determine if there's any rogue apps keeping the phone from sleeping. I also do manual syncing. Greenify is a great app to keep apps from running on their own. You can also use a custom kernel to limit max frequency and even undervolt. Kernels also come with different governors
Sent from my SPH-D710 using Tapatalk 2
godzilla61 said:
OK....now I'm lost as to which to try and use.....reading the posts to the provided links seems to give contradictory information as to where to start this journey.....
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Try the latest version....2.1
Anybody on this thread know anything about the pegasusq governer or how to implement it/install it?
rapman543 said:
Anybody on this thread know anything about the pegasusq governer or how to implement it/install it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=24233103&postcount=3
Read...Read...Read
After reading through the above posts you should have some useful ideas about what this governor does.Also...as for installing a governor, they will be included in the kernel that flashed with ur rom or a kernal of ur choosing(MAKE SURE IT WILL WORK WITH THE ROM YOU HAVE) Im new to this, so if there is another way I dont know about it. Do ur research... As for setting a governor.. There are many roms with built in performance controls as well as many apps to set them. I suggest (set cpu) . It has a setting that will make a zip so u can recover from ur settings if u bootloop. This is found after u install and give it root permission. Hit ur menu button and click SAFE MODE. You should have a nandroid; always and just because.I hope this helps.. Remember...Read...Read...Read..lol.. Good Luck.Also read this http://forum.xda-developers.com/showthread.php?t=2005306
Gil81 said:
http://forum.xda-developers.com/show...03&postcount=3
Read...Read...Read
After reading through the above post you should have some useful ideas about what this governor does.Also...as for installing a governor, they will be included in the kernel that flashed with ur rom or a kernal of ur choosing(MAKE SURE IT WILL WORK WITH THE ROM YOU HAVE) Im new to this, so if there is another way I dont know about it. Do ur research... As for setting a governor.. There are many roms with built in performance controls as well as many apps to set them. I suggest (set cpu) . It has a setting that will make a zip so u can recover from ur settings if u bootloop. This is found after u install and give it root permission. Hit ur menu button and click SAFE MODE. You should have a nandroid; always and just because.I hope this helps.. Remember...Read...Read...Read..lol.. Good Luck.
Click to expand...
Click to collapse
+1
You identify yourself as "new to this" but you nailed this post 110%!! Many people would do well to take what you said here to heart. If they did there would be MANY fewer "help me" threads.
CyberpodS2 said:
+1
You identify yourself as "new to this" but you nailed this post 110%!! Many people would do well to take what you said here to heart. If they did there would be MANY fewer "help me" threads.
Click to expand...
Click to collapse
Thank You...... I went ahead and added another link for him to read. I hope it helps. As to what you said, I like to think of myself as the poster child for the search button..lol..I think if you do the research it makes you feel better when it works and it is more likely to stick with you. This site is so great about that because there is just so much knowledge here to learn.I think some people get over-whelmed by it though or they are just unsure and need that go ahead push to know it works.
Ok since I can't ask a Dev a question about the kernel I want to install.....which I kinda understand, but being stuck not being able to ask questions about something specific after reading all the pages blows! (rant off) [Kernel] Lightning Zap! Phase 4 Updated 15JUN13 is causing a boot loop, I followed all the instructions to the letter, crossed every T, dotted all the I's. Thank god for backup! Since I can't ask the Dev a question I'm stuck!
godzilla61 said:
Ok since I can't ask a Dev a question about the kernel I want to install.....which I kinda understand, but being stuck not being able to ask questions about something specific after reading all the pages blows! (rant off) [Kernel] Lightning Zap! Phase 4 Updated 15JUN13 is causing a boot loop, I followed all the instructions to the letter, crossed every T, dotted all the I's. Thank god for backup! Since I can't ask the Dev a question I'm stuck!
Click to expand...
Click to collapse
Well, you're commenting on a thread about battery life, but not posting about battery life. That's not going to help you much.
I also read that you want to ask a question, but I don't see a question in your post. If you do have a question, a great place to post it would be here: [Official] One Stop FAQ Thread - Noob Friendly (All questions go here). Okay? :good:
erikalin said:
Well, you're commenting on a thread about battery life, but not posting about battery life. That's not going to help you much.
I also read that you want to ask a question, but I don't see a question in your post. If you do have a question, a great place to post it would be here: [Official] One Stop FAQ Thread - Noob Friendly (All questions go here). Okay? :good:
Click to expand...
Click to collapse
Well let me clarify it for you, it's my thread. The original question is still valid being as I was pointed this direction by a reply to my original post. Let me lessen your confusion on this matter......What other steps can I take to increase battery life......scripts didn't seem to help and a tweaked kernel put me in a boot loop....and whom do I ask if not the DEV?
godzilla61 said:
Well let me clarify it for you, it's my thread. The original question is still valid being as I was pointed this direction by a reply to my original post. Let me lessen your confusion on this matter......What other steps can I take to increase battery life......scripts didn't seem to help and a tweaked kernel put me in a boot loop....and whom do I ask if not the DEV?
Click to expand...
Click to collapse
Hey bro, easy on the tone. Because there are so many ways to ask the question, the best way is to just spell it out how you did above. Battery life depends on the apps/ROM/user all at the same time. I am on Project X ROM. It has Crossbreeder installed. Now I am not no where informative about that app other than a lot of people like it. So with that being said and it is installed on the ROM, I leave it. I also have ROM Toolbox Pro. I have adjusted my CPU control to 1000MHZ. I also have DS Battery Saver Pro set to custom and to kill all apps when the screen goes off. Last the ROM I am on comes with Greenify. A great app in saving battery. I also turn off data and only have WIFI on when I need it. No need to just let things run. With that I have had 50% battery life left after 11 hrs. That is my setup and may not work for you. The main thing is to understand that battery life for EACH phone is different no matter how many common denominators people may have. Team Venum did a comparison of ROM's and their respective battery life. I don't know the post, but if you type "battery life" in the search, then I am sure you can find it. As for you response, I was in your shoes at one time. It does help to be specific in your questions. Not saying that you weren't. Reading each and every post will get tiresome, but if you type in what you want in the search, you will get a slew of post to get info. I have only been a member for 4 months, but I have learned how to flash a ROM, Mods, push and app, setup custom home screen. I have even been given the honor of testing a ROM. If you still need help, you can PM me and I will do what I can. Have a great one.
godzilla61 said:
Ok since I can't ask a Dev a question about the kernel I want to install.....which I kinda understand, but being stuck not being able to ask questions about something specific after reading all the pages blows! (rant off) [Kernel] Lightning Zap! Phase 4 Updated 15JUN13 is causing a boot loop, I followed all the instructions to the letter, crossed every T, dotted all the I's. Thank god for backup! Since I can't ask the Dev a question I'm stuck!
Click to expand...
Click to collapse
Its fine,you can rant here...lol..Ok ,I need more info.....
rom you're try to use with lz kernal
how you went about flashing said kernel
did you have any other tweaks or mods flashed before flashing lzp_4
All of this info is important, so I can tell you what is wrong....Thanks..
Gil81 said:
Its fine,you can rant here...lol..Ok ,I need more info.....
rom you're try to use with lz kernal
how you went about flashing said kernel
did you have any other tweaks or mods flashed before flashing lzp_4
All of this info is important, so I can tell you what is wrong....Thanks..
Click to expand...
Click to collapse
Thanks Gil, this is exactly what I have done.
1. flashed from 4.03 to WILD-FOR-THE-NIGHT-07052013-d710, had no data....tried to find a fix for that...gave up after trying tweaks to help with the battery issue and no data.
2. Clean install of d710_PAC_JB_4.2.2-v23.0.0_20130719-015400, now have intermittent data, wifi works, blutooth works, flashed Fl24 modem with no apparent improvement in data connectivity, thought after reading a kernel flash might fix issues, here comes the boot loop....flashed smdk4412_p4 waited patiently for 2hrs watching Pacman chasing ghosts.....booted into recovery and ran my backup tried it 2 more times on clean flashs gave up after 5 hrs. By clean I mean wipe/reset, wipe cache, wipe dalvik, install from zip.
3. this is how I installed the kernel:
Make a backup
Download .zip to PC
Transfer .zip to sdcard
Reboot to recovery
Flash
Phone automatically rebooted after install
waited and waited......boot back into recovery. restore by backup.
everything has been done with CWM based recovery. I'm stumped....frustrated to no end......
godzilla61 said:
Thanks Gil, this is exactly what I have done.
1. flashed from 4.03 to WILD-FOR-THE-NIGHT-07052013-d710, had no data....tried to find a fix for that...gave up after trying tweaks to help with the battery issue and no data.
2. Clean install of d710_PAC_JB_4.2.2-v23.0.0_20130719-015400, now have intermittent data, wifi works, blutooth works, flashed Fl24 modem with no apparent improvement in data connectivity, thought after reading a kernel flash might fix issues, here comes the boot loop....flashed smdk4412_p4 waited patiently for 2hrs watching Pacman chasing ghosts.....booted into recovery and ran my backup tried it 2 more times on clean flashs gave up after 5 hrs. By clean I mean wipe/reset, wipe cache, wipe dalvik, install from zip.
3. this is how I installed the kernel:
Make a backup
Download .zip to PC
Transfer .zip to sdcard
Reboot to recovery
Flash
Phone automatically rebooted after install
waited and waited......boot back into recovery. restore by backup.
everything has been done with CWM based recovery. I'm stumped....frustrated to no end......
Click to expand...
Click to collapse
First off...I have had the lzp_4 boot loop on me. I pulled the battery,waited about 2 min. Put it back in and booted to recovery. Then I wiped cache and dalvik. Rebooted and it took off(booted fine). I have no idea why or how, but this worked for me. Now to my main concern. If you came straight from ics to a jb rom I think this is going to cause you issues, if you hadn't been on jb before. I suggest the one - click full restore(it wipes data,so back-up you're internal memory).This will get you're phone partition right for jb. After this. I think you should be able to flash what you want with no problems. I didn't see a problem with how you flashed. Wipe cache and dalvik on the kernal flashes you do.Here's the link for the one -click..
go to linked page and click on download ota at top of page
I would read through the page it sends you to well.Don't forget to thank those guys..Hope this helps.Hit me up if it doesn't.
.http://forum.xda-developers.com/showthread.php?t=2148072
Doing a one click restore worries me, I'm not on sprint any more and worried about losing my flash to my current carrier. Is this a concern I should have since I'm not used to working with odin? I'm more than willing to try another ROM also, I'm not locked into this by any means.....
godzilla61 said:
Doing a one click restore worries me, I'm not on sprint any more and worried about losing my flash to my current carrier. Is this a concern I should have since I'm not used to working with odin? I'm more than willing to try another ROM also, I'm not locked into this by any means.....
Click to expand...
Click to collapse
The carrier should not matter if you are on an E4GT phone. But if your trying to go to a JB ROM, you will need to aupdate to GB** for your phone. For sprint it is GB27. Have you tried RWilco12's repository to see if your carrier is listed? Also QBKing77 has a lot of videos concerning this specific phone. How to flash specific ROMs and upgrading specific build, modems and such. Something has got to work for you.
fitting toryBB
bigmike6200 said:
The carrier should not matter if you are on an E4GT phone. But if your trying to go to a JB ROM, you will need to aupdate to GB** for your phone. For sprint it is GB27. Have you tried RWilco12's repository to see if your carrier is listed? Also QBKing77 has a lot of videos concerning this specific phone. How to flash specific ROMs and upgrading specific build, modems and such. Something has got to work for you.
Click to expand...
Click to collapse
Well now I'm stuck on Sprints 4G boot screen just keeps looping.....WTH.....I've never had a phone be a pain like this....guess I let it kill the battery and see what happens. Recovery is there, not cwm so can't even restore my backup. I'm just frustrated by this phone! Gill, bigmike any idea which way to turn now?
godzilla61 said:
Well now I'm stuck on Sprints 4G boot screen just keeps looping.....WTH.....I've never had a phone be a pain like this....guess I let it kill the battery and see what happens. Recovery is there, not cwm so can't even restore my backup. I'm just frustrated by this phone! Gill, bigmike any idea which way to turn now?
Click to expand...
Click to collapse
What ROM did you flash? Was it ICS or Jellybean? What carrier are you on. That was never revealed.
Never kill the battery. I sed you tried" Wild for the night" and Pac something. Can you get to recovery?
X'ed out the game
Q&A for [ROM][SM-T900] CyanogenMod for Tab Pro 12.2 SM-T900 (v2wifixx)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][SM-T900] CyanogenMod for Tab Pro 12.2 SM-T900 (v2wifixx). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Rooting Tab Pro 12.2 with last firm done!
arcadia2uk said:
For rooting the latest firmware, did you use the CF-Auto-Root from the main site, marked KOT49H.T900XXUANB5, or a new one made for the KOT49H.T900UEUANI1? If the latter, would you mind posting a link to a T900UEUANI1 compatible version?
Click to expand...
Click to collapse
Don't needed. You can root the normal cf-auto-root with latest sock without problem.
After we pm chat last days about rollback to T900UEUAND4 as unique possibility for rooting, i decided to do a last try before that, and luckily works perfect:
-just did a factory reset to restore from B3 recovery i been trying to prev installed T900UEUANI1 stock, wipe caché with stock recovery, odined cf-auto-root and voilá, just rooted!
No need to do the old B3-rollback-prior-D4 method now. Just a normal auto-root with no hassling.
temp maybe?
chhaggerty said:
It sounds like you maybe having a "Sleep of Death" (SOD) issue. The T520 and P900 have had similar problems. I will out of town until Monday but I'll do some research and hope to have a solution soon.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
crpalmer said:
There is a deadlock in Samsung's code triggered by the CPU boost driver. Look in the t520 device repo for the commit that disables it (actually probably 2 commits because I removed some functionality that doesn't make sense for this processor).
Click to expand...
Click to collapse
Dauntless said:
Device: SM-T900
Android: 4.4.2 (Stock, unrooted)
Kernel: 3.4.39-2534013
When putting the tablet into sleep mode, it will automatically shut itself down. When I try to turn it back on, the tablet will only do so after I plugged in the charger. The battery itself is fully charged.
I've updated to the latest available firmware version that's available to me. I couldn't find any list of known issues, so I'm wondering if this is a common problem and if I should return my tablet?
Click to expand...
Click to collapse
Same here. It seems that the problem maybe is temperature: after some time charging it gets really hot and maybe can't awake from that and need rebooting.
I've disabled the magnet sensor vía 3rd app to off the close-lid functionality but don't improve the problem.
Here in summer the room gets to +30°c and the Tab ups to almost 65°c when it gets hot!
Maybe it just reach the temp threshold and self shutdown, or intend that not letting awake.
Perhaps CM11 build here charges battery too fast, with higher voltage than allowed and provoque overheating. I mean, i really feels that it's charging real fast..
Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app
lingarajug said:
Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Posted update last night, check it out
Thanks, btw, i was able to use ODIN to get a good version of TWRP and the ROM installed smoothly. I have encountered a few small bugs but nothing to report that is new. I noticed the "sleep of death" I think you are referring to, deep sleep resulting in a manual reboot to wake up. I have noticed my bluetooth disconnects and reconnects every few minutes during deep sleep..not sure why. will report back. Thanks SO SO much for the development, i love it, so sick of the green and blue and the settings tabs on this stock OS disgust me. I am curious tho, am I the only one who noticed significant slowdown and lag compared to stock? I do not put a lot of stock in benchmarks (skewed toward uncle sammy) but they also showed big slowdown....just my very humble and grateful early experiences. Thanks again.
total reflashing needed?
chhaggerty said:
Posted update last night, check it out
Click to expand...
Click to collapse
Well thanks, but,i don't see a flashing update but an entire 221MBs rom to flash..
Can you post just the little update file , if there's any, to flash above the installed rom?
I don't want to install rom, apps and config all over again.
Thanks!
-----
lingarajug said:
Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Yes you are right, i'd tried again and it SODs no matter what temp are. A shame.
-----
arcadia2uk said:
For rooting the latest firmware, did you use the CF-Auto-Root from the main site, marked KOT49H.T900XXUANB5, or a new one made for the KOT49H.T900UEUANI1? If the latter, would you mind posting a link to a T900UEUANI1 compatible version?
Click to expand...
Click to collapse
Well there's a problem right now, seems that this rom prevent to enter recovery.., this is what happen to me:
Reboot from Android with 'reboot to recovery' option and when the TWRP splash logo shows it enter in a bootloop always to this instance that TWRP logo appears.
Then i just installed the good old UAND4 rom and it works fine.
Maybe i shouldn't go to recovery direct from android to prevent bootloop happen and try to go the normal way from boot.
Don't know, maybe I'll try some day.., or maybe better wait to Android L comes to us.
Please advice all that stuff in the respective threads, i can't.., cause' these 'noobs-wait-to-10-posting-before' rules..
Greetings.
bertoxo said:
1. Can you post just the little update file , if there's any, to flash above the installed rom?
2. Yes you are right, i'd tried again and it SODs no matter what temp are. A shame.
3. Well there's a problem right now, seems that this rom prevent to enter recovery.., this is what happen to me:
Click to expand...
Click to collapse
1. You can "dirty"-flash (install w/o wiping) the new ROM over the old one - nothing to re-install - if you wish you could extract the kernel (boot.img) and flash it by Flashify
2. There haven't been reported any SOD issues after flashing chhaggerty's latest ROM version
3. I have had no issues with with TWRP after having flashed the KOT49H.T900UEUANI1 - I just assume that some parts of the Firmware, not touched by cm, has been improved (but since this is WIFI only, it might not be the case for a non phone device) why I preferred to make the update.
arcadia2uk said:
1. You can "dirty"-flash (install w/o wiping) the new ROM over the old one - nothing to re-install - if you wish you could extract the kernel (boot.img) and flash it by Flashify
2. There haven't been reported any SOD issues after flashing chhaggerty's latest ROM version
3. I have had no issues with with TWRP after having flashed the KOT49H.T900UEUANI1 - I just assume that some parts of the Firmware, not touched by cm, has been improved (but since this is WIFI only, it might not be the case for a non phone device) why I preferred to make the update.
Click to expand...
Click to collapse
1- but dirty flashing the update full rom performs well?
1.2- only the boot.img is needed for update?
3- have you tried the reboot-to-recovery option from android?
Thanks.
bertoxo said:
1- but dirty flashing the update full rom performs well?
1.2- only the boot.img is needed for update?
3- have you tried the reboot-to-recovery option from android?
Thanks.
Click to expand...
Click to collapse
The changes done between the two versions (99% sure) was only some modifications in the kernel-code. Why flashing the kernel only should be fine, it will resolve the SOD and also make it run cooler. But if you wish you can also dirty-flash. However, cover your bases with a full back-up.
No issues at all with the reboot to recovery option
arcadia2uk said:
The changes done between the two versions (99% sure) was only some modifications in the kernel-code. Why flashing the kernel only should be fine, it will resolve the SOD and also make it run cooler. But if you wish you can also dirty-flash. However, cover your bases with a full back-up.
No issues at all with the reboot to recovery option
Click to expand...
Click to collapse
Can you give me the boot.img update only to try (5MBs)?
220MBs in the posted download site go sooo sloow on any server..
Thanks a lot!
bertoxo said:
Can you give me the boot.img update only to try (5MBs)?
220MBs in the posted download site go sooo sloow on any server..
Thanks a lot!
Click to expand...
Click to collapse
HERE it is
unzip the downloaded file
place boot.img on your SD
use Flashify to flash the kernel
after this I believe flashify will boot you up in recovery, just reboot and you should be good to go.
Just remember to make a back-up for just in case...
HERE it is
unzip the downloaded file
place boot.img on your SD
use Flashify to flash the kernel
after this I believe flashify will boot you up in recovery, just reboot and you should be good to go.
Just remember to make a back-up for just in case...
Click to expand...
Click to collapse
Thanks!
Installed boot.img and works flawlessly. Now i can back using lid cover again and no more hangs.
I hope they can solve the auto-rotate thing next time.
flashing screen, powering down...
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!
spk99 said:
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!
Click to expand...
Click to collapse
My guess is that gaming need more power, why I would stop greeify and reset the governor to interactive while gaming. But other than that I have no ideas, as I haven't heard of this problem before.
This ROM is fantastic! Smooth, fast, responsive and just as described...big thanks.
spk99 said:
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!
Click to expand...
Click to collapse
I don't know if you noticed, but chhaggerty just released a version 3, maybe this will work as there has been some work on the governors.
chhaggerty said:
New update see OP
Click to expand...
Click to collapse
Can i use the 4.4.4 GAPPS instead of 4.4.3 you are posting?
arcadia2uk said:
Thanks for another quality update, notably when reading how other cm11 exynos versions always seems to break something. With your T-900 cm11, I have never had any issues. The latest version is still running smooth, the changes in the CPU governor will probably allow for better battery life with the added conservative setting. However, I don't know what trade-off this will have on performance.
Click to expand...
Click to collapse
Maybe they start to use the big.LITTLE behavior of the Exynos, instead of ever using just the full power a15 cluster (battery eater).
I've haven't tried it but since it's a 4.4.4 rom they should work fine.
Error flashing ROM
Hi guys,
I get this error message when I try to flash CM11:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset"
This is a brand new rooted SMT-900 Tab Pro 12.2". Here's some notes:
- I received the error using V1, V2, and V3, all receive the error message
- I downloaded two copies of v3 from two separate mirrors (CA and AZ), both receive the error message
- I did a factory reset and still received the error message
- Wiped davlik/cache/system partitions
- Tried on TWRP 2.7 and 2.8, both receive same error message
- All I have done to this tablet is root it, install TWRP, and create one backup
Any thoughts? I can try using CWM if someone can give me a quick overview of how to install it and remove TWRP (or keep TWRP).