[Q] AOKP JB Build Problem with 240 DPI - Samsung Galaxy Nexus

Hey guys, I have been an AOKP user since long. Have been using their Milestone6 until they released Jellybean builds.
Must say I am purely satisfied with these builds but have a small problem with this...Right now I am on JB Build 4.
I am getting tabs in two rows if I change the dpi of my phone to 240 or lower than that. 260 works fine though.
This never used to happen in Milestone 6. I am a 240dpi user and loves to see everything in one screen, but these two row splitting is annoying.
It happens in all the apps based on HOLO UI like Phone, People, Boid(3rd Party), etc.
Attached are the screenshots to explain my problem.
I tried looking into build.prop as well, but didn't find out what's the problem. Before reporting to AOKP guys, I want to ensure if this can be solved and this is seriously a bug or not!
Please help.
P.S: Landscape view doesn't have any problem. The problem persist only in portrait mode. However, Milestone 6 based on ICS never had any of such problems. Also, I know AOKP JB builds are still in their preliminary stage but this problem is a small things which I think need to be reported!

Use 241.
No visible change in applications other than fixes.

Thanks alot
Sent from my Galaxy Nexus using xda app-developers app

Related

Why do you like your ROM?

What rom do you have on your phone?
Why do you like it?
What dont you like about it?
Im curious to see what everyone is running
So far ive ran aokp, paranoid android, and cm10.
Im currently on cm10 and enjoy how professional it is. (explaining the swag button to potent galaxy buyers was kind of tough)
I would have kept paranoid android but the profiles didnt work and i didnt know how to use the dpi changer.
I also started this thread to see who uses android development ROMS instead of the original development ones
Im mainly interested in the non original android development roms users and their oppinions but everyone's answer is appreciated
My favorite was Codename Android, besides one major flaw that myself and very few others experienced: Impossible to send SMS longer than 160 characters, regardless of settings/reflashes/apn/etc. Just because it was the smoothest ROM for me.
I value UI smoothness above all else and have yet to find a ROM that is truly stutter free.
CM10 is ok, but if you go to clock and swipe to the side to go to timer it stutters like a pentium 2 running Crysis: Warhead.
Stock ICS ROM's lag, as well Facebook/third party app scrolling has constant stutter reminiscing of SGS1
JB Leaks (LIF, LIG, LIH) give me blackscreen reboots once in a while, although noticeably smoother than ICS.
I didn't mention battery life as quite frankly I can get a day of usage with every ROM I have tried so far which is nearly all of them.
I think I'm using stock ROM right now as I was fed up and just restored an old nandroid... I guess its ok, everything just works, lots of stutter's though. Doesn't have that premium feel you expect of a device at this price point.
inB4 go buy iphone5
scorpion667 said:
My favorite was Codename Android, besides one major flaw that myself and very few others experienced: Impossible to send SMS longer than 160 characters, regardless of settings/reflashes/apn/etc. Just because it was the smoothest ROM for me.
I value UI smoothness above all else and have yet to find a ROM that is truly stutter free.
CM10 is ok, but if you go to clock and swipe to the side to go to timer it stutters like a pentium 2 running Crysis: Warhead.
Stock ICS ROM's lag, as well Facebook/third party app scrolling has constant stutter reminiscing of SGS1
JB Leaks (LIF, LIG, LIH) give me blackscreen reboots once in a while, although noticeably smoother than ICS.
I didn't mention battery life as quite frankly I can get a day of usage with every ROM I have tried so far which is nearly all of them.
I think I'm using stock ROM right now as I was fed up and just restored an old nandroid... I guess its ok, everything just works, lots of stutter's though. Doesn't have that premium feel you expect of a device at this price point.
inB4 go buy iphone5
Click to expand...
Click to collapse
Run AOKP then, it's extremely fast and smooth.
Longcat14 said:
Run AOKP then, it's extremely fast and smooth.
Click to expand...
Click to collapse
I have tried multiple versions of it, still stutters on homescreen sometimes. Same Timer stutter as CM10 and annoying alarm bug (although there is a fix, it's inconvenient). As well the Nova launcher that AOKP uses, and pretty much all third party launchers have a little input lag due to non native integration or no hardware acceleration (not sure which, but the input lag is there).
Anyway I'll take my fluidity rant somewhere else, people seem happy with the current state of the phone.
scorpion667 said:
I have tried multiple versions of it, still stutters on homescreen sometimes. Same Timer stutter as CM10 and annoying alarm bug (although there is a fix, it's inconvenient). As well the Nova launcher that AOKP uses, and pretty much all third party launchers have a little input lag due to non native integration or no hardware acceleration (not sure which, but the input lag is there).
Anyway I'll take my fluidity rant somewhere else, people seem happy with the current state of the phone.
Click to expand...
Click to collapse
The childishness of aokp turned me off since i looked at the boot logo but my gripes can all be easily fixed /hidden.
I havent noticed the speed difference but i do see tge lag you speak about but ive dismissed it as a hardware being underpowered to the rom issue and dont notice it as much anymore
So im still looking for answers from non original development users but to everyone else
>> What are the Cm10 vs aokp major Differences?
Here is a quick look at some of the differences
http://techie-buzz.com/android/aokp-vs-cm10.html
Sent from my SGH-I747 using xda premium
Blazer Rom.
It's minimalistic, faster than stock without overclocking, great battery right out of the box, and EVERYTHING WORKS. take that jelly bean.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Because its my ROM. There are many like it, but this one is mine.
I'm currently using cm10 and I find very awesome. It's fast and has a lot of great features. I tried AOKP and decided that IMO cm10 was closer to actual 4.1, but AOKP had many more features.
Sent from my SGH-I747 using xda premium
I had been running AOKP for a week or so, I like its customization better than that of other ROMs.
I just yesterday found a new ROM called Paranoid KANGdroid. It pulls from CM10, AOKP, and Paranoid Android. Has pretty much all the features of all three. So much customization, I love it. Not fully stable, though, its only a few days old.

[ROM][23-03-14][Flinny] Vision - Andromadus - CM11.0 [alpha5]

Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Checkout http://andromadus.flinny.org for links/files/changelog's
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.
Current Build Changelog
Build 16
Rom
Should have fixed the zoom problem with browser some were having with large fingers/thumb presses.
Notification LED should be green again.
Disabled sliding picture animation when taking a picture for now.
Saga, rotation issue should be resolved again.
Everything else synced with CM.
Kernel
Patched to 3.0.66
Saga - S2W should be disabled by default on a clean install
Increased PMEM allocation on both SAGA and VISION as we were having out of PMEM issues sometimes when coming out of standby.
MDDI - sorry still need an updated kernel for you.
Checkout http://andromadus.flinny.org for previous changelogs
Looking forward to this
Flinny said:
Files still uploading...
Click to expand...
Click to collapse
Could you please reply back when you've made the files available? Thanks!
rubin110 said:
Could you please reply back when you've made the files available? Thanks!
Click to expand...
Click to collapse
Uploaded
Sent from my Nexus 7 using Tapatalk 2
rubin110 said:
Could you please reply back when you've made the files available? Thanks!
Click to expand...
Click to collapse
http://andromadus.codefi.re/ and sort by 'Date'
Wooo! Trying this
Can I flash directly over 4.1.2 build 129?
or would you recommend a clean wipe : ]
or check the link to the new website on the OP
I would suggest doing a wipe as Gapps etc are all different... if you do try an upgrade then I would suggest backing up... flashing rom/new gapps/wipe cache/dalvik at least.. then most likely finding it didn't work and having to wipe anyway
Nick.
Thx so much. I will try it.
Just tried installing directly over 129, rotation broke so I'm going to try from a full wipe. ( everything else is hunky dory really, although took a quite some time for the phone to calm down and get back to it's usual pace)
By the by, I notice the kill all icon from 129 is gone, is there anyway I can add that myself rather than wait for an update? ( as it's super handy!)
Thanks again flinny and Andromadus folks! My phone is even more woosh woosh and fancy than ever before.
Great job Flinny! You have done quite a lot.
just a question... what is the difference between the cm10.1 and the aosp 4.2? Is cm10.1 the beta release? or are they new test builds based off of cm and not just aosp?
jspina said:
Great job Flinny! You have done quite a lot.
just a question... what is the difference between the cm10.1 and the aosp 4.2? Is cm10.1 the beta release? or are they new test builds based off of cm and not just aosp?
Click to expand...
Click to collapse
ASOP is stock Android, CM10.1 is with Cyanogenmod and Andromadus tweaks. ( I.E more things to mess about with! yay)
Okay got all my apps reinstalled after a fresh wipe and this Rom is daaamn smooth.
All the default apps run without a hitch, and none of my extra apps have caused any issues either ( got 50 installed)
Just needs lock screen short cut tweaks, statusbar/notifcation tray colour/alpha picker and a kill all apps button and this would be puurrfect.
More than happy to use it as is though, runs great.
Pantherx12 said:
ASOP is stock Android, CM10.1 is with Cyanogenmod and Andromadus tweaks. ( I.E more things to mess about with! yay)
Okay got all my apps reinstalled after a fresh wipe and this Rom is daaamn smooth.
All the default apps run without a hitch, and none of my extra apps have caused any issues either ( got 50 installed)
Just needs lock screen short cut tweaks, statusbar/notifcation tray colour/alpha picker and a kill all apps button and this would be puurrfect.
More than happy to use it as is though, runs great.
Click to expand...
Click to collapse
Thanks. I know what the differences between the two are. I was just wondering if thats all that differentiated the two. And after looking at the titles its obvious that they are.
haha took me a few mins to realise this is the new cm 10.1 anyways good work as usual flinny downloading now
Sent from my HTC Vision using xda app-developers app
Am I being stupid or is there no developer menu item under settings? Additionally missing is the glorious Performance menu item too.
Also having some troubles connecting to wifi access points after the initial setup.
Flinny please make name theme more easy. It difficult to distinguish
Sent from my HTC Desire Z using xda app-developers app
rubin110 said:
Am I being stupid or is there no developer menu item under settings? Additionally missing is the glorious Performance menu item too.
Also having some troubles connecting to wifi access points after the initial setup.
Click to expand...
Click to collapse
Its missing in the settings menu for me also. And wifi works but sometimes it doesn't connect, everything else seems to work
Sent from my HTC Vision using xda app-developers app
Go to about phone and tap build number until it tells you that your now a developer....
Sent from my Nexus 7 using Tapatalk 2
Thanks flinny~~
It's so wonderful~
But I can't find the CM's function, like "Performance",
If the CM 10.1 have some function not implement??
Some features have not yet been ported to 10.1 by the CM team yet. But performance and developer are hidden in all 4.2 builds until you do the tap build number thing

[Q] Recommended CM nightly?

Was wondering if there was a recommended Cyanogen nightly in terms of stability, things working etc? Or alternativley are there other roms (other than stock) that are more stable/working? Downloaded last nights nightly but there seem to be quite a few things not functioning...
Sgt7 rom works great
--
Sent from my mind to your screen.
Thanks!
elitelemming said:
Was wondering if there was a recommended Cyanogen nightly in terms of stability, things working etc? Or alternativley are there other roms (other than stock) that are more stable/working? Downloaded last nights nightly but there seem to be quite a few things not functioning...
Click to expand...
Click to collapse
I haven't noticed anything not working, and I've been on the nightlies since they started.
What things ate not working for you?
Sent from my MB860 using Tapatalk 2
chronicfathead said:
What things ate not working for you?
Click to expand...
Click to collapse
I may have spoken too soon, a few issues were just me not being familiar with JB 4.2 and how to set it up, couple of issues I've been having is that formerly full screen games and other apps are no longer hiding the on screen buttons (with the Amazon firmware there was a small pull-out tab to get them), though perhaps there is a configuration switch I am missing for this? Also some video appears to be tearing, though to be fair this might just be the video app... Also CM seems to be ignoring whatever I set the homescreen grid to be.

[Q] How stable and reliable are the Android 4.4 ROMs?

At the moment there is no stable and reliable Android 4.4 ROM yet, but I hope this will soon change.
Perhaps we can compare the different ROMs here. Please note that I am not asking for best performance or lowest RAM requirement. These are secondary issues. The most critical issue is reliability.
The Google ROMs have always been the most stable and reliable. They were never perfect, but at least we could expect them to run for a week or longer without any significant error and without rebooting. In my experience, other ROMs, like the admirable CyanogenMod, came close, but never quite reached that same level of reliability. Given that the CyanogenMod crew works for free and in their free time, the quality they delivered has been astounding and admirable.
Nonetheless, reliability remains the biggest issue among the third-party ROMs.
So, if you install any of the Android 4.4 ROMs on your Galaxy Nexus, please report what you find. Please try to judge whether that ROM can be recommended for general use or whether the newbies had better stand back and wait for the next version.
Another question is: How user-friendly is the install procedure? Can you keep your apps and app data?
It is very unfortunate that the gnex community is not supported anymore due to 'hardware issues' or the 18 month timeframe. It is true that the ROMs made these days are not so 'reliable' and they may be buggy and cause force closes on certain applications. The new roms may never support cleanly and as stable as stock factory images by Google but its all the Gnex community can rely on from now. Personally, I feel the slimkat 4.4 ROM is acceptable considering it is only about less than a week old. They have been fixing bugs such as GPS tracking and such. I will be using it as my daily driver from now and just hope that the developers can make it as stable as the stock android ROM.
Sent from my Galaxy Nexus using xda app-developers app
a taste of kitkat perfect aosp leaked rom
i''ve installed yesterday a taste of kitkat with mpokang 1080p kernel.. some glitches when rotate screen but only one reboot using google now (i don't use gnow so it's not a problem for me) and i've a crash only on fifa14... battery good performance, no lags, no problems, trickstermod overclock to 1.4ghz no problems, facebook, whatsapp, viber, tango, hangout, 3G, Wifi, Bluetooth, GPS alla working without problems.. and now i'm testing battery..
Toro Plus
For us sprint (or Ting) users the 4.4 ROMs are not even installable. There have been two threads started and each one was locked after it became apparent that the developers did not have booting builds. I appreciate all the work devs do, but this keeps getting my hopes up. Hopefully, someone will get one working soon and we won't have any more false starts.
They are just alpha builds, experimental builds. Most of them have some glitches. They are not for daily use.
If you do not have necessary knowledge and do not have time to report bug, then I suggest you should back out on those alpha builds.
They're not even a week old. Give time and reap miracles afterwards
Sent from Samsung Galaxy Nexus @ CM10.2
It's a Nexus device. Things will improve over time.
I've been running the most recent SlimKat alpha build and it's been pretty solid. Phone feels rejuvenated. It is my work phone and worked flawlessly all day. The only restarts were Hangouts last night and when I was fiddling around with wallpaper settings after work, and forgivable graphics glitch during screen rotation. Otherwise, it has has felt like a new-ish phone today.
Thanks for the good information!
I think, when the builds go from alpha to beta and there are no obvious glitches any more, then would be the time to do some more thorough testing, particularly:
GPS, including track recording with My Tracks, Locus, or a similar app
Cameras with all their functions
Compass, gravity, and other sensors
Tethering via USB, Wi-Fi, and Bluetooth
Radio functions, particularly LTE and the general behavior with a weak or frequently interrupted signal
OTG with USB mass storage device, keyboard, etc.
I would recommend to report all defects not only here, but also to the maker of the ROM.
For now, they are pretty unstable, but I would keep an eye out for linaro's builds as well:
http://www.cnx-software.com/2013/11/06/android-4-4-kitkat-on-galaxy-nexus-rom-linaro-and-petition/
idk what you're talking about OP. i've run these custom roms more tha n week and they've been good. only reason the counter will reset is because I flash a new rom or flash an update or a mod.
These ROMs are very stable.
4.4 ROMs. give it some time. it's amazing that in less than 24 hours after the release of 4.4, we got a semi daily usable ROM from people that don't even work for Google.
I've been on SlimKat for a couple hours now. Clearly a ton of the SlimRom features are missing but considering that its an Alpha its not that bad.
Other than some graphical glitches here and there, which are very rare actually, there arent any other instabilities that I can see. Everything works fine. I dont know who is starting this rumor about 4.4 being unstable. Some ROMs may work better than others but thats due to different developers working at different paces. Bottom line is, 4.4 is perfectly fine for a daily driver. It just needs some ironing out.
Yeah, I'm running the SlimKat ROM, and its beautiful
Sent from my Galaxy Nexus running the Forbidden Update using xda app-developers app
Running Shiny 4.4. Good taste of KitKat. Sounds crazy, but I'm using it to test stuff out before it goes on the N5.
Biggest glitch seems to be with graphics, in that overlays of menus and random black boxes over some text in gmail and Chrome, make things unreadable and useless. Not to mention the random reboots when you can tell something happened that the GNex doesn't like.
IMO, they are not ready for use on a primary device. As in, at the end of the day, when I'm home, I pop my simcard out of my MotoX and out it in my GNex/3.4 to tinker. No maps to crash at the wrong time, I have other devices at the low-ready to surf on and more time to tinker. My gf loves me for this routine I've made for myself
Definitely a good taste of KitKat. Considering today would mark 1 week since release, on an unsupported device - its actually pretty stable.
LCD Density
I'm on SlimKat and my old eyes can't deal w/ the tiny text - even when changing default system font to HUGE in the display settings. build.prop has a value of 240 but I can't edit in ES Explorer even though the file props say it's writable. Tried an app but it loops and doesn't make any changes. Any ideas?
xMoment said:
I'm on SlimKat and my old eyes can't deal w/ the tiny text - even when changing default system font to HUGE in the display settings. build.prop has a value of 240 but I can't edit in ES Explorer even though the file props say it's writable. Tried an app but it loops and doesn't make any changes. Any ideas?
Click to expand...
Click to collapse
use rom toolbox, it worked for me
Inviato dal mio Nexus 7 con Tapatalk 4
xMoment said:
I'm on SlimKat and my old eyes can't deal w/ the tiny text - even when changing default system font to HUGE in the display settings. build.prop has a value of 240 but I can't edit in ES Explorer even though the file props say it's writable. Tried an app but it loops and doesn't make any changes. Any ideas?
Click to expand...
Click to collapse
1.Root first using chainfire SuperSU v1.65
2.Install RE(Root Explorer)
3.Hit Mount R/W
4.Open build.prop and change density to 320.:highfive:
Thanks - I was rooted already and made sure root explorer was on. Tried to change permissions in terminal, didn't work. Booted into recovery and mounted system, rebooted and hung at the google logo...so flashed FML and the DPI is 320 so I'm fixed
joytsay said:
1.Root first using chainfire SuperSU v1.65
2.Install RE(Root Explorer)
3.Hit Mount R/W
4.Open build.prop and change density to 320.:highfive:
Click to expand...
Click to collapse

[Q] Unable to change DPI

Hi guys, here's my issue with my Nexus.
It started maybe last night when I updated to the newest stable release of SlimRom 4.4.4 Build 7
After I updated, all seemed fine, but the icons in the global menu, and in my notifications were suddenly enlarged and made out of whack.
I then tried changing my DPI to slightly higher to fix the issue, through Textroider DPI. Now, the app made my DPI way too high, even though I had set it for something like 230 (originally 220)
I tried reverting to my original DPI which was 220, and according to the app, it is currently at 220...even though it isn't. Even in the build.prop it says my DPI is 220, but on the screen there is zero change. re-flashing the rom worked once, but eventually it stopped working. Currently, my screen looks as if it's running a tablet DPI of 300 or so.
Long story short, I am unable to change my DPI, even though in my build.prop it says my DPI is 220.
Is it only happening with that specific ROM?
Send from GN running ParanoidAndroid2.57 Jellybean 4.1.2 w/Tablet Mode
isajoo said:
Is it only happening with that specific ROM?
Send from GN running ParanoidAndroid2.57 Jellybean 4.1.2 w/Tablet Mode
Click to expand...
Click to collapse
I've used SlimRom for heck knows how long since I got my GNex. I have not tried flashing any other ROM, only the previous version of the ROM (4.4.2 Build 5)
The keyboard appears to be completely normal as if it was in 220 dpi, but the the rest of the interface including all the apps believe that it's in a high DPI.
I'm downloading another ROM as we speak and then flashing it to see if it fixes anything.
I hope you can at least get some idea of the problem I'm describing, as I lack the power to post a screenshot

Categories

Resources