Related
Figured perhaps a bug thread for the Rogers 2.2 update may be in order?
Not sure if this is a bug or not, but it does seem a bit odd. The lock screen usually has the text "swipe screen to unlock" or something to that nature (the part with the <<< and >>>) - mine had it to begin with in 2.2, however now it has dissapeared and I just see the little lock icon saying the phone is locked. Is there any way to get it back or is this a 2.2 "feature" so you see more of your background?
The 2nd problem I noticed I have already started a thread on (and no replies ) - it deals with contact linking and Facebook. Seems something is whacky there too possibly. The thread: http://forum.xda-developers.com/showthread.php?t=907088
j.smith said:
Figured perhaps a bug thread for the Rogers 2.2 update may be in order?
Not sure if this is a bug or not, but it does seem a bit odd. The lock screen usually has the text "swipe screen to unlock" or something to that nature (the part with the <<< and >>>) - mine had it to begin with in 2.2, however now it has dissapeared and I just see the little lock icon saying the phone is locked. Is there any way to get it back or is this a 2.2 "feature" so you see more of your background?
The 2nd problem I noticed I have already started a thread on (and no replies ) - it deals with contact linking and Facebook. Seems something is whacky there too possibly. The thread: http://forum.xda-developers.com/showthread.php?t=907088
Click to expand...
Click to collapse
Definitely a feature. I love the clearer lock screen.
Bug: Haptic feedback vibration is very low system wide (not including soft keys).
Bug: Voice Dialer (Voice Dialler) is misspelled in the App Drawer.
Bug: Going to Settings > Display > Font Style causes a crash.
All I remember so far but there has been several.
Enhanced said:
Definitely a feature. I love the clearer lock screen.
Click to expand...
Click to collapse
Confirmed feature of Froyo, or is this a Rogers/Samsung specific feature? Just wondering because it WAS showing up for a few lock screens right after the upgrade, then eventually stopped showing up - reboot/battery reset didn't get it back... haven't tried a factory reset yet to see if that fixes it (if it's broke).
Enhanced said:
Bug: Going to Settings > Display > Font Style causes a crash.
Click to expand...
Click to collapse
No problems here - did you have it set to a custom/non default font when upgrading? I had mine on default (I prefer that to any other font) and have no issues changing fonts.
I've had some issues with wifi losing it's internet / market connection after wake up sometimes. shows still connected, but no network access. i have to turn wifi off, then back on occasionally.
rnewton01 said:
I've had some issues with wifi losing it's internet / market connection after wake up sometimes. shows still connected, but no network access. i have to turn wifi off, then back on occasionally.
Click to expand...
Click to collapse
Go to Settings -> Wireless and network -> Wi-Fi settings. From this screen, hit your menu key and select Advanced and try changing your Wi-Fi sleep policy to Never... perhaps it's set to "When screen turns off" causing you to lose Wi-Fi whenever you lock your phone?
Oh, another bug possibly...
Go to Camera app and open Settings. Open the wrench tab and go to the 2nd page. Click the Update button beside Firmware update. Either of the next two menu choices ("Check version by network" or "Firmware update") seem to freeze the phone (power off required). Doesn't seem to happen all the time, but my first time trying to get the update to do something caused the phone to lock up in to camera mode.
Also, the "It will occur additional fee." message is quite fun... no idea what fees I will incur, or for what reason (and I won't even get in to the grammar issues).
j.smith said:
Confirmed feature of Froyo, or is this a Rogers/Samsung specific feature? Just wondering because it WAS showing up for a few lock screens right after the upgrade, then eventually stopped showing up - reboot/battery reset didn't get it back... haven't tried a factory reset yet to see if that fixes it (if it's broke).
Click to expand...
Click to collapse
Well it can't be a Froyo feature because no other manufactures use the same lock screen as they do. So it's a Samsung feature brought on by Froyo. Simply, it can't be a bug.
No problems here - did you have it set to a custom/non default font when upgrading? I had mine on default (I prefer that to any other font) and have no issues changing fonts.
Click to expand...
Click to collapse
Yeah, I had to it some other font besides the default font...guess I'm screwed now? Bugs like these make me more anxious to get real Froyo.
Enhanced said:
W..guess I'm screwed now? Bugs like these make me more anxious to get real Froyo.
Click to expand...
Click to collapse
This is real Froyo from Rogers.
Anyone noticing that it's very glitchy and not smooth?
sirknattar said:
Anyone noticing that it's very glitchy and not smooth?
Click to expand...
Click to collapse
Its much faster and smoother than 2.1 stock was for me. Did you set it up fresh? Older settings can cause issues.
you guys have this issue? you may not even know it until you try to use mass storage mode. I use iSyncr (lets me use smart playlists based on ratings) so I need mass storage mode.
http://forum.xda-developers.com/showthread.php?t=907854
My wife and I (each have a Captivate) have had none of the bugs you guys have mentioned.
All we have experienced is a faster phone and WAY better battery life.
The only thing that upset me is that the update deleted my Ocean Wave livewallpaper, but I just redownloaded it.
Did some of you guys experiencing bugs ever run a custom ROM? I am thinking maybe these issues might be because you did...
Re: Haptic Feedback.
I've noticed it too, it's much weaker than before.
I could have sworn that I saw the option to turn up the intensity before, but can't find it now.
I want to update, but all these bugs are not very comforting
Jeffu said:
I want to update, but all these bugs are not very comforting
Click to expand...
Click to collapse
Go for it..I installed it and so far the improvements have been great over 2.1
Battery life is much improved, its faster than stock 2.1 (and after applying Ryan's OCLF...its incredibly responsive)
If you do have a lagfix installed prior to upgrading you should uninstall that first. Thats what I did and didn't have much problems. my one issue with Swype was fixed by clearing the cache.
shawn122 said:
Go for it..I installed it and so far the improvements have been great over 2.1
Battery life is much improved, its faster than stock 2.1 (and after applying Ryan's OCLF...its incredibly responsive)
If you do have a lagfix installed prior to upgrading you should uninstall that first. Thats what I did and didn't have much problems. my one issue with Swype was fixed by clearing the cache.
Click to expand...
Click to collapse
I gave it a go on your recommendation. Updated with no issues, now to actually try using it...
Has anyone rooted after applying 2.2? If so, what did you use?
I've been having issues turning on WiFi on my phone ever since I installed the update.
I accidentally clicked Airplane mode on my phone this morning, now my phone has been trying to turn the WiFi back on for about 5 mins....
As for battery life, my phone the first few days after installing Froyo seemed great, but now it doesn't really seem as good? No idea why....
And I've noticed a bit of lag at times while navigating on my phone.
Using LauncherPro Plus as my home screen, haven't rooted or installed any roms or anything.
I have noticed that when you turn the phone on from when it is off, if you don't wait for the wallpaper to display before swiping your phone on, the phone will stall. Mine stalled for about 5 minutes before it responded again.
I'm having a couple of small issues:
1) I can't get the GPS to look position. It just displays "Waiting for Location" and sits there.
2) OCLG - I got about 1000 on quadrant score. It doesn't seem laggy but I wanted to apply this lagfix to see if it can be better. I tried runnig the first option in the menu (z4 rooting), and it tries to launch either a page or the market (not sure which) but says "Page Not Found", but when you close it and press back, it says the root was successful, but all the other options are still "unavailable" so I can't apply the lagfix. There's a second method in the menu to do a root and that one fails as well, so I'm not sure how to get this working.
3) Camera - I got the same problem as a previous poster for the firmware update where it says "fees will occur" then when I click "yes", it tries to launch a page/market (again not sure) and says "Page Not Found".
4) Rooting - not sure how to root because the previous method of putting my update.zip and doing it through the recovery menu fails.
Any help is appreciated.
I was running rooted lagfixed stock Rogers 2.1 before. Removed lagfix first and did a factory reset before updating to 2.2 through Kies.
After updating to 2.2 I re-rooted and lagfixed with no issue.
Things bugs I have noticed on my phone:
- Camera a few times had started up with a black screen only with usual camera options but it's as if it does not see anything from the lens (had done camera fw update on it. You can download it from Samsung Apps app)
- When viewing "Contacts" can't press Back button to exit it so I just press Home button. Small bug
- can't set up smtp outbound email settings on stock email app. Keep getting it can't connect with server even when manually inputting correct settings.
- Battery undetermined as i've been playing with GPS a lot testing it so it drains pretty quick.
- GPS - Had no problems with 2.1 (using GPS + "Use wireless networks") but it's been horrible on 2.2. Locks ok when stationary, fluctuating between 5-9 satellite locks (used lbstestmode to check) but when you are moving or when using it for Navigation, it will be ok for a short bit then would eventually start bouncing all over the place or start getting weak/lost locks. Was using it on the hwy one time and it would suddenly tell me to do a u-turn because it thought I was on a side road. (condition was clear and phone was by windshield).
What it did fix for me:
- Opening Gallery before would sometimes lock up the phone requiring battery pull in 2.1. Fixed for me with 2.2
- Running latest updated Maps would sometimes lock up the phone requiring battery pull in 2.1. Fixed for me with 2.2 but still somewhat useless because of issue mentioned previously.
I can live with all the bugs except for the abismal gps.
This is a continuation of the generic TCC8803 thread at http://forum.xda-developers.com/showthread.php?t=1119778
IMPORTANT - THERE IS A SYSTEM APP CALLED FWTOOL. DO NOT USE IT TO FLASH FIRMWARE OR YOU MAY END UP BRICKING YOUR TOUCHSCREEN. ALSO DO NOT FLASH ANY VERSION OF lk.rom OR YOU WILL BRICK YOUR TABLET.
To install clockworkmod
Download EM73-8K-recovery-signed.zip below. Rename it to update.zip and copy it to the root of your SD card.
With your tablet already turned off, press and hold down the Back button and then press the power on button while still holding down the Back button. This will open stock Recovery.
Use the buttons on the top of your tablet to navigate your way through recovery and to select menu items (menu = down, back = returns to previous menu, home = selects option).
Navigate to apply update.zip & follow the instructions. Reboot.
To use clockworkmod just press and hold down the Back button while powering up your tablet. Navigate the menu via the buttons (menu = down, back = returns to previous menu, home = selects option).
To make a Nandroid (clockworkmod) backup boot into clockworkmod recovery & navigate down to Backup then follow the instructions.
To root your tablet ** please see comment at end of post before continuing past this point
+++Make a full Nandroid (clockworkmod) backup before attempting this+++
Download & unzip Superoneclick from http://forum.xda-developers.com/showthread.php?t=803682 - NB you may need to turn off any antivirus program on your PC to allow downloading & use of Superoneclick.
Download & unzip the relevant Drivers folder (32 or 64 bit) from link below then connect your (powered on) tablet to your PC & point Device Manager to your unzipped drivers folder when it is looking for drivers.
Make sure USB debugging is allowed on your tablet (Settings -> Development -> USB debugging)
Right-click on Superoneclick.exe, select Run as administrator then click on the Root button. It will take 2 or 3 minutes for your device to be rooted.
This procedure has worked for my own tablet but I accept no responsibility if you end up bricking your device!
Another way to root your tablet is at http://forum.xda-developers.com/showthread.php?t=1119778
To stop battery drain & prevent screen from waking every few minutes - **only for original Kogan ROM**
(with thanks to hallokitty for this fix)
This happens because the tablet keeps looking for the 3G signal it cannot ever receive. To fix this, go to System/app using Root Explorer from the Market, delete (or rename) phone.apk and TelephonyProvider.apk. You will immediately start getting errors but just use the reset button at the back of the tablet and when you reboot the problem has been solved. If you ever want to restore these apk's (e.g. if you want to use a 3G modem) just flash the phone+telephony zip file below using clockwork mod.
Clockworkmod rescue backups
I've done a factory reset & wipe of my tablet & made clockworkmod backups which I've linked to below. Make sure you do a full Nandroid backup before applying any of these. Unzip the file & place it in the appropriate Nandroid folder on your SD card (/clockworkmod/backup/), don't try to flash the zip file using CWM! These are a slightly slimmed down versions of the ROMs - for the Kogan ROM I've removed phone.apk, telephony.apk, Email, Facebook, Twitter, FW tool (dangerous to have), ES Explorer, Live Wallpapers and ES task manager. I've upgraded Spare Parts to Spare Parts + and added Astro File Manager as a user app. I had removed most of these things from my ROM before I was ever asked to make this backup so if you want to reinstall them you can get them from the Market or flash the relevant apk's into the system/app folder using CWM. The ROM is still rooted. You will need to do a factory reset & wipe the Data partition & Dalvik cache with CWM prior to doing this. If you want to use a 3G modem you will need to flash the "phone + telephony.zip" file listed below with clockworkmod.
Kogan firmware clockworkmod rescue backup: http://www.mediafire.com/?izfedrz97iowi34
**If you're really lazy you can combine rooting the tablet, removing unnecessary system apps & applying the screen wake fix by installing clockworkmod then restoring the rescue backup (NB make sure you make your own Nandroid backup first!!!).
CM7 runs extremely well on the Kogan except for HDMI out & Camera which don't work yet. You will also need to install Gmail & Youtube apps from the Market if you want them. Make sure you do a full CWM/Nandroid backup before trying this as I had problems with an unresponsive touchscreen after flashing the most recent CM7 ROM. For more info head here.
Tips & Tricks
MoboPlayer is a good video player, particularly for its ability to let you change the volume & screen brightness by swiping up & down directly on the video you are watching. The volume softkeys on the Kogan are not visible if any app is in fullscreen mode.
Titanium Backup may not show all installed apps or any system apps. To fix this go to Titanium Backup's Preferences and tick "Force use system Busybox" and "Force use system SQlite".
OK mine has arrived lets see what we can do
flipside101 said:
OK mine has arrived lets see what we can do
Click to expand...
Click to collapse
Lucky you - they're really dragging their heels with mine. Can you upload the kernel & we can see about getting clockworkmod for it?
How do you rate it as a tablet? Is the keyboard OK? - some people have said it's a bit carp.
I got mine today. It's going back as soon as I can get Kogan to respond.
Turns itself on & off at random, poor quality screen, sound, responsiveness.
Touchscreen activates itself without being touched.
What was I thinking? I guess you get what you pay for.
Now if only I could get them to reply to an email.......
Ok i have to agree you get what you pay for so i had low exectations. Its no flyer,tab,transformer but then it was a 1/4 of the cost. Yes the screen has issues (partly i think due to the screen protecter and battery life is poor though ive had this on for about 2 hrs now and its about 2/3rds down.
All in all im happy though going to live with it for a bit and i reserve the right to change my mind.
Wil right more when i have aproper keyboard
yeh i get the same problem with the screen comming on and off randomly.. i wish i could stop that =P (would save the 3 hour battery life i have to 4 hours!)
you get what you pay for =P but i thought the screen was quite good considering.
did you try the recovery yet?
how nice would it be to port oxygen to the kogan haha
wlee2 said:
yeh i get the same problem with the screen comming on and off randomly.. i wish i could stop that =P (would save the 3 hour battery life i have to 4 hours!)
you get what you pay for =P but i thought the screen was quite good considering.
did you try the recovery yet?
how nice would it be to port oxygen to the kogan haha
Click to expand...
Click to collapse
The screen keeps coming on as the OS is looking for a 3G signal all the time. If you switch it to airplane mode it should stop happening. Or use http://www.appbrain.com/app/airplane-mode-wi-fi-tool/net.geekherd.airplanemode . Or you could even try adjusting the settings to use 2G only.
I can't adjust to 2g only on mine - it's greyed out.
Yes, I've put it back to factory setting a few times, but it's no better.
The switching on/off isn't the main problem (though it has used 30% of the batter life in 8 hours during the night).
The main issue is the touchscreen simply activating itself. If i go into a menu of any kind, it sometimes selects something for me. It happens too often to just ignore it.
Sounds like a faulty screen :-( - let us know how you get on returning it! If mine turns out to be rubbish when it arrives my Plan B is this one http://mp4nation.net/catalog/index.php?main_page=product_info&cPath=68&products_id=496
well im having the random on issues (thanks for the airplane mode idea ill give it a tray) but the screen activations are not a problem.
@dwl99 that mp4nation link is the same as the kogan (a rebranded em73) so its likely to have the same niggles i think
flipside101 said:
well im having the random on issues (thanks for the airplane mode idea ill give it a tray) but the screen activations are not a problem.
@dwl99 that mp4nation link is the same as the kogan (a rebranded em73) so its likely to have the same niggles i think
Click to expand...
Click to collapse
A lot of these tablets are very similar (Herotab C8, Dropad A8) but there seem to be some important differences in the components used. I've been lurking in some Heropad C8 forums and nobody seems to have reported touchscreen problems.
This one look exactl;y the same , button layout etc etc however i know what you saying as even within the same model different components can be swapped in as costs change between runs
BTW
Kernel
2.6.35.7
Build
EM73_SIS_GC2M_V2 20110516
WILL UPLOAD WHEN I GET A CHANCE TO DUMP IT
An app that sticks it in Airplane Mode when you put it into sleep mode is a good work around for now, try "Auto Airplane Mode" (I can't link because I haven't posted enough, it seems...
Hasn't randomly turned on since I installed this. Ahh, forget that, it seems to be doing it again, it just took a lot longer...
In general, this thing is a bit cheap and nasty, but I guess that's what I expected. The button placement is seriously weird, and the touchscreen and accelerometer are just inaccurate and jittery (try playing a game that uses the accelerometer! good luck!)
I feel like it could benefit a lot from a nice ROM though, to fix a few issues (where the hell is the accounts & sync menu?)
hallokitty said:
I feel like it could benefit a lot from a nice ROM though, to fix a few issues (where the hell is the accounts & sync menu?)
Click to expand...
Click to collapse
Been trying to find how to set these before
i found it once earlier on but i cant find it again!!!
it was not where i expected and i think i had to do a round about method to find it.
i have a feeling it had something to do when i was trying to sync email contact with a email app but i forgot which one lol..
dwl99 said:
The screen keeps coming on as the OS is looking for a 3G signal all the time. If you switch it to airplane mode it should stop happening. Or use http://www.appbrain.com/app/airplane-mode-wi-fi-tool/net.geekherd.airplanemode . Or you could even try adjusting the settings to use 2G only.
Click to expand...
Click to collapse
just FYI on the kogans you can activate aeroplane mode in settings then using the power controls widget on your home screen turn on wifi
it will keep the aeroplane mode on but wifi on as well atleast it worked on mine you dont need an app for it.
i actually wonder if the screen wake has something to do with background sync should try turn it off for a night and see.
Okay, so after being plugged in and fully charged, I unplugged it and left to drain overnight to see what would happen.
I had "Auto Airplane Mode" on, but as you'll understand, it helped, but not enough.
Even in Airplane Mode, the tablet would wake itself up, then "Auto Airplane Mode" would see the screen is on, and turn the wifi back on, then back off when the screen faded.
But, I'm thinking this might be because it has Sync enabled. I'm going to try it again with sync disabled.
The battery graph was a joke - it started smoothly going down at a reasonable pace, then -no lie- it spiked down.. then UP, then down, then up, throughout the night. It was at about 75% when I turned it back on after say, 8 hours. Then it dropped to 72%, then I plugged it in, and it immediately reported 98%. The biggest drain by a long way is "Mobile Standby".
However, for the most part, bar the bad accelerometer, terrible button placement, and slightly sharp edges, the hardware itself is not terrible for the money - 512MB RAM and 1GHz processor; I don't mind 800x480 at 7", it looks passable, although it's bad in sunlight. (Of course the viewing angles are bad, but for the cost, that's expected/OK).
But damn the software needs tweaking because it just has problems.
vv
Model number: EM73_SIS_GC2M_V2
Kernel Version: 2.6.35.7
Build number: EM73_SIS_GC2M_V2 20110516
Hi all since installing auto airplane I don't think im seeing wakes issues. I left the kogan overnight at about 50% battery and this morning it was at 35%. Ill test again tonight just to be sure as you seem to have the same build and kernel .
EDIT:
Ok i do still have it
Sent from my HTC Desire using XDA App
Though I have to agree the roms a joke accourding to quick system info 77% of my power useage has been down to mobile standby HUH.
Edit one thought is the 3g component in there for the 3g USB comparability and if so that was a new feature so could there be a rom that exists without it. I have added a topic in this forum asking if its possible to strip the 3g component out.
Sent from my HTC Desire using XDA App
Huh, no, it still seems to turn the screen on now and then even with sync off and in airplane mode. This thing needs a custom ROM as soon as possible. I imagine after a while people will start to sell them cheap because of problems that could mostly be fixed with better software, so I think it could be a pretty popular tablet for people willing to customise it..
Hi,
I am using the FatToad custom rom. Whenever I turn on my phone via power button the screen stays black. It doesn't look like the backlight is on. However, the menu button and back button light up. I tried using the volume rockers and home button to power on the screen but it's the same.
The screen does turn on after a couple tries. I have to press power button on (lights turn on), turn off, then back on. The number of tries varies. If I turn it off and back on immediately- then it comes back right away. Whenever I am done with a call, the screen stays off and I have to press the power button to get the screen back. I tried setting the phone to turn the screen on when plugging in charger cable but screen doesn't turn on right away. The auto-brightness seems to be working properly.
I didn't have this issue running the stock relay 4g rom. I have also tried the CarbonMod rom and OmniToad roms to see if it helped but would rather not have to go back to stock unless I need to.
I can live it with it but if anyone has a resolution it would be super awesome. Hopefully it's something simple that I messed up and not the phone itself!
Thanks,
-Alan
thebguard said:
Hi,
I am using the FatToad custom rom. Whenever I turn on my phone via power button the screen stays black. It doesn't look like the backlight is on. However, the menu button and back button light up. I tried using the volume rockers and home button to power on the screen but it's the same.
The screen does turn on after a couple tries. I have to press power button on (lights turn on), turn off, then back on. The number of tries varies. If I turn it off and back on immediately- then it comes back right away. Whenever I am done with a call, the screen stays off and I have to press the power button to get the screen back. I tried setting the phone to turn the screen on when plugging in charger cable but screen doesn't turn on right away. The auto-brightness seems to be working properly.
I didn't have this issue running the stock relay 4g rom. I have also tried the CarbonMod rom and OmniToad roms to see if it helped but would rather not have to go back to stock unless I need to.
I can live it with it but if anyone has a resolution it would be super awesome. Hopefully it's something simple that I messed up and not the phone itself!
Thanks,
-Alan
Click to expand...
Click to collapse
are you having this issue on all above mentioned roms....i have seen this issue before on other devices and is a deep sleep issue...i know the only rom you may be able to fix this on is my CarbonRom and done so by changing min frequency up a notch...if that doesnt work go down a notch....all other roms besides carbon have this feature force locked as far as i know so you cant do it on those roms
REV3NT3CH said:
are you having this issue on all above mentioned roms....i have seen this issue before on other devices and is a deep sleep issue...i know the only rom you may be able to fix this on is my CarbonRom and done so by changing min frequency up a notch...if that doesnt work go down a notch....all other roms besides carbon have this feature force locked as far as i know so you cant do it on those roms
Click to expand...
Click to collapse
I see. I will retry CarbonRom and up the min cpu and see if this issue goes away. Appreciate your feedback sir!
REV3NT3CH said:
are you having this issue on all above mentioned roms....i have seen this issue before on other devices and is a deep sleep issue...i know the only rom you may be able to fix this on is my CarbonRom and done so by changing min frequency up a notch...if that doesnt work go down a notch....all other roms besides carbon have this feature force locked as far as i know so you cant do it on those roms
Click to expand...
Click to collapse
I've got "FatToad" (nice rom, bad name) and the Trickster Mod app provides plenty of tuning options. Since the trouble manifests itself when the screen is off, I would look at mpdecision before I went raising the min frequency. Then again, I don't have many issues with getting my device to wake...
Anyhow, the app has options to tweak.
orange808 said:
I've got "FatToad" (nice rom, bad name) and the Trickster Mod app provides plenty of tuning options. Since the trouble manifests itself when the screen is off, I would look at mpdecision before I went raising the min frequency. Then again, I don't have many issues with getting my device to wake...
Anyhow, the app has options to tweak.
Click to expand...
Click to collapse
my Carbon rom is built differently than fattoad, cm, or omni...doesnt have lbcoders mpdecision touchboost amongst many other differences in its kernel
---------- Post added at 11:23 PM ---------- Previous post was at 11:16 PM ----------
thebguard said:
I see. I will retry CarbonRom and up the min cpu and see if this issue goes away. Appreciate your feedback sir!
Click to expand...
Click to collapse
if its at 192mhz go to 384mhz....if at 384mhz try 192mhz...if either dont work bump it up to the next highest mhz
I don't think changing the min cpu helped. Went up from 384 to 486. Then tried 594.
thebguard said:
I don't think changing the min cpu helped. Went up from 384 to 486. Then tried 594.
Click to expand...
Click to collapse
did you go to the lowest...also whats your method of flashing.....dirty flash? clean wipe?
REV3NT3CH said:
did you go to the lowest...also whats your method of flashing.....dirty flash? clean wipe?
Click to expand...
Click to collapse
The lowest option I had was 384mhz.
Flashing via CWM recovery: wiping data/system/cache/dalvik. Then CarbonRom and gapps. So clean wipe I think is what you are referring.
Sent you a zip to try via pm. Just let me know if it works.
Sent from my LG-VS980 using Tapatalk 4
Does this issue manifest itself when you have the phone plugged in? Can you get a logcat of the issue? Throwing things at the wall and seeing what sticks may not be the best resolution here. There are ways of finding out the underlying cause.
mpdecision is not the cause here (That only affects the secondary core) nor is min frequency (You can override it in the HypnoToad images too, just set another governor (like say 'conservative). In FatToad it may look like it resets because Cyanogenmod doesn't display the second core in the performance settings, but changing it is sufficient for testing. The official CM 11 builds do not have the touch boost (which only affects things after the phone is awake, and merely sets the secondary core's frequency up to 1184 Mhz when you are touching the screen, but the affect on the percieved performance of the phone due to this is immense)
Deep sleep is likely closer to the main cause because that affects both cores, and if the system isn't receiving the proper signals to wake back up, this can happen. Throughout development on apexqtmo, we've run into similar problems, and it's always helped by getting proper documentation from those who are experiencing the issues.
TL;DR: Trying random things likely won't solve this issue. Getting all the information you can will help.
Thanks again for all the help. I don't usually ask for any but I could not find much on my issue (or maybe I wasn't searching correctly).
I think I did the logcat correctly. See attached.
The thing that popped was:
D/SurfaceControl( 791): Excessive delay in unblankDisplay() while turning screen on: 269ms
Click to expand...
Click to collapse
When I would hit the power button and screen would not turn on, this would be there. I'm not really good with understanding this stuff. Hopefully this leads us in right direction though!
Edit: sorry forgot to answer your first question Magamo. This issue happens no matter if it's plugged in or not.
Edit 2: I watched the logcat from adb for awhile and I guess the above happens no matter what. I don't see any differences between if the screen turns on or not.
It looks like you have a hardware rev we're not supporting in our current kernel (which is why it works on stock). PM me if you want to mail your phone to me for analysis
This happened to a new device i purchased. After lbcoder and nard trailed through my logs, I was prescribed to resell the device. Your symptoms sounds identical to what I was experiencing. JB stock kernal works. But custom roms which since delved into the new edited kernel doesnt work on such devices. Since re-sold the device. Be interested to know if yours gets fixed where mine didn't. Good luck
Hi guys. I have a strange issue, that might be related to what's described in this thread.
Almost always when I open or close the keyboard, the screen goes blank for few seconds. One thing (that I think) helps is to press power button several times until the lockscreen comes up.
I am currently running LiquidSmooth 4.4.3, tried it with 4.4.4 and also some old backup 4.4.2 and the phones does it always. The critical position when it goes blank is just a millimiter when opening the keyboard from closed position.
Does any of you have the same experience? Can you please help me to determine either it's a ROM issue (deep sleep etc) or hardware issue?
I tried it also with the logos, boot animations and the screen goes blank too. So I fear it's hardware related - maybe a flex cable contact, but it would not come back so easily after few seconds. Another clue is that the keyboard lights and back+home stay on, but the screen goes blank.
I wish it's something that can be fixed by flashing or setting something as I waited few weeks to deliver my relay to Europe... Thanks for any help in advance!
sorgo said:
Hi guys. I have a strange issue, that might be related to what's described in this thread.
Almost always when I open or close the keyboard, the screen goes blank for few seconds. One thing (that I think) helps is to press power button several times until the lockscreen comes up.
I am currently running LiquidSmooth 4.4.3, tried it with 4.4.4 and also some old backup 4.4.2 and the phones does it always. The critical position when it goes blank is just a millimiter when opening the keyboard from closed position.
Does any of you have the same experience? Can you please help me to determine either it's a ROM issue (deep sleep etc) or hardware issue?
I tried it also with the logos, boot animations and the screen goes blank too. So I fear it's hardware related - maybe a flex cable contact, but it would not come back so easily after few seconds. Another clue is that the keyboard lights and back+home stay on, but the screen goes blank.
I wish it's something that can be fixed by flashing or setting something as I waited few weeks to deliver my relay to Europe... Thanks for any help in advance!
Click to expand...
Click to collapse
if its doing it an more than one rom it may be hardware...especially if its doing it at startup logo and bootani...does it do it on cm11 as well as omni?
REV3NT3CH said:
if its doing it an more than one rom it may be hardware...especially if its doing it at startup logo and bootani...does it do it on cm11 as well as omni?
Click to expand...
Click to collapse
Thanks for the reply. Yes the bootanimation and initial logo is telling enough about the cause of it. I must admit it's a hw problem. I tried to open/close the keyboard quicky instead of moving it slowly, but it occurs too. I'll try completely different rom with different kernel as the last chance
to hope for a sw issue.
I tried Omnirom with same result, but now I did a clean flash of the latest liquid and my impression is that this happens a lot fewer times than before. Maybe I just got the right velocity and force needed to open it gently I also installed just a few critical apps. Before I messed with Ultimate screen rotate etc.
But it now happens more when closing the keyboard. However, I'll rather buy new one, just ot have a backup of this great phone just in case.
http://www.cellulardr.com/samsung-t699-slide-flex/
Is this "the part" I need?
Do you have any experiences with this shop? It seems to me too much $40+shipping for that cable. Probably I'll just order another one from ebay, preferably new one and leave the current one for spare parts in the future.
Fixed today! You can see the state of the flex cable on the last picture in this post:
http://forum.xda-developers.com/showpost.php?p=56642402&postcount=35
So hey folks,
This is the most strange issue i've experienced with my OPO so far.. Already had many random reboots since i manually flashed 38R, but this night Bacon screwed things up.
I woke up, seeing my OPO in a boot loop, it was super hot aswell and has drained the whole battery. So i connected my charger, did a reboot.
'Android is upgrading. Optimizing apps.' - OK so far, but only a total of 106 apps (With my last runtime change to ART, it showed 188 apps..). W/e.
Now it comes. Phone boots up - language defaulted. Whole settings reverted to stock. Apps are still there, but data is lost. :crying: Media on phone is untouched.
Suddenly i see these super strange buttons - they are NOT in their usual CM11S-Design!! And i did not change any visual stuff. [Attached Screenshot of notification screen]
Top right button to switch to quick actions does not work anymore, no reaction.
Home button completely not working aswell.
Also if i shut down and charge, the charging animation is completely different and colored instead oft OPO's normal one.
Restart menu back one low-level functionality aswell..only restart and shutdown possible [Attached Screen]
It's like my phone reverted itself to half generic android.
Guys, what the Heck happened?!
I mean, i will prolly just hard reset and reflash my phone later this day, but really.. WTH is this?? Any similar experiences so far? Or any Problem solutions?
Thanks for your time and replies..
Wasnt able to post in OPO Forums so far (server error >.>) but will update this thread if i get more info.
Attached screen shows that Rom status seems normal..
Hello World,
I recently purchased a SGN 12.2 Pro - Model Number SM-P900.
I flashed CyanogenMod onto it, and now its Android Version is 5.1.1
The CyanogenMod version is 12.1-20151104-Unofficial-v1aWIFI
The kernel version is 3.4.104-gd233b3f
Now for the most part the system runs smooth and w/o problems, but 7 or 8 times out of 10 when it goes asleep (screen is off and no program is actively running in the foreground, but the system was not shut down), I can not wake the tablet back up again.
Matter of fact, I end up having to perform a hard reboot on the tablet (pressing the power button until I force a reset) to get it to respond again.
I ran a logcat session in the background to catch any error, but the recorded log did not any error when this happened. It just suddenly stopped recording.
For me it seems like the system is going into some sort of hibernation mode, from which it only awakes after a hard reset.
But I don't see any such setting as "hibernation" in my system panel, and I certainly didn't install any such program on my tablet.
Now I am getting afraid that I might end up corrupting the filesystem or some important database by forcing these hard resets all the time.
That is why I need to find out what's going on here - anyone got some constructive ideas about it?
To rule out any potential hardware issues, you might want to try seeing if the problem occurs on stock as well.
ShadowLea said:
To rule out any potential hardware issues, you might want to try seeing if the problem occurs on stock as well.
Click to expand...
Click to collapse
Nice idea, but I need the functionallity of CM, and I also rely on my tablet for work - so I can't play "flashaholic" here.
But I have upgraded my CM Firmware three times in a row by now, and if this is CM related, then all those firmware packages would have to cause the same problem - with me being the only one who suffers from it (because I didn't read anyone else having this problem in the CM comment threads).
Really? Cwm for functionality? Even Snote doesn't work in cwm thus for a note device cwm is waste of space although for devices without spen i recommend cwm as well and do you want your problem to be fixed or not if yes then flash stock firmware to check if it's software or hardware related.
Osama chohan said:
Really? Cwm for functionality? Even Snote doesn't work in cwm thus for a note device cwm is waste of space although for devices without spen i recommend cwm as well and do you want your problem to be fixed or not if yes then flash stock firmware to check if it's software or hardware related.
Click to expand...
Click to collapse
Those are pretty brazen and broadband condemnations of a custom ROM that has won many distinctions and is even considered by industry groups as a replacement for STOCK ROMs.
And since SNOTE is part of Samsung's most crappy Software Suite, I truly would not regard *that app* as a benchmark of quality.
Now do you have any links to confirm your loudmouthed dismissal of CM, or does that fall into the same category as urban myths such as "openSUSE isn't real Linux" and "Virus Scanners are useless"?
And by the way: CM = Cyanogen Mod (Custom Firmware); CWM = Clockwork Mod (Custom Recovery).
Not the same by a longshot - and I use TW for recovery anyway.
PS: I found a solution by now in installing an app which prevents the tablet from going into deep sleep mode (-> CPU_WAKE_LOCK). As it seems at times the tablet would come back online after some seconds, *if* I let go of the power button in time. But since I have the tablet hooked up to a power source most of the time anyway, I don't need deep sleep mode, and I was never good at counting seconds when pressing the power button.
That app resolved the "sleep of death" issue for me.
PS#2: As a systems admin I generally refuse advise of the kind of "just reinstall (flash) from scratch and see if it fixes the problem", for that is *not* debugging, its just being too lazy to perform root cause analysis.
Masinissa said:
Those are pretty brazen and broadband condemnations of a custom ROM that has won many distinctions and is even considered by industry groups as a replacement for STOCK ROMs.
And since SNOTE is part of Samsung's most crappy Software Suite, I truly would not regard *that app* as a benchmark of quality.
Now do you have any links to confirm your loudmouthed dismissal of CM, or does that fall into the same category as urban myths such as "openSUSE isn't real Linux" and "Virus Scanners are useless"?
And by the way: CM = Cyanogen Mod (Custom Firmware); CWM = Clockwork Mod (Custom Recovery).
Not the same by a longshot - and I use TW for recovery anyway.
PS: I found a solution by now in installing an app which prevents the tablet from going into deep sleep mode (-> CPU_WAKE_LOCK). As it seems at times the tablet would come back online after some seconds, *if* I let go of the power button in time. But since I have the tablet hooked up to a power source most of the time anyway, I don't need deep sleep mode, and I was never good at counting seconds when pressing the power button.
That app resolved the "sleep of death" issue for me.
PS#2: As a systems admin I generally refuse advise of the kind of "just reinstall (flash) from scratch and see if it fixes the problem", for that is *not* debugging, its just being too lazy to perform root cause analysis.
Click to expand...
Click to collapse
You may be right but generally in samsung firmwares there are problems with the firmware itself...anyway...if you do find the root cause let me know although when I installed the cyanogen mod 12 this didn't happen I think it was a problem of wake lock in some early builds of rom. Have you experienced this after updating to latest builds?
Osama chohan said:
You may be right but generally in samsung firmwares there are problems with the firmware itself...anyway...if you do find the root cause let me know although when I installed the cyanogen mod 12 this didn't happen I think it was a problem of wake lock in some early builds of rom. Have you experienced this after updating to latest builds?
Click to expand...
Click to collapse
Hi Osama,
the problem startetd after I had installed some software tools for power management and activated CM's own CPU governor.
That is why I suspected this not be a case of a software loop caused by a program or Firmware bug, but a problem with the system waking back up from deep sleep mode.
Now I could have just uninstalled everything and disengaged the CPU governor altogether, but as I wrote earlier on, I don't think highly of such "let's reset it all to zero and see if at fixes things" approaches.
Also, I liked the battery savings options, I just needed a way to prevent the CPU from going all the way down into deep sleep mode.
I found that solution in the form of a small APK on the market place, which does exactly that - and only that.
It prevents the CPU from being turned off (CPU_WAKE_LOCK), whilst still allowing for the screen, bluetooth, WiFi and so on to be turned off, to save battery power.
That fixed my problem almost completely, and now it happens only when the app (I use RedEye) for some reason isn't auto-activated at boot.
Masinissa said:
Hi Osama,
the problem startetd after I had installed some software tools for power management and activated CM's own CPU governor.
That is why I suspected this not be a case of a software loop caused by a program or Firmware bug, but a problem with the system waking back up from deep sleep mode.
Now I could have just uninstalled everything and disengaged the CPU governor altogether, but as I wrote earlier on, I don't think highly of such "let's reset it all to zero and see if at fixes things" approaches.
Also, I liked the battery savings options, I just needed a way to prevent the CPU from going all the way down into deep sleep mode.
I found that solution in the form of a small APK on the market place, which does exactly that - and only that.
It prevents the CPU from being turned off (CPU_WAKE_LOCK), whilst still allowing for the screen, bluetooth, WiFi and so on to be turned off, to save battery power.
That fixed my problem almost completely, and now it happens only when the app (I use RedEye) for some reason isn't auto-activated at boot.
Click to expand...
Click to collapse
I'm glad that you fixed the problem and sorry that i couldn't be of any help.