Develop Bugs

[Q] HTC One V boots fine but becomes unresponsive

I am having problems with my phone becoming unresponsive.
Specs
Android Version
4.1.2 - Black JellyBean
Baseband Version
1.00.00.0521_1
Kernel Version
3.0.56
[email protected] #1
I had to flash the baseband version to the current version so that I could fix the bootloop that I was having. Right now the phone boots fine and for about the first 30 seconds my phone works great. After I try to load an app or two the phone gradually slows down until it becomes almost unresponsive or takes about 5-10 seconds to load something that should be almost instant. Ive tried two different rom's and same problems with both. Eventually the launcher will stop responding and the screen will glitch out.
On a side note, sometimes when I lock the screen and go back into my phone it will run smooth again until I try and hit the home button or open any apps.
Thanks,
Derek

Your using simons ion build for 4.1 right? Try the Jan 3rd release in his goo.im it isn't built with ion so you'll get camera and it might be a little more stable i haven't even tried his ion 4.1 because when i was on 4.1 i used his Jan 3rd kernel and it was totally bugless with pacman 19.3
(I'm on evervolv 4.2 ion ATM)
Sent from my HTC One V+ (Because the X+ isn't as bamf as my V+)
If I helped you don't say thanks, click it!!

An update to my problem. I haven't done anything to my phone except for that I left it on while it was glitching out and it somehow became stable.. I have a few small graphics glitches and it restarted once on me but its running fine as of now.. very strange. If my problem persists ill try that kernel

Try this
http://forum.xda-developers.com/showthread.php?t=1987032
And tell if this works to reduce lag even more.

phone
how do I flash a kernel when it is an iso? I need a .zip file

lytesson said:
how do I flash a kernel when it is an iso? I need a .zip file
Click to expand...
Click to collapse
It is an apk.Just download and install it.

mihirengg19 said:
It is an apk.Just download and install it.
Click to expand...
Click to collapse
No not the link you sent me, I don't think that has anything to do with my problem.
The "SuperSick-01_03_13-0033cdmarelease" comes as an ISO file

lytesson said:
No not the link you sent me, I don't think that has anything to do with my problem.
The "SuperSick-01_03_13-0033cdmarelease" comes as an ISO file
Click to expand...
Click to collapse
The apk reduces lag in general.hence suggested it since you're having lag.

[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?

Cm11 for t0lte on t0lteatt.

Well I've been running cm11 builds for t0lte on my t0lteatt (technically t0ltecan but same thing) for months with no issues. Until the dreaded March 4th nightly dropped. There were over a hundred commits that night, and something broke compatibility with my device. It keeps getting signal, then phone force closes and signal is lost. Then it gets signal, etcetera in an eternal loop. I'm wondering what I could do about this? Could a modem fix this issue? Is there anybody else out there who has been running this ROM on a t0lteatt?
I'm only asking because my device isn't supported by CM11, so I was very happy to find I could run the international build just fine. Now what do I do for CM love??? Aaaagh! Help would be awesome guys, who knows a possible solution?
Sent from my thumbs to your face.

mertin said:
Well I've been running cm11 builds for t0lte on my t0lteatt (technically t0ltecan but same thing) for months with no issues. Until the dreaded March 4th nightly dropped. There were over a hundred commits that night, and something broke compatibility with my device. It keeps getting signal, then phone force closes and signal is lost. Then it gets signal, etcetera in an eternal loop. I'm wondering what I could do about this? Could a modem fix this issue? Is there anybody else out there who has been running this ROM on a t0lteatt?
I'm only asking because my device isn't supported by CM11, so I was very happy to find I could run the international build just fine. Now what do I do for CM love??? Aaaagh! Help would be awesome guys, who knows a possible solution?
Sent from my thumbs to your face.
Click to expand...
Click to collapse
Have you tried flashing the latest drop? cm-11-20140306-NIGHTLY-t0lte.zip
Maybe stuff is unscrewed now. Nightly's are crap shoots.
Only stable releases I see are 10.X. There's a reason for that......
Have you tried any of the hybrid ROMs, like OmniROM or Dirty Unicorns. You can't swing a dead cat without hitting a killer option on those.

Yes I've tried all the newer nightlies too. It is working fine for t0lte users (which makes sense, because it's made for them) which leads me to believe it's just people like me running it on a variant device who are missing out. It works as intended on the proper device, so I don't see why they would change it back. Other ROMs just don't seem as polished and I'm OCD so rough edges are a dealbreaker. Cm11 has bugs, but none that affect my personal usage so that's why it is my daily driver. Thanks for the tip tho I'm still investigating!
Sent from my thumbs to your face.

mertin said:
Yes I've tried all the newer nightlies too. It is working fine for t0lte users (which makes sense, because it's made for them) which leads me to believe it's just people like me running it on a variant device who are missing out. It works as intended on the proper device, so I don't see why they would change it back. Other ROMs just don't seem as polished and I'm OCD so rough edges are a dealbreaker. Cm11 has bugs, but none that affect my personal usage so that's why it is my daily driver. Thanks for the tip tho I'm still investigating!
Sent from my thumbs to your face.
Click to expand...
Click to collapse
Well, it's not really different.....
[Q] difference between t0lte and t0lteatt
http://forum.xda-developers.com/showpost.php?p=42038043&postcount=5
Credit T-Macgnolia

dicksteele said:
Well, it's not really different.....
[Q] difference between t0lte and t0lteatt
http://forum.xda-developers.com/showpost.php?p=42038043&postcount=5
Credit T-Macgnolia
Click to expand...
Click to collapse
I also have a t0lteatt running the CM11 nightly for t0lte. I also installed the nightly that resulted in not being able to boot, to solve it I rebooted my phone manually to recovery and installed the previous days back over the top and I fixed it. Then I wait a couple days and tried the next nightly which worked. I am currently running yesterdays (030632014) without issue.
TDLR: the nightly from the 4th left me broken, none of the nightly's before that point ever broke my phone, also none since then have broken my phone.
Good Luck!

Mazamuda said:
I also have a t0lteatt running the CM11 nightly for t0lte. I also installed the nightly that resulted in not being able to boot, to solve it I rebooted my phone manually to recovery and installed the previous days back over the top and I fixed it. Then I wait a couple days and tried the next nightly which worked. I am currently running yesterdays (030632014) without issue.
TDLR: the nightly from the 4th left me broken, none of the nightly's before that point ever broke my phone, also none since then have broken my phone.
Good Luck!
Click to expand...
Click to collapse
Thanks for the help, but it's still broken on my end. (Just tried the same nightly) This is getting really weird. It's happening right away, clean install. Can't get the popup to go away long enough to do anything. Any suggestions what I could try? It's making me mental!
Sent from my thumbs to your face.

mertin said:
Thanks for the help, but it's still broken on my end. (Just tried the same nightly) This is getting really weird. It's happening right away, clean install. Can't get the popup to go away long enough to do anything. Any suggestions what I could try? It's making me mental!
Sent from my thumbs to your face.
Click to expand...
Click to collapse
I am not sure I understand the symptoms, are you saying that it boots up just fine but the phone keeps getting and losing signal? Or is it booting up just fine then rebooting after the phone gets and loses signal?
Welll no matter I would take a full backup of your system and then wipe it clean and install the known working 10.2, just to see if it is indeed a hardware problem. If 10.2 works then maybe take a nother backup of that you can at least swap back and forth while you work on the issue.

Mazamuda said:
I am not sure I understand the symptoms, are you saying that it boots up just fine but the phone keeps getting and losing signal? Or is it booting up just fine then rebooting after the phone gets and loses signal?
Welll no matter I would take a full backup of your system and then wipe it clean and install the known working 10.2, just to see if it is indeed a hardware problem. If 10.2 works then maybe take a nother backup of that you can at least swap back and forth while you work on the issue.
Click to expand...
Click to collapse
Hey thanks for working through this with me, I really appreciate it! What's happening is it boots just fine. But I get the error popup "com.android.phone has stopped". When I hit okay it immediately comes up again. Forever. I also just had a scary missing imei problem happen just now and spent the last couple hours getting THAT sorted out. But now I'm back on the march 1 nightly and everything is just fine. I just can't run anything newer than that and I don't get why.
Sent from my thumbs to your face.

They just posted an M4, maybe that will work?
Sent from my GT-N7105 using xda app-developers app

Mazamuda said:
They just posted an M4, maybe that will work?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
They did? I don't see it on get.cm?
Sent from my thumbs to your face.

Its on the cyanogenmod.org blog.
Sent from my GT-N7105 using xda app-developers app

Wooooooo I got today's nightly running (march 8th)!! I had a sudden urge to try a different recovery just to make sure I had tried everything. Installed philz touch, then installed CM. This time it finally worked! I wonder if it was twrp giving me problems all this time. Just so bizarre I had zero issues updating every day for months and then suddenly just couldn't get it working at all.
In any case it seems good for now. Thanks for all the advice!
Sent from my thumbs to your face.

mertin said:
Wooooooo I got today's nightly running (march 8th)!! I had a sudden urge to try a different recovery just to make sure I had tried everything. Installed philz touch, then installed CM. This time it finally worked! I wonder if it was twrp giving me problems all this time. Just so bizarre I had zero issues updating every day for months and then suddenly just couldn't get it working at all.
In any case it seems good for now. Thanks for all the advice!
Sent from my thumbs to your face.
Click to expand...
Click to collapse
Excellent.
Was it TWRP 2.6.3.1 ?? I think that's the one that works with newer ROM builds. At least for me.....
Or ....... Was it the March 8th build ...... Did you flash that in TWRP ?
Also, keep a copy of each on your phone. If one doesn't work just flash the other, then you can reboot to recovery to the other one.

mertin said:
Wooooooo I got today's nightly running (march 8th)!! I had a sudden urge to try a different recovery just to make sure I had tried everything. Installed philz touch, then installed CM. This time it finally worked! I wonder if it was twrp giving me problems all this time. Just so bizarre I had zero issues updating every day for months and then suddenly just couldn't get it working at all.
In any case it seems good for now. Thanks for all the advice!
Sent from my thumbs to your face.
Click to expand...
Click to collapse
That was going to be my next question. I have heard lots of reports of people running CM11 and having problems with TWRP, I use CWM and it has always been rock solid.
Glad your back up and running, enjoy the crack-flashing!

dicksteele said:
Excellent.
Was it TWRP 2.6.3.1 ?? I think that's the one that works with newer ROM builds. At least for me.....
Or ....... Was it the March 8th build ...... Did you flash that in TWRP ?
Also, keep a copy of each on your phone. If one doesn't work just flash the other, then you can reboot to recovery to the other one.
Click to expand...
Click to collapse
It was 2.6.3.1 and I even tried the newer 2.6.3.7 for t0lte and it didn't work. But all good with cwm. There must have been some tiny change that twrp wasn't flashing properly. Whatever it was, just glad to have that behind me!
Sent from my thumbs to your face.

mertin said:
It was 2.6.3.1 and I even tried the newer 2.6.3.7 for t0lte and it didn't work. But all good with cwm. There must have been some tiny change that twrp wasn't flashing properly. Whatever it was, just glad to have that behind me!
Sent from my thumbs to your face.
Click to expand...
Click to collapse
Most excellent. Congrats

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

curious

Hello everyone I got the nextbit robin the other day, and seem to notice some things. wondering if its normal.
I get the fuzzy snowy screen for a few seconds whenever the device is locked and i go to open it and also when i unlock the screen from twrp. Does anyone have this?
Also I noticed on the latest twrp 3.1.1-0 that the time is off by like nine hours? cant seem to figure how to fix it. other than that i am running the latest aicp and loving the device.
thanks

the_rooter said:
Hello everyone I got the nextbit robin the other day, and seem to notice some things. wondering if its normal.
I get the fuzzy snowy screen for a few seconds whenever the device is locked and i go to open it and also when i unlock the screen from twrp. Does anyone have this?
Also I noticed on the latest twrp 3.1.1-0 that the time is off by like nine hours? cant seem to figure how to fix it. other than that i am running the latest aicp and loving the device.
thanks
Click to expand...
Click to collapse
The twrp thing is normal.
But i dont know about the "fuzzy snowy screen". Was that on stock too or is it just in the custom rom?
Cheers, Jim

the_rooter said:
Hello everyone I got the nextbit robin the other day, and seem to notice some things. wondering if its normal.
I get the fuzzy snowy screen for a few seconds whenever the device is locked and i go to open it and also when i unlock the screen from twrp. Does anyone have this?
Also I noticed on the latest twrp 3.1.1-0 that the time is off by like nine hours? cant seem to figure how to fix it. other than that i am running the latest aicp and loving the device.
thanks
Click to expand...
Click to collapse
jimandroidnerd said:
The twrp thing is normal.
But i dont know about the "fuzzy snowy screen". Was that on stock too or is it just in the custom rom?
Cheers, Jim
Click to expand...
Click to collapse
TWRP has a minor issue with the display showing a rainbow-grainy type screen before showing before it shows what it's supposed to.
Lineage OS (And based ROMS, AICP is based on LOS?, correct me if I'm wrong) have a bug where it shows a similar type of screen (Only black and white [Fuzzy snowy screen]) before returning to normal. This issue is not present on OmniROM, AOSPA and I assume some other ROMS that I have not tested (Including stock, I hated stock ). We can only hope that is fixed in the future.
I wouldn't be worried about the problem/s Hope this helps.

jimandroidnerd said:
The twrp thing is normal.
But i dont know about the "fuzzy snowy screen". Was that on stock too or is it just in the custom rom?
Cheers, Jim
Click to expand...
Click to collapse
DECHTECH said:
TWRP has a minor issue with the display showing a rainbow-grainy type screen before showing before it shows what it's supposed to.
Lineage OS (And based ROMS, AICP is based on LOS?, correct me if I'm wrong) have a bug where it shows a similar type of screen (Only black and white [Fuzzy snowy screen]) before returning to normal. This issue is not present on OmniROM, AOSPA and I assume some other ROMS that I have not tested (Including stock, I hated stock ). We can only hope that is fixed in the future.
I wouldn't be worried about the problem/s Hope this helps.
Click to expand...
Click to collapse
ok that i did notice that i was on AICP and it did that. so to cancel out anything i returned it to stock and then flashed the 7.1.1 update just got giggles, and flash twrp all good. I am going to stay stock for a while.
Now is the time being off in twrp another bug?

the_rooter said:
ok that i did notice that i was on AICP and it did that. so to cancel out anything i returned it to stock and then flashed the 7.1.1 update just got giggles, and flash twrp all good. I am going to stay stock for a while.
Now is the time being off in twrp another bug?
Click to expand...
Click to collapse
I think so but I'm not sure. I think I managed to set it to the correct time at one point but forgot lmao (soz).
Keep an eye out to see if the Robin LOS maintainer has fixed the issue. Once done and LOS based roms update their sources you'll be able to flash AICP again without the bug