yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Q&A, Help & Troubleshooting] Deleted member 3777576:
For novels or other mostly only-with-text books - Note 2, otherwise for scientific/IT/photography books with plenty of diagrams, formulas or photos - 10" tablet (Note 10.1 - ideal) and Note 2 (as always-with-you). As for me the difference in real screen size between nook/kindle on E-Ink and Note 2 are insignificant, but resolution, color and overall versatility are incomparable.

Cool Reader and Moon Reader.
[Galaxy Note II Q&A, Help & Troubleshooting] sami3000:
I have personally prefer moon reader plus, I find it easy on my eyes
[Galaxy Note II Q&A, Help & Troubleshooting] Grant Barker:
I think the Note 2 is fine for reading eBooks.

There are many eBook readers to choose from and try for yourselves.

The following screenshots were taken from a Samsung Galaxy Note 2:

Android eBook Readers

Of course you can read in landscape too, which I haven't shown.
[Android Apps and Games] ilikov:
Hey everyone,

Here comes a new game on the Android Play Store!

Cash Button Race is a game where you have to be the fastest to get to the GOAL! Create your free account and reach 1 MIL hits on a button and YOU WIN $100 REAL CASH!

Download:

Mod edit: No paid apps without a free version for xda members - thread closed.
[Android Apps and Games] muneebrocks:
so let me get this straight

100 people buy an app for $2.42x100=$242

and then finally one of us gets $100?

While you pocket the rest?

I am sorry but really??
[Android Apps and Games] westpak:
Mhh i think you wont even get the 100$.. also i think its very easy to make with a vnc server and some windows makros.. or gamecih or whatever.
[Android Apps and Games] ilikov:
The game is one time purchase, and there will be 2 or 3 rounds... Depends how many people buy the game.

The calculation is almost right, except Google takes 30% out of each sale, so it will be 2.42 - 30%x100 = $170

Then I give the winner $100 bucks and I get $70... I think it's worth consider the time spent to develop this game.

And if it turns out to be more successful then just this, The prize will definitely go up, but for start, I think it's fare like this.

Best Regards,

Ivan
[Android Apps and Games] ilikov:
One thing I hate in life are those SPAM games or ads all over the web!

I am an honest man, and will send $100 dollars to the winner via email as soon as we get a winner!

There is a server security, so gamecih or other 3rd party software won't affect the numbers.

Thank you for your opinion on this westpak, I appreciate it!

Ivan
[Android Apps and Games] Archer:
Please read the forum rules before posting again.

11. Don’t post with the intention of selling something.

Don’t use XDA to advertise your product or service. Proprietors of for-pay products or services, may use XDA to get feedback, provide beta access, or a free version of their product for XDA users and offer support, but not to post with the intention of selling.
[HTC One S] ID#:
HTC removed the mail (and tasks, 4x4 music, stocks...) from sense. Is there any possibility to get it back on one s and sense 5?

And the calendar widget from sense4+ would be nice as well...
[Galaxy S II Q&A, Help & Troubleshooting] hssn601:
Hi All,

i am new to android i want to know if its possible to upgrade (kcc-cmm-sec-shwm250s) to android 4.0 or jelly bean.

currently my korean firmware is changed to gt-i9100 and running android 2.3.4 without any problem.

i want to upgrade it to jelly bean or ics (english) which gt-i9100 have

if its possible kindly share any guide...

Thanks in advance :)
[Galaxy S II Q&A, Help & Troubleshooting] hssn601:
from a web i have found this method .. should i do this to my korean shwm250s converted to gt-i9100 ??? please help

How to Install Android 4.1.2 Jelly Bean Update on Galaxy S2 I9100 via XWLSS NeatROM

Step 1 - Download Android 4.1.2 XWLSS NeatROM for Galaxy S2 I9100 on the computer.

Step 2 - Connect and mount the phone's USB mass storage on computer with USB cable.

Step 3 - Without extracting, copy the downloaded XWLSS NeatROM zip file to the root folder on your phone's SD card.

Step 4 - Switch off the phone and disconnect its USB cable from computer.

Step 5 - Boot the device into Recovery Mode by pressing and holding Volume Up, Home and Power buttons together.

Step 6 - Once the device boots into CWM Recovery, perform a full data wipe task by choosing Wipe Data/Factory Reset. NOTE: Use Volume keys to navigate and Power button to select an option in the Recovery Mode.

Step 7 - Perform Wipe Cache Partition and wait until the process completes.

Step 8 - Once the process completes, perform Wipe Dalvik Cache as well. This will prevent intermittent boot loop issues and other ROM related errors. To do this, go to "advanced" option and then select Wipe Dalvik Cache in CWM recovery.

Step 9 - Return to the main recovery menu and choose Install Zip from SD card.

Step 10 - Click Choose Zip from SD card. Use volume keys to navigate to NeatROM zip file that you copied earlier to your phone's SD card and choose it by tapping the Power button. Confirm the ROM installation on next screen and the installation process will begin.

Step 11 - Once the ROM is installed, go to "+++++Go Back+++++" and hit Reboot System Now in the recovery menu. The phone will now reboot and the first boot might take about five minutes to complete. So, leave it alone.

Your Galaxy S2 I9100 is now running on Android 4.1.2 Jelly Bean based XWLSS NeatROM custom ROM. Go to Settings > About Phone to confirm the firmware version installed.

[Source: XDA Developers]
[Nexus 4 Q&A, Help & Troubleshooting] mangomonkey00:
i'm new to nexus devices and really loved it i bought it about 2 months ago

and now i'm facing some screen flickering issue only in the bottom half its like black and then back sometimes it pretty quick and sometimes its not that currently i'm on pa3.96 latest and i'm seeing this issue after android 4.3 update didnt had this while on android 4.2.2 any rom

i'm unable to understand that its a hardware issue or software issue

and also i'm using screen calibration can that cause this problem i believe it wont be the one but..
[Nexus 4 Q&A, Help & Troubleshooting] AlbertoWayfarer:
Probably it's because you flashed a JSS kernel in a JWR Rom or viceversa. Try checking your ROM/Kernel

Sent from my Nexus 4 with Tapatalk 4
[Nexus 4 Q&A, Help & Troubleshooting] mangomonkey00:
no i'm already on the right kernel but the flickering is only in the bottom half of the screen
[Sprint HTC One (M7)] afkellner:
Just installed this ROM. Looks great. everything works EXCEPT network.

On the lock screen it says : ROAMING - PREFERRED SYSTEM

What should I have the settings under "Mobile Network" set to? Thanks.
[Sprint HTC One (M7)] Rirere:
What you should be looking at is the thread for the Nocturnal ROM.

http://xdaforums.com/showpost.php?p=43790000&postcount=2

In particular, the list of things that aren't working.
[Sprint HTC One (M7)] afkellner:
Thanks, I found the thread. But I can't post theere. That's where I got the ROM from.

According to the developer and other users, the recently uploaded V3 has fully functioning LTE. But it doesn't work on my phone.
[Sprint HTC One (M7)] Rirere:
I've seen references to LTE, but given it's still an in-development ROM I'm not surprised it's finicky. Were you sure you were getting LTE beforehand? It's entirely possible that this ROM is also going to handle the 3G/LTE handoff differently and is falling back to another signal type.
[Sprint HTC One (M7)] afkellner:
Yes, I was getting full 4G LTE service right before flashing this ROM.

I think I am narrowing it down to the setting NV / RUIM/SIM

When it is set to NV, my phone connects to the network but no data.

When it is on RUIM/SIM , I get the roaming message.

:confused::confused::confused::confused:
[Sony Xperia L] saaj:
Why every time I get this error?

Now send package you want to apply

to the device with "adb sideload ,filename>...

status 255

Restarting adbd...

No package received.

Installation aborted.

It is not driver problem, once I get this error even cable is connected or not!!

Please, any help!!!!

Thanks in advance...
[Sony Xperia L] DeviousFusion:
How are you sideloading the files?
[Sony Xperia L] shusterpo:
I have similar problem.

when select (with power button) "apply update from ADB" in recovery mode

I have got this:

Now send package you want to apply

to the device with "adb sideload <filename>"...

status 255

No package received.

Installation aborted.

without "Restarting adbd..."

Device do not wait for any commands

When device is in recovery mode ADB returns error: device not found

Step by step what I'm doing:

- cevice connected, USB mode enabled

-In ADB dir in my computer cmd:

> adb kill-server

>adb reboot recovery

After device gets to the recovery mode and with volume buttons selected "apply update from ADB" and confirmed with power button a previously mentioned message was returned.

When I try to use "adb wait-for-device" in fast boot or recovery mode a device will never been found.

Device flashed with stock 15.0.A.2.17 and ROOTed
[Sony Xperia L] Abruzini:
I have the same problem.. Any solution? :s
[MDA II, XDA II, 2060 ROM Development] maryadi:
Hello XDA Fans, Pleased to help me, i had downloads Himalaya wm2005 rom upgrade, but i missed information about how to upgrade my XDA II to WM2005 step bye step procedure. maybe xda2jojo can help me ! or send me manual upgrade to my email in tauchos@yahoo.com. thanks .[/b]
[MDA II, XDA II, 2060 ROM Development] christiankirana:
cannot

gak bisa bang, WM2005 lagi dilarang untuk sementara sama microsoft.... katanya gak bole dibocorin...
[MDA II, XDA II, 2060 ROM Development] Brent Nicholson:
I would like to know how to upgrage to WM2005 and where do I get the download?
[MDA II, XDA II, 2060 ROM Development] maryadi:
How to Upgrade XDA II to WM2005 Step bye Step

christiankirana :

gak bisa bang, WM2005 lagi dilarang untuk sementara sama microsoft.... katanya gak bole dibocorin...

Maryadi : oh jadi sekarang ini sdh dilarang yah ? wah kalo gitu saya ketinggalan dong nih upgrade.... knp tdk dari awal polling aja yah saya upgrade ! heheheehehheh

btw, ente kok bise bahase indonesia seh ?apa ente asli orang indo ? salam kenal deh sama putre betawi ! hehhhee
[MDA II, XDA II, 2060 ROM Development] xda2jojo:
All about wm5 (magneto) here: http://buzzdev.net

register and login...

PS:Procedure attached to a downloaded files

==============================================

Semua tentang wm5 (magneto) di sini: http://buzzdev.net

mendaftarkan dan login.

PS: Prosedur lampiran ke downloaded menyimpan
[Galaxy S III Q&A, Help & Troubleshooting] thefunnyone:
Vibration is not working on my phone. Ive resetted my phone 2 times but still its not working. I cannot send it to repair. But i may try to repair that myself. Need assistace .
[T-Mobile Samsung Galaxy S 4] 3r0k:
Hello my Fellow s4 users,

Let me start off by saying I am looking for a little guidance here. I am fairly comfortable with rooting, modding, NANdroiding, Flashing, bricking, unbricking, following instructions and using the search button. I am a little dumbfounded on some of the issues I am having.

The issues seem to be isolated to touchwiz based roms only. GE and AOSP ROM's are not part of this problem.

My problem is that anytime I flash a TW based rom (For Example: The little Minions Rom, Infamous, or Wicked), which flash just fine, upon loading or the first time System UI always crashes. I click ok and let the phone sit for about ten minutes to settle. I reboot, and go through the setup wizard ( I have also done it where I skip the setup wizard altogether, with the same results.)

At this point everything is ok.

Until I try to do anything else. I experience extreme Lag, problems with apps Like the phone and Contacts, Titanium Backup is simply non-functional.

So at this point I assume it is user error.

So I Odin back to stock, run triangle away and start fresh.

I repeat this process, and root using the CF-Auto root, and reflash a rom with the same result.

The only thing I can think to do at this point is ODIN back again and try a different Root method.

Does anyone have any ideas or input?
[T-Mobile Samsung Galaxy S 4] Biker1:
Personally, I'm running Infamous S4 4.0 ROM w/BioShock 1.0 Kernel and 3.1.1 3Minit Framework. Have not experienced the issues you're describing though. You seem to have taken many of the appropriate steps to attempt to solve your issues.

The steps I'd do and some stuff I'd look at, whether related to your issues, and/or tried already are:

- if using TWRP Recovery 2.6.0.0, flash TWRP 2.5.0.2.

- if not already, format card, if 64gb, to Fat32, as some ROMs won't run ExFAT.

- Full Wipe and ODIN Samsung Stock Firmware.

- Save files needed and Full Wipe, including device memory, as you may have a conflict with certain files.

- with Infamous S4, it has Root, so it's not necessary to root via CF-AUTO-ROOT, but can't hurt I guess. CF-AUTO-ROOT is my preferred choice for rooting.

- Uninstall and reinstall TiBu if having issues after doing the above.

- Sometimes when there are issues after flashing ROMs, wiping Cache and Dalvik cache can rectify many issues.

- make sure running appropriate Kernel for the M919. Appropriate Radio goes without saying, although most ROMs don't have the Radio cooked in because the wrong Radio can Hard Brick.

Anyway, I'm sure I missed something which may turn out to be the Golden Challis :laugh:, but the above hopefully will help.

As a note, and possibly to get more feedbackffrom the source, you can post your inquiry regarding Infamous S4 in thetthread as all are extremely helpful, and the Developers offer excellent support. The same with Minions, as they are part of the Infamous Team. I don't run Wicked ROM but have heard excellent feedback, and their support appears to also be excellent.

Feel free to copy this post if you'd like to post it in Infamous S4 thread, as there'll be others to expand on my response ;)
[T-Mobile Samsung Galaxy S 4] Gunkk:
OP:

What phone?

What baseband?

What recovery?

I am M919 tmobile

MDL

CWM.

...and have no issues with Wicked 5.1.
[T-Mobile Samsung Galaxy S 4] 3r0k:
Def gonna give the downgrade of TWRP and some of the other things you said a shot. Thanks for the info, will head over to the infamous thread after.
[T-Mobile Samsung Galaxy S 4] Biker1:
ODIN Recovery tips

You may find TWRP 2.6.0.0 the cause of some issues, and that 2.5.0.2 will resolve them.

I'll post some ODIN Recovery tips, if you should need them:

Here's the TWRP 2.5.0.2 file:

https://hotfile.com/dl/230303459/7ce1553/openrecovery-twrp-2.5.0.2-jfltexx.tar.html

Install with ODIN.

Steps to follow........

Method #1 -

Place file in PDA box*

Uncheck all other boxes.

Press start.

When installation is complete, unplug usb cord and pull the battery.

Insert the battery but Don't turn on the phone.

Place phone in Recovery mode via the Power + Volume up buttons.

Method #2 -

The other way I've read to install TWRP Recovery is:

Place the TWRP 2.5.0.2 tar in the PDA box*

Check the auto reboot box and f time reset box.

Start the installation and let the phone reboot.

I believe the above method is the method of choice, but sometimes the Recovery doesn't take, so Method #2 above is recommended.

Here is an explanation why:

http://xdaforums.com/showpost.php?p=41166759&postcount=28
[T-Mobile Samsung Galaxy S 4] 3r0k:
everything same as you except Im using twrp.
[T-Mobile Samsung Galaxy S 4] Gunkk:
There's your sign...
[T-Mobile Samsung Galaxy S 4] 3r0k:
Ok, getting home in a bit will keep you guys updates. thanks for the help.
[T-Mobile Samsung Galaxy S 4] Biker1:
Sounds :good:

ODINing 2.5.0.2 I think will solve your issues.

Wipe cache and dakvik cache after booting into Recovery and prior to booting system.

If still issues, start with ODINing Samsung Stock Firmware and Full Wipe. Internal wipe most likely Not necessary.

Hopefully nothing else will need to be done after TWRP 2.5.0.2 is installed ;)
[T-Mobile Samsung Galaxy S 4] 3r0k:
Yea, still gettting errors.

Even tried to switch to CWM, and that had issues with backing up.

Looks Like I am gonna ODIN Back and full wipe.
[T-Mobile Samsung Galaxy S 4] Biker1:
Yes, ODIN the Samsung Stock Firmware and start with a clean slate.

ODIN TWRP 2.5.0.2 and you should be good to go.

If you have the Firmware downloaded already, and checked the md5 checksum to insure your download matches the file, it won't take you long at all.

20m all together;

Firmware.

Recovery

ROM/Kernel

Infamous S4 Roots you, so hopefully you'll be up & running i nno time.

Sometimes just flashing the Firmware and starting from there, saves much trouble shooting time, avoids unsuspected and inadvertently installed conflicts and simplifies things back to its basics.

In your case, TWRP 2.5.0.2 only was worth a shot ;)
[T-Mobile Samsung Galaxy S 4] 3r0k:
Ok, some wierd developments here. I ODIN back to stock and everything goes fine. FLash the TWRP 2.5.0.2. Make a backup. Factory Reset, Wipe Data, Cahe, Dalvik, and System ( tried re odining back to stop reflashing everything and NOT wiping system just to see, same result.) flash infamous, when I get to the initial setup wizard, SystemUI still crahses then settings crash. Go back to Recovery, flash wicked, and now everything flashed fine on Wicked. No force closes or anything, running buttery smooth. I guess this solves half of my issue.
[T-Mobile Samsung Galaxy S 4] Biker1:
If you:

- did a Full Wipe

- ODINd Samsung Stock Firmware

- ODINd TWRP 2.5.0.2 Recovery

- checked your ROM download

- Flashed your ROM (with Kernel cooked in)

- Wiped cache and dalvik cache

and your still having issues, there must be an answer. I just don't have it, but I'd say the issue is a conflict with something that is installed or not installed on the S4.

Something to look into which will cause Boot-loops is if you have the wrong 3Minit app installed which is causing a conflict with 3Minit Framework. It happened to me with Alpha 6.0 because I didn't install the updated 3Minit app first after boot up, and attempted to use the older version I had installed on Infamous S4. I caused the issue in this instance.
[T-Mobile Samsung Galaxy S 4] 3r0k:
Followed that exactly. I cant even get to the point on the infamous to install the 3minit app. Everything crashes in the setup wizard.
[T-Mobile Samsung Galaxy S 4] Biker1:
At this point the only thing I can suggest is to:

- take a step back and a deep breath, and come back to the issue later on with a 'fresh set of eyes' so to speak.

I know that when I start troubleshooting any issue I may run into, Android or something else entirely different, I sometimes get frustrated and tunnel vision, and I keep making the same mistake each time, which of course doesn't resolve the issue.

I then come back to the issue and say, 'Hmmm, how'd I miss that?'

And there are times when I'm looking at an issue I'm having and I just can't see where the problem is, so I get 'another set of eyes' to view the issue and that person says 'here's your problem,' and I'm like, 'Wow, how'd I miss that? Thanks!'

I'm not saying that the above applies to you in your given situation, just mentioning it from the standpoint of my experiences and those of others.

Regarding troubleshooting, sometimes it does takes 'a fresh set of eyes' to look at the issue, as the person looking at the issue has a fresh aspect to what they are viewing, and not tunnel vision which can happen due to repetitiveness, frustration and many of other things. And more than not the solution ends up being a very simple one.

Sorry to be so long winded, But hopefully something in the above comments helps you to resolve the issues your having.
[T-Mobile Samsung Galaxy S 4] Skipjacks:
And you say this only happens on Touchwiz roms?

What about the stock touchwiz after you odin back to stock? Does that give you similar problems?

If so Im wondering if you have a faulty piece of hardware that touchwiz uses but aosp doesn't. So the hardware is still bad in aosp but its never activated so it doesn't cause the error. But if the stock rom works the that theory is shot....

Sent from your phone. You should be careful where you leave that thing.
[T-Mobile Samsung Galaxy S 4] 3r0k:
Stock ROM works great.

Wicked is now working and running great also.

I cannot Get Inbfamous to boot with out a ton of force closes. Even after ODining back to stock. Then Flashing TWRP and then flashing Infamous.

I guess Ill have to stick with Wicked for now, not like thats a bad thing at all. Im just ticked off when things dont work for me but they do for everyone else.
[T-Mobile Samsung Galaxy S 4] 3r0k:
No apology needed, you have by far been the most helpful.

Maybe Ill just wait for a new build to come out and go from there.

Maybe Ill possibly look into a log cat to send the Dev. I dont know if the log can catch the errors in my process but maybe.
[T-Mobile Samsung Galaxy S 4] Skipjacks:
Are you restoring data from other installs? Like are you using titanium to restore your apps and stuff?

If you are, and you are letting Titanium restore system data like settings and what not, that could be causing your issue. You can use titanium to restore things like data usage and wifi passwords because custom roms don't typically modify those parts of touchwiz so the data is still valid. But if you restore some other system data from one rom to another for things that have been modified you will cause failures like you are getting.

If you are doing this, try installing Infamous and not restoring any data at all. Just use it like it comes out of the box for an hour and see if youn still have the closes.

Sent from your phone. You should be careful where you leave that thing.
[T-Mobile Samsung Galaxy S 4] 3r0k:
If I did restore any other system data it would be coming from other touchwiz ROMS, however I am not. The problem is at least on the ROMS I am having difficulty with I cant get far enough to reinstall TiBu anyways. The systemUI crashes immediately as soon as the setup wizard loads, then when I get to the Wi-Fi password screen, the settings force close and the Setup Wizard starts all over again.
[T-Mobile Samsung Galaxy S 4] Biker1:
Thanks for those kind words ;)

If you feel like troubleshooting a little later on, I suggest you flash Alpha S4 6.0 by the Infamous Team.

http://xdaforums.com/showthread.php?t=2362636

I'm running it now without issue.

I suggest this because:

- it will help to isolate the issue you are having.

- you are no issue running Wicked, but you have an issue running Infamous S4

- I have a feeling you wont have an issue running Alpha 6.0

- if you run Alpha without issue, then there is obviously an isolated issue running Infamous S4 in particular and flashing it to you device, whether it is a conflict, setting, a wiping issue or whatever it may be.

- If you install Alpha without issue, you may have done something slightly different that you're unaware of, which would enable you to run Alpha with success but not Infamous S4

- if you are not successful in running Alpha, and the issues are the same, this may help to isolate the issue whose cause would be attributed to a commonality, which can be in the ROMs or in the installation install/set up.

The above may help figure this out if you feel up to it.

I posted the differences in the Infamous S4 thread regarding Alpha S4 6.0 here:

http://xdaforums.com/showpost.php?p=44647611&postcount=3950
[T-Mobile Samsung Galaxy S 4] 3r0k:
I will absolutely try this later tonight when I get home. Thank you so much for all your help and suggestions.
[T-Mobile Samsung Galaxy S 4] Biker1:
Anytime.

Let me know ;)
[T-Mobile Samsung Galaxy S 4] 3r0k:
Ok, SO a little update:

- After some research I found that the SystemUI will ALWAYS force close upon boot.

- I installed Jamison's Alpha rom and DID NOT restore anything.

Everything seems to be running fine now, I wonder if some how TiBu restores may have been part of the issue.

I think Im gonna flash the bioshock kerenel, and I need to find the right 3minit framework app because i paid for mine and its on 3.2.1