[Q] I have some strange Kernel issues !!! - Samsung Galaxy Nexus

Hello folks! As the title says I have quite a strange issue with some kernels (Franco,LeanKernel and STOCK!!). I flash the kernels after flashing a rom ,doing it clean(all the wipes) and the phone is working fine for couple hours or a day,after that it just going verry sluggish even in appdrawer or when switching desktop screens. I looked at the CPU frequencies and they change as they shouldn't,I can tell that somethig isn't right with the cpu...I have this issue only with those kernels. I tried stock roms,4.2.x roms,flashed even google images to be sure it's stock,tried them with AOKP 4.2 and 4.1 ,CNA and the list could go on...
Is someone else having the same issue??
Any fix for this? I really want to try franco's kernel!!!

1. Hmmm, are you running a live wallpaper?
2. Do you face the same issue while using Trinity Kernel?
3. Are you sure you do not have any app such as SetCPU which is controlling the speed of CPU?
4. If you set the CPU speed back to normal, does this fix the issue?
5. How much space is mostly left on your sdcard?
I hope the answers of these questions will help to identify your problem much bettER

I don't have the same issue with faux's and trinity kernels . I don't have any program,i don't use a live wallpaper, how I can speed back to normal the cpu?

calinoii said:
I looked at the CPU frequencies and they change as they shouldn't
Click to expand...
Click to collapse
I thought you have checked the CPU speed/frequency using an app like "AnTuTu CPU Master".
calinoii said:
how I can speed back to normal the cpu?
Click to expand...
Click to collapse
Using AnTuTu CPU Master, check the speed set for the CPU when the phone is sluggish and if it something other than the normal 1200 MHz then modify it back to normal. This is what I meant

The frequencies changes verry verry fast,that's when the phone becomes sluggish,i have mini freezes,lots of them

calinoii said:
The frequencies changes verry verry fast,that's when the phone becomes sluggish,i have mini freezes,lots of them
Click to expand...
Click to collapse
I think some background processes are causing this so the CPU is trying to respond to them.
I suggest that you do a full wipe, install a ROM and use Franco's kernel, but do not install any other application on your phone, only default ones installed already with the ROM, maybe Gapps as well just to have a usable phone for some time, then check after a day whether it is again sluggish although there are no applications at all or it is still running fine. At least we would be able to know that maybe one of your application is not compatible well with these kernels and causing this mess.
You may want to avoid wiping so try to force stop the applications running in the background (and cached processes as well) to see if one of them is causing this problem.
Good Luck

I did wipe the data and didn't install any application and I have the same issue :-s

calinoii said:
I did wipe the data and didn't install any application and I have the same issue :-s
Click to expand...
Click to collapse
Do you use any widgets?

Nope

I am not sure I have helpful suggestions anymore except to be sure that you are using the correct Franco kernel whether you are running a 4.1 ROM or 4.2 one.
I hope other members can solve this problem for you. Maybe you will get a bettER help if you discuss this with the Franco kernel users on the Franco kernel thread.

Thanks anyway,i'll post this issue on franco's kernel thread and hope for a fix...and be sure i flashed the correct version of kernel )

Anyone? Please?

calinoii said:
I have some others with the same problem,but thisis the latest,no one could help me this far.I already did what you suggested me...I`m sure I did the clean wipes,just installed gapps and nothing else...when it was getting little hot the freezes were starting too,I think i did all I could,many people in this forums adviced me and still nothing,maybe franco's the only one who can help me with this...
Click to expand...
Click to collapse
Carrying on from here where we were in franco's thread. If you're flashing gapps then clearly you aren't using stock ROM like I told you to try. So, my suggestion to you for troubleshooting remains the same:
osm0sis said:
Well that's really peculiar. I'd try flashing stock again using fastboot. I'd fastboot oem lock, then fastboot oem unlock to wipe, then flash the entire image set as in efrant's thread just to make sure it all gets wiped. But unfortunately, like I said, if stock kernel doesn't work over a fresh fastboot flash of Google's factory image on your device there's still something very wrong, and it's likely wrong with the device itself.
Click to expand...
Click to collapse
osm0sis said:
Use the latest Google Factory Image for your device like I suggested, then you can see if you get the OTA immediately or you can flash it yourself. Do all this before you put any apps on, and don't let it put any apps on and see if you still have the issue with a completely stock setup.
Click to expand...
Click to collapse
Please report back only when you've followed that to the letter.

Tried both,the ones from the images,and the gapps on a stock flashed rom via recovery...I'm trying to resolve this for over 2 weeks now...
L.E : Ok,I will pm you when I manage to have some time for doing this again,thanks for your kindnes

I don't care how many times you think you've done it correctly before, I want you to try it AGAIN. And make sure you've completely wiped by using fastboot oem lock and unlock, then follow efrant's thread to the letter for flashing the entire image set. Factory Images ONLY, no stock-ish kitchen garbage.
I'm happy to help you but you've got to follow my instructions, since this is what I would be doing if I had this issue on my device.

Ok,I will,is there anyguide for locking and unlockingthe bootloader ? or simply "fastboot oem lock" and after "fastboot oem unlock" ?

calinoii said:
Ok,I will,is there anyguide for locking and unlockingthe bootloader ? or simply "fastboot oem lock" and after "fastboot oem unlock" ?
Click to expand...
Click to collapse
Yeah those are the commands. That's it. :good:
I think it's mentioned in efrant's post too, but no special guide necessary. Use the adb and fastboot that he attached too if you're new to fastboot.

I'm used to fastboot,I don't even need the guide to see the commands now,I think I used them like 100 times last 2 weeks )

Fair enough. Please follow the guide anyway though, and be sure to also flash userdata.img and recovery.img to be completely stock. You can fastboot boot cwm.img if you need it to flash your OTA afterwards. We just need you at 100% stock so we can try to figure this thing out. Also maybe hold off on adding your Google account so it doesn't start forcing apps onto your device. It could very well still be a rogue app issue so we need to try and keep your device as empty as possible to see if we can rule out hardware defect. :good:

Should I install any apps?
I did everything you said,now i'm waiting for it to boot up

Related

Rooting Gnex GSM/HSPDA v4.0.2 Optus Stock

Hey guys!!,
Yet another of my noob questions BUT, this time I think I'm going to take the plunge and root my Gnex!!! *scared* haha
I'm just having to many frustrating things happening on my stock Gnex, low responsiveness to the touch, slow-ish and well, isnt this what its all about!! =)
So a quick one, if anyone can point me in the most normal, simple and customizable direction, what do I do? I have searched for a while now so I have an idea where i want to go, either, Cynagon or AOKP...I'm hearing great things about AOKP...there from the same devs yeah?? (a guess)
So, I have a Samsung updated Gnex, in Aus and with optus. I'm technical so I'm getting a grasp on whats what but still not to clear on Kernels and radios....bit worried about that. Clockwork I'm guessing is like a boot manager?? Just asking that while I was here...
So Odin? Wug? CF-Root? I'm just not sure...
Thanks soooo much in advance guys.... I already appreciate your help. =)=)
*Excited!!!*
Cheers!!
P.S. I'd also very much like to return to stock form later on if I want...like locked oem and restored stock rom... =)
Helmet321 said:
Hey guys!!,
Yet another of my noob questions BUT, this time I think I'm going to take the plunge and root my Gnex!!! *scared* haha
I'm just having to many frustrating things happening on my stock Gnex, low responsiveness to the touch, slow-ish and well, isnt this what its all about!! =)
So a quick one, if anyone can point me in the most normal, simple and customizable direction, what do I do? I have searched for a while now so I have an idea where i want to go, either, Cynagon or AOKP...I'm hearing great things about AOKP...there from the same devs yeah?? (a guess)
So, I have a Samsung updated Gnex, in Aus and with optus. I'm technical so I'm getting a grasp on whats what but still not to clear on Kernels and radios....bit worried about that. Clockwork I'm guessing is like a boot manager?? Just asking that while I was here...
So Odin? Wug? CF-Root? I'm just not sure...
Thanks soooo much in advance guys.... I already appreciate your help. =)=)
*Excited!!!*
Cheers!!
P.S. I'd also very much like to return to stock form later on if I want...like locked oem and restored stock rom... =)
Click to expand...
Click to collapse
Try my ToolKit in the dev forum. Its simple, straightforward, easy to understand, there is a 1-click option which will do everything and every step is explained in detail.
http://forum.xda-developers.com/showthread.php?t=1392310
You can also use my ToolKit to flash a Stock Google Rom if you ever want to in the future.
With regards to Roms there are lots available to try by very experienced developers that will make your phone better and plenty of kernels to make it run ALOT faster. I use bigxie's Rom and franco's kernel.
Mark.
Hi!!,
Thanks so much for your reply!
Funny as, I was JUST reading your guide. Awesome work man, very informative.=)=) and it would of taken some time to compile!. =/
Arm, I'm just wondering what file I need to backup to got back to the rom I'm on now? I want to be able to go back, if needed.
I don’t know what kernels are all about, and what do I need to do about Radios?? If I have the wrong one or something, does that mean I wont have signal?? Or bad call/signal reliability?
I'm looking at the build 23 of AOKP...I'm hearing its the go...and if i have a wrong kernal rom radio combo, what’s that going to do??, that’s if they correlate?? haha
Is security as issue?? Since these are built "freely" is there any exposure of private info?
I'm sorry for smashing you with all this, I'm just trying to get all the info before I do anything and to have a failsafe if I need to return for warranty.... =/
Thank you in advance!!! =)
Cheers.
P.S. Is Bigxie Apex?? I hear good things about that too!! haha. Its so hard, theres so many out there... Apex, Gummy, AOKP look great. I also really want a responsive, battery lasting, fast and importantly "stable" phone. So, not sure what you recommend. =)
Thanks already!! =)=)
Helmet321 said:
Hi!!,
Thanks so much for your reply!
Funny as, I was JUST reading your guide. Awesome work man, very informative.=)=) and it would of taken some time to compile!. =/
Arm, I'm just wondering what file I need to backup to got back to the rom I'm on now? I want to be able to go back, if needed.
I don’t know what kernels are all about, and what do I need to do about Radios?? If I have the wrong one or something, does that mean I wont have signal?? Or bad call/signal reliability?
I'm looking at the build 23 of AOKP...I'm hearing its the go...and if i have a wrong kernal rom radio combo, what’s that going to do??, that’s if they correlate?? haha
Is security as issue?? Since these are built "freely" is there any exposure of private info?
I'm sorry for smashing you with all this, I'm just trying to get all the info before I do anything and to have a failsafe if I need to return for warranty.... =/
Thank you in advance!!! =)
Cheers.
P.S. Is Bigxie Apex?? I hear good things about that too!! haha. Its so hard, theres so many out there... Apex, Gummy, AOKP look great. I also really want a responsive, battery lasting, fast and importantly "stable" phone. So, not sure what you recommend. =)
Thanks already!! =)=)
Click to expand...
Click to collapse
If you goto settings, about phone then it will tell you all about your current rom build. If its a yakju build then its a stock google rom and can easily be found and reflashed via my ToolKit. If its been put on by your operator then you wont be able to obtain it online and you are best backing it up (unless you dont mind putting the google stock rom back on).
To do that you will need to set your drivers up first. This is important as nothing else can be done without this step. If you have Windows xp or 7 then its pretty easy, you can install the drivers automatically via the GNex ToolKit, then reboot your pc. Goto settings, developer options on your phone and tick 'usb debugging' then connect the usb cable to your phone (with it booted into Android). This should install adb drivers which are needed for communication when your phone is booted into Android. Start the ToolKit and select your current build version (which can be found in settings, about phone). At the top of the Main Menu you should see a serial number under adb mode which means your device is recognised in this mode. Select reboot options (19) in the ToolKit and Reboot phone to Fastboot (3). This is a bootloader mode for the phone outside of Android where you can flash and manipulate certain parts of your phone. As this mode is at a much lower level then the operating system it can be your saviour if your phone locks or wont start and you need to flash back to stock.
Once the phone has rebooted to fastboot mode the fastboot drivers should be installed on your pc. If nothing happens try unplugging and replugging the usb cable to initiate the drivers. If the drivers have installed before the ToolKit refreshes then you should now see the serial number at the top under fastboot mode this time. You NEED both fastboot and adb drivers installed on your pc for everything to work.
After the drivers have been set up you will need to Unlock the Bootloader to be able to have access to system areas on your phone. BE AWARE that unlocking the bootloader will erase EVERYTHING all data on your phone including the Internal Storage (virtual SD Card) so copy anything you need to from your Internal Storage accross to your pc and use the Backup option in the ToolKit to save any installed apps and associated user data that you want to keep. This is done in adb mode so your phone will need to be in Android.
If you want to back up your current Rom then Unlock the Bootloader, reboot your phone into Android, go through the setup quickly (as the phone will have been wiped), then goto settings developer options and enable usb debugging. Start the ToolKit and in the Main Menu select 19, 3 to reboot back to fastboot mode. Then you can BOOT into CWM Recovery without flashing it (9) and select backup/restore to backup your Rom/user data/boot image to a datestamped folder inside a folder called Clockworkmod on your Internal Storage. The rebooting into Android step after unlocking the Bootloader is important as cwm will not work properly without doing that.
Once that is all done you are ready to reboot into Android from cwm, get back to fastboot mode as before and select 1-click option (7). You will get a message on the unlock stage saying that your device is already unlocked but then it will just skip to the next stage. Be aware that when the device boots into Android the first time this is to let the user enable usb debugging for adb operations and if you have already done this then the ToolKit will wait for about 3 minutes before carrying on. Be patient as the ToolKit hasnt frozen, its just set to pause before carrying on.
Ok now thats all over with, on to your other questions lol. I would advise trying either romanbb's AOKP (build 24 should be up today) or bigxie's Apex 1.02 to start. Personally I use Apex as it has loads of customisation and runs very well but saying that I will be trying romanbb's new build when it is out.
Kernels are like the drivers of your phone. They set up how it works and what it can do. Custom Kernels can give better battery life and more power, performance, stability so its well worth trying them once you are rooted. They will tell you what builds they are compatable with but if you are thinking about the above Roms then you will be on Android build 4.0.3 and most new kernels work with that. I use franco's kernel but there are ALOT of established kernel developers working with the Nexus so you could try fugumod by nikademus or trinity by morfic. These are all flashed via cwm (download file, copy to Internal Memory, reboot to recovery mode once you have cwm flashed). You can enter cwm by rebooting to fastboot and using the volume buttons to select recovery, then press power to select, or from the reboot phone options in the ToolKit (19,4 in adb mode).
Bootloaders and Baseband/Radio updates are something to think about but not really needed if your phone is running fine. You wont notice any change if you update the bootloader as its just like updating your bios on a pc. Just gives some extra functionality or updates some deep down settings. Radios control the communication part of your phone and updating to a new one may improve battery, signal, wifi, gps lock. You can update them by either grabbing a premade zip and flashing via cwm or download the .img file and flash that via the ToolKit.
Dont worry about malware included in custom roms as long as its by an established developer. They would never put anything dangerous to the end user in one of their roms as it would harm their reputation and if anything was found by a user the rom would be taken down imediately by us mods to keep you safe.
I think thats everything you will ever need to know lol. Sorry theres alot I wanted to make sure you had all the ammunition you needed to continue and it took soo long to write I had lunch half way through
good luck.
Mark.
Ohhh man, thank you sooo much. That’s a lot of info and I really appreciate you taking the time to explain that to me Mark. Thank you!!!!
Ok, I’ve been watching some videos, one off of GalaxyNexusRoot.com. I think its his YouTube chan… He's seems pretty cool. Shows you what to do. I sort of want to do it manually so I'm understanding it all?, if that makes sense? I like to know exactly what my device is doing, why and how? haha. I'm a bit pedantic like that.
Arm, only a couple of things....I'm draining your life here...haha
I have a Samsung updated Gnex, throwing that in FYI. =) Not sure if the warranty centre would realise, probably so I should back it up as it is...on this note quickly, I do want to have a yakju (Google) updated phone though...hehe.
When I back up, does it flash everything? the rom, kernels and radios? (Mostly for my Stock setup for reversion, and understanding...)
With roms, where can I get the G'apps from? (If needed) And or the SupUser/Root files? (Separately I mean, so I can do this manually...if I'm understanding it properly... =/ )
Also, do these apps and others update as normal? Or di i have to update the whole ROM to update them? Like Maps (Navigation more importantly), GTalk, MarketPlace etc...?
And finally....phew...haha arm, sorry....
I'm looking at doing this because currently my device just seems a little non-responsive, laggy-ish and its turned off once.. =/ Is this all normal?? I thought for a minute my screen was faulty, like touches don’t always respond...I mean 90% of the time they do...I know, I'm nuts but it just ruins it for me... I uninstalled Beautiful Widgets and it’s sort of been better…maybe some apps aren’t configured with ICS yet also…I'm thinking it just could be the build? What do you think??
It's kind of weird to think that an individual dev has made. and is making more progress than the developers of the phone/software?? hahah...Anyway, I hope I've made some sense and I really, really, really appreciate all this Mark, all your time and patience with me. =)
Thanks again!!!!
P.S.... This should be it I SWEAR!! haha....
Just wanted to put these here...these are "some" of the problems I've been having... =/
http://forum.xda-developers.com/showthread.php?t=1500545
http://forum.xda-developers.com/showthread.php?t=1490335
http://forum.xda-developers.com/showthread.php?t=1500236
http://forum.xda-developers.com/showthread.php?t=1487946
Thank you...again!!!
I just want to thank the OP for asking the right questions and taking the time to figure out how "hack" his/her phone correctly instead of jumping in blind.
I hope other beginners follow the OP's lead.
That is all.
Sent from my Galaxy Nexus using xda premium
Helmet321 said:
Ohhh man, thank you sooo much. That’s a lot of info and I really appreciate you taking the time to explain that to me Mark. Thank you!!!!
Ok, I’ve been watching some videos, one off of GalaxyNexusRoot.com. I think its his YouTube chan… He's seems pretty cool. Shows you what to do. I sort of want to do it manually so I'm understanding it all?, if that makes sense? I like to know exactly what my device is doing, why and how? haha. I'm a bit pedantic like that.
Arm, only a couple of things....I'm draining your life here...haha
I have a Samsung updated Gnex, throwing that in FYI. =) Not sure if the warranty centre would realise, probably so I should back it up as it is...on this note quickly, I do want to have a yakju (Google) updated phone though...hehe.
When I back up, does it flash everything? the rom, kernels and radios? (Mostly for my Stock setup for reversion, and understanding...)
With roms, where can I get the G'apps from? (If needed) And or the SupUser/Root files? (Separately I mean, so I can do this manually...if I'm understanding it properly... =/ )
Also, do these apps and others update as normal? Or di i have to update the whole ROM to update them? Like Maps (Navigation more importantly), GTalk, MarketPlace etc...?
And finally....phew...haha arm, sorry....
I'm looking at doing this because currently my device just seems a little non-responsive, laggy-ish and its turned off once.. =/ Is this all normal?? I thought for a minute my screen was faulty, like touches don’t always respond...I mean 90% of the time they do...I know, I'm nuts but it just ruins it for me... I uninstalled Beautiful Widgets and it’s sort of been better…maybe some apps aren’t configured with ICS yet also…I'm thinking it just could be the build? What do you think??
It's kind of weird to think that an individual dev has made. and is making more progress than the developers of the phone/software?? hahah...Anyway, I hope I've made some sense and I really, really, really appreciate all this Mark, all your time and patience with me. =)
Thanks again!!!!
P.S.... This should be it I SWEAR!! haha....
Just wanted to put these here...these are "some" of the problems I've been having... =/
http://forum.xda-developers.com/showthread.php?t=1500545
http://forum.xda-developers.com/showthread.php?t=1490335
http://forum.xda-developers.com/showthread.php?t=1500236
http://forum.xda-developers.com/showthread.php?t=1487946
Thank you...again!!!
Click to expand...
Click to collapse
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
What does stock stand for?
udmbrian said:
What does stock stand for?
Click to expand...
Click to collapse
It means the version that the manufacturer put on the phone before it was shipped or a version that is supplied by the manufacturer. Unaltered by developers.
Mark.
mskip said:
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
Click to expand...
Click to collapse
Thanks again!!!!
Ok cool. So when new versions of the apps come out on the market, I wont be able to update them normally will I? Which is ok but just wondering how that is going to go down. Haha.
Lastly, sorry man, I'm almost there. Haha. CWM doesn't backup kernel? Like my stock one?
So it basically makes a "phone" image, ExtPartition and all? Or can you choose these options?
Right, I'm so close now I reckon, today will be the day... I can feel it!!! Haha.
Thank you again!!!!!!!!!
Sent from my Galaxy Nexus using XDA App
Helmet321 said:
Thanks again!!!!
Ok cool. So when new versions of the apps come out on the market, I wont be able to update them normally will I? Which is ok but just wondering how that is going to go down. Haha.
Lastly, sorry man, I'm almost there. Haha. CWM doesn't backup kernel? Like my stock one?
So it basically makes a "phone" image, ExtPartition and all? Or can you choose these options?
Right, I'm so close now I reckon, today will be the day... I can feel it!!! Haha.
Thank you again!!!!!!!!!
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Yes of course you can update google apps via the market as normal.
Cwm will back up your boot image which contains the kernel. So yes it does back up the kernel.
You can not choose which options to back up but you can choose which parts you want to restore via the advanced restore option in cwm.
Let me know how it all goes
Mark.
El Daddy said:
I just want to thank the OP for asking the right questions and taking the time to figure out how "hack" his/her phone correctly instead of jumping in blind.
I hope other beginners follow the OP's lead.
That is all.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hey El Daddy,
Thanks man. I try to reframe from being a pain in butt.... not sure how I've gone with that but, Haha. I appreciate what your saying. I just want to be sure what I'm doing and to have, as Mark said, all the "ammo" I need.
Cheers.
Sent from my Galaxy Nexus using XDA App
Great questions and answers from both of you. Just got this phone and trying to figure out where to start. Briefly read the toolkit instructions. Just haven't had the time to sit down and plow through it. Thanks both of you.
mskip said:
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
Click to expand...
Click to collapse
Thanks so much again Mark...This is Great!!
Ok, just before I do this...I'm like right here at the PC...ready! haha...
I understand all of it now, well. in theory...
Thank you for the DL link to the root.zip...
I DL'd the android SDK Kit zip also, but there’s no fastboot.exe??? Or anything like what I need?? haha, I may just be missing something here...
One of you links on you manual guide is broken...I think, that’s where you had it...I didnt want to harass you again but just some final things. =)
I'm really after all of what I need to this manually...for knowledge etc?? Hope you understand... You made this wicked awesome Kit, and I'm stupid and not using it...hahah...
So as far as I can see, I need:
- Samsung Drivers - which I have and that bits done... =)
- fasboot.exe etc (Android SDK Gear)
- Latest CWM.zip
- **Rom of my choice, which I'm going to take your advice and go with Apex. =) Latest 1.02 yeah??
- Franco Kernel, I'll try stock, but my feeling on it is that that’s probably been my major issue, or the cause of most of them... =)
Phew....I think that’s it...am I on the right track??
I cant thank you enough with all this Mark....seriously...your a very patience man. haha
Cheers. =)
**Update**
P.S. I have attached a file. Mark can you check it out and see if that what I need in regards to Android SDK stuff? I just got this now after I posted the above....
Thanks again... =)
***Update...again....haha***
Arm, just looking at these files, whats the boot.img? does that get copied over to the phone? Or is it just a command? The su & Superuser files in this zip are like a different size and modified later than your ones (newer??? =/)....I'm not sure what that would really mean...probably has nothing to do with anything but just thought I'd check with you....
Helmet321 said:
Thanks so much again Mark...This is Great!!
Ok, just before I do this...I'm like right here at the PC...ready! haha...
I understand all of it now, well. in theory...
Thank you for the DL link to the root.zip...
I DL'd the android SDK Kit zip also, but there’s no fastboot.exe??? Or anything like what I need?? haha, I may just be missing something here...
One of you links on you manual guide is broken...I think, that’s where you had it...I didnt want to harass you again but just some final things. =)
I'm really after all of what I need to this manually...for knowledge etc?? Hope you understand... You made this wicked awesome Kit, and I'm stupid and not using it...hahah...
So as far as I can see, I need:
- Samsung Drivers - which I have and that bits done... =)
- fasboot.exe etc (Android SDK Gear)
- Latest CWM.zip
- **Rom of my choice, which I'm going to take your advice and go with Apex. =) Latest 1.02 yeah??
- Franco Kernel, I'll try stock, but my feeling on it is that that’s probably been my major issue, or the cause of most of them... =)
Phew....I think that’s it...am I on the right track??
I cant thank you enough with all this Mark....seriously...your a very patience man. haha
Cheers. =)
**Update**
P.S. I have attached a file. Mark can you check it out and see if that what I need in regards to Android SDK stuff? I just got this now after I posted the above....
Thanks again... =)
***Update...again....haha***
Arm, just looking at these files, whats the boot.img? does that get copied over to the phone? Or is it just a command? The su & Superuser files in this zip are like a different size and modified later than your ones (newer??? =/)....I'm not sure what that would really mean...probably has nothing to do with anything but just thought I'd check with you....
Click to expand...
Click to collapse
Looks like everything in that zip is ok for what you want to do. The superuser.apk is a different size but im sure it doesnt matter.
In order to push the 2 files across to your phone you need to have booted into Android using an insecure boot image. This is a stock boot.img that has has some simple text changes to allow temporary root access (otherwise the files wouldnt copy across) Using fastboot you boot the boot.img file and then once you are in Android you push the files across and set their permissions. When you reboot your phone your original boot image will be used and you should have permanent root via the files.
Looks like you are all set
MArk.
Oh ok. So it doesn't stay on the phone?, its temporary??
So if this file say, is corrupted or malicious, (not really possible probably byt...) I'm in trouble? haha
Sorry, I have everything I think now, I grabbed the SDK of the Android website and I'm comfortable with that cause its "legit" I suppose. It doesn't have a boot.img file though. Can I make one myself so I know where its coming from? And where does this normally come from?
Silly stuff I know but, I told you, I'm CRAZY!! haha....
One very last thing...the permissions, whats that part all about...
Other than that, I'm pretty sure I'm sweet now...I also grabbed the latest CWM zip off the website too...so I'm cool with that.
......geez.... I'm killing you aren't I....I think you deserve (need) at LEAST 1 beer after all this....haha...
Thanks x 1,000,000...seriously.... =)
Helmet321 said:
Oh ok. So it doesn't stay on the phone?, its temporary??
So if this file say, is corrupted or malicious, (not really possible probably byt...) I'm in trouble? haha
Sorry, I have everything I think now, I grabbed the SDK of the Android website and I'm comfortable with that cause its "legit" I suppose. It doesn't have a boot.img file though. Can I make one myself so I know where its coming from? And where does this normally come from?
Silly stuff I know but, I told you, I'm CRAZY!! haha....
One very last thing...the permissions, whats that part all about...
Other than that, I'm pretty sure I'm sweet now...I also grabbed the latest CWM zip off the website too...so I'm cool with that.
......geez.... I'm killing you aren't I....I think you deserve (need) at LEAST 1 beer after all this....haha...
Thanks x 1,000,000...seriously.... =)
Click to expand...
Click to collapse
Its perfectly possible to make your own boot image but to be honest you might take another day or 2 to get all the required components and research what you need to do lol
If you go to your settings, about phone screen and tell me the build version (4.0.1, 4.0.2) and whether its a gsm or lte device (im assuming gsm as lte is america/canada) then I will attach the boot image I made for that device so it will definitely be right and safe. You can also use the su and superuser.apk files I attached earlier if you are unsure about them.
I dont mind all the questions as long as you end up feeling confident enough to get your phone rooted mate I would rather people ask too many (but the right) questions than just go blindly into something have no understanding about and end up in trouble.
Mark.
Your a legend Mark, I swear!!....haha
Ok, well, its a GSM, 4.0.2 Samsung updated Nexus....I think... I can attach some images. =)
The end of the line here...haha, arm, I just watched a video that completely skipped the boot.img part...weird...anyway, with the "su" part, I have 2 files there, as you've kindly provided, but in that step doesnt it need to be a su.zip sort of configuration? Just running it by you before I do this...
P.S....again....haha, arm, if I'm thinking about this right, does the step with "fastboot boot boot.img" will that affect the stock image?? As I think, if I'm right you have to do that "before" you flash your recovery?? In my mind would it be right in assuming....
-Unlock bootloader
-Flash recovery
-Make a Back up (so to get all the rom, including the auto restore recovery??)
-Set SU perms...with su.zip or su+superuser.apk... (if I'm right also, this step only if you want root perms on stock?, not sure what you would do with it though, only if you want to remain this way I suppose... =/ )
Is this right??
I was reading your "manual" post and I'm a little confused...as in, you cant reboot into Android after flashing recovery (to back up) as it will delete it, but to do so, you need to reboot into Android to delete the auto recovery flash file?? And you need su perms yeah?? Am I right here, I'm probably going crazy-ier...haha cause I've been at this for 2 days...haha...
Seems the boot.img step is the same as if you would flash a su.zip...(which I dont have, only the su file (no extension) and the su.apk...) not sure if thats the same...just getting my head around it here.... =)
Maybe I'm thinking CWM will "back up" the su perms etc and affect the "stock rom"...if you back it up with the perms, wouldnt that be included?? Maybe thats were I'm getting it wrong...haha.
Finally...........serious.....
If and when you delete the auto recovery file (if that really does delete it completly, I'm probably wrong about that too...) how does it restore??
Thanks mate. =)=)
I think thats it...when I have my head around these final things...and the last couple of files...Its time.... =)=)
Helmet321 said:
Your a legend Mark, I swear!!....haha
Ok, well, its a GSM, 4.0.2 Samsung updated Nexus....I think... I can attach some images. =)
The end of the line here...haha, arm, I just watched a video that completely skipped the boot.img part...weird...anyway, with the "su" part, I have 2 files there, as you've kindly provided, but in that step doesnt it need to be a su.zip sort of configuration? Just running it by you before I do this...
P.S....again....haha, arm, if I'm thinking about this right, does the step with "fastboot boot boot.img" will that affect the stock image?? As I think, if I'm right you have to do that "before" you flash your recovery?? In my mind would it be right in assuming....
-Unlock bootloader
-Flash recovery
-Make a Back up
-Set SU perms...with su.zip or su+superuser.apk...
Is this right??
I was reading your "manual" post and I'm a little confused...as in, you cant reboot into Android after flashing recovery (to back up) as it will delete it, but to do so, you need to reboot into Android to delete the auto recovery flash file?? And you need su perms yeah?? Am I right here, I'm probably going crazy-ier...haha cause I've been at this for 2 days...haha...
Seems the boot.img step is the same as if you would flash a su.zip...(which I dont have, only the su file (no extension) and the su.apk...) not sure if thats the same...just getting my head around it here.... =)
Maybe I'm thinking CWM will "back up" the su perms etc and affect the "stock rom"...if you back it up with the perms, wouldnt that be included?? Maybe thats were I'm getting it wrong...haha.
Finally...........serious.....
If and when you delete the auto recovery file (if that really does delete it completly, I'm probably wrong about that too...) how does it restore??
Thanks mate. =)=)
I think thats it...when I have my head around these final things...and the last couple of files...Its time.... =)=)
Click to expand...
Click to collapse
There are 2 ways of rooting your phone. The easier (and non learning way) is to flash cwm recovery and flash the superuser.zip straight to the phone. If this is what you watched then tbh you might as well be using my ToolKit as you wont learn anything from the experience. The other way is the method my ToolKit uses which is to boot the phone with the insecure boot image to gain temporary root, then using adb to push the 2 files that I sent to your phone and set their permissions, then rebooting to complete the root procedure. The 2nd method is the one I thought you was gearing up towards and the best way if you want to actually learn something, otherwise as I said you may as well use the ToolKit.
I have attached every file you will need for the 2nd method and if yo uread below these are the instructions you will need to follow to root your phone. Extract the attached files to a folder on your pc, browse to this folder then HOLD the Shift button on your pc while right clicking on a blank area of the Windows Explorer. Select 'Open command window here' which will open a command prompt in the correct folder where your adb and fastboot files are.
These instructions are for after you have installed drivers:
fastboot-toolkit devices
Click to expand...
Click to collapse
this will return a serial number if your drivers are installed.
fastboot-toolkit oem unlock
Click to expand...
Click to collapse
and follow the instructions on the phone to unlock your bootloader.
Now if you boot into Android RIGHT after unlocking the bootloader it will restart the boot half way through so you want to do this normally BEFORE using your insecure boot or the reboot half way through will lose your insecure access (if you get me)
fastboot-toolkit reboot
Click to expand...
Click to collapse
to get your first boot in. Once the phone has booted up and you have gone through the setup wizard, go to settings, developer tools and select 'usb debugging' to enable adb control.
adb-toolkit devices
Click to expand...
Click to collapse
should return a serial number if your adb drivers are installed.
adb-toolkit reboot bootloader
Click to expand...
Click to collapse
to get back into fastboot so you can boot from the insecure boot image
fastboot-toolkit boot boot_gsm_ICL53F_insecure.img
Click to expand...
Click to collapse
to boot your phone into Android from the insecrure boot image. Once your phone has booted into the lockscreen you can carry on with
adb-toolkit root
adb-toolkit remount
Click to expand...
Click to collapse
to mount your /system folder for root access.
adb-toolkit push su /system/bin
adb-toolkit push Superuser.apk /system/app
Click to expand...
Click to collapse
pushes the 2 files across to the correct folders on your phone.
adb-toolkit shell chmod 06755 /system/bin/su
adb-toolkit shell chmod 06755 /system/app/Superuser.apk
Click to expand...
Click to collapse
sets their correct permissions.
Lastly if you are flashing cwm then you will need to rename the recovery restore file if you are on a samsung rom. If this file is present on your phone and cwm is flashed, then on the next reboot the stock recovery will be restored and you will lose cwm. To get back to stock recovery in the future you just flash a stock recovery image.
adb-toolkit shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p-old
Click to expand...
Click to collapse
will rename the file is it is present.
Thats it! Reboot your phone and you should have root You can check this by downloading root checker from the market or just download a root app such as adfree or setcpu.
Mark.
I see you are replying to my thread already as I was making some changes so re-read the instructions as I rearranged them a bit to make more sense lol.
MArk.

Constant Reboots!! PLEASE HELP!!!!

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

[Q] Unresponsive screen after flashing ROM/Kernel

Hello All,
First time post and as an offering, I will say 'thanks' to anyone that responds in a positive manner to my post (trying to win some friends) :laugh:
Here's my issue, I have an Arc S LT18i.
Unlocked bootloader and rooted.
Whenever I flash anything custom the touch screen fails to respond, i've flashed LupusV7, slim bean 3.1 and 3.2 (with arc fusion 3.6 and 4.5) and Super Jelly Bean. All seemingly start without any issues and the physical buttons work no problem. BUT the screen refuses to work in anyway at all!!
I have made sure I wiped the system, cache and delvak (sp?)
Any help greatly appreciated, I am a NOOB but underneath it all I'm just trying to make the most of this wonderful Arc S...
Anything you want to know, please ask away...
Please help.
Namaste
Ricky:fingers-crossed:
Try doing a clean install
- Flash stock ICS .587 ftf
- Flash Kernel
- Wipe data,cache & dalvik
- Install ROM
sent via XPERIA™
Same thing!!
msc3169 said:
Try doing a clean install
- Flash stock ICS .587 ftf
- Flash Kernel
- Wipe data,cache & dalvik
- Install ROM
sent via XPERIA™
Click to expand...
Click to collapse
Hello and thank you for the reply...
I flashed stock ICS .587 (world india) from this site talk.sonymobile.com/thread/35239
Does that count as stock ICS .587?
And then followed the rest of the instructions, the exact same thing happens... buttons work but the touch screen does not!?
Any other ideas please? Or does anyone else have a suggestion?
Thank you very much for taking the time to reply to me.
Ricky
ricky7D said:
Hello and thank you for the reply...
I flashed stock ICS .587 (world india) from this site talk.sonymobile.com/thread/35239
Does that count as stock ICS .587?
And then followed the rest of the instructions, the exact same thing happens... buttons work but the touch screen does not!?
Any other ideas please? Or does anyone else have a suggestion?
Thank you very much for taking the time to reply to me.
Ricky
Click to expand...
Click to collapse
Are you using compatible ROM and Kernel?
僕のLT18iから送られてきた
compatible ROM and Kernel
popthosegaskets said:
Are you using compatible ROM and Kernel?
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Hello, thanks for the reply...
According to the Slim Bean page, I can use ANY kernel with that rom. But also, if I just have the Lupusv7 Kernel on there, the touch screen doesn't work within that, so not a ROM/Kernel conflict I belive.
I've also tried other Kernel/ROM combinations, same thing keeps on happening. Touchscreen works 100% with a SE restore, stock ROM.
Any other ideas please??
ricky7D said:
Hello, thanks for the reply...
According to the Slim Bean page, I can use ANY kernel with that rom. But also, if I just have the Lupusv7 Kernel on there, the touch screen doesn't work within that, so not a ROM/Kernel conflict I belive.
I've also tried other Kernel/ROM combinations, same thing keeps on happening. Touchscreen works 100% with a SE restore, stock ROM.
Any other ideas please??
Click to expand...
Click to collapse
It's best to use the recommended kernel as stated on the ROM thread. Try another kernel and see how things go.
僕のLT18iから送られてきた
You sure you installed device-specific patch / chose correct phone in AROMA?
Kernel or ROM issue?
popthosegaskets said:
It's best to use the recommended kernel as stated on the ROM thread. Try another kernel and see how things go.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Hello,
As previously mentioned, the reccomended kernel is Lupusv7, When i flash this Kernel into recovery mode, all looks well but as it has a touch screen interface this still doesn't work!
I'm presuming that it cannot be a conflict as it's happen before I instll the new ROM etc... the touch screen doesn't even work within the GUI of the Lupusv7 kernel.
I can get multiple ROMS to load with different kernels but so far, none have booted with the touch screen working!!
I am very much a noob but have read loads of articles on how this should be done, unless i'm missing something very obvious which isn't stated then I dont see anyone else having this issue.
Any clues people? :good:
Thanks, Ricky
AROMA?
Someguyfromhell said:
You sure you installed device-specific patch / chose correct phone in AROMA?
Click to expand...
Click to collapse
Hello Someguyfromhell,
I haven't used AROMA, the guides i've been reading haven't mentioned this!?
This is the process I went through:
flashed stock ICS ROM
flashed kernel
wipe data/cache/davlik
flashed rom
rebooted, ROM loads up and the touch screen doesn't work.
Any help you can give me on AROMA, links etc?
I'm looking right now, but a 'leg up' would be great.
Thanks for the reply.
Ricky
here what to do
- Make sure you had installed Official 4.0.4 ftf pack
- When flashing official ftf pack remember to exclude / tick these things:
1. simlock.ta (Exclude TA)
2. Kernel.sin (Exclude kernel)
3. FOTA (Exclude FOTA)
After flash successful, power on your phone and let it start completely
- Now you can start to install any ROM
1.Flash the Recommended Kernel: Vengeance , KTG Anzu , RUSH
2. Place ROM on SD card
3. Power off the phone and boot into CWM
3. Backup and restore > choose Backup
4. Wipe Data/Factory Reset
5. Mounts and storage > Format /system
6. Advanced > Wipe battery stats
7. Install zip from SD card > Choose the rom
8. if rom uses aroma Follow on screen instructions on AROMA, remember to choose "Unlocked bootloader" and also the correct kernel modules and of course the correct phone model
9. After complete installation tick "Reboot" and let the phone restart
10. Give the phone a good full charge, and enjoy ur phone !
11.THE MOST IMPORTANT THING PRESS THANKS if I helped
ricky7D said:
Hello Someguyfromhell,
I haven't used AROMA, the guides i've been reading haven't mentioned this!?
This is the process I went through:
flashed stock ICS ROM
flashed kernel
wipe data/cache/davlik
flashed rom
rebooted, ROM loads up and the touch screen doesn't work.
Any help you can give me on AROMA, links etc?
I'm looking right now, but a 'leg up' would be great.
Thanks for the reply.
Ricky
Click to expand...
Click to collapse
Then did you install the device-specific patch?
ok man, you've got the same problem like me
First thing, all roms that make your touch screen doesn't work will based on cm (e.g. cm10, slim, any jb).
and ALL STOCK roms will get no problem.
There's lot of people here got this problem and still has no clue why this problem occure to ours, so sad story.
Someone says that the touch screen firmware sould be updated to the lastest version, but i don't know how.
One solution that i found is, remove the battery to turn off then turn it on to reboot again and again. If you lucky enough, the touch screen will work like a miracle!
and the success rate is also <50% ( based on my experience only)
AROMOA guide?
Someguyfromhell said:
Then did you install the device-specific patch?
Click to expand...
Click to collapse
on all the ROM guides, I have never seen a part where it says i should install a device specific patch, do you have a link to where these may be?
Or even a ROM with guide where it says this? I'm very happy to follow that to get this working. I have no preference to CM10, Slim Bean, Racing Bean etc... as of yet i've not been able to use any of them.
Thanks for the continued response.
Ricky
THANK YOU
eakav said:
ok man, you've got the same problem like me
First thing, all roms that make your touch screen doesn't work will based on cm (e.g. cm10, slim, any jb).
and ALL STOCK roms will get no problem.
There's lot of people here got this problem and still has no clue why this problem occure to ours, so sad story.
Someone says that the touch screen firmware sould be updated to the lastest version, but i don't know how.
One solution that i found is, remove the battery to turn off then turn it on to reboot again and again. If you lucky enough, the touch screen will work like a miracle!
and the success rate is also <50% ( based on my experience only)
Click to expand...
Click to collapse
Ah ha... sounds like you have the same problem as me!
Did you manage to get any JB ROM working? If so, which one, just so I can try that also...
Does anyone else have an idea on how to update the touch screen firmware?
Really appreciate the feedback, thank you one and all!!
Ricky
ricky7D said:
Ah ha... sounds like you have the same problem as me!
Did you manage to get any JB ROM working? If so, which one, just so I can try that also...
Ricky
Click to expand...
Click to collapse
This solution is the one that i think it can move some files which related to touch screen.
http://forum.xda-developers.com/showpost.php?p=34593771&postcount=23
But sorry, it still get sometimes for the touch screen didn't response :crying:
However, as i mentioned above; you can get ALL jb rom working :fingers-crossed:
But depends on your luck. Just turn it off when the touch screen didn't response, then turn it on again (and again) untill it work.
I hoped that the new linux kernel will solve this...
No touch
eakav said:
This solution is the one that i think it can move some files which related to touch screen.
http://forum.xda-developers.com/showpost.php?p=34593771&postcount=23
But sorry, it still get sometimes for the touch screen didn't response :crying:
However, as i mentioned above; you can get ALL jb rom working :fingers-crossed:
But depends on your luck. Just turn it off when the touch screen didn't response, then turn it on again (and again) untill it work.
I hoped that the new linux kernel will solve this...
Click to expand...
Click to collapse
I have same issue have tried many stock based roms and kernels no problem but any CM based rom I have no touchscreen.
You can reboot and about 1 in 5 times it will work
Maybe it only affects certain versions of the phone. I even tried re-locking bootloader and doing official sony update then tried CM again I tried 7.1,9 and 10
same problem.
Here's where I am...
UPDATE:
So, here is where I am. Using advice from previous replies I have managed to install Xperia Ultimate HD and this is working off of the Lupus kernel without any issues. I'm still unable to get ANY Jelly Bean roms working...
Maybe my device will just not work on JB :crying:
Any other tips or tricks are greatly appreciated, would love to get JB working on here my beloved Arc S.
Ricky :good:
Any news here?
I have the same issue over here with a colleagues LT18i
I have same problem, touch screen doesn't work on many different kernels... only work on stock kernel
Any news about this problem?

[Q] How do I improve battery life ie what tweaks work?

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] [ROM][SM-T900] CyanogenMod for Tab Pro 12.2 SM-T900 (v2wifixx)

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).

Categories

Resources