Hi guys,
anyone else having issues while playing music via stock player and browsing internet? Especially when page is loaded, music stutters from time to time.
VegaComb 3.2 latest official update.
Have you tried the unofficial honey ice updates. They are available over at tablet roms. Dont have the problem you have with them. You could aslo try a different music player, some use more system resources than others.
Hope it helps
Hi, thanks for the advice. I was interested in flashing it over my Vegacomb, but as my Vega already came flashed, I am not very familiar in how to do flash the honey ice over it. I was reading the forum, and as far as I understood, I can reboot to recovery (via Vegacomb->POwer button-> Recovery), then delete caches and install the update. I am not sure what will happen with my apps or if this is good approach. Maybe some hint/link?
Related
This is my journey from Eclair to Froyo - read only if you have ample time. You have been warned !
I had never tried even rooting my Galaxy I5801 so I was a bit hesitant to upgrade my DDJG6 Eclair to DDJP2 FROYO even via Kies. After some days of the official release I finally plugged my phone to update. But alas, Kies constantly showed "operation timed out" (poor connectivity ?) and I was left with no other choice but Odin
DAY 1:
Downloaded the flashing package and the relevant firmware, connected and fired up Odin as per the tutorial. Loaded the packages and started the process with a prayer on my lips. The first boot nearly gave me a panic attack but the tutorial did calm me down and voila ! I had successfully flashed Froyo. Thereafter I also loaded my backed up contacts & memo data through Kies sync.
DAY 2:
I was happy with my effort and started explorin the possibilities of FROYO including app2sd. All fine until I decided to install a flashlite plugin later that day. The system starting freezin so I rebooted. The problem recurred and I again rebooted. This my boot screen got stuck on the "GTI5801 - Samsung" screen. I knew I was screwed but since I could access download / recovery mode (even though wipe data or cache didnt work) I knew it was only a "soft brick"
Day 3:
Geared up to reflash my phone through Odin. This time I took some unusual steps - removed bootloader & sbl and extracted dats.rfs from DDJG6 & added it to DDJP2 tar package. Flashing was succesful and I had started to sort of like the entire process.
Day 4:
Was disappointed with the improper implementation of swype so I decided to install swype beta. Root, delete, register and install - simple ? That's what everybody says.... Downloaded superoneclick, enabled USB debugging and rooted (Z4root didnt work). Now the delete process was tricky. Couldnt make sense of titanium backup so tried another method. Since root explored is paid app and terminal emulator is beyond my scope, installed super manager from market. Gave superuser permission and started deleting relevant swype files - I think it was 2 from /system/app, 1 from /system/lib and 1 from /data/data. Registered for swype beta and downloaded it as advised on the website. I write this post with swype beta.
Everything is working fine now - almost !
PROS - learnt flashing, knew the benefits of rooting, now can manage my apps and memory a bit better
CONS - My music player is screwed. For that matter, any music player I have downloaded and tried is having the same problem. The player doesnt play some music files, skips it or even if forced to play remains mute although the music play status bar moves. I checked the file properties and played them on PC. They are either Mp3 or M4a. Do I need to reinstall the music player coz it sounds like its become corrupted ? But then it plays some tracks flawlessly
I am in debt to XDA Galaxy 3 forum members and rudolf in particular for helping me out at crucial junctures. Now if only I could solve this problem !
jg6 is an eclair rom right? That could be causing problems, mizing eclair and froyo.
Did you do a factory reset after flashing (I suspect you did if you followed a tutorial).
Also, removing boot and spl is not unusal, it is HIGHLY RECOMMENDED, always do it! (this is mostly for other people reading this thread)
Nice story... Waiting for day 5+
@stubborn - yup, i did a reset but the music player problem persists. I included the data.rfs file from eclair to froyo coz I was somehow convinced that its absence in the DDJP2 had causes my system to freeze the first time
@kyrillos - Day 5+ testing isnt exactly detailed. The only thing I noticed is that the battery drain was more than DDJG6 eclair or maybe its the battery bug acting whimsically (as it usually does). Havn't modified or tested the GPS so no comments. Installed Gingerbread keyboard but not exactly to my taste. Still using a combo of swype and regular tap.
BTW - ur ROMS are damn good judging by the features, performance feedbacks and screenshots. However, It will take me another leap of faith to flash one of those since the complexity involved is beyond my current level of expertise (or rather the lack of it !)
Any ideas / tutorials on deleting the stock music player app and reinstalling it (with apk files, if possible) ?
First of all I searched and noone really has a definite answer.
I am running the Tiamat OMG Rom. Not running setcpu, just installed the rom the way it was mentioned in the thread and that is all. Everytime I go on the stock browser, it just closes without warning after a couple of webpages load.
I have tried doing a factory reset and then installing the rom, clearing the cache using manage applications, wipe cache/dalvik/fix permissions on CWM, tried another browser, installed different kernels (lauahpad), tried overclocked, reinstalled the BRD honeycomb 3.1 update...all in no particular order....and the browser still closed on its own without warning. All this happened after I installed the Tiamat OMG rom.
I don't know what to do.
any help?
Any suggestions?
I'm pretty sure it's not a Tiamat issue- see this thread, too- we somehow must have picked up a bit of JS while browsing <some site> as it apparently started happening last Thursday night and is affecting a lot of people (even unrooted users) who have JS on and using any Webkit-enabled browser (the stock one, Dolphin, etc. but NOT Opera or FF).
It is still doing it even after taking the ROM and kernel off??
kcrudup said:
I'm pretty sure it's not a Tiamat issue- see this thread, too- we somehow must have picked up a bit of JS while browsing <some site> as it apparently started happening last Thursday night and is affecting a lot of people (even unrooted users) who have JS on and using any Webkit-enabled browser (the stock one, Dolphin, etc. but NOT Opera or FF).
Click to expand...
Click to collapse
Thanks for the response!! I am tracking this issue with the thread you gave me. Thanks again!
before this , my a500 is on HC 3.2. because of HC 3.2 doesnt have root access yet , so i downgraded it to 3.0.1 using this and update to 3.1..
and because of that , my media directory can't be played by default music player or any media apps and my pics can't be displayed at gallery. But the media file is still intact in my storage. what happened ?
and it kept showing my "Maps" has stopped unexpectedly , i never used that app ! T.T
Are you still on the unstable 3.0.1 that you downgraded to, or did you flash a new rom? If you're still on 3.0.1 with root, then flash a new custom rom and see if that fixes your issues. If you're still experiencing random force closes, I'd try reflashing the rom. Had to flash mine three times before everything got ironed out.
Still new at this myself, but hope that helps...
Since you downgraded and rooted, I would suggest trying a 3.2 ROM and see if that fixes your problems. Sounds like your ROM is in an unstable state. Also as smhism stated, sometimes you have to try more than once to get everything working. Also make sure you follow all the steps carefully in CWM so that you wipe everything before upgrading and installing new ROMS, otherwise you could experience issues like that one.
i'm on 3.1 (stock rom) rooted 4.010.40_COM_GEN1..
i did upgrade it using unstable updates on the link above..
but i guess i dont want to flash some new roms now , coz i got a lot of other things to take care of..
or maybe it can't be played and detected because of i'm updating using unstable updates ?
I would try to do the downgrade to 3.0.1 again and then upgrade to 3.1 once more and see if anything gets changed. Also, did you root 3.0.1 before updating to 3.1?
Greetings,
I'm not salty enough to post in the Dev threads, so here I am.
I'm usinging the vs980 on the latest Mahdi release in combination with the dorimanx kernel, and ART. So far everything seems stable except for Bluetooth. Streaming media works just fine, but when I pair it with my vehicle, which has phone and media, it goes into a pairing crash loop.
I've searched the forums and haven't found anything related to my problem. Someone mentioned disabling the hardware buttons, but that's not an option I have under settings->buttons.
Any other suggestions? I thought about making a backup and then do a clean install on the stock kernel using dalvik but I don't know why that effect BT.
-Phillip
Hi all, I am new here. I was referred by a friend who knows more about this than I do. I think I understand how to get fastboot and TWRP, so that is taken care of already. Now the problem with my OP2 running OxygenOS latest version, everything stock, is that it freezes up after unlocking, and the whole phone is just terribly throttled at this slow speed for a long time. All inputs are extremely delayed, and touchscreen is nearly unusable after the lag begins. There are so far two temporary fixes I found: 1) reboot phone 2)wait it out/keep unlocking until it doesn't lag. I also have been unable to make a copy of my internal storage via USB, as it gives unspecified error during copying. And lastly, the screen dims on its own sometimes at random while anything related to auto-brightness should be off. Fortunately, I was able to make a hard copy of my internal storage thru some wifi file manager apps. Now my friend pointed out that my phone's issues could be related to a bad kernel. To remedy this, he told me it would be good to flash a new kernel onto my phone. I considered changing roms to CM, but apparently a lot of functionality is lost when doing this. He told me that I could retain Oxygen OS while flashing a new kernel, but I am not sure how to do this. I came across a post in the android dev section regarding hydrogen os, and I read that it performs better than Oxygen OS, but has minor issues of its own. I am interested in flashing this rom/kernel (I am not sure which is which). Here is the link in that section of the forum I found http://forum.xda-developers.com/oneplus-2/development/rom-h2os-hydrogen-os-ota-clean-stable-t3195636. I see it says that it is working on Indian OP2, and running stock rom and stock kernel. Does this mean that my north american OP2 won't be able to get this rom? Also if it is the stock kernel, does that mean it is the same kernel as the one currently installed on my phone? Anyways, if anyone knows about my phone's problems, or has a way to fix it let me hear it please. Thank you!
Tzheng456 said:
Hi all, I am new here. I was referred by a friend who knows more about this than I do. I think I understand how to get fastboot and TWRP, so that is taken care of already. Now the problem with my OP2 running OxygenOS latest version, everything stock, is that it freezes up after unlocking, and the whole phone is just terribly throttled at this slow speed for a long time. All inputs are extremely delayed, and touchscreen is nearly unusable after the lag begins. There are so far two temporary fixes I found: 1) reboot phone 2)wait it out/keep unlocking until it doesn't lag. I also have been unable to make a copy of my internal storage via USB, as it gives unspecified error during copying. And lastly, the screen dims on its own sometimes at random while anything related to auto-brightness should be off. Fortunately, I was able to make a hard copy of my internal storage thru some wifi file manager apps. Now my friend pointed out that my phone's issues could be related to a bad kernel. To remedy this, he told me it would be good to flash a new kernel onto my phone. I considered changing roms to CM, but apparently a lot of functionality is lost when doing this. He told me that I could retain Oxygen OS while flashing a new kernel, but I am not sure how to do this. I came across a post in the android dev section regarding hydrogen os, and I read that it performs better than Oxygen OS, but has minor issues of its own. I am interested in flashing this rom/kernel (I am not sure which is which). Here is the link in that section of the forum I found http://forum.xda-developers.com/oneplus-2/development/rom-h2os-hydrogen-os-ota-clean-stable-t3195636. I see it says that it is working on Indian OP2, and running stock rom and stock kernel. Does this mean that my north american OP2 won't be able to get this rom? Also if it is the stock kernel, does that mean it is the same kernel as the one currently installed on my phone? Anyways, if anyone knows about my phone's problems, or has a way to fix it let me hear it please. Thank you!
Click to expand...
Click to collapse
I had the same issue with O2. I changed kernels and the problems persisted. A also word the device and started from scratch through fastboot and the issues persisted. I ended up on hydrogen and I've never looked back. There is a flashable zip in that thread for the newest full version .11. Follow the steps wipe everything besides internal storage, flash the full v11 zip and boot the phone. After this reboot to recovery (power and volume down). Flash the gapps and super su zip if you want root. After this you should be able to add your Google account and be good to go. One thing I did was remove all Chinese apps and the stock launcher. I use trebuchet launcher from cm 12.1. Phone runs incredibly smooth now. I recently started running AK kernel as well. The oxygen version works with hydrogen. I have been averaging between 5 and 7 hours of SOT for battery with up to 8 if I'm just watching videos. Hope this helps. The ROM is a little simpler and the notifications settings are different. But you can set apps to have priority notifications and they function similar to oxygens notifications at that point. Everything is in the thread if you have any questions I'll try to help you.