Related
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..... ?
Has anyone figured out yet why some devices auto-update the market to version 3 and some don't?
I guess it depends on the rom you are using, but what exactly makes the difference that some devices just don't update themselfes? I am using Oxygen, and my device does NOT update itself, though i have market-updater.apk.
Don't get me wrong i hate the new market, I was just wondering.
I am also using Oxygen, but mine updated to 3.1.5. So it should not be ROM based.
smhtc said:
I am also using Oxygen, but mine updated to 3.1.5. So it should not be ROM based.
Click to expand...
Click to collapse
This is getting more and more mysterious... Now what is it that stops my desire from updating?
Dunno. google say if your device doesnt update, open the market then press home (to leave it running) and it *should* update
I'm running stock Froyo and was glad that it hadn't updated based on everyones feedback however over the weekend I was out and didn't connect to a wifi network for a couple of days and all of a sudden the market app updated itself to 3.1.5 !!
I'm actually not that disappointed as whereas there are noticeable differences in speed / load times it isn't that bad.
It's a mistery to me, too... with a lot of sense roms, no way to get the update.. as soon as i installed the latest cm7 nightly it updated instantly!
btw I preferred the old 2.3.x, much faster than the 3.1.5, expecially with low connection networks..
RyoSaeba254 said:
It's a mistery to me, too... with a lot of sense roms, no way to get the update.. as soon as i installed the latest cm7 nightly it updated instantly!
btw I preferred the old 2.3.x, much faster than the 3.1.5, expecially with low connection networks..
Click to expand...
Click to collapse
It seems totally random... A buddy's completely stock wildfire did autoupdate to 3.1.5. Now he has installed cyanogenmod and market won't autoupdate anymore. Basically the opposite of what happened to you.
Btw I hate the new market too, it is awfully slow, not useable under EDGE, and it has huge bug for cached items.
It's not random. Build.prop decides it
TouchPal-d from my Desire running Supernova Extreme Rom - 450 apps and counting. .
Now, after I updated to oxygen 2.3.1, my market also auto update itself
Droidzone said:
It's not random. Build.prop decides it
Click to expand...
Click to collapse
Can you be more precise? Is there a way I can change something in rom's build.prop so I have rom which absolutely cannot update market by itself?
I have the Acer A100 running 2.007.04_EMEA_GB, has anyone had this auto update yet? or is there any word when we will get the ICS update here in the UK?
also if I were to flash one of the ICS roms or the 3.2GEN1 rom, would I need to root the Tablet first? or is it just put the update.zip on the external SD and boot into recovery?
Cheers
aj79 said:
I have the Acer A100 running 2.007.04_EMEA_GB, has anyone had this auto update yet? or is there any word when we will get the ICS update here in the UK?
also if I were to flash one of the ICS roms or the 3.2GEN1 rom, would I need to root the Tablet first? or is it just put the update.zip on the external SD and boot into recovery?
Cheers
Click to expand...
Click to collapse
I got the OTA update to my 2.007.04_EMEA_GB this morning here in Quebec (07/05). I was concerned because all the comments seemed to be about GEN1 or 2, but decided to just be patient. Nothing had led me to believe that Acer wouldn`t provide an update despite some of the hysteria that was being whipped up in some threads over on acertabletforums. The Acer website stated the roll out would take a week or so and previous experience with phone updates has taught me you can wait up to a month for these things to happen.
I was reluctant to use the full ROM provided by Zeronull as I didn`t want to change my tablet version to a GEN1 as I still have 9 months of warranty (which would have been invalidated). Until Acer release the source so the modders can bring significant changes in performance/functionality, I`ve avoided the temptation to install CWM.
The update came in two parts the same as for the GEN1/2. The first brought Honeycomb up to date and the second was ICS. It is perhaps worth noting that update only appeared when I checked manually rather than waiting for an auto check.
I don`t have my tablet to hand at the moment to give you the full ROM version, but I recall it ended in a 15. Crucially though, it is still an EMEA_GB version of the ROM with all the language packs included.
Performance is MUCH improved, with boot up time now at 50sec where previously it took 1min20.
Zen Pinball scrolls super smoothly in the close up view now whereas it lagged in HC.
Both cameras seem to register colour better than before as experienced on Skype this morning (though they are still very mediocre). Anecdotally, audio seemed a bit louder too with me not needing the volume at max the hear the caller. This however could just be the individual circumstances of the call and I will test more later.
Browsing is faster with pages like Eurogamer and Engadget loading quicker and not "tiling" when scrolling down fast. Also, the ability to customize the font size makes reading web pages for extended periods much more comfortable.
Apologies for being a bit long winded; I hope my response was helpful.
Hello,
My phone is currently on Stock i927UCLJ3 with root, wifi teher and keyboard light fixes added.
The issue is that AGPS is not functional, location detection takes very long, every GPS start is like a cold start.
I have tried several times to sniff any network communication during GPS start, but only NTP packets, no requests to xtragps or google.
See attached image for my /system/etc/gps.conf file listing.
Is there any way to get it working with my current firmware?
I wonder if anybody has the same issues.
the problem is that you're on stock samsung rom, and not on AOSP. to tell you the truth, you wont get a fast gps lock until you flash a new rom, but it's worth it! for example cyanogenmod 10 is waaay faster in every details. gps, boot time, scrolling smoothness, etc. you really should flash it.
soadzoor said:
the problem is that you're on stock samsung rom, and not on AOSP. to tell you the truth, you wont get a fast gps lock until you flash a new rom, but it's worth it! for example cyanogenmod 10 is waaay faster in every details. gps, boot time, scrolling smoothness, etc. you really should flash it.
Click to expand...
Click to collapse
Anything not reliable on cyanogenmod 10 ?
Bluetooth is mentioned in the Dev forum.
Can the /etc/gps.conf and sirfgps.conf from cyanogenmod 10 be used on stock, or that wont work ?
Maruzko said:
Anything not reliable on cyanogenmod 10 ?
Bluetooth is mentioned in the Dev forum.
Can the /etc/gps.conf and sirfgps.conf from cyanogenmod 10 be used on stock, or that wont work ?
Click to expand...
Click to collapse
you can use the gps.conf from cm10, but I think it's not related to the problem,because it contains the same as on stock. The source of the gps issue is much deeper I think.
There are a few things that don't work on cm10. On skype, or viber (any similar progs) sound gets slow and it's not understandable. Also "face unlock" feature doesn't work, but who uses it anyway? With the keyboard and kbbacklight fix, it has no other issues I think.
cm10.1 is a different story, it has all the issues as cm10 has , plus keyboard backlight is not so good (it's related to the capacitive keys' lights, therefore it lights also when keyboard is closed. not so battery-friendly, but some fellows are already working on it). WiFi tethering also doesn't work, and correct me if I'm wrong,but I think there are some problems with bluetooth as well.
Long story short I (would) use cm10 with the related fixes (keyboard stuffs). I use the original version of dman's, because it contains the original kernel and I hated the "deep sleep bug" on thegreatergood's kernel, but I think it's already fixed (not uploaded though).
mr.Scamp said:
Hello,
My phone is currently on Stock i927UCLJ3 with root, wifi teher and keyboard light fixes added.
The issue is that AGPS is not functional, location detection takes very long, every GPS start is like a cold start.
I have tried several times to sniff any network communication during GPS start, but only NTP packets, no requests to xtragps or google.
See attached image for my /system/etc/gps.conf file listing.
Is there any way to get it working with my current firmware?
I wonder if anybody has the same issues.
Click to expand...
Click to collapse
Searching you will find many have this issue, not just on the Captive Glide but those also on ICS.
Have a look at this link: http://forum.xda-developers.com/showthread.php?p=24763092
This thread may help too: http://forum.xda-developers.com/showthread.php?t=2029120
I personally have fiddled with gps.conf and sirfgps.conf to try and get a faster lock, in particular from cold boot.
For me:
gps.conf = nothing seems to effect first lock time.
sirfgps.conf = some changes bring the first cold boot lock time from 4 mins down to 1 min (no amount of changes has ever brought the cold boot lock fix to faster than 1 min, if anything it made it longer the more changes I made), after the initial lock, it locks in 15 secs.
** Correction, if the GPS has not been used for more than a day, its goes back to taking 1 min to lock. **
My current gps.conf is default, I even left the NTP server to Canada, even though I'm in Australia, since it made no difference.
I've got no AGPS reference in there either, as again didnt seem to make a difference.
These are the changes I currently have in sirfgps.conf. They are slightly different to melvatron's in the other thread I've mentioned, as it seems that different options are better for some and not others.
SIRFGPS.conf (truncated, changed options only)
###
EXTERNAL_LNA=0
FREQUENCY_AIDING=1
SENSOR_AIDING=1
SSL_ENABLED=0
ATT_NETWORK_OPERATOR=0
ICS_NETWORK_OPERATOR=1
###
Maruzko said:
Searching you will find many have this issue, not just on the Captive Glide but those also on ICS.
Have a look at this link: http://forum.xda-developers.com/showthread.php?p=24763092
This thread may help too: http://forum.xda-developers.com/showthread.php?t=2029120
I personally have fiddled with gps.conf and sirfgps.conf to try and get a faster lock, in particular from cold boot.
Click to expand...
Click to collapse
Thank you for the links,
they helped me much.
I have tweaked my gps.conf and sirfgps.conf using the fixed files as examples.
Seems, it works for me, fix is much faster now.
I wonder why the default values are almost unusable in 4.0 Official ROM.
mr.Scamp said:
Thank you for the links,
they helped me much.
I have tweaked my gps.conf and sirfgps.conf using the fixed files as examples.
Seems, it works for me, fix is much faster now.
I wonder why the default values are almost unusable in 4.0 Official ROM.
Click to expand...
Click to collapse
Can u tell me what settings you have changed in both files that have helped the most ?
Sent from my SGH-I927 using xda app-developers app
Maruzko said:
Can u tell me what settings you have changed in both files that have helped the most ?
Click to expand...
Click to collapse
My current files:
Code:
# diff -urw /sdcard/sirfgps.conf /system/etc/si>
--- /sdcard/sirfgps.conf
+++ /system/etc/sirfgps.conf
@@ -23,16 +22,16 @@
EXTERNAL_LNA=1
REF_CLOCK_26MHZ=1
UART_BAUD_RATE=0
-FREQUENCY_AIDING=0
-SENSOR_AIDING=0
+FREQUENCY_AIDING=1
+SENSOR_AIDING=1
SET_ID_IMSI=1
DEBUGGING_FILES=0
-SSL_ENABLED=1
+SSL_ENABLED=0
CERTI_VERSION=0
CP_RESPONSETIME=2
CONTROL_PLANE=1
ATT_NETWORK_OPERATOR=0
-ICS_NETWORK_OPERATOR=0
+ICS_NETWORK_OPERATOR=1
SGEE=0
EMC_ENABLE=1
LOG_PATH=/data
gps.conf differences attached as image, because of URL posting restrictions
Those tweaks did not work for me.
GPS fix was fast not because of new configs, but because of cache.
When I tried to use GPS some days later, time to fix was around 2 minutes.
Did you try FasterGPS from the market + reboot?
sbiricuda said:
Did you try FasterGPS from the market + reboot?
Click to expand...
Click to collapse
Tried, with no effect.
http://forum.xda-developers.com/showthread.php?t=2029120&page=2
10 days later gps locks in 17 seconds... ics4.0.4 uclj3
GPS works great on CyanogenMOD 10.1, so I suppose it was a firmware issue.
Some stats:
stock 2.3.5 - GPS ok
stock 4.0.4 - GPS very slow, looks like receiver sensivity is too low
cyan 4.2.2 - GPS ok
Hi,
I really like to upgrade my N7100 to KitKat, but with every KK-ROM I've tried I wether had camera- and/or bluetooth-issues.
Sometime the camera takes some photos and then freezes, sometime I can make one call via bluetooth and the dialer freezes while making the second call.
Only a reboot solves these problems (or my "Restart Camera"-app) - but with this problems I really don't want to use KK-ROMs.
Does anybody has a recommendation for a KK-ROM, maybe in combination with a custom kernel?
I would really appreciate any help!
Best regards
cool400
cool400 said:
Hi,
I really like to upgrade my N7100 to KitKat, but with every KK-ROM I've tried I wether had camera- and/or bluetooth-issues.
Sometime the camera takes some photos and then freezes, sometime I can make one call via bluetooth and the dialer freezes while making the second call.
Only a reboot solves these problems (or my "Restart Camera"-app) - but with this problems I really don't want to use KK-ROMs.
Does anybody has a recommendation for a KK-ROM, maybe in combination with a custom kernel?
I would really appreciate any help!
Best regards
cool400
Click to expand...
Click to collapse
The same issues here. I really don't understand this can't be fixed.
Dr.Ketan’s Rom For Galaxy Note 2 (International) N7100ZCUEML2 KitKat
According to me there are lots of good ROM for N7100
You can search on google
Dr.Ketan’s Rom For Galaxy Note 2 (International) N7100ZCUEML2 KitKat
Shiny Rom For Galaxy Note 2 (International) N7100ZCUEML2 KitKat
SLIM Rom For Galaxy Note 2 LTE (International) N7105XXDMF2 CM 10.2
Regards
M Haroon aejaz
cool400 said:
Hi,
I really like to upgrade my N7100 to KitKat, but with every KK-ROM I've tried I wether had camera- and/or bluetooth-issues.
Sometime the camera takes some photos and then freezes, sometime I can make one call via bluetooth and the dialer freezes while making the second call.
Only a reboot solves these problems (or my "Restart Camera"-app) - but with this problems I really don't want to use KK-ROMs.
Does anybody has a recommendation for a KK-ROM, maybe in combination with a custom kernel?
I would really appreciate any help!
Best regards
cool400
Click to expand...
Click to collapse
Thanks for your reply - but as the title says I'm looking for KitKat-ROMs.
But all ROMs you mentioned are JellyBean (4.3) ROMs!
Is there any recommendation for a KK-ROM without camera/bluetooth-issues?
Otherwise I will have to wait for official Samsung 4.4.2-ROM like announced on the official Samsung-website:
http://www.samsung.com/us/support/faq/FAQ00059206/82024/EFC-1G6FFEGSTA
Best regards
cool400
AOSNP works for me
I installed the AOSNP rom from this link:
http://forum.xda-developers.com/showthread.php?t=2638434
Then gapps from here:
http://forum.xda-developers.com/showthread.php?t=2012857
I used these files from the above link:
GApps Core 4.4.2
~20 MB-
Playstore-
Syncing apks and libs, etc.-
Google Camera 4.4.2
Automatically removes AOSP Camera/Gallery and adds Google Camera/Gallery
AOSP Calendar Sync 4.4.2
Adds syncing ability for AOSP Calendar (not in Core or Standard packages)
My wife has been using it for 6 days wit no camera or Bluetooth issues.
She uses Bluetooth Jaber about 5-6 hours a day.
Only complaint is battery drain, but maybe when the developer is back up he will be able to resolve it.
It's very fast and stable so far, if it wasn't she would definitely let me know. :laugh:
Since I don't think KitKat has been officially released for Note 2 yet... I suspect there is non without issues. Best to wait until official version comes out for developers to play with (which should hopefully be within next 2 months).