Hello
I installed the KANG ROM found in the following thread [ROM][KANG]CM9 ICS 10.1 WiFi Preview 02/08/12 and the boot screen seems to refresh/scroll endlessly. Once the lock screen comes up (which scrolls endlessly as well), if I press the power button to turn screen off and then switch it back on, the display is stable.
I use the Korean Version SHW-M380W (Galaxy Tabl 10.1 Wifi 32GB). I tried Galaxy Task Slim 13.1 and other ICS Roms found on XDA, but the result is same.
Can someone please let me know a fix for this?
Thank you so much.
Ping
Ping...
Doesn't anyone else face this issue?
I don't think it supports the korean tab
Hmm I saw that if I restore /boot from stock image backup in HC 3.2 this issue was solved. Tried and tested it and worked fine. But when I upgrade to ICS, there is no /boot to restore from. Just tried it with the Hc 3.2 /boot and the system hanged.
Probably different ramdisks as ics kang is based of devices they own and custom via the model as the Korean tab is not part of it you may need to request or hope someone donates one to them, and if it was the official update of ics it would work but these are custom made builds based off the source ics package given by Google so it isn't an official update like HC3. 2
Sent from my GT-P7500 using Tapatalk
Thanks
Thank you for your reply.
have you tried romans?
Romans
You mean the AOKP one right? Yeah, I have tried it, but the same issue
I mean, the one from here: http://forum.aokp.co/page/releases
Build 28 to be specific. Strangely, the same (screen jumping) issue was there with CWM as well. And pershoot was kind enough to make a new CWM just for Korean tab. I wonder what changed though (Am quite a newbie to rooting and stuff, so dont really know where to go to)
The pershoots CWM which fixed a screen jumping issue for CWM (not for boot screen though) is found here: http://forum.xda-developers.com/showthread.php?t=1360588
Thanks bro.
So its all fixed?
Oops, I missed the whole point Actually, I had tried that after the [ROM][KANG]CM9 ICS 10.1 WiFi Preview 02/08/12 version, but the issue persisted. Its only with the bootscreen that this issue exists. Once we go to the lock screen, the issues still exists, but a screen off -> screen on (using the power key) quickly restores the screen back to the non-fluctuating version.
Wait, why havent you used kang by Roman? Its already coming to 4.0.4
Build 29
Thanks Misledz: I tried out Build 29 located in the following page:
http://forum.aokp.co/page/releases
Still the problem persists
I think you need a clean wipe, like generally wipe everything off it, a factory reset and stock firmware flash, then see if it persists.
Only this solution worked for me on EU version:
http://forum.xda-developers.com/showthread.php?t=1555984
Tried that but still no luck
snpetit said:
Only this solution worked for me on EU version:
http://forum.xda-developers.com/showthread.php?t=1555984
Click to expand...
Click to collapse
I guess I have the same recovery. The issue is not with the scrolling recovery, but with the scrolling lock screen. Did it get fixed for you as well? Am using AOKP build 30.
Thank You!!!!
snpetit said:
Only this solution worked for me on EU version:
http://forum.xda-developers.com/showthread.php?t=1555984
Click to expand...
Click to collapse
Thank you so very much!! The issue which was bothering me for the last three months is now solved. Life saver..
By every one
I bought sgs2 some days ago
Now its rooted and installed aokp build 4 for sgs2
I have tried all ROMs here for sgs2 but I find 2 problems nearly in every custom ROM
1:
My music sound decreses with custom ROM
With stock ROM it was too loud in hands free but with custom ROM it is comparatively low
Any solution for this problem because I don't want to use stock ROM and also don't want to lose sound volume
2: second problem I faced not in all but in most jelly bean roms is auto flash
When I press back button for go to home from camera app its led flash on for a moment and then off
Any one know why these problem are occurring even with some stable ROMs like cm9 and all based on cm and aokp ROMs have this problem
Plz help if you know
So my question is that why music sound decreses in custom ROM ??? Is it happening only with me or some other people also suffering from this problem ?????
Hi all,
Scenario: got tired of unstable custom ROMs, did a full wipe(/data/system/cache) flashed stock rom (4.0.4 XEN) for my region. After setting up the first time ran Odin again to root with new Siyah v5.0.1. Got rid off Vlingo using Apex launcher trick(or Go launcher EX).
Now I noticed tonight I no longer have any home button lag with only the above changes to my phone. In other words happy me. However I cannot find any suggestions for any home button lag fix in Siyah's changelogs while the Vlingo assistant with it's annoying lag was present at first boot before kicking it off with the launcher trick. Now this used to result in no more Vlingo but still lag when pressing home.
Does anyone know if anything changed in the Stock rom 4.0.4 or Siyah 5.0.1? Don't get me wrong, happy with the result Just curious.
This is just from personal experience of using my galaxy s2 and by no means an expert...
But I never use the stock rom (with the exception of gingerbread) because anything after gingerbread lags like hell on my s2.
The only reason I can think of are the bloatware from samsung taking up all the hardware resources of the phone, thus slowing it down. Whereas I find most custom rom "cleaned" up the phone and require less resource to run.
I don't believe there is a problem with the kernel but I can be wrong!
If you are afraid of unstable custom rom, why not try CM9 stable mod? It has served me greatly.
rom
postfatal said:
rom
Click to expand...
Click to collapse
What does that^^^^ mean?
Using GT - I9100
I thank those who give helpful comments
I expect the same from others.
naeads said:
This is just from personal experience of using my galaxy s2 and by no means an expert...
But I never use the stock rom (with the exception of gingerbread) because anything after gingerbread lags like hell on my s2.
The only reason I can think of are the bloatware from samsung taking up all the hardware resources of the phone, thus slowing it down. Whereas I find most custom rom "cleaned" up the phone and require less resource to run.
I don't believe there is a problem with the kernel but I can be wrong!
If you are afraid of unstable custom rom, why not try CM9 stable mod? It has served me greatly.
Click to expand...
Click to collapse
This isn't about bloatware but the delay which was programmed into the stock to wait for a second press on the home key because of voice commands/Vlingo. In 4.0.3 deleting Vlingo did not fix the lag because it was hardcoded in the stock ROM.
Hi guys! I'm new to all of this.
I rooted my Galaxy S2 on a whim with the dorimax kernel.
Now I have the following trouble: There is a noticable lag between pressing the home button and closing the app/returning to the home screen.
This effect started happening after I installed the offical JB update from my provider the dorimanx kernel made it a lot more noticable(ICS was way faster in that regard... which puzzles me quite a bit)
What do I have to do to reduce this problem? Change something in the settings or install a non-stock ROM?
----------
Also three other questions out of curiousity:
Can I use the dorimax kernel with the neatrom?(as the need rom comes with another kernel, I would have to flash the dorimanx kernel on top of it after installing everything?)
If I made a nandroid backup before installing Neatrom: would I be able to return everything to how it was(stock SAMSUNG Rom with dorimanx kernel;by simply selecting my backup under the restore option in CWM) before installing neatrom in case I dont like it?
What is better: The CM that is based on JB 4.1 or NeatRom? Is the CM version based on 4.2 usable, or do they still have some annoying problems? <----I guess there is still no stable build for 4.2 under CM?
Thank you very much guys.
If I get positiv comments I'm gonna flash neatrom first thing tomorrow morning. I allready have nandroid backup and saved a lot of my favorite apps with TB.
Another QuestioN: Would I be able to install the Samsung Stock email app from a TB-Save on another rom?<-- I know that you shouldn't do this with system apps(I dont want to reenter the server adresses for my email account in an other app)
Heraku said:
Hi guys! I'm new to all of this.
I rooted my Galaxy S2 on a whim with the dorimax kernel.
Now I have the following trouble: There is a noticable lag between pressing the home button and closing the app/returning to the home screen.
This effect started happening after I installed the offical JB update from my provider the dorimanx kernel made it a lot more noticable(ICS was way faster in that regard... which puzzles me quite a bit)
What do I have to do to reduce this problem? Change something in the settings or install a non-stock ROM?
----------
Also three other questions out of curiousity:
Can I use the dorimax kernel with the neatrom?(as the need rom comes with another kernel, I would have to flash the dorimanx kernel on top of it after installing everything?)
If I made a nandroid backup before installing Neatrom: would I be able to return everything to how it was(stock SAMSUNG Rom with dorimanx kernel;by simply selecting my backup under the restore option in CWM) before installing neatrom in case I dont like it?
What is better: The CM that is based on JB 4.1 or NeatRom? Is the CM version based on 4.2 usable, or do they still have some annoying problems? <----I guess there is still no stable build for 4.2 under CM?
Thank you very much guys.
If I get positiv comments I'm gonna flash neatrom first thing tomorrow morning. I allready have nandroid backup and saved a lot of my favorite apps with TB.
Another QuestioN: Would I be able to install the Samsung Stock email app from a TB-Save on another rom?<-- I know that you shouldn't do this with system apps(I dont want to reenter the server adresses for my email account in an other app)
Click to expand...
Click to collapse
I'm Sure someone else will know different but for me the lag was always there and I never heard of a way to reduce it, I've been using an s3 mini today running 4.1 and there is considerable lag between pressing the button and returning to the home screen so it could be a fault in Samsung JB rom's. Try neatrom, as I understand it's blazingly fast and a considerable improvement over stock.
I've been running cm10.1 for a while and it still has some big bugs (hardware composer etc) that will probably never be sorted due to Samsung's unwillingness to release their sources, and the FM radio does not work. However everything I use works the odd game doesn't (real racing 3) due to I believe the Mali drivers but other than that everything else is running ok. Recent updates have made it very fast and for me it's faster than any "stock" based rom.
Yes you can use dori kernel with neatrom and cm10.1 as well, although you will need the 9.xx kernel.
You can use the stock email app on neatrom and any other stock based rom but not on Cyanogenmmod or any other AOSP based rom.
Yea backup in CWM and you can restore it if you don't like Neatrom.
Hope some of this helps
I own a Galaxy S4 I9505 device.
Earlier I was running the stock based Custom ROM (Imperium 16.1, Android 4.4.2) on my S4 and there was no problem at all. That ROM gave me supreme performance, stability and battery life.
And then official Lollipop (5.0.1) was released by Samsung. I flashed the latest stock based custom Lollipop ROM on my device and the problem started (or may be the problem started because I have dropped my device once).
Now what happens is ... after I flash a ROM everything is working fine. But then after some uncertain period all the sensors stop working on the device.
Sometimes the issue is resolved by a simple restart, at times I have to clear the Cache and sometimes I have to clear the Cache and Dalvik Cache**.
All the sensors start working and after some time suddenly, all the sensors stop working.
I have tried all stock based Custom Lollipop ROMs and even AOSP based Lollipop ROMs, but this problem is persistent with all the Lollipop ROMS.
I have even tried Original Lollipop Firmware (flashed through odin), but the problem persists.
I open the back-cover and tightened all the screws, thinking it could resolve the issue. But the problem persists.
I am not able to decipher if this is a Software or Hardware issue.
Can anyone help me on this? Has anyone faced this type of problem? :crying:
I am not sure if this is the right place to post such a question. If it isn't please guide me to a proper thread.
Thanks
Since you just said you drop the phone.. i think it has something to do with that... looks like a hardware issue..
radz.min said:
Since you just said you drop the phone.. i think it has something to do with that... looks like a hardware issue..
Click to expand...
Click to collapse
@radz.min thanks for the screen shot .... you think it could be a hardware issue ... but as i mentioned .... sensors work good for half an hour or so and then they stop working ... if it was a hardware issue ... it should not work at all .... right ??