Related
So I recently flashed CM7 and I have had some time to download all my apps and get things configured I came up with some questions and had a bit of a boot loop issue.
Ill start with the boot loop issue. A few days ago I noticed while on charge it just kept booting over and over. I have this happen from time to time on my rooted Eris with CM. No biggie I just unplug and things work themselves out. But not with the Nook. I turned it off and powered back on but its just kept booting. Sometimes it would make it to the desktop and then reboot, sometimes it wouldnt make it past the splash screen before rebooting, and sometimes it would make it to the desktop and I get an ADW Launcher error then it reboots. I followed the same procedure I followed when I originally flashed it and its been 3 days now working just fine. This time I only downloaded the apps I really needed and I currently have no SD card in it. The one I used before was the same 8 Gig card I used with Nookie Froyo (Can that card just be formatted within CyanogenMod or do i need to format it on my pc?). So Im thinking maybe that was the problem? But then I found this thread. http://forum.xda-developers.com/showthread.php?t=1043623&highlight=cm7+boot+loop Someone mentions an issue with the battery going dead. That could be it as well because it did die out just before I put it on charge that night. Any thoughts? Like I said I already reflashed just hoping I can avoid that from happening again. Im keeping track of downloaded apps and changes while testing atleast a day before doing more.
Next up is the Notification Bar. Are there any options for changing the color or maybe even the icons themselves like the WiFi, Battery, Notifications Buttons. I like the icons themselves just fine but hate how they are not all one neutral color. I like to change themes but always feel like I need to match up with something green.
So whats the deal with Wallpaper? My Eris has handled every size wallpaper Ive thrown at it. Beautifully if I may add. But the Nook struggles. Ive read some on the subject here and thought I had a decent solution when I was running Nookie Froyo but things are different on CM7. The only way I found to get decent resolution is using the browser to Google search wallpaper and setting wallpaper from within the browser. As you can imagine you dont always get the crop you want. Do I really have to crop every wallpaper specifically for my Nook or is there an easier way?
Overclocking. Boy its been a lifesaver for my Eris but im not sure about the Nook. I was impressed with a score of 1629 at the stock 800Mhz. But I wonder....was that score legit? I ran a bunch of tests back to back and they went something like this 1450, 1527, 1549, 1532, 1596, 1612, then the 1629. With the exception of that one time every test got a better score. Now when overclocked to 925 my best score was 1634 after 6 runs the first was in the 1300 range. I changed the CPU setting within CyanogenMod Settings but I wonder if I need to clear cache first? I was also looking into downloading Dalringrins kernals but can I just add his kernal to the card I used to flash CM7 originally and just flash the kernal? Or do I need to start all over?
Video and streaming video? Whos running a slick video streaming setup over their home network? What are you using and can it be an all in one setup including support for my Nook, Eris, PS3,and various laptops? Ive purchased some harddrives for movie storage but I dont want to rip my DVD collection in some specific format thats only good for one device. Id also like to load some movies and shows right on my SD card for times when I may be away from a connection. What do you guys suggest? My research has turned up many different formats and resolutions. Its been difficult to piece it all together.
I realize this is alot and much of what Im asking may be buried here in these forums but this thread will serve two purposes. To help me organize and speed up the process of getting my setup functioning the way I want. This post also in know way means ive given up on any of this. Im still working on all of it on my own. Researching and testing as time allows.
CyanogenMod-7.0.2
CWM-3.0.0.6
Well, as far as wallpaper goes, the perfect size ratio for wallpaper seems to be 1200 x 1024 at 169 ppi (pixels per inch). Gallery, Quickpic, and other image apps I've used crop to that ratio.
Gallery does some weird quality degradation (or it's resizing it) so my test image looks a smidge less sharp than it does setting wallpaper in Quickpic, for example. It looks absolutely crisp at those dimensions when set with Quickpic or Zeam (when Zeam is default wallpaper agent, it automatically expands crop tool for entire image at this size/ratio).
I've been saving my wallpapers at 1200x1024 (169 ppi). I'm not sure how it would affect your wallpaper if you've used an app like LCDDensity to change the Nook's pixel density from the default (169ppi).
Re: Video streaming
http://www.videolan.org/doc/streaming-howto/en/
You may be more interested in: http://www.videolan.org/doc/streaming-howto/en/ch05.html (Video on Demand and Multiple Streaming via VLM / VLC Player)
Quickpic is exactly what I needed. Works great!
Im gonna start looking into the VideoLan links tonight. Is this something you use? Im familiar with VideoLan but I remember having difficulty with their software before. I think it was when I was trying to stream from a TV tuner in my desktop over WiFi. Probably not the fairest situation to form a judgment.
Since My OP Im 90% sure I got stuck in that boot loop described above because the battery went dead. Mainly because I did it again but this time on purpose. I now have two Nook chargers. I dont think it would have been an issue again but now theres no chance. Anyone have a car charger?
Im also not going to mess around with overclocking for awhile. I realized lately. It runs great whats the point in rushing?
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
They dont't need to support non standard dpi but they should let applications to show up in Market. This is the reason I downgraded the Market version on my phone, but this is not a solution. I hope Google will let the users decide what dpi is best for them.
Yep but as long as they fear claims and complaints nothing may happen...
At the same time the 2 persons I've been dealing with have been very cooperative and asked me lots of questions. Gave them app details, logs and after a few weeks they came back with this conclusion.
Which sort of makes respect them, after all, I'm only one of nearly 200 million Android users!
blackspp said:
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
Click to expand...
Click to collapse
Seen a couple of these pop up so far. The problem has been affecting me for a while now, but I just figured out what caused it last week. Lots of people (myself included) seem to have thought nobody else had this problem.
Post: Changing DPI and new market makes apps incompatibility
Post: [Q] Cannot update multiple installed apps, is it the new market?
blackspp said:
Yep but as long as they fear claims and complaints nothing may happen...
At the same time the 2 persons I've been dealing with have been very cooperative and asked me lots of questions. Gave them app details, logs and after a few weeks they came back with this conclusion.
Which sort of makes respect them, after all, I'm only one of nearly 200 million Android users!
Click to expand...
Click to collapse
I'm almost surprised it took so long for them to notice that trend, considering they surely have facilities to notice trends in their databases. Score one for XDA! (Very cool of Google to provide such tailored support, though!)
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
schizo said:
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
Click to expand...
Click to collapse
To "permanently" change your DPI to "XYZ", add these lines to /data/local.prop:
Code:
ro.sf.lcd_density=XYZ
qemu.sf.lcd_density=XYZ
(Note: If /data/local.prop does not exist, you may create it yourself.)
- OR -
If you would prefer that the change not persist when flashing a new ROM, you could edit /system/build.prop, which should already contain the "ro.sf.lcd_density" property unless you're on a 160dpi device. /system/build.prop will be overwritten any time you flash a new ROM, even if you do not wipe first.
Both of these methods will require a reboot for changes to take effect.
---
Alternately, if you would like to avoid editing system files by hand, there is an app called Blade Buddy which allows you to modify various properties in /data/local.prop, including LCD density.
To save your changes from Blade Buddy, tap Menu -> Save. If you choose not to reboot, you can then tap Menu -> Apply to apply the changes in RAM and restart the UI to see them in action. (Applying density without rebooting seems to be hit-or-miss.)
---
Regardless of how you set your LCD density, the Market will exhibit the incompatibility bug.
As a workaround, I have set my density "permanently" with Blade Buddy and use LCDDensity for Root to revert to default once and a while, so I can launch the Market and get all my updates. LCDDensity for Root is designed specifically to change density temporarily, on-the-fly, and on as many devices as possible.
Thanks, Mr. Bezeek. Actually what I'm looking is the permanent solution of not having to temporarily switch back and forth. As for editing .props I already have experience before with my Streak. Hehehehe
But still, thanks anyway and hope you not offended. I like it the way you help others in precise and detailed manner. Keep it up, bro *thumbs_up*
Not a problem, just doing my bit to make sure the information is out there.
As far as avoiding the temporary switching goes, I'll be on vacation for the next week, but I intend to try a little hacking when I get back, to see if I can find a way to spoof the dpi. That is, if Google doesn't throw us a bone in the meantime.
Users have reported that older versions of the Market still work. The one shipped with the latest OTA for my Evo worked for me, and I suspect that any version released before they changed the Market UI will. YMMV.
Just thought I'd toss this out there... I have a Droid X. When running MIUI 1.8.19 on it, I don't have this problem. I can set my density to 200 and the newest market (3.1.3) still works as expected. Seems as though with all the other ROMs I've tried (both blur and 2nd init), I couldn't access a lot of stuff unless I set density back to 240. I can't remember for sure, but I might have been able to set stock .602 (rooted) to 200 with no problems as well - but I'm a little iffy on that. So it would seem that MIUI has done something (perhaps not intentionally) to work around the problem. I just wish I had the smarts to figure out what that might be.
Edit: I realize that this is not a Droid X forum, but I was thinking this info might help somehow. Thanks.
tslovejoy1969 said:
Just thought I'd toss this out there... I have a Droid X. When running MIUI 1.8.19 on it, I don't have this problem. I can set my density to 200 and the newest market (3.1.3) still works as expected. Seems as though with all the other ROMs I've tried (both blur and 2nd init), I couldn't access a lot of stuff unless I set density back to 240. I can't remember for sure, but I might have been able to set stock .602 (rooted) to 200 with no problems as well - but I'm a little iffy on that. So it would seem that MIUI has done something (perhaps not intentionally) to work around the problem. I just wish I had the smarts to figure out what that might be.
Edit: I realize that this is not a Droid X forum, but I was thinking this info might help somehow. Thanks.
Click to expand...
Click to collapse
Good to know! Being able to compare a "working" ROM to mine will surely make it easier to identify a workaround.
Nice info never noted this before!! yeah i dint get any updates over a last few weeks. Im at 200 dpi.
I've been switching back to 240 periodically to get updates, not a big deal to me, but would be nice if things worked normally. My only real issue with running lower dpi (160 here) is that some apps don't scale properly. IE the Dialer.
blackspp said:
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
Click to expand...
Click to collapse
Thank for this information! I've been wondering why some standard apps weren't compatible.. It's weird, since they work if you side load them ...
I hope google finds a solution.
---------- Post added at 02:59 PM ---------- Previous post was at 02:51 PM ----------
I just switched from 190dpi to 160. Angry birds seasons is now compatible( wasn't with 190dpi)
Dank U vriendelijk
Wow. This has been driving me crazy trying to work out why apps where missing. Guess I need to swap to 240 occasionally for updates.
I am using 200 / 192 DPIs from day one. (3 months). its working fine.I never faced incompatibility issue with market. however some games doesn't run correctly which usually i don't play.
i have a workaround idea, and i started a thread to discuss here: http://forum.xda-developers.com/showthread.php?t=1288150
The google support thread for this is here: http://code.google.com/p/android/issues/detail?id=19744#makechanges
I still have this issue and if you do a web search you'll see that many still do. Reply in the support thread to raise awareness ! or if you have a workaround please share You also might want to check out his Idea thread, if you have some developing skill please help.
schizo said:
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
Click to expand...
Click to collapse
I came from a streak as well and it's this is the biggest annoyance I've had with the sgsii.
The reason why i enjoy Android over any other mobile OS is because i can tailor the OS to how i want it. Not allowing me to download apps because I'm using a non standard density is crippling.
For now, i urge everyone to go to the google support thread and simply press click the star. No need to comment (unless you found a fix), the more stars the issue gets, the more likely Google will look into it.
Seems to be fixed with the latest market version.
Sent from my GT-I9100 using XDA App
Ke11ett said:
Seems to be fixed with the latest market version.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
yeah i seem to be ok ive just got the version from androidpolice last night. im on 3.3.11 now, still cant install stuff from the website though says my phone is incompatible for everything lol
Hi all,
Been on the forums awhile for my HTC EVO 4G, so I know the routine I've searched this forum as well as others but had difficulty finding the answers I was looking for. I purchased an A500 on Friday and was hoping that I had quite the bargain, but was surprised at the problems that the device has had right out of the box with regards to scrolling and touchscreen responsiveness. Here's the breakdown.
Problem: It seems that anytime I need to scroll the interface, whether it's in the Browser (stock, Firefox, Dolphin all had the same problem), in drop-down dialog boxes, or even in Gallery or main home screen, scrolling is inconsistent at best, and at worst, completely unresponsive. However, in the case of Facebook or Browser, when the behavior begins, if I put the tablet to sleep and immediately bring it back up, scrolling works just as I would want/expect it to.
Caveats: There is an app that I have used, called "Fluid Monkey", that is basically just a fluid physics simulator (free on the Market). Similar scrolling gestures does NOT have inconsistent behavior, the screen and interface are very responsive, so to me it implies it's not a hardware issue.
Steps Taken So Far: I've successfully rooted the device, installed Thor's CWM, backed up the stock rom, and installed Icylicious, as it seemed to be one that was very obviously supported by CWM (I didn't want to go too far in modding it should I need to return it for a refund). While it does seem that there is a bit better overall performance, I am still experiencing the same interface issues. I have also tried the three touch sensitivity settings, but haven't noticed a difference. I have also found the following things to try:
Using V6 Supercharger Script (supposedly supports ALL devices);
A particular tweak to framework.jar that requires the use of baksmali
I guess the short of it is, has anyone else experienced this same problem right out of the box? Is there a simple fix for this? I really like the device, but it was the last one in stock (clearance as well), so I don't want to take it back if I can fix it. Any help would be greatly appreciated. Thank you!!
I've had this problem before. The short answer is, it's probably a background process eating up CPU. Best idea to solve it is to do a clean install of your ROM (optimally one with as much as possible crap removed/deactivated, lightspeed is the extreme in that direction -- it is pretty much bare metal, though other custom ROMs are pretty good in that matter also and give a bit more user comfort), then install your apps, one at a time (or restore with TB), run the app, then see if the problem is there.
Another thing you can try is using one of the ICS custom ROMs (they won't screw up your bootloader, the original leak will) and see whether forced HW acceleration can do you any good...
Thanks haag... I had done the clean install of Icylicious (the ICS rom) last night after a full backup/wipe. Even during the first set-up process of setting up the time zone, it took me five minutes to get the drop-down to scroll up to my proper timezone. This was before any extra apps were installed!
Despite my initial assessment, I am starting to feel that the device is unfortunately doomed on the hardware side. I hope there's more suggestions I can try today, otherwise it's going back to the store.
I've seen many people here who are quite savvy with this little device, and I really don't want to return it if I can resolve the issue, but I'm running out of ideas... does anyone have any other ideas I can try, or is it an unfortunate lost cause?
Try Flexreaper R11 you won't be disappointed. Sounds like you are on an older version of ICS that had alot of touchscreen problems. You want to make sure you are on 1.031 or newer version of the leaked ICS roms.
wrathx said:
I've seen many people here who are quite savvy with this little device, and I really don't want to return it if I can resolve the issue, but I'm running out of ideas... does anyone have any other ideas I can try, or is it an unfortunate lost cause?
Click to expand...
Click to collapse
I Would probably advise flashing a 3.2.1 rom, like Honeylicous. I believe he has all the garbage pulled out. This will give you a good base idea if there is a defect with the tab.
In your case, before you go messing around installing any more of the ICS BETA roms, think about it for a minute. Because you'll need to flash bootloaders appropriate to the rom on a couple of them. And this will just be more headache when you discover you indeed have a hardware issue, and have to go back to stock to return it. Remember that the ICS builds, are all Beta.
Try Honeylicous, or any of the 3.2.x roms without a whole lot of mods to them. Make sure you do your wipes and formats properly, then check for the defects. You want to make sure all traces are removed from the previous rom.
There are actually some stock rooted roms available.
I appreciate the suggestions! That was one of the reasons I chose Icylicious, it seemed to have fewer steps and requirements to install and mess with. I may try and backup my current set-up and load up Honeylicious and see if that helps.
Again, thanks all... I hope I don't have to reply further in this thread
wrathx said:
I appreciate the suggestions! That was one of the reasons I chose Icylicious, it seemed to have fewer steps and requirements to install and mess with. I may try and backup my current set-up and load up Honeylicious and see if that helps.
Again, thanks all... I hope I don't have to reply further in this thread
Click to expand...
Click to collapse
No Problem!
Just make sure you follow all the instructions as far as wipes and formats. And... make sure you have a good recovery backup.
Suddenly I am unable to add mi locker wallpapers to favourites, touching the little heart on the lock screen has no effect whatsoever, although it has worked before...
It's a pity, because I really like some of the wallpapers and would love to save them, but somehow my Axon won't let me do this anymore. Multiple mi locker and phone restarts did not fix the problem unfortunately and also I doubt that there is a saving limit of 7 (the ones I saved before the issue) as moving them didn't help either.
I'm fully stock and not rooted (yet) and using the G model (B08, obviously).
Did anyone else encounter the same problem and knows how to fix this, or at least how to save the pictures anyway?
Thanks in advance
It works again, but no idea why. I'm confused ?
If I'm not mistaken only some can be saved, specifically older ones. I never saw an option to save any of the newer ones.
Hi all. Your android solution may be here. I have installed most of the recent android builds available. The below build from konstakang has worked and for me has a good functionality and minimal crashes so far.
http://konstakang.com/devices/rpi3/CM14.1/
I have tried the more recent Oreo 15.1 build but this one has a better display performance. There is a bug with not being able to change the wallpaper but will check with konstakang how to get working.
I tried the build before looking into over clocking but a revisit greatly improved performance and less lag by editing config.txt. Accessed config.txt from a root search via Nautilus after flashing the downloaded image via etcher. Only added
force_turbo=1 #Voids Warranty!
boot_delay=1 #helps to avoid sdcard corruption when force_turbo is enabled.
I didn’t go any further with over clocking as this seems to make the difference. Not seen the CPU temp more than 70c yet. Check out the below link.
https://haydenjames.io/raspberry-pi-3-overclock/
Finally to get things up and running no need for the play store at all so I wouldn’t even bother. It only causes major crashes and Aptoide is sufficient. I have root access from the settings menu and have downloaded quick root reboot. Chrome and Showbox along with mx player. All working. CPUx gives stats such as core temp. Will be able to get terminal access also from app download. The media apps do seem to shutdown occasionally but i hope a wifi dongle upgrade add-on will sort this out.
http://en.aptoide.com
Hope this helps someone and let me know if have the same or different luck. Big up to the developers and website authors!
I tried the 8-10-17 build, and I could any apps I installed would crash immediately. I could not get the resolution to fit my TV screen either after changing resolutions in the boot config. Have you ran into any issues like this?
I had problems with older builds from the same source and others. Even paid for one from Exton but he's a rip off merchant. Try this one that I had in the op.
http://konstakang.com/devices/rpi3/CM14.1/
Read the FAQ about root access and download quick reboot from Aptoide.
As I said it works reasonably well. Try the over clocking and apps from Aptoide. Also reboot a couple times I've read makes a difference with things crashing. If you find an app continuously crashes then uninstall and try different one.
My TV displays fine. 49inch 4k. I guess if yours doesn't from first boot then could Google for the correct config.txt script. This newer build seems to detect the TV resolution but don't quote me on that.
I wouldn't go for the newer konstakang Oreo build as was laggy but of course give it a go if you like. Konstakang builds seem to be the best on the net so far and I've tried loads since the new year. See what the next one is like as well as he's pretty up on current development.
is this a stretch img?
Not sure what you mean by stretch?
I'm guessing this is also for the RPi 3B+?
This was done on the pi3b. I don't know if it's works on the newest model.
Stops bootlogo n shuts down
First boots situation
Flashed with etcher