yashsingh1/xdaforums huggingface dataset:
[About XDA developers] FearTheCowboy:
I'm somewhat frustrated by this too. I'd like to add to discussions in the surface subforum, but I'm still a noob here. I don't have pedantic questions to ask, so I can't rev my post count in meaningless ways in other forums.

Perhaps someone could drop the minimum post count in that forum?
[Galaxy S III Q&A, Help & Troubleshooting] MOLOTOFF27:
Hi guys, I have a problem about the 4.2 keyboard..

I am using 3x4 with t9.. The problem is that I don't want that the keyboard auto complete the letters.?

I will flash 4.1.1 original Samsung keyboard..

could someone give me the link where I can download 4.1.1 stock keyboard or update the keyboard..

thx already..:)

Samsung Galaxy SIII cihazımdan Tapatalk 2 ile gönderildi...
[Galaxy S III Q&A, Help & Troubleshooting] MOLOTOFF27:
Please can someone help me ?

Samsung Galaxy SIII cihazımdan Tapatalk 2 ile gönderildi...
[Galaxy S III Q&A, Help & Troubleshooting] norpan111:
You uninstalled stock keyboard and installed 4.2 keyboard? How?

Skickat från min GT-I9300 via Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] MOLOTOFF27:
No I installed rom, but I can't use 4.2 keyboard because of this I will flash 4.1.1 keyboard..xS

Samsung Galaxy SIII cihazımdan Tapatalk 2 ile gönderildi...
[Galaxy S III Q&A, Help & Troubleshooting] MOLOTOFF27:
I know it was my false, I had confused the sections..

Samsung Galaxy SIII cihazımdan Tapatalk 2 ile gönderildi...
[Galaxy S III Q&A, Help & Troubleshooting] norpan111:
What rom had 4.2 keyboard?

Skickat från min GT-I9300 via Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] Glebun:
most of them do
[Galaxy S III Q&A, Help & Troubleshooting] mahall1988:
just off the top of my head and i could be wrong but doesnt omega files app have a link to the stock keyboard
[Galaxy S III Q&A, Help & Troubleshooting] MOLOTOFF27:
I don't know if it is 4.1.2 or 4.2 I'm using rgui rom..

Samsung Galaxy SIII cihazımdan Tapatalk 2 ile gönderildi...
[Galaxy S III Q&A, Help & Troubleshooting] mahall1988:
yes just checked it does have samsung keyboard
[Galaxy S III Q&A, Help & Troubleshooting] MOLOTOFF27:
Impossible no one know how l could find it.. xS :(

Samsung Galaxy SIII cihazımdan Tapatalk 2 ile gönderildi...
[Galaxy S III Q&A, Help & Troubleshooting] MOLOTOFF27:
I am always waiting for help :(

Samsung Galaxy SIII cihazımdan Tapatalk 2 ile gönderildi...
[Galaxy S III Q&A, Help & Troubleshooting] norpan111:
Is rgui miui? Based on aosp or samsung?

Skickat från min GT-I9300 via Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] MOLOTOFF27:
I'm not sure but I think it's based on aosp? How can I know it?

Samsung Galaxy SIII cihazımdan Tapatalk 2 ile gönderildi...
[Galaxy S III Q&A, Help & Troubleshooting] MOLOTOFF27:
I need help xS

Iyi Forumlar..

Samsung Galaxy SIII Cihazımdan Gönderildi...
[Galaxy S III Q&A, Help & Troubleshooting] MOLOTOFF27:
Could someone help me ?

Iyi Forumlar..

Samsung Galaxy SIII Cihazımdan Gönderildi...
[Galaxy S III Q&A, Help & Troubleshooting] norpan111:
You can't have Samsung apps with aosp roms

Skickat från min GT-I9300 via Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] MOLOTOFF27:
I still search for the keyboard, but I couldn't find it.. :mad::(

Iyi Forumlar..

Samsung Galaxy SIII Cihazımdan Gönderildi...
[HTC One X+] f100cleveland:
When I boot into recovery, it'll give me the TWRP screen, the one you get before it goes to the touch screen, then the screen goes black and boots to the white htc screen stays there. I flashed CWM and it'll boot into the recovery, the recovery pops up but I'm unable to select anything and after about 3-5 seconds, it goes black and boots to the white htc screen. I've flashed the correct boot.img also just in case that got messed up but that doesn't seem to help either.

Any ideas on stuff I can try next?

Oh yeah, also, it seems that I lost the ability for my computer to see whats on the internal storage. It just shows up as pictures and nothing else. I tried on two different computers that I'd synced up with before and they both act the same. I can use root explorer and see everything is still there. But from the computer, there is nothing.
[HTC One X+] f100cleveland:
Ended up flashing stock recovery and doing a factory reset. Sucks I lost all my sdcard data, but at least I can get to the recovery now.
[RAZR HD General] R3dbeaver:
Hello,

I got the regular (Droid) RAZR XT910 from Rogers and now they're offering me a deal to upgrade to a new phone for (nearly) free.

So far, i'm loving my XT910 even if Moto broke my heart back then after releasing the MAXX since my biggest pet peeve is the battery life... but other than that (and the "ok" screen) it's a great phone! nice and thin, the way i like it.

But few months ago RAZR HD is out and it seems to fix everything I loath from XT910... and I was drooling over it. But now? Not so sure.

So would anyone recommend for or against me upgrading to RAZR HD at this point of the year? Or anyone can recommend another phone? (no, we don't get RAZR HD MAXX here in Canada)(but we do have Galaxy SIII...)(..or iPhone5)

Thanks!
[RAZR HD General] thund3rbay:
You love the razr ? your really love the razr hd !

Samsung Galaxy S3 is a great device.... but call quality and RF ( signal ) is not good as the RAZR HD ...

Galaxy S3 have many roms ... Razr HD is limited for the moment ... but Razr HD have the bootloader unlocked !

Galaxy S3 if you use the stock rom have touchwiz ... i really don't like !
[RAZR HD General] R3dbeaver:
it does??

also, CES is out today. Tegra 4 announced. Should i just wait a few more months?
[RAZR HD General] Motorolalover:
It's always good if you can wait... I have been in same situation and finally decided to get the Razr HD. Technology is always evolving.. and trust me whatever phone you buy, it will be outdated in few months. So imo.. Go check Razr HD in the store.. if you really like it.. go for it.
[RAZR HD General] R3dbeaver:
Thanks! Last question, is the Rogers version has jelly Bean yet?
[RAZR HD General] danifunker:
Hey Buddy,

I helped out in the RAZR forum for a while... I'm still helping out there of course but I totally recommend the RAZR HD. This is a very nice phone and the battery life is amazing. Coming from a Droid 4 (which had the same size battery as a RAZR OG) this battery lasts me an entire day with what I consider abuse (excess usage), yesterday I really killed it (spent time in a movie theatre and a comedy club, where there is 0 signal) and I still ended up down to around 19%.

The UI is great, and the phone is much smoother than any OMAP processor devices I've ever used.

Saying that, you might want to wait I always change my phones like once a year anyways; but this is the first phone that I've purchased (on Rogers) since I've went Android, and the HD interface is really beautiful. The Jelly Bean upgrade is just around the corner, I think it will be dropping later this month according to Rogers, and I have a feeling there will be a much larger development community built here since the bootloader is a straightforward unlock, which means I might not jump ship on the entire device once Moto stops making updates for it.

If I could change one thing in the phone, it would be the amount of memory as I would have thrown in 2GB RAM, to ensure it can run the next version of Android, but either way this phone is awesome.
[Android Apps and Games] jujuburi:
If you're a Swype user you probably already know how much problem we were having with dictionary wiping issue, auto space issue etc.

I think they have learnt something from their mistake and finally bring an update. The new version is 1.4.0.11523. Attaching apk is against the rules here, so just go to http://beta.swype.com/android/get/ and download it.

No registration is needed as well.

Sent from my GT-N7100
[General Questions and Answers] thehorseandroid:
I own a Samsung galaxy mini and i was trying to install a custom ROM but during the process the screen went black and nothing responds not even the charger but the phone does get warm during charging even tho nothing shows up on screen. If i plug the USB to the computer and press Home key, vol UP and the power key the computer recongised a device is connected and install drivers for a Samsung modem and stuff but yet again nothing on the phone screen i have tried using Odin and the program reconises there is a device connected also but when i begin to do the process Odin either crashes on the PC or it gets to set up connection then the timer is going but nothing happens on screen or on Odin.

pls help as i really am tired of using a crappy back up Nokia

Daniel
[General Questions and Answers] sembre:
Samsung service centre

Problem solved .:rolleyes::rolleyes:
[Galaxy Note II Q&A, Help & Troubleshooting] adytum:
Well that's intriguing. Sorry if I missed it in your extensive post, but have you tried going all stock and updating to 4.1.2 via kies or stock update to eliminate or confirm whether it's something in 4.1.2 itself? I haven't checked in a while (from Norway myself), but I believe official 4.1.2 is available for Scandinavia now.
[Galaxy Note II Q&A, Help & Troubleshooting] niehof:
I have this strange reboots on my N7105 also. I'm on 4.1.2 with Deadman12' DLL1 Rom. I was not able to reproduce the reboots. Did not have them with T-Mobile branded 4.1.1 Rom.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy Note II Q&A, Help & Troubleshooting] E90 Commie:
Yes, I have also tried to flash the emergency DLJ2 ROM including PIT repartitioning without success. I have also tried the LL7 stock ROM a couple of times, in those cases with full wipe made in CWM before rebooting into download mode and flash through Odin (PC).

Since I hadn't any success with any 4.1.2 ROM even if the reboot frequency varies, it seems to be some kind of compatibility problem - the question is what.

When I flashed the LL7 stock ROM, it updated the bootloader and radio without any problems so now I am on BP 0.2 with the LL7 radio and latest bootloader. Without any problems.

Interestingly, the ROMs that has worked best (with 4.1.2) has been Kingdroid 2.1 and JellyBam 3.3.0. Since the reboot frequency varies, it seems to be differenses in the ROMs that causes it.

It is also worth to mention that I have noticed different reboot frequency on the same ROM in connection with reflashing.

That somehow points towards a CWM problem. I.e. that something goes on during the flash and that "something" somehow causes problems with the 4.1.2 ROMs.
[Galaxy Note II Q&A, Help & Troubleshooting] E90 Commie:
This certainly points towards some kind of compatibility issue with 4.1.2 ROMs.

There is one theoretical possibility and that is if there are different batches of N7100/N7105 and that there are some kind of internal difference that creates the problems.

Otherwise, I suspect the CWM.

As I wrote before, on the N7000, I experienced problems with CWM flashing and solved them by switching to the RedPill Recovery in Abyss 3.9 kernel. It is also worth to mention that CWM worked well later, with ICS and JB. That problem persisted during the GB times with older kernels.
[Galaxy Note II Q&A, Help & Troubleshooting] adytum:
Have you tried twrp? Though I can't see how the procedure of flashing zips or having a certain recovery latent on your phone could affect rom behaviour, it's worth a shot.

If it were me, I'd approach it pseudo-scientifically, and start going completely stock and wiped unrooted, updating to 4.1.2 through the phone ota, simply leaving it in standby for a long time without doing or installing anything and see what happened. There might be the off chance that your NAND could be corrupted, so as to eliminating a few options, doing tests in a completely stock, non-Odin'ed environment could get you on your way.
[Galaxy Note II Q&A, Help & Troubleshooting] E90 Commie:
Thanks for the answer.

I will try the suggestions but I think that I will wait a little while, perhaps for a newer update than the LL7 since I have spent many days troubleshooting already and since I also formatted my memory card and therefore removed my old Titanium backups (in order to start fresh), it has taken me a while to configure everything again.:D

I have considered NAND corruption and that is why I tried a PIT repartition with the emergency rescue firmware posted here. I have also done full wipes including format /system.

It is worth to mention that the strange thing here is that stability returns immediately when I flash BatteryPlus 0.2/4.1.1.

The other important thing here is that the reboot behavior depends on the ROM, complete stock DLL7 reboots insanely, Kingdroid and JellyBam works for a far longer time before rebooting. What I think is strange, regarding the theory of NAND corruption, is the fact that there is no problems with the flashing itself and on the same time, the behavior differs between different ROMs. Since the difference is hours between the first reboot, it is really hard to pinpoint the exact cause.

The only idea I can think about then is to flash stock ALJ3 through Odin and then try to run the OTA from there.
[Galaxy Note II Q&A, Help & Troubleshooting] duowing:
It seems like you might need to do what others are doing to try and see what's going on. You may need to start pulling the last_kmsg log. It's /proc/last_kmsg Unfortunately I don't know how to read them well, but others do. This at least could help to give a clue as to what's going on. I was going to ask if you did the format /system, but I saw you mentioned you've done that before. I see that you've also mentioned about trying a full reset with noting installed, but have you tried without installing accounts or at least say restoring accounts like google, samsung, and dropbox, but turning off the sync/backup/restore for them?

Also one thing to try and this bugs me about odin. Is a lot of these full odin firmwares still don't seem to wipe everything. So after flashing through odin you may want to boot to regular recovery and do a factory reset. I've had issues where after flashing new firmwares with odin my phone wouldn't boot. It was leaving /data or not completely wiping /data and I would run into staying at boot logo or if I got the phone on continuous force closes. I was going into cwm or whatever recovery and doing what you said. Format /system, /data, /cache. Then I'd battery pull wait about 10-15 seconds, then put the battery back in and go to download mode. Then I would flash the odin file which would then set up everything 100% factory. Of course I'd have to re-use the CF-root package, but that's not a big deal. I've encountered the odin issue not doing a proper wipe with my N7000, N7100, i9300, i777, i747. Also for what it's worth custom roms don't matter that much to me so I've completely stuck with stock recovery and just use mobile odin to flash new firmwares or kernels. I also use the latest Perseus kernel.
[Galaxy Note II Q&A, Help & Troubleshooting] mitky82:
Hm, and i have randomly reboots after update to 4.1.2

Nothing is help me, wipe device,factory reset, wipe memory and all thing. Only when remove chrome from system app reboots stoped. From 2 days i dont have that app installed on phone and problem is gone. I cant explain how it affect to system, but problem is	gone.

Try :)
[Galaxy Note II Q&A, Help & Troubleshooting] E90 Commie:
I have taken the following steps during the flashing:

1. Wipe Data

2. Wipe Cache

3. Wipe Dalvik Cache

4. Format /system

5. Format /preload

Some of the 4.1.2 ROMs reboots already during initial setup, i.e. they fail to complete the setup guide. The reboot can happen after putting the Google account in or under Dropbox setup for example. Otherwise, it reboots without doing anything in some cases.

The strange thing is that immediately when I flash the BP 0.2 from the same recovery, stability returns. So I can have everything else the same, just flashing BP 0.2 and everything works great.

Regarding Odin. The procedure I have followed when I flashed stock DLL7 that way has been:

1. Boot into CWM, wipe data/factory reset, wipe Dalvik, format /system and format /preload (just in order to have everything wiped since the stock ROM doesn't do it).

2. After wiping in CWM, reboot into stock recovery/download mode and flash the DLL7 by Odin.

It is also worth to mention that I have checked the MD5 checksum on all ROMs in order to make sure that they are OK.

Still, despite wiping in CWM before flashing DLL7, the rebooting persisted.

Since it seems like this thread provides great input, I am planning to spend tomorrow with a new attempt to get 4.1.2 up and running.

I am going to remove Chrome and start from the stock 4.1.2 but will try to move to a custom ROM quickly since I want deodex etc. One option is obviously to flash a deodexed stock ROM or something.
[Galaxy Note II Q&A, Help & Troubleshooting] E90 Commie:
Sounds great, I will try that tomorrow then.

Flash a new 4.1.2 ROM, just skip the initial setup and then remove Chrome as soon as possible and hope that it will solve the problem.

Edit: BatteryPlus 0.2 doesn't have Chrome at all. It would be great if that is the cause of the reboots and perhaps already tonight I will do a very simple test by flashing one of the custom ROMs through CWM and then put Root Explorer in ASAP and then remove Chrome. Then I can watch the device over the night.

The theory is certainly interesting.
[Galaxy Note II Q&A, Help & Troubleshooting] mitky82:
Strange, but helps for me. Hope and for you :)

Dont flash rom again if you are now on 4.1.2

Just wipe dalvik and cache, fix permisions and start phone.

I dont reflash rom, just eliminate one by one system app who i dont use and test for some time.

Mostly reboots i have when i surf in internet with stock browser. About a 10-15min an BAM-reboot. Now i use with hours stock browser and dont have any reboots after remove that app. Im not shure that from rom or that who i update from market is buggy, but never use again chrome :)

Dont remove CromeBookmarksSyncAdapter.apk that apk is for sync bookmarks with stock browser and google.
[Galaxy Note II Q&A, Help & Troubleshooting] E90 Commie:
I am on 4.1.1, BatteryPlus 0.2.

My reboots hasn't been in the browser though, most of them has been in completely random manner. Either during initial setup or randomly in different apps or when the device has been completely untouched, for example during the night.
[Galaxy Note II Q&A, Help & Troubleshooting] mitky82:
I have in other app, but mostly in browser. I dont know, try and test. Hope problem is gone ;)

With 4.1.1 i have too, but for time to time, for 2-3 days is one restart. After 4.1.2 i insane from reboots.

Sorry for bad Eng, but i think you understand me :)
[Galaxy Note II Q&A, Help & Troubleshooting] E90 Commie:
I saw a possible explanation in another thread about issues on XXDLL7. It seems to point toward some kind of problem with CWM/custom recoveries in general and the XXDLL7 with the updated bootloader.

That could be a possible explanation for the problems.

I can live without a custom recovery for a while but I don't like it very much since I want to be able to flash mods etc.

The theory seems to be that Samsung changed something in the partition scheme in the XXDLL7 which results in problems when a custom recovery is used.
[Galaxy Note II Q&A, Help & Troubleshooting] E90 Commie:
Latest update:

I have just made a full wipe including format /system in CWM and reflashed XXDLL7 through PC Odin followed by an extra factory reset (wipe data) in stock recovery.

I tried an emergency restore with Kies but it proposed the old ALJ3 since it seems like the DLL7 isn't released for Sweden yet (and I bought the device there).

So now I will see how it behaves with this stock ROM again.

I also made a Triangle Away since my counter was standing at 8.

At the moment, the device should be 100% stock, stock ROM, recovery, bootloader and everything.

Edit: As a further precaution, I disabled Chrome from Settings.

I also skipped through the Setup Guide.

Edit 2: At the moment, it seems to be more stable than before. I experienced reboots almost immediately on this ROM. Could it be that simple that an extra wipe is necessary after flash before first boot?
[Galaxy Note II Q&A, Help & Troubleshooting] E90 Commie:
New update:

I encountered the reboots again under stock XXDLL7. I have therefore flashed Android Revolution HD and will monitor it and see what will happen. I flashed it with full wipe, format /system and everything.

The only anomaly I noticed at the moment was "the Clock has stopped" so I froze that app. I ran an extra wipe after flashing and topped up with fix permissions (despite this, the Clock app acted up).

I flashed with CWM 6.0.1.5 and rerooted with the standard package containing it.
[Galaxy Note II Q&A, Help & Troubleshooting] mitky82:
Save you important data and wipe device from stock recovery. They remove everything from you INTERNAL SD CARD.

And instal stock rom with odin. After that again wipe from stock recovery. Then root and use phone like you want.Do you test that?
[Galaxy Note II Q&A, Help & Troubleshooting] E90 Commie:
Yes, I usually wipe the internal SD card when I flash.

Now, I am going to try to extract the logs. I had another crash with ARHD 8.0 now, it had been up for 2 hours 55 minutes (before that 2 reboots with approximately 20 minutes in between) and now when I activated WiFi, Settings just FCed and then it rebooted.

When I flashed the stock ROM, I wiped everything and after that, wiped again from stock recovery. Still rebooting....

Now with ARHD, it seems like the reboot behavior is similar to the stock ROM.

I am now going to see if I can find anything in the kernel logs.
[Galaxy Note II Q&A, Help & Troubleshooting] E90 Commie:
Latest update: I restored the device through Kies and flashed XXDLL7 through Odin 3.07, before I used Odin 3.04.

The old data remains, I didn't wipe at the moment. Interestingly, it seems to be smoother in operation now and I am ready to monitor the behavior during the night.

I rooted and flashed CWM to it too since that is a prerequisite for me.

If I notice reliable operation over the night without any reboot, I will enter step 2 and flash Kingdroid 3.0 and continue from there.

I really hope that I am on the right way now.
[Galaxy Note II Q&A, Help & Troubleshooting] duowing:
For that last_kmsg file you need to post more, usually the kernel crash is actually before the part you posted. You could just attach the last_kmsg file to your post.
[Galaxy Note II Q&A, Help & Troubleshooting] E90 Commie:
So, here is two logs.

Unfortunately, it seems like the strange rebooting continues under 4.1.2. '

Today, I have made complete flashes using Odin 3.07, including NAND rewrite and also PIT repartitioning together with flash of the XXDLL7 stock ROM.

I have also flashed TWRP recovery in order to check if there has been a problem related to the CWM. I have also tried the latest CWM 6.0.2.7.

I am now running HyperDroid Pegasus 1.0 and the latest RedPill 1.0.1 kernel and I tried to increase voltages slightly. The strange rebooting continues. As further experimenting, I have replaced the older CWM-root package with CF Autoroot and I have also made full Kies restore of the old ALJ3 stock ROM before flashing XXDLL7 stock.

Just when I wrote this post, another reboot happened. I attach this Kmessage log too (it is the third one).

Now, I am really at a loss here. I can't even think about what the cause is since I have now tried different recoveries, further complete wipes, Odin flashes and also noticed that Chrome seems to have no effect at all since it isn't installed in HyperDroid Pegasus either.

The interesting detail is that ALL 4.1.2 ROMs behaves similarly when it comes to crashing. It is always completely random, sometimes when the USB is plugged in, sometimes not. Sometimes on a completely stock ROM without root and mods, otherwise with root and mods installed. It doesn't matter what kind of configuration that is being used, immediately when it is a 4.1.2 ROM - it offers random reboots.

I hope someone can see any clue from the logs.

I am afraid that I have to return to BatteryPlus 0.2 again.
[Galaxy Note II Q&A, Help & Troubleshooting] E90 Commie:
I uploaded the three last_kmsg logs I have. The last two is very recent.