Develop Bugs

DISCONTINUED - [ROM][02-june-11][patch update] A7Comb (Honeycomb 3.0) v0.2a

The adaption of the newly released VegaComb / honeycomb 3.0 for our tegra2 brothers (advent vega and Adam) and is getting to a state where its usable and the latest alpha4 release for Vega is working quite well on Folio100 as well. with a few modifications of course...
I cannot take full credits for the intensive work done on this honeycomb 3.0 , that is primarily done by NotionInk Adam and Advent Vega developers , which are: MrGuy , newbe5 , corvus , HomerSp I added some kernel changes and image adjustments to support A7.
Download A7Comb 0.2a patch update here
installs like any other "Update.zip", rename the downloaded file to Update.zip
Download A7Comb 0.2 full image update here
installs like any other "Update.zip" (extract the Update.zip from this downloaded zip file) and make sure you "wipe" / factory reset.
Alternate kernel, with original softkeys enabled can be downloaded here
this is also used when you change density setting to 130, so you get the "gingerbread" launcher running instead.
Rename this download to Update.zip and copy directly to sdcard. no unpacking for this is required.
So what is status on a7 port.
- Wifi works, you need to reboot the first you enable it, and it will scan correctly.
- touchscreen seems 100% ok. (did not test multitouch apps)
- Adobe Flashplayer blank (just keep pressing upper left corner like normal to get fullscreen and it works)
- too many apps in the apps list makes them go outside screen.. one solution might be to change density. see build.prop and maybe try 110 instead of the current 120.
You can write whatever status or reported finding, but please check, its not already in the advent/vega issue list, as it share alot with their image.
I will do what is possible to bring it to a better state, but i cannot promise anything and maybe patches from vega/adam might actually work on A7 depending on what they change. (if its a patch)
v0.2a
- Increased 2d/3d performance
- polaris office fixes
- brightness control fix
v0.2 updates
- using newest updates from VegaComb (Gmail and other googleapps now shows correctly)
- Market can now be used for login with an Googleaccount.

reserved for me

I did get bigrushdog to take a look into making us a kernel he is the one who has been working on them for the xoom.

And its online.

Thanks for HC dexter I am testing it now...

Been playing with it for a few hours. touch on the screen is hit or miss at best. Market is a non-starter. Titanium Backup is crashing every other app install. Unable to load Amazon App Store anymore (just stuck in a non-ending registering cycle) But on a good note looks great in landscape, Portrait not so much. Wifi started right up after restart and found my network just fine. Will play a little bit more.

Google Apps working now!!
Ill post the new image later on.. and "Books" now stays (was automatically removed before)

Had to revert back to 1.42, no soft key work. Will wait for new update..
Sent from my A7-040 using Tapatalk

tumpy said:
Had to revert back to 1.42, no soft key work. Will wait for new update..
Click to expand...
Click to collapse
softkeys disabled.. Honeycomb do not use them anymore
Look at the bottom left, thats your control buttons.. thats pretty much what as example "motorola xoom with honeycomb 3.0" looks like now.. so its no error , i disabled those on purpose..
problem is that you got half the screen size of a "certified" tablet, so not much room for pressing buttons and resolutions very low.. so you're missing alot due to the lack of space.. and thats pretty much why A7 is never getting a proper honeycomb when minimum requirements are 1280x800

Soft keys were removed If I had read correctly due to the fact HC has them and dex seen no reason to have two of them. I like the idea of not having them means you don't have to worry about hitting them on accident

http://www.slatedroid.com/topic/179...otloader-froyogingerhc-works-for-notion-roms/
adams kernel was this the basis a source you used to make changes to ours?

rombold said:
http://www.slatedroid.com/topic/179...otloader-froyogingerhc-works-for-notion-roms/
adams kernel was this the basis a source you used to make changes to ours?
Click to expand...
Click to collapse
no, i used StreamTVNetwork's released source from their website..
you cannot use other devices unless you once again try to adapt the drivers to the kernel, which is a big one, since no one did, you can imagine how much work it takes..
you modifiy the existing kernel you got for your device, which the git changes where possible into your existing code, and update where it requiress it.
So we could maybe get the 1.5Ghz update, but im not sure if i can extract and diff it so we can implement into the a7 kernel.

I wasn't meaning did you use that kernel. I guess I could have been a bit clearer. What I meant was seeing how that kernel is adapted to be used with HC could that be off benefit to a dev for our a7. Using it as a guide to some degree

This may be a silly question but...with a dedicated gpu could not the ROM resolution actually be resized to fit the A7? I mean this is not a case of trying to increase resolution (at its native resolution you can't get more than it can reproduce) but down converting it. In other words (This may be a bad example) a standard 720p television that can receive a 1080p signal but down-converts it to 720p.

amwilliams9 said:
This may be a silly question but...with a dedicated gpu could not the ROM resolution actually be resized to fit the A7? I mean this is not a case of trying to increase resolution (at its native resolution .
Click to expand...
Click to collapse
with the next update, im uploading in some hours you can use Market, then download the "Density" app, which can change density (not resoluion) but everything becomes smaller and its harder to hit the soft buttons in lower left side, so you know (as i tried it)

Hi Dexter: Thanks for your work. I m new w A7 and try yet this update but bluetooth not turn on...
wait for you new release. Thanks again.

v0.2 is online
V0.2 is online. Got Googleapps login fixed, so you can use Market and Gmail (Using apps from latest VegaComb)
ming_a said:
Hi Dexter: Thanks for your work. I m new w A7 and try yet this update but bluetooth not turn on...
wait for you new release. thanks again.
Click to expand...
Click to collapse
i can almost say 100% Bluetooth will never work on this rom!
so don't wait for it, then you can start looking for a new tablet with 3.0

Notice the 02 image is much smaller than previous image, about to test this one..I think GB will be out best bet for the A7, I am satisfied with froyo, if HG is out of our reach how about Gingerbread..is it possible Dexter?..
Sent from my A7-040 using Tapatalk

tumpy said:
Notice the 02 image is much smaller than previous image, about to test this one..I think GB will be out best bet for the A7, I am satisfied with froyo, if HG is out of our reach how about Gingerbread..is it possible Dexter?..
Sent from my A7-040 using Tapatalk
Click to expand...
Click to collapse
no, basically a7 is stuck on in 2.2. a 2.3 release still require a formal 2.6.36. kernel which vendors do not adapt drivers for, so if any 2.3 arrive, it will be like this one, using a 2.6.32.9 kernel. maybe with a few patches upto 2.6.32.34 or so, but still using the old drivers vendors delivered..
the guys found out several "libs" of 40MB+ were not needed at all, so i removed them as well..

Weird, Upon first install i recived " Installation aborted" Due to some E:Can't find entry for META-INF/com/google/android/update-binary. Any ideas? Trying install again from fresh download.
Update: No go 2nd time around..... ?

Lowest working screen density

I've moved to the HOX from the HD2 - still prefer the HD2 at the moment (was running pongsters hyperdroid gbx v12 rom). I really liked the low lcd density of 167 and now having the 312 it just feels like I’m using a toy. If I root the phone and change the density what’s the lowest I can get away with - or root a rom which has a low density (any recommendations?)

Pilch2k said:
I've moved to the HOX from the HD2 - still prefer the HD2 at the moment (was running pongsters hyperdroid gbx v12 rom). I really liked the low lcd density of 167 and now having the 312 it just feels like I’m using a toy. If I root the phone and change the density what’s the lowest I can get away with - or root a rom which has a low density (any recommendations?)
Click to expand...
Click to collapse
thats a tough one. i think the density is already perfect for the screen size. i would not even imagine trying to change the density on this bad boy just yet. plus do not forget..you might change it but launchers will look out of place specially Rosie. you might get away with it with Apex launcher or Nova but do not forget about the phone apk as well ie dialler.. you will have to have mdpi apks. so until someone releases a rom that it would be compatible i would say stay away. but then again backup your rom when you root and just try it out for yourself..if it works great..if not just restore and that is it and if you do try go down to 240dpi

[Q] Color profiling with CyanogenMod

It's not a secret that AMOLED screens like the one installed in S4 mini have wider color range than IPS what often results in over-saturated images which were prepared for standard sRGB range.
Stock S4 mini ROM has means to change color profiles. So the question is - if this functionality also included/planned to be included in S4 mini's CM and kernel CM uses for this model? Could profiles be anyhow adjusted?

It's on my to-do list.

Really glad to hear it, Arco! Thanks!
Could you please share a bit about mechanism behind that? Is it really some driver/kernel-space functionality or it is being implemented on higher levels?

metaxaos said:
Really glad to hear it, Arco! Thanks!
Could you please share a bit about mechanism behind that? Is it really some driver/kernel-space functionality or it is being implemented on higher levels?
Click to expand...
Click to collapse
Haven't really looked at it yet, but I think both kernel and user space changes are needed.

arco68 said:
Haven't really looked at it yet, but I think both kernel and user space changes are needed.
Click to expand...
Click to collapse
Hi arco68,
I'm also interested in a solution for the over-saturation problem of the amoled of my S4 mini. Before that I'll keep my stock rom that has the profiles included.
In the meanwhile any progress on that?

S4 Mini oversatured display - solution!
Finally I found something that really works: S4minisettings.apk
http://forum.xda-developers.com/showthread.php?t=2558702&page=11
look for F4k's post
This build is for cm 11 (4.4 kitkat). The only thing is you have to manually put it to system/apps/ folder and then correct the permissions to
rw,r,r (644)
otherwise it doesn't work.
To get really natural colors instead of the oversatured ones you have to set mode to "natural" and temperature to "normal". Sometimes you have to switch the display off and on to get the settings applied.
Great thanks to F4k!

Cool!
Finally i get rid of this unnatural colours,
thanks peter and f4k! :good::good::good:

If you're interested I've developed an App called "ColorModeChanger" to adjust colors and saturation. You cn visit XDA thread at: http://forum.xda-developers.com/showthread.php?t=3154845

resolution/Make writing much smaller

Hey,
I have a small question again.
My wife has the LG P700 and used until recently one of Rome SlimBean.
There it was, that's all been somehow smaller, which had more space on the desktop.
I do not know how to describe it .... on the PC, I would say that the resolution has been changed.
Well anyway, I did like the totally good and I wonder if you can also transfer it somehow to the DHD / apply.
Does anyone know what?

Normally I would say DHD has smaller DPI, but they both have the same screen size and same resolution.
The solution would be to set smaller fonts in setting or change ROM (generally AOSP ROMS (or Sense3.6) have smaller UI elements than Sense4)

Some roms have custom DPI options, if you're finding that your rom is too big/small ParanoidAndroid might be a good bet.

Hey,
Thanks for the replies.
Has anyone had experience with TEXTDROIDER_DPI?
This is probably the one to change.
Currently I have 240 DPI. The app hits me 220 ​​DPI ago. I get displayed I definitely want to make a backup of what I have done.
According app it can happen that you get a Bootloop and then have to change a file.
Now before I try out, I prefer to ask ... maybe someone has done it already experiences.
CyanogenMod version:
20,131,022-4.3-beta6-Ace

changing DPI may look tempting, but in most cases it will mess up graphics by making UI elements look blurry. Moreover, you may have problems with apps compatibility.

Changing resolution on V30B (D855)

Hi guys !
Here is the thing. I used to change the resolution of my G3 (D855 - 16GB) on stock to 1080P, and it was amazing.
Since Marshmallow, there's a few problem if you do that. Let me explain :
I managed to lower the resolution of the rom with ADB to 1080p, everything was right, but the DPI was too big, obviously ! So i lowered it to 540, the limit of LG apps, and everything was fine, but the problem is, it's still too big. It's one of the problems of the G3 that i can't stand. The DPI is too big, even in stock 1440P. I tried different things, to lower the DPI under 540, and here is the results :
1 ) Lower the DPI of the rom under 540 : Force close on LG Apps
2) Lower the DPI of the rom under 540 and use App Settings to put all the LG Apps at 540 DPI, it somehow worked but there was a lot of incompatibilites that were not in Lollipop. That was what i used to do on my Lollipop Rom.
3) Leave the DPI to 540 but change all the daily used apps to a DPI under 540 : It worked too, but the System UI was still too big.
4) Same as 3, but change the DPI of SystemUI under 540 : It worked too, but everytime i call was received, i couldn't answer because of force closes.
So here's my question. Can someone help me to figure how to lower the DPI of SystemUI and getting the phone to still work ? Or share with me another method to do it, ideas that i can try, etc, i'm open to suggestions !
Thanks !

Actually, I used to go through the same steps as you described, on Lollipop. I got everything to work, with 1080p and dpi around 440 I believe. My experience was, that App Settings would pretty much fix any misbehaving app after the dpi change, including the call/message apps. The only thing that continued being weird was the default LG home screen, which still had blank, broken icons and widgets so I had to replace it with Nova Launcher, which worked like a charm. This was about half a year ago, and when I done it on my phone, I repeated the same process on my friend's G3 (same ROM, same process).
My G3 would work fine for a while, but eventually, at some point during the 3rd or 4th system restart, it would always get bricked, stuck on the LG logo while booting. Always had to restore my backup., try again, but to no avail.
My friend's G3, on the other hand worked just fine ever since, which I can't quite wrap my head around, since it's the same phone, with the same ROM and the same procedure.
So I would also like to know if it's possible to create a stable 1080p system with MM now. As to your call problem, does it force close even though you applied the fix to it in App Settings?

I also replaced my launcher by Nova Launcher, on stock or modified, i prefer Nova Launcher, a lot more options to customize it.
I'm actually using a modified 1080P Marhsmallow Rom, but it's not stock, it is on AICP (based on CM13 MM i think), and it is working fine, but it's not stock. The camera is not as good as stock.
I dont know why your phone had this problem though, i never had this on mine.
I'll try again the same steps that i described, on the fulmics marhsmallow rom, that is eventually coming in a few days.
For the phone force close problem, i tried multiple things, and it didn't work with a custom DPI set with app settings on the phone APP. That's why i tried to put the whole system at 540 DPI and my personal apps at 400. And as described in my first post, it worked good, but systemUI was too big.
Maybe i can try differents xposed modules to customize the SystemUI to make it smaller without modidyfing the DPI of the whole app?...

Bump... Is really no one interested by downgrading the resolution of the G3?... You should at least try, it is good for gaming and fluidity.

Lymnoreia said:
Bump... Is really no one interested by downgrading the resolution of the G3?... You should at least try, it is good for gaming and fluidity.
Click to expand...
Click to collapse
If you put "Game optimizer" setting ON, then all games are run in 1080p.
You can find it under "Battery & power saving" option.
Therefore, there is no reason to downscale resolution on Marshmallow

Same here. Just flashed Fulmics 3.1.... Set my DPI to 540 but still find the UI too big unlike when I was on Ti-x lollipop. I browse facebook regularly and the chatheads are way too big for a 540 DPI, heck, it's even smaller when I was on lollipop with the same DPI. It's kinda annoying considering how big the G3's screen is... big UI just waste space. I'm loving the new marshmallow rom but this one is really a nuisance.