Hello everyone,
First of all, I hope this is the right corner and I've collected enough information - I couldn't find anything closely related to my issue.
Now, I've got the first big problem:
Regarding the support of Tablet devices, some apps just don't offer any possibilty to install them. Now, to avoid this problem, I've changed the LCD density to 240dpi.
The Prime is still able to boot normally and everything is working just fine - except for the Launcher: It crashes every 2 seconds and the buttons on the bottom of the screen are cut away just like the one for the app menu in the upper right section so that I've only reached the settings by some tricks so far.
So far, I own my Prime for roughly 1 1/2 months, my Prime is rooted, NOT unlocked and has the most up-to-date firmware installed on it.
Up to now, I tried to factory reset via settings and wipe data with Volume Down + Power button combo.
Apart from that, I think I heard that the dpi settings are to be found in the build.prop file.
Sorry for letting you read this much, but I think this reduces the overall time to spend on it.
I hope that it's possible to get it back working. I miss the Prime experience
Thanks in advance for any help!
Solved!
So, after some hours, I managed to get the Prime back to life by myself:
The build.prop file was the key to success; With some actions in the ADB-Interface and permission changes, it's possible to revert a bad dpi value to default via USB debugging.
If anyone's further interested, I'll try my best to explain how exactly it's working.
Related
Hi guys,
I finally installed Windows 7 bootcamp on my Mac, and went away on flashing kernel to XWKDD_insecure.tar, and rooting the S2 with S2 Root app. Everything went smoothly, and I now have TB Pro with a couple of apps frozen.
However, one very noticeable change after I flash and rooted was that my Applications button is very hard to activate. I thought I had imagined it, but when I unlock via Widgetlocker slider, and tap the Applications icon on the bottom right, nothing happens with the normal pressure I am used it. To activate it, I must push down with a little force for a second or two, let go, and it will go to the application folder. Also, I have also notice that when I wake the phone, the unlock widgetlocker slider is slightly unresponsive at first, I must also apply more force, hold it for a second, and slide for the slider to work. Before I rooted (6 hours ago), I can lightly tap the application icon, or light slide the unlock slider, and it would work.
Another weird thing is also buttons on the screen works fine thus far.
Anyone have this rather weird problem? I am slightly regretting rooting the phone, because the applications icon just wouldn't budge despite multiple taps... I've tried battery pulls, etc, but the problem persists, especially right after I unlock the phone.
Any input is much appreciated!
Thank you
Did you found a solution? I have the same problem, but I don't know if it's because rooting? This is really annoying.
Same here after CF-root.
and let me add that the return touch key (below the applications icon) isn't so responsive as before rooting!
I thought I was just imagining but I am "glad" you guys having the same problem.
Looking forward for a solution.
Maybe asking Chainfire ?
Well I just installed a stock rom, same thing.
My 'back' button is very un-responsive as well. it's like I really have to hit the spot for it to react.
Am having the same issue with the back key and i am still stock non rooted
cruzantis said:
Am having the same issue with the back key and i am still stock non rooted
Click to expand...
Click to collapse
Non rooted you say, interesting...
I thought it is because I rooted it.
gil80 said:
My 'back' button is very un-responsive as well. it's like I really have to hit the spot for it to react.
Click to expand...
Click to collapse
cruzantis said:
Am having the same issue with the back key and i am still stock non rooted
Click to expand...
Click to collapse
This is certainly not the first time I've heard about such complaints, infact a few friends also had this issue as well they had their phones replaced.
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
wizardknight said:
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
Click to expand...
Click to collapse
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
arrrghhh said:
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
Click to expand...
Click to collapse
arrrghhh, I noted your post in the ROM development thread regarding the start up sequence in the OMGB kernel for the AUO panel. Perhaps this would solve my issue as well. If this change could be added to the next edition of this ROM my device would be virtually bug free.
As noted in the thread, we do not have any RHOD100s to test with. It is very unlikely that this will happen. If you would like to make your own kernel with these changes I can post it.
issue or not?
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
paolora999 said:
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
Click to expand...
Click to collapse
try using AItype Keyboard Plus which supports multiple languages and keyboard layouts
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
paolora999 said:
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
Click to expand...
Click to collapse
startup.txt files are only for the SD card versions of the android roms.
You would need to edit the keyboard map. Here is generic android keyboard map info.
There may be apps out there than can change your keyboard map, but I don't know any details about that.
Also in the future it would be best to start your own thread, rather than using an unrelated one. Better yet, post the questions about the rom you are working with in the thread for that rom.
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
MTN_Cool said:
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
Click to expand...
Click to collapse
Did you read the link that covered screen calibration listed under related goodies, or did you search for the threads that cover screen calibration under android? Tell us what you have tried, but didn't work.
No idea what you mean by the ram is not 100.
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
arrrghhh said:
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
Click to expand...
Click to collapse
idc if they will move my question the the original one...
but i can't fix my calebration points...every time i need to launch the HTC program :\
Problem resolved?
akk29 said:
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Click to expand...
Click to collapse
In an attempt to bring this thread back on topic I thought I'd report back that the original problem has not happened for a few weeks. My setup is essentially unchanged, the only change is that I have been using One Power Guard to try and improve battery life, which by the way seems to be effective. Managed 13hours with light use (few calls/occassional data for email web browsing)
Anyway it could be coincidence but it is possible that one of the tweaks performed by the app has sorted this issue. Since nobody else has reported the same problem I'm not sure how useful this info is but hopefully it may be of use to someone.
...yes I STILL use the Lapdock
Anyway, after I remove my phone from the Lapdock it freezes and goes crazy for a few seconds as usual, but this time as well as others it seems to have left the wallpaper in a landscape orientation, even when I turn my phone upright for protrait orientation.
Have a look:
http://i.imgur.com/nbCcBtA.png
http://i.imgur.com/RjZsXsk.png
What is especially wierd is what you see on the second .png when I try to change the wallpaper to see if that does anything, the selector square has turned into a rectangle as if the phone was still on landscape. The icons, widgets and all else do rotate, just not the wallpaper. I am left with no other options as the settings for wallpaper on stock 2.3.6 leaves me only the option to change the backgroind image and it seems that I am the only one on the interwebs that is posting this issue.
The ROM and kernel is stock, I am using ADW Launcher but I am certain that that is not the culprit, I removed it but the problem persisted. I am also using Ubuntop 1.1 something or other but I doubt that is a culprit either.
Any ideas? Thanks so much in advance.
mynameisj said:
...yes I STILL use the Lapdock
Anyway, after I remove my phone from the Lapdock it freezes and goes crazy for a few seconds as usual, but this time as well as others it seems to have left the wallpaper in a landscape orientation, even when I turn my phone upright for protrait orientation.
Have a look:
http://i.imgur.com/nbCcBtA.png
http://i.imgur.com/RjZsXsk.png
What is especially wierd is what you see on the second .png when I try to change the wallpaper to see if that does anything, the selector square has turned into a rectangle as if the phone was still on landscape. The icons, widgets and all else do rotate, just not the wallpaper. I am left with no other options as the settings for wallpaper on stock 2.3.6 leaves me only the option to change the backgroind image and it seems that I am the only one on the interwebs that is posting this issue.
The ROM and kernel is stock, I am using ADW Launcher but I am certain that that is not the culprit, I removed it but the problem persisted. I am also using Ubuntop 1.1 something or other but I doubt that is a culprit either.
Any ideas? Thanks so much in advance.
Click to expand...
Click to collapse
What happens after a battery pull?
Are you able to access recovery with the stock rom? just thinking about a dalvik wipe or a data wipe/factory reset? (maybe some bits of software not acting properly and a reset might help)
I don't have any experience with the Lapdock but maybe it is a software glitch?
barry_ said:
What happens after a battery pull?
Are you able to access recovery with the stock rom? just thinking about a dalvik wipe or a data wipe/factory reset? (maybe some bits of software not acting properly and a reset might help)
I don't have any experience with the Lapdock but maybe it is a software glitch?
Click to expand...
Click to collapse
The problem persists after a battery pull and re-insertion. Since it wasn't the VERY first thing I did, recovering the img of the current rom didn't work as the problem occurred BEFORE I saved a backup, although the problem DOES go away when do a from-scratch recovery using a fruitcake system/kernel/webtop img.
So would wiping the Dalvik cache not mess up my setup or anything? I may consider doing that as I'm not looking forward to doing a clean wipe every time this problem happens, and it happens VERY easily.
Thanks
Wiping Dalvik won't change any settings or cause any problems and it might help.
I am still thinking that your problem is a software glitch - one workaround might be to fix the wallpaper in the 'horizontal' position by unticking the 'auto-rotate' setting (not sure if this would effect your lapdock experience though )
One last workaround would be to reinstall your Rom without a data wipe (so all your settings/apps are still there) and see if that helps.
barry_ said:
Wiping Dalvik won't change any settings or cause any problems and it might help.
I am still thinking that your problem is a software glitch - one workaround might be to fix the wallpaper in the 'horizontal' position by unticking the 'auto-rotate' setting (not sure if this would effect your lapdock experience though )
One last workaround would be to reinstall your Rom without a data wipe (so all your settings/apps are still there) and see if that helps.
Click to expand...
Click to collapse
Dalvik cache is wiped and the wallpaper orientation option was ticked and un ticked but the problem STILL remains. I suppose my next step is to re-flash the ROM, but I'm hoping that doing so won't wipe and restore webtop to stock (it's on Ubuntop instead).
Here's another kicker! I don't have this problem on LIVE wallpapers, orientation works just fine there, only on static wallpapers am I seeing this issue.
Anyway, I've looked into debugging the display on the native OS to try to a fix together, I'll see how that goes...
How do other apps behave? Also stuck on landscape or not?
I'm thinking it could be a launcher issue after all if that's the only place where this is happening.
ravilov said:
How do other apps behave? Also stuck on landscape or not?
I'm thinking it could be a launcher issue after all if that's the only place where this is happening.
Click to expand...
Click to collapse
Thanks for the feedback,
The behavior of the other apps are good, no issue with them whatsoever.
I have already uninstalled ADW launcher and stayed stock for a few hours and that didn't resolve the issue. I shall do it agin but this time reman in stock for longer.
I got the launcher BECAUSE the stock home screen doesn't rotate and I prefer to mount my phone sideways in my car. What is baffling is that it DOES go to landscape orientation when I plug the phone onto the Lapdock. Weird.
I was wondering if anybody else had this problem but the more I search the more I find that I may be the only one with the isssue, thus I'm thinking it can be due to my personal phone setup rather than a glitch. If I DO find a fix, I'll put it up nonetheless...
I have the exact same issue with Atrix 4G and ADW launcher
I have the exact issue you described and I did the same but ni good results so far. The only difference is that i was using the multimedia dock instead of the laptop dock (which I was thinking to buy). I just got the phone yesterday and the dock today and when testing for the 1st time i got the wallpaper wrongly oriented.. any help?
I installed after that the wallpaper wizardii app to see if it could fix it but no luck..
Thanks a lot.
Elomx said:
I have the exact issue you described and I did the same but ni good results so far. The only difference is that i was using the multimedia dock instead of the laptop dock (which I was thinking to buy). I just got the phone yesterday and the dock today and when testing for the 1st time i got the wallpaper wrongly oriented.. any help?
I installed after that the wallpaper wizardii app to see if it could fix it but no luck..
Thanks a lot.
Click to expand...
Click to collapse
Buggy wallpaper configuration. Try this, it might help.
- Install GO Launcher EX and set your wallpaper.
- Every time after undock the phone, press menu > wallpaper > press lock and and unlock for few times.
It work for me.
Just to chip in that I had the same (or very similar) problem: Nottachtrix ROM, ADW Launcher, multimedia dock. Swapping out the launcher to GO Launcher EX per AeroMiku's suggestion has worked for me ... for the moment!
OK so I got my Z4 tablet three days ago. Fantastic construction, fantastic specs on paper.
I had a Z tablet up until last weekend that I sold for a good price and got this as a much needed replacement.
Both are LTE versions.
Anyway, here are some things I've noticed and I would like to have your comments on.
1) The "antitheft" system for the first two days seemed to be a PITA. As my device is set for three users (me, my wife, my son), it kept popping for the others that it locked and needed MY credentials to unlock. I did unlock it at least five times for each, which means I can't really be... far from the device and let them use it. That I use two step authentication, makes things even harder. Once my "authenticator" phone was out of power and I had to wait several minutes to unlock the tablet. Yesterday I updated to latest firmware and I haven't noticed the issue since. But it's just one day, it may come back. Once (before updating firmware) I tried to disable My Xperia (although I love the find my device feature) so they could work, but it kept me "waiting". In the end I pressed back and it didn't get disabled. Any similar experiences with the theft protection?
2) Backlight (set in auto) seems to be too dark some times. I clicked on the intensity bar, set it brighter while STILL in auto (like it is now set to have a brighter "base value"?). Does this sound normal?
3) This is not a Z4 issue, I also had this in Z. It's probably a lollipop thing or I don't understand something properly. Clicking the volume buttons I can set it to "no" sound from home screen. Or so I think. Because even if I set it to "off", apps STILL have sound and I have to RE-adjust the volume to off from within the app (without the "priority buttons" under the volume bar)... Am I the only one to find this stupid?
4) Anybody notices some lag or ESPECIALLY stuck web browser, when other profiles (users) have run apps? If I reset the device and not visit the other profiles, the device is more snappy. If some other user goes in, even quiting every app they run, the device seems to get slower when back in "owner" user. Still fast but not as "snappy". Anybody noticed the same?
5) Any idea when we get Android M? Will we get 5.1 before that? I mean official firmware. Anybody?
6) Is there a way to go to test menu? The tablet Z method doesn't seem to work.
7) Serious. No restricted profiles. Why? Sony support replied that lollipop has this disabled only on 3G/LTE devices (that makes no sense), yet my Z was also LTE and both are on lollipop 5.0.2 and it DID have restricted profiles. What's up with that?
Thank you for your time people, have fun.
...wow
2) Yes.. brightness is usually set a little low at first for battery purposes.
3) There are different volumes for different things. Using the volume rocker on the home screen and putting it all the way down will only adjust ringer/notification volume. In-app sounds will use the media volume which you will need to adjust while media sounds are playing or you can adjust it in your sound settings. Not stupid imo, just gives more flexibility.
5) It'll come when it comes.. nobody knows except google and sony. I'd like to hope we'd get 5.1 before 6.
(pending something on the other questions above)
2) So the set value, when brightness is in "auto" is like a base value?
3) Well I find it stupid. Why: Because when I am in home screen I used to be able to manage the universal audio settings of the device. Turning device to mute, would turn it to mute. As simple as that. Also clicking a simple icon next to volume bar, you could separately adjust notification and ringer and stuff like that. Now? You THINK you set your device to mute, but you have only set the notifications. You sleep in a silent house (next to the wife or something), start a game, it YELLS with the last volume settings, ignoring that you set the device to mute in home screen and you have to "run" and re-adjust the volume to zero, usually with some delay (in the meantime waking everybody) since the device won't let you adjust anything while loading the game. No, I call this stupid.
5) Well if it won't delay 6, I don't mind for 5.1. But I want 6 the soonest possible.
Hi guys,
I just flashed android 10 on my oneplus 3 via Havoc v3.4.
I was wondering, whether somebody were able to help me with a kind of special problem.
So I'm using my home button to put the phone to sleep by long pressing it. This can be set in the phone settings. so far so good.
But now on android 10 the duration of said long press seems to be unnecessarily long, like over a second. Thats really annoying, when you just want to put your phone away and have to keep your finger on that capacity button for that extra amount of time.
So I was wondering, whether there might be a relatively simple way of tweaking the build.prop or something, to change the duration of said time_out ?
I already tried the hold/delay in the google settings, but that's just for touch inputs on the screen.
Also the forum search didn't pop up any usefull results.
Thanks so far!