Related
Hi,
i developed an app ("my days") and it works in the emulator also on my g1 and for quit a lot of users.
now i got a mail from a "HTC HERO" User and he say the app crash from the beginning. (an earlier version worked for him... the new version include widgets and mass of new features, so i dont know where to start searching)
So what could be the prob, whats the different. It makes me quit unhappy, i thought android is compatible to all android devices.
Any ideas?
greets
chris
HTC Hero is not a released phone yet, and tell him to not complain about using unreleased alpha code on his phone.
I do apologize, it was not my intent for this to seem as "complaining", it was only something that occurred and I was wondering if anybody else had run across this issue.
I fully understand that this is a pre build.
But how is anything ever going to get solved if issues are not brought forward.
Paul
thanks
yes.. it looks he used a alpha version or so.. thanks for your reply... i just thought to come crazy.
he answered:
"
so I found out what the issue is and I do appoligise that this was my issue. I ran a program that takes and converts the apk's stored on the apps folder to odex files and the issue is that when I did the update it replaced the apk file but left the odex file and that must have caused the conflict. I removed the odex file and the apk file then reinstalled the v.8 version and all is good.
I do appoligize, I should have done some more research on my end.
"
so finaly it looks he knows a bit about android rooted phones (maybe more than me so may you tell me in short what does this odex stuff is?
greets
chris
odex = optimized dexopt-wrapper, it's supposed to make the phone/apps run faster, especially on appstosd.
ok thanks... even i guess for a simple coder like me i can not really have an advantage from it (from a point of an unrooted user/developer).. or just to learn something new?
because to makes apps run faster.. for sure i am always interested in
Vanilla Flavored AOSP
Gtablet AOSP is a project for pure vanilla Android with the Gtablet. It aims to be barebones and as true to the AOSP code as possible. The Google AOSP code is modified as little as possible to provide functionality, and the ability to boot. It is stripped down for modification by the end user.
Using CyanogenMod device files, Pershoot's latest kernel (20110328, 2.6.32.36), and some cherry picked cyanogenmod/nv-tegra files, a functional 'rom' and a github repo for this project has been created. As functionality has been added since inception, more pieces from Cyanogen are making there way in (browser fix and tweaks, some under the hood stuff, internal storage fixes, etc) to improve overall experience. All variances from original AOSP code is visible via the public git.
Huge props to the Gtablet and the Cyanogen development community. Without your work, this wouldn't be possible.
Huge thanks to EJHart for his direct assistance with this project. Also, thanks to Bekit, Pershoot, GoJimi, Cyanogenmod team, Google... and I am probably missing others... This project would not be where it is without all of their work.
To use this rom, you will use ClockwordMod to flash the zip file as you would any other rom. I have only used ClockworkMod .8 in my testing.
DISCLAIMER: I cannot be held liable for anything you do to your GTablet. Make sure you are comfortable with recovery tools, such as nvflash, before proceeding. Though the rom is quite functional and stable in basic testing, this project is in early beta stages.
Download RC2 --http://www.mediafire.com/?t2rwxm9p9e4bcb7
MD5 -- fbb79ab9f4da245bb3ab2a320369f95b
*NOTE* GAPPS 20110307 for MDPI will not work.
Use the 20110120 MDPI GAPPS (for example, http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110120-signed.zip).
Known Issues:
Most if not all the issues facing Cyanogen 7
Changes since RC1:
Latest Pershoot 20110328 kernel.
Browser crash loading google.com homepage is now fixed. This should resolve browser fc across the board.
Added User Agent, Fullscreen, Zoom controls, and Incognito to Browser.
Added Reboot to Power menu (intentionally excluding the recovery/bootloader options).
Fixed EMMC and basic information for Internal Storage in Settings->Storage.
Removed phone signal indicator, and tablified numerous text values.
Latest from AOSP Master (not much new since RC1).
Removal of extraneous junk, like speech recorder, voice dialer, and mms.
Retired changelog:
RC1 - Beta2:
My Apps now works in Market. Google Maps no longer force closes. -There is a downside to this-. The fix involves altering the LCD Density, which causes some apps to not scale properly.
Media on EMMC is now scanned and available in Music/Gallery/etc.
Live Wallpapers work.
Pershoot kernel 20110307
A bunch of under the hood stuff due to major changes upstream from AOSP.
Beta2 - Beta1:
AOSP is now pulling from master branch, making it version 2.3.3_r1.
Camera functions for still pictures. No mirroring or rotation issues. Video recording still not working.
Latest NVidia 3991 libs included (noticeable performance increase).
Pershoot kernel 20110301
Beta1 - Initial release:
Fixed EMMC.
Steamlined compile process.
Addition of Spare Parts/Dev Tools (possibly removed in future versions)
BUILD YOUR OWN:
GitHub -- https://github.com/aosp-gtablet
Use this project from github to create your own image:
repo init -u git://github.com/aosp-gtablet/gtablet-aosp.git
The process for CM7 will work. Run extract-files.sh, run envsetup.sh, lunch, make -j[X] bacon. Anything more is outside the scope of this post.
** Additional notes -- GoJimi's Soft Buttons are available in the source code, but are disabled in this release.
I am a minimalist, and I know there are others. I hope others enjoy, and help make this a better project
Please let me know what bugs you find so I can work on them! Thanks.
Sold! Will give this a try and report back. Nice writeup too. Is it true, development only available on linux?
Thanks.
I have done all my work in Linux, so I wouldn't know of any other way to create an image. Sorry.
Holy crap! This rom is whip fast! Have you installed gapps or monitored battery life on it yet?
jooky2000 said:
Holy crap! This rom is whip fast! Have you installed gapps or monitored battery life on it yet?
Click to expand...
Click to collapse
I have installed GAPPS, they work with the exception of the same Market/My Apps bug found in the CyanogenMod rom. I think it's fast too. I have not run battery test, or benchmarked it thoroughly. Someone has already recommended a possible fix for the 3d textures, that might help Quadrant run successfully. Without textures and all, I did get one run of Quadrant to complete (after numerous tries) and received a ~2100 score. Not the best, I know, but it still seems very snappy.
Not a quadrant user myself. Just the feel of it is impressive. I will report back with battery stats tomorrow.
Solid work getting this to the masses. Thanks.
What's with the weird Japanese keyboard and application that's included?
jooky2000 said:
What's with the weird Japanese keyboard and application that's included?
Click to expand...
Click to collapse
I assume you're asking about the Input Method options? I did not customize those, it's built with the full build of AOSP.
Please confirm what app you are talking about.
Has anyone tried MarketEnabler to see if it fixes the market issue?
just an FYI not sure what reports are coming in about it not working with 3.0.0.5 of CWM, but I was able to install it running 3.0.0.5.
-Josh
Excellent work, guys. Once everything works this will be my primary ROM.. since my wife also uses the tablet.
Yes Japanese IME keyboard and whatever that japanese character app is.. I don't read japanese (or Chinese) heck if I know.
Cell related services murdered my battery so swapped out for now. Fast ROM though thanks for sharing.
jooky2000 said:
Yes Japanese IME keyboard and whatever that japanese character app is.. I don't read japanese (or Chinese) heck if I know.
Cell related services murdered my battery so swapped out for now. Fast ROM though thanks for sharing.
Click to expand...
Click to collapse
Can you expand on what you removed? Just certain apks?
Would you send me a copy of your extract-files.sh? I'd like to see what you're pulling. Is the audio driver for the G Tablet open source? I'd be curious to see if we can't build a 2.3 driver.
gdanko said:
Would you send me a copy of your extract-files.sh? I'd like to see what you're pulling. Is the audio driver for the G Tablet open source? I'd be curious to see if we can't build a 2.3 driver.
Click to expand...
Click to collapse
The image is built using the device files from the CM7 repo, lightly modified and forked to it's own repo. This includes extract-files.sh, which is identical to that in CM7. I didn't see a point to re-invent the wheel on this step, as bekit & co. have done such an excellent job. It does not impact on the outcome of this being an AOSP image. Among other things (like defining hardware specifics in BoardConfig.mk), the device files bring in the core libraries already on your GTablet. This includes libaudio.so.
So ive installed this bad boy but ive seemed to have lost the market any ideas
jivy26 said:
So ive installed this bad boy but ive seemed to have lost the market any ideas
Click to expand...
Click to collapse
Same problem here. Market is not present.
You have to install google apps. Use the one for cm7/gingerbread found here http://goo-inside.me/gapps/ flash the zip as you would a rom in recovery.
can you please put screenshots?
If the rom is based on GB then screen shots at this point are not possible as ddms doesnt work with GB. It looks just like plain jane vanilla android.
WARNING: TRYING TO CUSTOMIZE YOUR VIEWSONIC MAY LEAVE THE DEVICE IN A BRICKED STATE. PLEASE MAKE SURE YOU FULLY UNDERSTAND HOW TO USE NVFLASH BEFORE TRYING THIS INCASE SOMETHING GOES WRONG AND YOU NEED OR WANT TO GO BACK TO THE VIEWSONIC STOCK TNT ROM.
What we offer here is a new way to keep you in full control of your tablet. Our 1.8 Honeycomb Kernel offers Speed, Reliability, and new added features. This kernel is a spin off of the Pershoot Honeycomb Kernel Source Code & want to thank Pershoot for all his work on the kernel already. You do not have to Flash your device or even update to a different ROM to feel the benefits of the Linux Box Solution Honeycomb Kernel...
Updating to the Linux Box Solution Honeycomb Kernel couldn't be easier. No wiping of User/Data is necessary. If you are already running a Honeycomb ROM then your good to go. This kernel was designed for Tegra 2, Harmony Board based devices. The LBS 1.8 Honeycomb Kernel has only been tested on a Viewsonic Gtablet. If any other developers with the Specified Tegra 2 & Harmony Board based devices wants to give this Overclocked Powerhouse a try please give me your feedback once you have tested it out.
Features as of Version 3.2:
Increased Kernel Cache Sizes from 256kb to 512kb
Improved Stability
Overclocking (Kernel is Overclockable to 1.4Ghz)
USB Mass Storage ( If your favorite Honeycomb ROM doesn't offer USB Mass Storage drop this Kernel in and Full Support is there)
Improved Video Play (480P Plays, Not sure about 720P but 1080P Does Not Work)
Git Hub Source Location: https://github.com/linuxboxsolution/LBSGtab
Linus Torvald Repo: http://android.git.kernel.org/platform/kernel/tegra.git
Pershoot Repo: https://github.com/pershoot/gtab-2632.git
For anyone in doubt or wondering. This Kernel has been fully updated with Pershoot's source code from his 7/2 update. Next changes to the source code are taken from Linus Torvalds Repo Source to help merge Pershoot's and Torvalds Source to make a more efficiently running Kernel.
Download Link:
LBS 3.2 Honeycomb Kernel: http://linuxboxsolution.com/linux-b...tions-Viewsonic-Gtablet-Honeycomb-Kernel-3.2/(increased kernel cache size for improved stability)
LBS 1.9.2 Honeycomb Kernel: http://linuxboxsolution.com/linux-b...ons-Viewsonic-Gtablet-Honeycomb-Kernel-1.9.2/(Wifi configuration changes to help people with wifi connectivity issues)
LBS 1.8 Honeycomb Kernel: http://linuxboxsolution.com/linux-b...tions-Viewsonic-Gtablet-Honeycomb-Kernel-1.8/ Initial Release
1. Download the zip file for the Kernel Version you want to the Root of your SDCARD Partition.
2. Rename file to update.zip
3. Reboot Tablet into Recovery Mode (When Tablets Off hold 'Power' Button and 'Volume +' Button at Same time till Recovery Mode is Shown On Screen)
4. Using Volume -/+ to navigate the Clockwork Mod Menu go to apply /sdcard/update.zip
5. Once Installation of New Kernel is done Reboot the Tablet & Enjoy your newly found Feature Set and Performance Improvements
aww what the hell i'll give it a go...currently running BoS 6.0 and it's smooth...I'll post back with Quadrent scores for those who care about them.
Updated: well it might be me but the lockscreen seems more responsive, Video plays about the same but im in Rockplayer, Quadrant was 2677 using Quadrant Advanced. Kepp up the work guys.
Update: Ok well been playing with it and just found out No WIFI here. it won't pick up any signel...this might be just me but so far Reboot + turning wifi off and back on did not fix it i'm going to wipe cache and see if it resoves it.
Update: as of right now the Update did not fix the problem nor did wiping cache/data...Going back to my nandriod and i'll watch for updates.
Also i'm using a static setup with WEP Security if that helps...it shows my old connections but won't connect or find new ones.
Awesome please do but if you haven't yet try the updated version.
I had an exchange with you on slatedriod about "your" new kernel. You admitted that it is based on per shoots old GB codebase with your new wiz bang improvements. Why don't you say that here and say that this kernel is an L BS modified version of his kernel. You must just be looking for donations for the work of others?
you're going to continue updating illuminate with this right?
how have you improved playback of video in this kernel? is the improvement rom agnostic?
WiFI Issues
Well I was having intermittent WiFi problems with Illuminate until I flashed this Kernel, now I am just getting an error when I try to connect to WIFI.
jbrianj said:
Well I was having intermittent WiFi problems with Illuminate until I flashed this Kernel, now I am just getting an error when I try to connect to WIFI.
Click to expand...
Click to collapse
Try the latest pershoot GB kernel. And/or try the Flashback of BoS roms
Hi Everybody,
I need some help. I installed this rom into my malata zpad. First opening, there was no problem but after restarting, touchscreen was not worked.
I reinstalled, but same problem was occurred. My touchscreen is not working, only back and home button, which are physical button, are working.
What can I do?
I noticed this behavieur with the latest Version before I hadn´t any problems
I read today that this is Pershoot's latest + cm7 modules. No changelogs, no submissions to github. I read in the rules here something about "don't do anything to get us in trouble". To me this kernel looks like something that might do just that.
I loaded this kernal on top of illuminate yesterday. Couldn't determine if this was already part of the rom or another update to the kernal. In any event it did add some pep to it. Haven't figured out all the improvements yet. It did however mesh nicely with illuminate.
For the record I think this kernel is only compatible with illuminate and bos. Flashing this or clemsyns ver11 onto Flashback breaks the wifi.
ramerco said:
This thread has turned into a joke with no information other than a re-compiled version of pershoot's kernel.
Can it be closed please.
Click to expand...
Click to collapse
No, it is working well. Thanks dev we appreciate all your work. Been driving this one around for a few days to see what was different -- speed. Still investigating but don't stop because you are the only HC dev that works on the kernal and the rom itself we definitely need more like you. Looking forward to your next works!
Kernel source needs provided as per GPL. All this looks like is a rebranding of someone else's kernel - to dispel that belief please provide source and changes or else this will be removed as it would be in violation of the rules.
edirector said:
No, it is working well. Thanks dev we appreciate all your work. Been driving this one around for a few days to see what was different -- speed. Still investigating but don't stop because you are the only HC dev that works on the kernal and the rom itself we definitely need more like you. Looking forward to your next works!
Click to expand...
Click to collapse
He would need a 'first' work to have any 'next' works. Someone who actually took the time to research a little web history might find that the guy is merely a thief of others' ideas and work. They might find that the guy also has multiple usernames and accounts on various threads, in different forums, and actually "talks to himselves" in those threads. They also might find that the guy is also pretty much clueless, and would have exactly a 0.0% chance of developing his own kernel.
I'm not saying they would, I'm just saying they might.
I'd run stock on my Gtab before I ever TOUCHED this.
Just sayin.
By the way, 'eDirector'...In no way was I implying that you could be just another one of linuxboxsolution's 'NPC's.
Of Course I wasn't.
REMOVED my post, as it's off-topic and no longer relevant.
roebeet said:
When I posted in the other thread, I did mention that I didn't know the history - I suppose this is the "other" thread that some had mentioned?
Again, I haven't delved into this kernels and mods, and I do agree mostly with what tlbardelljr had written - "stealing" is a very gray area here. Most of my own ROMs are just mash-ups of other people's work that I tried to make into something more usable for me, and possibly the community.
But, I usually try to give credit also. If I'm using pershoot's ROM, I document that. If I'm using gojimi's framework changes for Brilliant Corners, I give him a nod. If I'm using the Adam HC base for BoS, I give them a nod as well. It's not only good manners, but it's also part of the rules here. If you're going to take, you should give credit. It's not rocket science.
I am not saying that's what's going on here - I haven't looked into these allegations, myself. But jerdog had commented two days ago and I think his comment is not only valid but it's something that needs to be responded to by the OP. That would certainly answer the question and put this to rest.
Click to expand...
Click to collapse
Hello Roebeet,
This may help but I am not sure for I am not a developer...Git Hub Source Location: https://github.com/linuxboxsolution/LBSGtab. Boy I wish I was for I would be on my way to Silicon Valley with my latest brainstorm for the Android platform that's why I respect what you guys can do so much. I can package your coding, sweetly I might add, but I am not a coder.
REMOVED my post, as it's off-topic and no longer relevant.
Offended by what's going here!
Comments removed as promised.
REMOVED my post, as it's off-topic and no longer relevant.
Im on cm9 and it looks like the new chrome update broke compatibility? Is this true for others?
Edit: just read the comments on the google chrome beta site and this was posted...
For you guys who are complaining about Google dropping custom ROMs support, that's not true.
I have a Samsung Galaxy S running CM9/Android 4.0.3, and also faced the "error" message when running the new version of Chrome. But when I looked a little bit deeper into the problem, I discovered that it is a ROM issue, not really Google's or Chrome's fault.
The problem was that the ROM had "Gingerbread" as a build ID + fingerprint, that's why Chrome wouldn't let me use it. Now I changed it to IML47K and everything is running fine, i.e. Chrome running on a CM9 custom ROM.
So if you have this issue, don't blame Google, instead, wait for a "fix" from your ROM developers.
Sent from my SPH-D700 using XDA App
Yea, Google disabled Chrome on custom roms... makes no sense. Short blurb about it on Engadget.
Same thing happened with my Touchpad running ICS, and user Foggytown posted a fix which worked for TP, may also work for Epic. I'm not running ICS for Epic so can't test myself.
Backup before doing this:
foggytown said:
HP Touchpad running CM9 Alpha 2
Here is how I fixed it: Back up your build.prop, and find the line for ro.build.id and change the value to IML74K. Reboot. Enjoy new Chrome update.
I haven't found that the change breaks anything.
Click to expand...
Click to collapse
Chrome Fix ... Caveat
I wrote a detailed analysis of the Chrome Beta issue in this blog entry. Be sure to read the warning!
wtogami said:
I wrote a detailed analysis of the Chrome Beta issue in this blog entry. Be sure to read the warning!
Click to expand...
Click to collapse
Works great.
Sent from my Cyanogenmodded Epic4g! Wanna fight about it?
wtogami said:
I wrote a detailed analysis of the Chrome Beta issue in this blog entry. Be sure to read the warning!
Click to expand...
Click to collapse
You could also fix it through the terminal emulator (as root):
# mount -o remount,rw /system
# vi /system/build.prop (change relevant line to ro.build.id=IML74K)
Hello. I have had a Kindle fire since Jan of this year. It has been my first tablet/android device. I've had a great time playing with it, learning about rooting, bricking and unbricking thanx to this awesome forum and really want to express my gratitude for all the help provided by this site.
I am a medical student and I bought the device specifically for an app for my licensing exam. I feel like I have one last hurdle to overcome in understanding how to manipulate this device, that being a method of altering the way that the market apps recognizes the kindle. I have seen various mods that cause the device to show up differently.
My question is: what is the best mod to facilitate this and only this?
-I have everything as I like it so I prefer one that changes only this aspect.
Thanks a thousand times in advance.
Edit the build.prop file if you know how to, just change the model name to another device like the Galaxy Tab or something and you'll have a bunch more apps in the market.
Just use the modified build.prop from THIS thread and you will be all set.
thanks guys. I've read about build.prop. Gonna check out this link
I read through that link. It only supports CM7. I have had both CM7 and CM9 and prefer stock + go launcher. Do you know of any preset build.prop's that support stock?
edit: Obviously didnt read far enough, here it is: http://forum.xda-developers.com/showthread.php?t=1439916
I will test it out then update. Thanks again!
edit2: Modaco Gr6 is the mod to flash for those seeking to run stock vs. CM7/CM9. I got access to the file I needed and many other apps. I dont think i am seeing the entire android market though.