yashsingh1/xdaforums huggingface dataset:
[Defy General] Kayant:
Thanks for that will do ;)
[Defy General] :
I have this problem.

[ 05-07 21:22:14.363 197:0xc5 E/dalvikvm ]

ERROR: must specify non-'.' bootclasspath

[ 05-07 21:22:14.373 197:0xc5 W/dalvikvm ]

CreateJavaVM failed: dvmClassStartup failed

[ 05-07 21:22:14.373 197:0xc5 E/AndroidRuntime ]

JNI_CreateJavaVM failed

Help? :)
[Android Software Development] Fmstrat:
Hi all,

I have been working on an HTML5 based reader similar to Flipboard that would work in Android, iPad, Windows 8, etc. However, with news that Flipboard will be releasing to Android this year, I'm debating on if it's worth my time to finish. A few things of note:

It's powered by google reader

It actually has a better image grabbing engine that FB for image detection

Around 32 page layouts thus far

Scales areas and fonts dynamically to fit any resolution tablet/screen

Grabs the first few pages, then keeps going in the background for quick start

Here's a link to check out the super-pre-alpha: http://youtu.be/g3hNYtNVGJM (so you can see it already grabs articles and sorts areas and images)

What do you think? Should I put the time in to finish it for everyone?

Thanks,

B.
[Android Software Development] typongtv:
I think if u can manage to create and page transition effect that makes flipping through them as exciting as it is on Flipboard then ur App will sell itself....i don't see that on your video.... it's laying out new nicely though.

try to focus on visuals and gestures.
[Android Software Development] Fmstrat:
Yea, it's complete alpha stages right now. I don't even have the code in for viewing an article. I won't be taking the exact FB effect, but was planning on making a swipe effect of some kind, but don't want to spend the million hours finishing this out if everyone says "Why bother, we'll use FlipBoard." :)

Thanks,

B.
[Android Software Development] typongtv:
Put in mind that Flipboard announced that the company will release the app only for chosen devices ....so if your app suits older less powered devices and have some cool features that are optimized for smooth browsing and doesn't consume battery ...then i think u should work on it and don't give up .

second of all you should know by now people lke to try out new apps every now and then ...we get bored fast my friend ;)

good luck developing ..but if u loose interest then it's also ok .....maybe u will come up with something even better :D
[Android Software Development] Fmstrat:
Yea, now that the APK is out I'm seeing that Flipboard is working fine on older devices, I think I'll hold off. While I'm happy to continue building this, I don't see much point unless Flipboard doesn't come out tablet optimized. Happy to give people another option, but I only have a limited amount of time, and could never compete with the feature list that FB provides.

Thanks,

B.
[Nexus S Q&A, Help & Troubleshooting] Forcystos:
http://i49.tinypic.com/54dik4.png

Auto-sync is off, network location is off. How the hell do almost 4GB of data get consumed by this?

Running AOKP M5 and Matr1x kernel 19.0 CFS, but it's been like this before (previous AOKP versions and previous Matr1x versions only).
[Nexus S Q&A, Help & Troubleshooting] doublesack:
I had the same problem... I googled the problem but only found some people saying its caused by the browser bookmark synchronization. But this is switched off if autosync is off so this can't be the problem for you (as it wasn't for me too).

i reflashed the rom (same rom, no wiping) which solved the problem.
[Nexus S Q&A, Help & Troubleshooting] Forcystos:
But I have reflashed the rom a couple times, with and without wipe, and nothing.
[Nexus S Q&A, Help & Troubleshooting] doublesack:
Did you try another ROM too?
[Android Q&A, Help & Troubleshooting] Kayant:
I just recently finished porting and compiling the gummy rom from source to the motorola defy but i can't get it to boot probably :D... i can boot it through 2nd boot but i get an android.process.com error :(

Logcat - kayant@kayant-laptop:~$ adb logcat

- waiting for device -

--------- beginning of /dev/log/main

I/ARMAssembler( 1117): generated scanline__00000077:03545405_00000000_00000000 [ 36 ipp] (50 ins) at [0x409e21e8:0x409e22b0] in 183106 ns

I/ARMAssembler( 1117): generated scanline__00000077:03545405_00000A05_00000000 [ 37 ipp] (58 ins) at [0x409e22b8:0x409e23a0] in 152588 ns

I/ARMAssembler( 1117): generated scanline__00000077:03545405_00000A08_00000000 [ 37 ipp] (59 ins) at [0x409e23a8:0x409e2494] in 183105 ns

I/init ( 1996): == init.rc: on init -----------------------

I/init ( 1997): == mapphone: on init ----------------------

I/init ( 1998): == mapphone: on init ----------------------

I/init ( 2023): == init.rc: on fs -------------------------

I/init ( 2024): == mapphone: on fs ------------------------

I/init ( 2066): == init.rc: on post-fs --------------------

I/init ( 2067): == mapphone: on post-fs -------------------

I/init ( 2077): == init.rc: on post-fs-data ---------------

I/init ( 2078): == mapphone: on post-fs-data -------------------

I/init ( 2102): == mapphone: on early-boot ----------------

I/init ( 2103): == init.rc: on boot -----------------------

I/run-parts( 2106): kernel.sched_latency_ns = 10000000

I/run-parts( 2106): kernel.sched_min_granularity_ns = 1000000

I/run-parts( 2106): vm.dirty_ratio = 0

I/run-parts( 2106): vm.dirty_background_ratio = 5

I/run-parts( 2106): vm.vfs_cache_pressure = 100

I/run-parts( 2106): vm.oom_kill_allocating_task = 1

I/run-parts( 2106): vm.min_free_kbytes = 4096

D/AndroidRuntime( 2123):

D/AndroidRuntime( 2123): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<

D/AndroidRuntime( 2123): CheckJNI is OFF

E/dalvikvm( 2123): ERROR: must specify non-'.' bootclasspath

W/dalvikvm( 2123): CreateJavaVM failed: dvmClassStartup failed

E/AndroidRuntime( 2123): JNI_CreateJavaVM failed

I/run-parts( 2106): Zipaligning...

I/run-parts( 2106): Zipalign complete! Runtime: 00:00:01

I/run-parts( 2106): kernel.sched_latency_ns = 10000000

I/run-parts( 2106): kernel.sched_min_granularity_ns = 1000000

I/run-parts( 2106): vm.dirty_ratio = 0

I/run-parts( 2106): vm.dirty_background_ratio = 5

I/run-parts( 2106): vm.vfs_cache_pressure = 100

I/run-parts( 2106): vm.oom_kill_allocating_task = 1

I/run-parts( 2106): vm.min_free_kbytes = 4096

I/boot ( 2163): Set 32mb of RAM free.

I/mountsd ( 2167): Checking filesystems..

I/run-parts( 2106): e2fsck 1.41.11 (14-Mar-2010)

I/run-parts( 2106): /dev/block/mmcblk0p2: recovering journal

I/run-parts( 2106): /dev/block/mmcblk0p2: clean, 11/124928 files, 26309/498900 blocks

Can anyone help me please???

Thanks :D
[Epic 4G Q&A, Help & Troubleshooting] dirtbag1975:
I'm experiencing an issue with all recent versions (34 on) where stock camera doesn't work. All I get is a gray screen. I've tried clearing data to no avail. I've also installed camera fx which gets the camera working, but the orientation is broken. Don't understand this bug, but it has transcended 2 different Epic's.
[Epic 4G Q&A, Help & Troubleshooting] GuestK00145:
You should have asked this in AOKP thread, instead of making this one :)
[Epic 4G Q&A, Help & Troubleshooting] dirtbag1975:
I don't have access to post in the development threads.
[Epic 4G Q&A, Help & Troubleshooting] GuestK00145:
Post something two more times and you'll be able too :)
[Epic 4G Q&A, Help & Troubleshooting] KennyG123:
Also read Forum Rules

Questions go in Q&A

Thread moved

Thanks

Friendly Neighborhood Moderator
[Epic 4G Q&A, Help & Troubleshooting] mjben:
I had that problem. You need to use a new kernel. There is a shadow kernel or samurai available that will fix it.

It's been my experience that the camera generally doesn't work on CM or CM based roms. It escapes me why the kernel developers manage to get the camera working but the cm team doesn't.

sent from a secret underground bunker
[Epic 4G Q&A, Help & Troubleshooting] dirtbag1975:
I ended up flashing a nandroid of previous working version then flashed milestone 5.2 and the new gapps and the camera works! I didn't clear anything just flashed right over it. I've noticed the camera has been flakey on the CM9 builds, like the flash and focus which are know bugs. I haven't read anyone with this issues I was experiencing. I've been lurking these forums since November of 2010 when I got my Epic, and have been really successful rooting and roming because of it. However I just started to post in the forums so I apologize for posting here. Thanks for all the help.
[Epic 4G Q&A, Help & Troubleshooting] mjben:
Flaky is right. Even when the camera "works" on CM9 builds it doesn't work properly. Saying it is sluggish is too kind. Focus is a problem. And try using the camera after taking a video- (hint, it hardly works at all.)
[Epic 4G Q&A, Help & Troubleshooting] dirtbag1975:
Honestly the camera is the only issue the keeps the CM9 builds from being daily drivers. Otherwise I love the them. A lot of people complain about battery life, but honestly I think having the roms running them is worth it. I even bought a 3500mA battery off amazon for 8 bucks to circumvent the extra battery drain, which also happens to be the best 8 bucks I've spent in a long time. Once the Devs get the camera bugs ironed out I won't see a need to go back to the gingerbread builds.
[Epic 4G Q&A, Help & Troubleshooting] mjben:
Broken camera is a Hallmark of CM.

I really loved ICS otherwise, and managed to overlooked the ridiculous battery drain, which I believe has a little to do with shotty sprint service over the past two weeks. Constant loss of signal.

A 3500mah, really? I should have done some better research. I just bought a pair of 1800's off eBay for $10. Kinda disappointed to hear that there is a 3500 that works. And for $8.
[Epic 4G Q&A, Help & Troubleshooting] dirtbag1975:
Yup 8 bucks shipped with Prime membership! Sprint has been upgrading the towers in my area for 8 weeks now and from what I've been told that won't be done until the end of June. The service is so bad now that it's unbearable. Dropped calls, crippling data speeds, sms not going out and or being received. I've complained to Sprint and have been told that the my account will receive a credit once the LTE rollout is complete. I'm not going to hold my breath, but if they don't I might start shopping around for a new carrier as my contract will be up.
[Galaxy S II General] mikeinhull:
After rooting and flashing my SGS2 loads off times and the counter was on over drive I installed Resurrection Remix pro v1.1 and though this would be the last flash, everything was great with it and I really looked cool but then things started going downhill. First the camera went down and so did the camcorder app and then the wifi as well so I thought ok go back to stock and start again, then when I was flashing stock the phone just froze so I took the battery out, put it back and tried to restart it but it didn’t…….I tried everything to get it working with no luck and I thought **** the warranty is void, idiot, what am I gonna do, so this is why I have an A level in lying. I rang Samasung up and spoke to a lovely lady from India call centre, as you do, told her it won’t start up, no lights, sound nothing and what I said to her is that I was trying to download the new ICS from kies, said it started to install it and after about 5 secs the phone went dead, anyway Samsung posted out a pre-paid jiffy bag the next day and in the description problem I wrote about what I’d done and posted it off the same day thinking $HIT what have I done, I’m gonna get it back with Samsung telling me to shove the phone up my arse. Anyway 5 days later the delivery turned up at the house and I was shaking, sweating and crying so I thought I’ll take it out the bag without reading the documentation etc and just try and turn the phone on and guess what lol lol lol it was fixed, my heart nearly missed 100 beats, couldn’t believe it or am I just lucky guys cos I feel damn lucky but now my only problem is I’m scared to death of flashing any new custom rom in case it happens again and can’t download anything using kies so I guess it’s just me, the mobile and touchwiz gingerbread ****e lol hope this helps people.:)
[Galaxy S II General] JJEgan:
Kies is always a good excuse .

Two choices one stick to Kies or two join XDA development take all the precautions read the faqs and instructions and take the very slight risk of bricking or paying for warranty .

jje
[Galaxy S II General] brezzo:
Couldn't you have reset the counter with a USB jig or something? Before it hit too many flashes?
[Galaxy S II General] mikeinhull:
thanks

Hope i'll never to have to use that kies get-out-clause again but have bricked it loads of times but my best friend "jig" helps me out lol:D
[Galaxy S II General] mikeinhull:
but the phone went down when I flashed it so didnt have chance to jig it and that's why I was ****ting meself but all ended fine thank fuk
[Galaxy S II General] Deleted member 4038153:
Committing fraud is never a good excuse. I'm disappointed how often that is recommended here, especially given the rules.

9. Don't get us in trouble.

Don't post copyrighted materials or do other things that will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably don't want to do it here either. This does not mean we agree with everything the software piracy lobby try to impose on us, it simply means you cannot break any laws here, since we'll end up dealing with legal hassle caused by you. Please use common sense: respect the forum, its users, and those that write great code.
[Galaxy S II General] Prankey:
I have been writing up here that custom flash counter do not have any reference to warranty irrespective of big shots here using their overclocked brain claiming that it voids the warranty.

Only thing to know is that if Samsung finds you have custom firmware, they will install the official and check the phone. If they find the phone defective on stock firmware, they will proceed with regular warranty claims as usual. THAT IS IT!
[Galaxy S II General] mikeinhull:
well lovely samsung installed the 2.3.6 official when i started it up, better get used to that now lol
[Galaxy S II General] JJEgan:
Completely wrong why would Samsung send out a letter to service centres stating that custom roms and root both void warranty and to look on the phone for root applications .

Why would their be reports of service centres actually turning customers away with root or custom phones .

Why would XDA mods constantly state that this will void your warranty .

Why was my SGS rejected under warranty as it had a custom firmware .

Why say it does not void warranty when the warranty conditions says it does . Even if users get away with custom or rooted roms .Its wrong to say hey guy its not against the rules and even more so when you are not going to back their rejected claim with the money to pay for a repair or are you .

jje
[Galaxy S II General] madquack:
If you were seriously "I was shaking, sweating and crying" from a cell phone than you need to seek immediate medical and psychological help.
[Galaxy S II General] ephraim:
Cool story bro. Good thing you got your phone back and running :)
[Galaxy S II General] Prankey:
No where in the warranty terms and condition it stays that custom ROMs void warranty. Also there is NO WHERE stated in the custom flash counter that it voids the warranty. I know its bit of a gray area and Samsung CAN turn down warranty repairs/replacement/refunds, however through appropriate escalations and contacting the right people certainly should help as there is no way Samsung can say that you "rooted your phone? hell its you who infected it with the deadliest virus and its about to explode so no warranty for that!".

I am not telling folks here that we should encourage others using custom firmware/kernels, but only telling to use them with caution but don't ASSUME that it voids the warranty just because you use them. I have dealt with Samsung and still do with open issues never resolving, I take a refund and move on. Custom firmware or not, I ensure that I use the phones with utmost care and keep them like new with even a scratch but use it at maximum of its potential while also not living with Samsung's strictly official ROMs as they miss about half the features I would want to have on my phone.

Remember - Samsung themselves release source code for their Kernels and put Open Source Android on these phones. Restricting ourselves to their official ROM only guarantees seemless warranty support, taking a diversion do not imply it voids the warranty. While I agree that we should seek support only when having official ROM without root, custom ROM counter doesn't mean it voids the warranty anyway!
[Galaxy S II General] mikeinhull:
prankey

so what your saying is that rooting or custom roms dont void warranty then
[Galaxy S II General] bartoloandre98:
buy an iphone

Sent from my SGS2 powered by cm9 love
[Galaxy S II General] Gustopher:
I think the only safe conclusion to draw from the above is 'opinions differ'.
[Galaxy S II General] mikeinhull:
iPhone lol never, only like the best not the worst
[Galaxy S II General] mikeinhull:
Gustopher we need to know what we can or cant do on OUR phones dont we
[Galaxy S II General] mikeinhull:
well being a Yank rdubyah you'd know all about sweating
[Galaxy S II General] JJEgan:
Not going to even bother replied to this question hundreds of times posted the official Samsung letter re root etc even read the warranty in full .

Your choice and any other idiot that wants to avoid the facts and take the risk .

jje
[Galaxy S II General] mikeinhull:
thanks for replying, now who's the idiot lol
[Galaxy S II General] BarryH_GEG:
Any manufacturer can claim customer induced damage at any time. If they refuse warranty service, whether they are right or wrong, you're screwed. If they are wrong, no matter how sweet or nasty you are, and how many supervisors you speak to, you can't make them repair your device. With it in their hands you'll have two choices: 1) pay what they're asking, or 2) get it back the way you sent it. Anything else requires either an attorney or filing complaints with whatever advisory body oversees such things in your country. Either way, by the time you're done, the value of all the effort you've invested is probably worth more than the original cost of the device. If you check out the Prime forum Asus has actually turned customer induced damage in to a new revenue stream applying exorbitant charges with greater and greater frequency.

Comparatively, Samsung's great at being cooperative with repairs. I noticed a hairline crack in the bezel of my phone near the headphone jack after having it for 11 months. They sent me a jiffy bag to ship it from the U.S. to the UK and just called to say it's been repaired after a week with them. I only have to pay 10GBP to have it shipped back. And a cracked bezel screams customer induced damage.
[Galaxy S II General] mikeinhull:
glad you got it sorted out thanks to us brits, see we are good at something
[Galaxy S II General] Prankey:
WOW so now you want to name folks here for being least smart to ensure seamless service from Samsung and you being most sensible paying for the service for using a custom ROM?

I don't know what DIKTAT you have from Samsung, however as I said, we just have to be safe and send the phone with official ROM without any trace of custom. Even if we can't clear the custom ROM counter, that should not cause any denial of service. Infact, most probably after the service center install Stock ROM, the counter gets reset anyway (as they seems to usually install using USB jig kind of method).
[Galaxy S II General] sahibunlimited:
So even Chainfire comes in breaking the rule number 9?(triangle away)

Terminator runs on android:cool:
[Galaxy S II General] Emporioo:
OP confirmed for 13 year old ******
[Galaxy S II General] Burgscheinkerkdeiktraast:
Can busybox alone void warranty at all? I don't have root but RootChecker says I have busybox installed where I manually removed it from xbin :)
[Galaxy S II General] SPBoss:
I'm not worried at all if I brick my phone. I'll just disable the RIL and tell them I lost it. Then I'll have two S2's lol :D

Sent from my Galaxy SII I9100
[Galaxy S II General] blade30p:
What do you mean disable the RIL?
[Galaxy S II General] SPBoss:
I can't say anymore. I do not agree with fraudulent activity and I'm pretty sure xda doesn't allow it either.

Anyway.. just keep your phone in flight mode for the time being. Will save battery

Sent from my Galaxy SII i9100
[Galaxy S II General] blade30p:
I don't agree either, I just wondered what it was, google told me days ago anyway :)
[Galaxy S II General] alc027:
That's fiction.

Flashing custom firmware CAN damage your phones hardware permanently. Samsung will not ever take responsibility for damage that you inflict on your device (and rightly so). That's why the "custom firmware get-out-of-warranty-free card exists".

I work for a phone company (no, not Telstra) and am responsible for sending devices for manufacturer warranty service. If your device is showing a yellow triangle or the flash counter >0 then your device will be rejected on the spot. Then I need to place a persistent note on your account to notify everyone who looks at it in the future that your device is no longer warranted.

Rry? It just so happens that I have my warranty policy here. Let me quote a bit:

The wording is broad enough to exclude any activity that is not written in the user manual, or by performing any activity yourself that is performed at a Samsung service centre.
[Galaxy S II General] SPBoss:
I'm glad I work in a solicitor's firm. No company ever says no to me.. they know it would cost them more to argue instead of giving me a replacement :D

Sent from my Galaxy SII i9100
[Galaxy S II General] karendar:
So what you're saying is: If you mess your phone up, people bend over backwards to replace it for you just so they don't hear you whine? Yeah, that's great.

What happened to people owing up responsibility for their actions? It just means if you have influence, you can bypass common sense... Kinda disturbing. It's like the people who want Gokhanmoral to send the broken RC6 kernel to mess up their phones to get an easy replacement.

If I break my phone and they tell me it's out of warranty because of a modification, I live with it, count my losses and buy a new phone. (Sell the broken one on ebay of course) It's just fair play.
[Galaxy S II General] SPBoss:
People who don't do backups or take risks without reading things first and damage their phones are silly to blame anyone but themselves lol.

I'm insured on my phone so its fine for me to update rooms and kernels without being bothered, because I can take that risk :)

Sent from my Galaxy SII i9100
[Galaxy S II General] karendar:
That's not really what I was refering to. But being careless because you're "covered" is pretty odd to me. And insurance costs in the long run, but if you're willing to claim it for your gadget and it helps you sleep at night, more power to you.

My comment was based on:

Which is pretty much considered insurance fraud... But hey! What can I do.
[Galaxy S II General] norpan111:
I don't get it.. If you really brick your device, why would you disable RIL? and if it's not really bricked: just take the sim card out because you won't ever be able to use it as a phone again since your imei will be "banned", "locked" or whatever word is the correct
[Galaxy S II General] SPBoss:
Guys if you read my later post I said I was just kidding lol :)

Sent from my Galaxy SII i9100 running ICS Remix Rom 1.8.1 with Siyah Kernel
[Galaxy S II General] alc027:
try me :)
[Galaxy S II Q&A, Help & Troubleshooting] edsonmassao:
Hi all! I loaded the last versions of Ressurection Remix 1.8.1 and Hydrogenics 04.05. After that when I try to download my apps in the Google Play Store it tells me that my device isn't compatible with the app :confused:

Does anyone facing the same problem?