Database Users

constant FC's, freezes and reboots :(

Hey guys, I've had my transformer for just under a year and love it to death, but for the last couple of days it has been giving me hell! I was running ARHD 3.4.1 with Guevor's ICS kernel (can't remember version, either 19.4, 20 or 21). Anyway, all was well until I changed to ARHD 3.5.1 and switched to raymanfx's harmony kernel to try it out. I couldn't get my videos to play on mxplayer, FC's on apps, random freezes and tablet kept randomly rebooting. So I reflashed ARHD 3.5.1 again, same, reflashed guevor kernel, same, updated CWM to Rogue XM Touch Recovery v1.5.0-R1, same. Finally used this method: http://www.theandroidsoul.com/update-and-restore-eee-pad-transformer-to-stock-ice-cream-sandwich/ to flash back to stock, no root, no nothing annnnnd... same! Same issues no matter what I try. So my question is, with a few weeks of ASUS global warranty left (bought it in HK so I can't take it back to 'shop') can/should I send it back now that it's flashed back to stock without them finding out I rooted it? Or is there something I'm missing that you guys can think of. Please let me know asap in case I do need to send it back. Thanks in advance. Oh and let me know if you need more info

Maybe a stupid question...
Did you do a factory reset in between flashing the different roms and kernels? Full factory reset, wipe cache and dalvik?

Not a stupid question at all, but yes, I tried all three
Sent from my R800i using Tapatalk 2

I can't think of anything else causing that behaviour. Restoring apps, data and system data with Titanium has been a source of trouble for me in he past. Restoring setCPU with profiles that don't work well with the new kernel for example. But I guess that's not the case here. At least stock ROM should be working.
Sorry, maybe someone else has another idea.

Samsung GT N7000 strange issue fixed

Hi
Want to share with you an issue which seems to be fixed in a little different manner. I have been experimenting with different ROM, last was with Ultimate and when the update came i updated to XLT4. Post this series of issues so uninstalled the ROM, rebuild with Paranoid and still issue was there - system will reboot at random intervals. All the kernels tried and experimented as given but restarts wont stop. Worse thing is that it will enter a boot loop or stuck at Samsung log. Also tried to check APN settings, all the technical steps in every forum.....but no result.
Finally the new version XLT5 and XLT6 tried but still the problem existed. As a check i installed Ram booster (though i never believed in task killers) and strange but true no more restarts and works smooth.
I am not sure if this is how this should have been resolved, but will be happy if any users faced this issue and a similar thing resolved the problem. Now running with XLT5 and a RAM Booster things are pretty smooth with all root privileges.
Thanks for your time.

Did you wipe data/factory reset first before flashing roms? That might be causing the problems

HELP! System UIDs Inconsistent

Hi guys,
ok so basically I asked for help on this in a thread thinking it was ROM related, but now I know it's not. I flashed cm 10.2 after stock 4.3 and what happens is that when I try to restore my backups they don't work (I mean TB installs them, but they FC as soon as I open them). Thinking it was CM related I tried another 4.3 ROM and same issue there (I tried all 4.3 ROMs on xda).
I then decided to go back to 4.2.2 thinking it was 4.3 related and again with yesterday's PAC nightly the issue is still there...
This is what I see when I reboot my phone:
"System UIDs Inconsistent
UIDs on the system are
inconsistent, you need to wipe
your data partition or your
device will be unstable.
I'm Feeling Lucky"
Any ideas guys?

Get the Fix Permissions application from the Play Store.
Sent from my Nexus 4 using Tapatalk 4 Beta

theraf90 said:
Hi guys,
ok so basically I asked for help on this in a thread thinking it was ROM related, but now I know it's not. I flashed cm 10.2 after stock 4.3 and what happens is that when I try to restore my backups they don't work (I mean TB installs them, but they FC as soon as I open them). Thinking it was CM related I tried another 4.3 ROM and same issue there (I tried all 4.3 ROMs on xda).
I then decided to go back to 4.2.2 thinking it was 4.3 related and again with yesterday's PAC nightly the issue is still there...
This is what I see when I reboot my phone:
"System UIDs Inconsistent
UIDs on the system are
inconsistent, you need to wipe
your data partition or your
device will be unstable.
I'm Feeling Lucky"
Any ideas guys?
Click to expand...
Click to collapse
you can find a solution in this post:
http://forum.xda-developers.com/showpost.php?p=9365024&postcount=4
I tried it and it worked.

[Q] Custom ROM Problem with Keyboard and Home Button

I'm sorry to sound noobish, but every time I flash a ROM on my Nexus 4 (mako) that isn't a Cyanogenmod build (10.2-20130904-NIGHTLY-mako) , my home softkey becomes completely useless and the AOSP or AOKP keyboard constantly crashes. I was told this is a known bug in certain source codes as far as the keyboard is concerned in 4.2.2 builds, but I'm still mystified by the home button issue and as to why I other people can be using the same ROMs that I can't without a problem. Is there a certain version of GAPPS that I can flash to avoid this problem, or is there a known fix? I always wipe data and cache when flashing, so I'm pretty sure this isn't a user error, other than which version of GAPPS I'm flashing (gapps-jb-20130813-signed.zip).

trevorftard said:
I'm sorry to sound noobish, but every time I flash a ROM on my Nexus 4 (mako) that isn't a Cyanogenmod build (10.2-20130904-NIGHTLY-mako) , my home softkey becomes completely useless and the AOSP or AOKP keyboard constantly crashes. I was told this is a known bug in certain source codes as far as the keyboard is concerned in 4.2.2 builds, but I'm still mystified by the home button issue and as to why I other people can be using the same ROMs that I can't without a problem. Is there a certain version of GAPPS that I can flash to avoid this problem, or is there a known fix? I always wipe data and cache when flashing, so I'm pretty sure this isn't a user error, other than which version of GAPPS I'm flashing (gapps-jb-20130813-signed.zip).
Click to expand...
Click to collapse
The known issue you are talking about is the JSS deadlocks? if yes, then it is not the problem with you.. for you it force closes the keyboard.. are you following the procedure of installing rom properly? are you doing dirty flash (flash without wiping data)? you can find out if gapps is responsible by booting into a freshly installed rom without installing gapps and see if the problem persists..

You should also format the /system partition when you flash a new rom.
For some roms the Home button stop working for me and to fix it I had to install gapps, but most CM based roms I use don't have that issue.
As for keyboard, I always delete the default keyboard from the rom and use Google Keyboard.

Andre_Vitto said:
The known issue you are talking about is the JSS deadlocks? if yes, then it is not the problem with you.. for you it force closes the keyboard.. are you following the procedure of installing rom properly? are you doing dirty flash (flash without wiping data)? you can find out if gapps is responsible by booting into a freshly installed rom without installing gapps and see if the problem persists..
Click to expand...
Click to collapse
Please explain what JSS deadlocks are. I don't dirty flash. I always wipe data. As for the keyboard and home buttons not functioning properly,I have this problem with XenonHD, PACman ROM, AOKP and CM variants.

trevorftard said:
Please explain what JSS deadlocks are. I don't dirty flash. I always wipe data. As for the keyboard and home buttons not functioning properly,I have this problem with XenonHD, PACman ROM, AOKP and CM variants.
Click to expand...
Click to collapse
No your problem is not the jss deadlocks.. it happens when you type very fast or something.. it phone vibrates for like 5-10 sec and then restarts. I dont think its your problem. Sorry mate I have no idea why you are having the keyboard and homescreen issue even when you are are doing a factory reset every time you flash.. and why its not happening with CM 10.2..

Andre_Vitto said:
No your problem is not the jss deadlocks.. it happens when you type very fast or something.. it phone vibrates for like 5-10 sec and then restarts. I dont think its your problem. Sorry mate I have no idea why you are having the keyboard and homescreen issue even when you are are doing a factory reset every time you flash.. and why its not happening with CM 10.2..
Click to expand...
Click to collapse
Well, that's unfortunate. I've found that the RevoltHD ROM doesn't have problems, but that's because it's got integrated GAPPS.

Been having the same issue with my Nexus 4, after installing GAPPS the keyboard crashes and the home button stops responding. Did anyone figured it out by any chance? Thanks.

I still don't know what caused it, but I figured out that more recent nightly versions of those ROMs don't have that problem. I'm using AOKP currently and that used to be a problem ROM.

Take off vibration and sound and all the bells and whistles and your keyboard should be fine if the issue isn't Rom specific. Also, it could be kernel related.....try boosting touch input if nothing else
Sent by flying midget

I get the same problem, I factory reset each time I switch ROMs. I was trying with Vanir a couple of days ago and couldn't get the home button to work, tried OmniROM and it worked perfectly, went back to Paranoid it worked perfectly again, went back to Vanir and it didn't work. Was odd.

Hello Everyone,
Nexus 4
Paranoid Android 4.2Beta1
Franco Kernel
I just upgraded to PA 4.2Beta1 from PA 4.1.......
after installing the rom.....when i use my browser or messenger where we require keyboard....the Keyboard doesnt pop up....whats up with this....and also the back button of my navigation bar doesnt work.......this even happened with carbon rom a few days back...when i was experimenting with it.....but then i restored to PA4.1 due to the above given problems....plz offer a solution to this...

The same problem

keyboards not working
please help me my keyboards are not working . i have installed an custom rom.

Problems with CM12.1

Hello,
I have posted this on the cyanogenmod forum but everyone seems to be on holiday as I'm getting no replies. I'm hoping someone on here can help.
I recently had CM12.1 running on my S5 SM-G900F for about six months with no problems. I then switched over to CM13 and used that for about a month without any problems.
I decided to go back to CM12.1, I flashed the same CM12.1 Snapshot file that I had been using previously and it installed without error but when I rebooted the phone it would crash and reboot in a loop during start up. I wiped the phone and tried the install again about four or five times having the same problem until on the final attempt it managed to load the OS. Now that I have the OS running I cant connect to WIFI, the 'back' and 'recent apps' buttons on the phone don't respond (the home button does work), the camera app doesn't work (I get the error 'Can connect to Camera') and it keeps crashing and restarting on reboot. Everything else seems to work but the phone seems sluggish and there may be other errors that I haven't come across yet.
I thought that there may be a problem with the zip file I was flashing so I downloaded it again but it did the same thing. I've tried wiping and reinstalling several times but I get the exact same problems. The file I'm flashing is:
cm-12.1-20151007-SNAPSHOT-YOG4PAO333-klte.zip
If I go back to CM13 everything works fine so the problem is only with CM12.1.
I'm at a lost to explain why this keeps happening as I've had this running fine on my phone previously and wiping the phone and starting again doesn't do anything to solve the problem.
Any ideas please?

Come on people! Have a guess, I'm really stuck here!

I myself have not installed any custom roms on my s5 yet (bc of knox 0x0 lol) but try reverting back to the stock rom and then install cm12.1 again, maybe it could work.

Thanks, but I've tried that. Both stock rom and CM13 work without a problem. The issue only seems to be with CM12.1.

Can you tell what bothered you to go away from cm13 back to cm 12.1?
caned_monkey said:
Thanks, but I've tried that. Both stock rom and CM13 work without a problem. The issue only seems to be with CM12.1.
Click to expand...
Click to collapse

ezantera said:
Can you tell what bothered you to go away from cm13 back to cm 12.1?
Click to expand...
Click to collapse
CM13 sucks!!! snapchat and instagram keeps on crashing, now I'm using resurrection remix 5.7.3, that sucks too!!