Sorry if this has been addressed elsewhere, I really don't know what to call this or the best keyword to describe it; I have a Galaxy Tab 10.1 WiFi only and have tried out a few builds of ICS (one from CM9 and the other AOSK or whatever it is). I have even tried the latest build (33) and still have this problem. I had a Comic Reader app where if I swipe up or down, it would change the comics (left and right would change the comic by date). There seemed to be a problem where I'd swipe up and it would think I was swiping horizontally instead. It was driving me crazy.
The best way I can describe a test would be:
Download Temple Run (game that you must swipe up, down, left and right). Try beating the first level. It was impossible for me to beat because I would try to swipe up and it would go down or left instead, etc. Just really off... anyone else have this issue?
This is the only thing that is hindering my tablet from having ICS; I could care less for the camera, my phone's camera is 100x's better anyways....
thanks!
i have that problem to i am using pershot builds
Same issues here with Temple Run (pershoots latest build)
I have similar problems in F18 Carrier Landing game. In the menu, my touches and gestures seem to be interpreted randomly and so are they in-game...
No solution known to me though...
I also noticed this.
It's a ICS issue or the ROMs aren't 100% compatible touchscreen drivers.
Expect issues with the ICS you're using.. why? its because all of them are in beta.
Oh I know that there will be issues; I was just posting to see if others were having the same problem and/or if there were any possible solutions available. Hopefully the developers are aware of the problem and will fix it in upcoming releases, if at all possible. At least I know mine isn't the only one doing it. I could care less about the camera working, but this off-swiping makes me go back to HC for the time-being.
XIInator said:
Oh I know that there will be issues; I was just posting to see if others were having the same problem and/or if there were any possible solutions available. Hopefully the developers are aware of the problem and will fix it in upcoming releases, if at all possible. At least I know mine isn't the only one doing it. I could care less about the camera working, but this off-swiping makes me go back to HC for the time-being.
Click to expand...
Click to collapse
Try the latest build from pershoot http://droidbasement.com/galaxy/roms/cm9/p4wifi/ (after flashing, you have to replace the boot.img). Temple Run works fine now.
Thanks! I will definitely try it. But one thing, what do you mean by "replace the boot.img"?
Edit: Hmmm I must be missing something, I keep getting the "assert failed: getprop("ro.product.device") bla bla bla. Restoring previous ROM, too tired to think for now... I'll check back here later... thanks!
XIInator said:
Thanks! I will definitely try it. But one thing, what do you mean by "replace the boot.img"?
Edit: Hmmm I must be missing something, I keep getting the "assert failed: getprop("ro.product.device") bla bla bla. Restoring previous ROM, too tired to think for now... I'll check back here later... thanks!
Click to expand...
Click to collapse
Replacing the boot.img is no longer necessary, now you have to flash the ICS of your preference (just use a recent build, the one in http://droidbasement.com/galaxy/roms/cm9/p4wifi/ is ok.) and the new kernel in pershoot's blog: http://droidbasement.com/db-blog/ (direct link for the ics kernel for the p4wifi (26/04/12) http://droidbasement.com/galaxy/ker....4_p4wifi_ics-oc-xtra-vfpv3-d16_fp-042612.zip ). This may not be always necessary if the build you're flashing already has the latest kernel.
About the assert failed, you need to flash a new recovery (cwm) via Odin, use this one: http://droidbasement.com/galaxy/roms/cm9/p4wifi/
SWEET!!! Thanks so much!!
I was able to follow your instructions to the letter (sort of) and I can play Temple Run without a hitch! It was driving me crazy trying to browse through the comics in Comic Reader.
I said "sort of" because I installed the recovery image, and flashed the ICS rom, but forgot to flash pershoots kernel. When I tested the Temple Run, it was doing the same weird touch issues. I was about to give up when I realized I didn't install the kernel. Installed the kernel, and sparks flew! Well, Temple Run was completely playable! So it appears that installing pershoot's latest kernel is what made the difference. So for those who are having similar issues, follow Maple Syrup's directions.
Thanks again Maple!!
I had the same problem with Shadowgun. The latest pershot kernel sorted it!
Related
After Plants v Zombies released on the Amazon app store I was happy (that it released and was free) then sad (BC it didn't work on any rom I was running) then happy-ish (b/c I found that it ran on VEGan v1.0 b5.1). This rollercoaster of happiness drove me to make the game work on a froyo rom I like enough to run froyo.
Anyway, if you like PvZ AND can/do/want to run a BL1.1 Froyo ROM, this kernel could be for you. I can't tell you much about it because i didn't compile it, I just extracted it from VEGAn b5.1 and packaged it up with wifi driver's into koush's AnyKernel update.zip format. I have installed over a handful of froyo Roms with great success (I have run it the longest on a derivative of Calkulin's rom). I have not had any noteworthy issues. I have not tried it on anything other than Froyo.
Warnings: Use at your own risk, backup first, know how to nvflash, etc.
What this does: Replaces your gTab kernel with one that (among other things) runs Plants v. Zombies without the dreaded freeze every two minutes.
To install: Flash zip file with CWM, wipe cache and dalvik cache, reboot.
Tips: Set wifi to never sleep.
NB: I think this goes without saying, but if you are on a vanilla VEGAn b5.1 then there is no need for this.
UPDATE: This kernel can experience the "Sleep of Death" issue where the tablet won't wake properly form sleep. A couple things to avoid that are:
1. After installing the kernel format cache, dalvik, and run fix permissions (all within CWM).
2. Make sure you are running a ROM that was not installed over another, ie. you have done a data wipe at some point after installing the custom ROM you are currently on. Restoring user apps and data with TB is fine, but a full data partition restore with CWM from another ROM can cause big issues.
3. Press the power button a little longer (maybe a 250-500 ms) rather than just a tap, and then wait a few seconds before pressing again.
4. Use power control widget or something similar and just toggle off wifi when you aren't using the tab for a long time (it saves battery too).
Download: Attached to post...
UPDATE 7/4:
Peggle, another Popcap title has the same issues. It works flawlessly on this kernel. Pershoot is looking into the issues (thanks pershoot!) soon (http://forum.xda-developers.com/showpost.php?p=15282076&postcount=1597).
Good work, Ramerco,
Always enjoyed reading your posts, as well as from a few great non-dev posters as TEK112, goodintentions, tjevans, etc . . .
BTW, PvZ is running fine on Beasty. It is a fun and hard to beat.
Dave,
mydave1 said:
Good work, Ramerco,
Always enjoyed reading your posts, as well as from a few great non-dev posters as TEK112, goodintentions, tjevans, etc . . .
BTW, PvZ is running fine on Beasty. It is a fun and hard to beat.
Dave,
Click to expand...
Click to collapse
really? no freezing? even on more complex levels? what is the kernel (you can see it from the about device/about tablet settiings page)
VEGAn 5.1 Froyo has a pershoot 1.1bl kernel that was compiled back in December. Is this really the only kernel that works, not even newer pershoot 1.1bl kernels? I wonder what was changed in the newer versions?
I've never used that game - I heard it's just as addicting as Angry Birds so I've avoided it like the plague.
yeah, not even pershoots first released standalone kernel from January works. I have no idea what's different. maybe it is from before the nvidia 10.9.9 stuff he mentions in his kernel thread.
FYI PvZ is fine on 3588, and so is Samaraui (another game people complanin about not running well on some ROMs). Stock isn't sexy or cool, but when I'm actually using a full-screen App I can't tell the difference between ROMs anyways.
mike_ekim said:
FYI PvZ is fine on 3588, and so is Samaraui (another game people complanin about not running well on some ROMs). Stock isn't sexy or cool, but when I'm actually using a full-screen App I can't tell the difference between ROMs anyways.
Click to expand...
Click to collapse
Funny that it works well on 3588. When I was testing, I may have only tested 4349 stock. But now I can't really remember. I actually really like the TnT status bar and the wifi and battery widgets in it. I also really like the Home screen and the settings app even though the settings is missing a few key things (you can always temporarily swap to stock settings for those). My point is, I like the stock-ish rom, but I also like to have root and long press Home to switch apps.
roebeet said:
VEGAn 5.1 Froyo has a pershoot 1.1bl kernel that was compiled back in December. Is this really the only kernel that works, not even newer pershoot 1.1bl kernels? I wonder what was changed in the newer versions?
I've never used that game - I heard it's just as addicting as Angry Birds so I've avoided it like the plague.
Click to expand...
Click to collapse
To answer Roebeet's and potentially other's question,
This is the only bootloader 1.1 kernel for Froyo that works for Plants vs. Zombies. All others freeze shortly after game launch that I've tested.
I tested the last 2 released versions of BL 1.1 (& BL 1.2 as well) kernels from pershoot or clemsyn of Froyo, GB, & HC kernels with adjacent 1.1 or 1.2 Android ROMs just for the heck of it--> all PvZ fail blog entries for me.
Someone in another forum mentioned BoS HC 3.3 PvZ working, but it didn't work for me. I sure wish it did.
Here's what Froyo ROM's work with the PvZ Kernel:
VEGAn-tab 5.1.1 bl1.1--> PvZ success & Roebeet Netflix fix works too
Calkulin-Clemsyn v.5 bl1.1 -->PvZ success- fastest gameplay & not working Roebeet Netflix fix
TnT lite 4.4.0 Froyo bl1.1--> PvZ success & not working Roebeet Netflix fix
Peggle has the same issue with other kernels. OP Updated to reflect. Popcap must have some crazy code stuff going on.
spideyngo said:
To answer Roebeet's and potentially other's question,
This is the only bootloader 1.1 kernel for Froyo that works for Plants vs. Zombies. All others freeze shortly after game launch that I've tested.
I tested the last 2 released versions of BL 1.1 (& BL 1.2 as well) kernels from pershoot or clemsyn of Froyo, GB, & HC kernels with adjacent 1.1 or 1.2 Android ROMs just for the heck of it--> all PvZ fail blog entries for me.
Someone in another forum mentioned BoS HC 3.3 PvZ working, but it didn't work for me. I sure wish it did.
Here's what Froyo ROM's work with the PvZ Kernel:
VEGAn-tab 5.1.1 bl1.1--> PvZ success & Roebeet Netflix fix works too
Calkulin-Clemsyn v.5 bl1.1 -->PvZ success- fastest gameplay & not working Roebeet Netflix fix
TnT lite 4.4.0 Froyo bl1.1--> PvZ success & not working Roebeet Netflix fix
Click to expand...
Click to collapse
I just nflashed back to BL1.1 and installed VEGAn-Tab 5.1 and then the 5.1.1 supplement. All the animations just show up as black blocks, is there something I'm doing wrong. I tried it both before and after installing flash 10.3, don't know if that matters.
Had that happen once or twice. Just kill the process and try again. The game uses tons of memory, suoometimes works better when you kill background apps. I know android is supposed to be great with mem mansagment, but it seems like some things run better wghen you kill background memory hogging apps.
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.
I did a clean install of tytung's NexusHD2-ICS-4.0.3-CM9 V1.2.
It installed well and fast, looked awesome.
Then, during the set up phase (when personalizing the phone), I get error popups about "android.process.acore".
I did many flashes, but still, the popup comes up.
Any fix for this?
Ok, just an update. The error no longer comes up, but a new one. Lol.
It's now the contact process that comes up.
And WiFi doesn't turn on.
Maybe it's the rom. Did you get this error with other version of Android as well?
Cenobite_ said:
Maybe it's the rom. Did you get this error with other version of Android as well?
Click to expand...
Click to collapse
No. This was the first time I saw this kind of error.
I'm testing out if it will happen with a cLK installation method.
Update : Doesn't even boot with cLK. Flashing MAGLDR back
Ok. Here is the conclusion for my device.
1) ROM boots fine.
2) WiFi doesn't work
3) Getting "com.android.contacts" popup error
Gonna flash back to more stable ROMS.
@tytung : any possible fix to this?
v 1.2's a bit buggy. 1.1's the best!
Geek998 said:
v 1.2's a bit buggy. 1.1's the best!
Click to expand...
Click to collapse
Do you still have the link available to v1.1?
The thread itself was updated for v1.2.
Quick update.
I'm trying it again, and it seems to be working fine now, except for a few bugs.
1) WiFi is working fine now.
2) Contacts process still FCs. Doing a workaround to get this fixed (Will post outcome)
That's it for now.
I am officially giving up on this ROM.
For some reason, it;s just broken for me.
Back to good and stable Sense 3.5 ROMS :/
DOWNLOAD HERE:
NexusHD2-ICS-4.0.3-CM9 V1.1
ICS is better than Sense UI. Sense is now a bloated piece of crap expect for it's weather animations.
(Just my opinion)
I'm just holding off ICS for now, till dev for them is more advanced, and of course, more stable.
I love how ICS handles and runs on an HD2. Smooth, fast, and intuitive.
But for some reason, it just doesn't work on this darn phone. Lol!
Huge update!!
I tried V1.3 (for the heck of it).
Lo and Behold! No errors, smooth installation and usage.
Perfect
Gonna try to install the A2SD script. Hopefully it doesn't bug the this out "
Hi,
I just wanted to ask, which one of the cm9 builds is better for daily use, and why?
What are the major/minor bugs in both of them?
Thanks in advance
I'm using CM9 from Turl... it's very stable... Only issue I have is that some games FC.
thanks, what abaut the battery life? does hdmi-out work?
Fantastic battery life all things considered. Its my daily. Switched over from joker to turl, find it more stable
Current Turl1's v8 CM9 is OK for my day-to-day life.
Some features are not implemented (profiles), some are in process of fixings (camcorder) etc.
Some apps FC from time to time or even always.
But for my d2d it's OK.
In my opinion, Turl's v8 is a little bit more stable than Joker's. Both far from perfect tough. I went back to GB for now...i might just wait till the firsts official ICS leaks for our device.
Sent from my MB860 using XDA App
same as DJLuis, Turl is the most stable but still some glitches, missing features and dodgy camera implementation.
Also back on GB Notachtrix now until official or leaked
i used joker's rom for a while!!
but some things are broken though !!
the fp scanner, laggy video playback on default player (3rd party video player does the job) !! camcorder, etc !!
some minor call bugs also !!
back to morrisoft cm7 rom !!
Thanks for all the answers.
I think i`ll first use a cm7 rom.
So if i want to unlock my bootloader, this also works for firmware 4.5.141 ,doesn´t it?
http://forum.xda-developers.com/showthread.php?t=1182871
Give a read through this thread:
http://forum.xda-developers.com/showthread.php?t=1501532
A lot of people are having problems unlocking and rooting with 4.5.141. That thread gives detailed step-by step instructions on what to do.
As for CM9, I have been using it since day 1 and have been nothing but pleased. It is true, a few things don't work. but it's only a matter of time, I believe, before we get a fully functional ROM. You may want to try it out just to satisfy your curiosity. Just as a forewarning, you do have to do a full system wipe when switching between CM7 and CM9. That being said, it may be easier to just try out CM9 and if you're not pleased revert to CM7. It'll be a lot more painful to get everything set up on CM7 only to have an updated CM9 appeal to you again in a few weeks and have to wipe everything.
And yes, I do believe CM9 has HDMI out.
Good luck unlocking! Btw, I have been using joker's builds from the very beginning. I have been more pleased with them than with Turl1s.
Thanks, I already read this thread, but it´s more about having problems, when updating from 4.5.91 to 4.5.141, if you´ve had an unlocked bootloader at 4.5.91
I can just find links to this thread
( http://forum.xda-developers.com/showthread.php?t=1182871 )
which i had mentionend before. so this should work.?
anyone?
sorry for my impatience, but i´m really afraid of hard-bricking my phone...
I used that script and I had stock gingerbread 4.5.91. I have no idea what version firmware you are talking about since I haven't been on official firmware since then
- make sure you are AT&T Atrix, that script is only for AT&T
- if this is some later AT&T update then I'm afraid you'll have to search yourself.
Wipe necessary even though they tell you it isn´t
On Joker´s website, it says that wipe is not necessary between versions of CM9. I tend to disagree, as I have had multiple issues with Gmaps, App management, etc... that just disappeared after a fastboot wipe.
I think a lot of problems discussed here are due to dirty flashes and I would advise strongly to wipe when installing a new rom.
ok.
Is there anyone, who unlocked his bootloader on firmware 4.9.141 ?
I couldn´t find concrete instructions or how to´s
Danger! If you start down the cm9 path forever will it dominate... etc.
In all seriousness its buttery smoothness and updated time and date entry systems, cut paste, etc. and general os features improve all your apps and make it impossible to ignore so avoid until ready or be prepared to be a beta tester for quite a while!
Matt
Sent from my MB860 using XDA
I'm using jokersax 0.3 beta. It works great the only bugs I have is no video recorder and switching from portrait to landscape in browser causes a force close
metlca said:
anyone?
sorry for my impatience, but i´m really afraid of hard-bricking my phone...
Click to expand...
Click to collapse
just follow the instructions here and u'll do fine....
http://forum.xda-developers.com/showthread.php?t=1302423
mine works like a charm, as for roms...., if u r going for CM7, u got a a lotta choices and idk what to recommend u.
but... if u r looking for CM9, turl's v8 is a good place to start.....
but if ur gonna use CM9, as new n improved rom come out almost every week, get comfortable to wiping data, flashing new rom and restoring backups very often....
for backups, use titanium backup for ur apps...and MyBackup from rerware for your sms, call logs and contact or let google restores your contact if u enable the backup and restore in the setting...
pho_lone said:
just follow the instructions here and u'll do fine....
http://forum.xda-developers.com/showthread.php?t=1302423
mine works like a charm, as for roms...., if u r going for CM7, u got a a lotta choices and idk what to recommend u.
Click to expand...
Click to collapse
Thank You
So did you unlock your bootloader on firmware 4.9.141 and it worked fine ?
Widgets
Feeling pretty noobish right now...flashed from CM7 to Jokersax CM9 .31 today and I love the look and feel of it. How do you load widgets in CM9? I use the phone for business and Touchdown for Exchange for my email. I use one of the Touchdown widgets to be able to instantly view new email without opening the full blown app. But with CM9 I can't figure out how to load the widget.
Like I said, feeling pretty noobish right now. Help please.
Latest Downloads
CM10.1 http://d-h.st/i3V
CM10.2 https://drive.google.com/file/d/0B1V_hMyelDz0Rm1nenlqT2JKWkE/edit?usp=sharing AS OF 21.11.2013
UNOFFICIAL FAQ FOR CM10.1/10.2
DOWNLOAD AND INSTALLATION
Q: Where’s the download?A: The initial FXP release had an incorrect kernel – you can download a working version of ROM from here. http://d-h.st/TPT
This ROM has since been updated a download can be located here. http://d-h.st/i3V
If you wish to try a CM10.2 (that’s Jelly Bean 4.3 – have Sony actually released a 4.3 ROM yet?) one can be downloaded from the link above.You can also download the correct version of GAPPS for Jelly Bean 4.3 here. http://brintaylor.info/Android/CM/gapps/
For the CM10.2 build you should use this link to report bugs. https://docs.google.com/forms/d/185s...9UINQ/viewform
Uberlaggydarwin plans to take a 'light touch' approach to support via XDA, so don't necessarily expect an answer to a query if you post in this thread
It seems like FXP have delayed releasing for our device for now, but information about CM builds that are being actively supported and developed can be found in this thread for now.
Q: How do I install?
A: You need an unlocked bootloader and an installed recovery. BACK UP your current ROM to your external SD card. Put the ROM and GAPPS on your external SD card. Boot into your recovery, do the necessary wipes, flash the ROM, flash GAPPS, reboot, victory. Disclaimer: if it breaks your phone, it’s your fault.
Q: Do I need to install the supplied kernel before installing the ROM?
A: No, unlike older xperia models CWM is able to flash both the kernel and the ROM at the same time. There is no need to use fastboot or flashtools to flash the kernel first, just a working recovery and an unlocked bootloader on your phone.
Q: Can I use another kernel instead?
A: No, for now only the supplied kernel will work.
Q: I’ve installed the ROM but can’t find the play store?
A: Immediately after installing the ROM you should install the 4.2.2 version of GAPPS (Google Apps) – this installs the play store and several other applications that Google regard as essential to the Android experience. This can be found here – http://goo.im/gapps/gapps-jb-20130812-signed.zip
Q: How do I update to the latest version of the ROM?
A: Once you’ve downloaded the latest version to your SD card, boot into recovery. No need to wipe your data, though you probably should wipe cache and dalvik cache (I don’t know whether this is done automatically as part of the installation but it can’t do any harm). You don’t need to install GAPPS again as this is a firmware update, not a new installation.
However if you’re moving between versions i.e. 10.1 to 10.2 you should definitely do a factory reset – the ROM may well work fine without a data wipe, but it may not and any problems might not be immediately noticeable (making bug tracking difficult). I would advise you NOT to report bugs if you’ve moved between android versions without a factory reset.
Q: When will they release a version that works on a locked bootloader?
A: Never. Some the features of the ROM simply won’t work very well/at all on a stock kernel. If you are rooted you can simulate some of the features with apps and mods though.
POST-INSTALLATION QUESTIONS
Q: I’ve installed the ROM – I can use Titanium Backup to reinstall all my apps right?
A: Yes and no. They may work fine, they might not – you are better off letting Google’s back up service restore all your apps. If you restore an app using Titanium or similar software and it’s buggy, there’s no point reporting it – re-install the app instead, perhaps even the ROM.
Q: 4G isn’t working – what do I do?
A: It’s not enabled by default on CM10.1 so you must do the following.
Go to the dialpad/phone.
Dial in the this number: *#*#4636#*#* (This will bring up "Phone info").
Tap WCDMA from under "Set preferred network type".
Select "LTE/GSM/CDMA auto (PRL)".
The 4G LTE network should now be activated.
Q:Where’s USB mass storage?
A: After ICS Google stopped including it in their Android builds, as such mass storage mode is not a feature that was kept by CM for Jelly Bean. Individual manufacturers do what they want though, which is why Sony, Samsung and others still have it. Skilled modders may be able to add to ROMS based on this development, I reckon they might be able to patch this one to include it too
Q: This ROM is buggy as hell and drains my battery – how do I let the developers know?
A: Logcat and/or a kernel log - or it didn’t happen for bugs.
Better battery stats for battery drain.
There are lots of guides out there showing you how to take logs and how to record battery stats.
Anecdote – I activated Google+ yesterday as I like the auto-photo upload feature but wakelock detector revealed it was killing my battery (I think it’s dodgy on stock too). The choice was the app or the ROM, I chose the ROM.
Q: After installation something random doesn’t work – what do I do?
A: Check the thread to see if other users have mentioned the issue and to see if the developer has posted a solution. Also, you’re on XDA, you’re an advanced user, you have unlocked your bootloader, thrown out your warranty and accepted the consequences. So please try to resolve the issue yourself. In general if you are having a problem and no one else is, it will be a problem with your phone/download/installation.
Phone - obviously a hardware fault can't be foreseen by the developer and have you unlocked your bootloader!
Download - Most downloads are fine. But I've flashed enough ROMS to know that sometimes a file gets corrupted and sometimes they say they are complete when they are not. Sometimes I've been careless and clicked on the wrong download, sometimes the website hosting the site is haveing a a bad day, sometimes the developer puts the download in the wrong place too The first things to check are the name and size of the file - if these tally you're probably fine to install. If you want to be extra cautious you can check the MD5 hash to see if your download matches. Sometimes the file gets corrupted on upload - nothing anyone can do about that...
Installation - (Please back up your orignal ROM). Typically you'll be installing this ROM using a recovery from another ROM/kernel/MOD - so if you have problems installing , it might be that you have a bad recovery.
The wipes really need to be done to ensure the smooth running of your phone, but as you've backed up, the 15 seconds you spend properly wiping should not be much of a chore.
If you're one of the first downloaders, I guess there is some merit in saying you couldn't install, but if it's been out for a while and there are loads of posts saying 'what a great ROM' there's little point posting 'won't install'. Describe exactly what you've done and someone might help.
Bear in mind there are apps/hardware that the developers of this ROM won’t have heard of/care about - so if something doesn’t work properly on your phone it could be for numerous reasons. Either way, this may be something you have to live with. Alternatively, if the app is essential to you, you’ll have to return to a backup.
Remember this ROM is in development, there are no promises of perfection and no one is forcing you to use it. However, the right kind of feedback is always welcomed by the developers and may be acted on – the wrong kind will often be ignored.
Q: What does a perfect bug report look like?
A: Go here. http://forum.xda-developers.com/showpost.php?p=46935640&postcount=313
Q: What are the known bugs?
A: FM radio doesn’t work.
A: Attempts to offline charge cause the phone to boot.
A: 4G activation is not remembered between boots for CM10.1.
A: For 10.2 there is a known battery drain issue related to WiFi. See the solution here. http://forum.xda-developers.com/showpost.php?p=46923723&postcount=301
The following issues have been reported by some users, but others say it doesn’t affect them. They are regarded as hardware issues – anecdotal ‘me too’ posts will be ignored. However, supply a log and your phone’s date of manufacture and the developer may look into it (this might help you prove that your phone is faulty, so it’s a worthwhile exercise).
Erratic touch screen response.
Reading external SD Card in recovery and in use.
As others have said this is possibly the most stable first CM build they’ve encountered and I agree – it’s definitely suitable for daily use. I've been using it from release and haven't had a single reboot/app crash or freeze.
http://uploaded.net/f/q3au96
CM 10.1 released for huashan
Its cm for our phone right?!??
Sent from my ZTE Blade G using xda app-developers app
Thanks for sharing. I saw yesterday in the changelog that both 10.1 and 10.2 where announced on FXP 242 (10.1 in beta and 10.2 in alpha), but I can't find the 10.2 download anywhere.
Maybe they don't publish public download links for alpha versions ?
Parkside said:
...no announcements, I can't keep it to myself. You'd do the same right?
Click to expand...
Click to collapse
Its safe to download huanshan cm file for our phone.(know that huanshan is code name for our phone)????
Sent from my ZTE Blade G using xda app-developers app
Yes take a look
karma123 said:
Yes take a look
Click to expand...
Click to collapse
Wooohooooo im so happy i cant wait to test itThanks to FXP team !
When i flash it im gonna make review wohoooooo
Sent from my ZTE Blade G using xda app-developers app
---------- Post added at 12:06 PM ---------- Previous post was at 11:58 AM ----------
karma123 said:
Yes take a look
Click to expand...
Click to collapse
Can you tell me what file to download??
Sent from my ZTE Blade G using xda app-developers app
Download this :- http://uploaded.net/file/7ntq0zp6/from/q3au96
Flashed and booted. Its nice. But some screen flickering while scrolling. Like in settings etc etc. But that can resolve with enable the " Disable Hardware Overlay" option from Developer Settings
What about performance ? Can you run antutu bench ? how much is free / used RAM ? etc.
thanks
Are mirrors allowed? Can somebody mirror this file? Im sorry but uploaded has failed me several times already...
mmm273 said:
What about performance ? Can you run antutu bench ? how much is free / used RAM ? etc.
thanks
Click to expand...
Click to collapse
Now only i flashed this. I dont have any apps installed. So performance is awsom now. Free RAM is 509 and used 333
ok, only for compare - what antutu score ? With stock ( fresh flash) i have 21 000...
Screen Flicker
Hi @Rajeev
I didn't experience screen flickering at ALL in ANY test builds so I find this really difficult to believe but I'm happy to take a detailed look at it ..
Log's plus video(so I can see what you mean) would be useful so I can get this possible ?issue? and if it is an issue then I'll get it resolved.
None whatsoever for me so this is a really weird issue....
Thanks
I have the flickering too ! And the phone often soft freezes. Seems like the app isnt updated anymore on screen. It can also be just the keyboard for example. Hiting recent tasks unfreezes it but systemui sometimes freezes until reboot.
Sent from my C5303 using xda app-developers app
uberlaggydarwin said:
Hi @Rajeev
I didn't experience screen flickering at ALL in ANY test builds so I find this really difficult to believe but I'm happy to take a detailed look at it ..
Log's plus video(so I can see what you mean) would be useful so I can get this possible ?issue? and if it is an issue then I'll get it resolved.
None whatsoever for me so this is a really weird issue....
Thanks
Click to expand...
Click to collapse
Hi Bro @uberlaggydarwin
Yes i am saying truth only.
1) While Scrolling in settings Its flickering like waves. But its not coming after Click the " Disable Hardware Overlay" Function.
2) When i press the Reboot option its rebooting but its rebooting like something weird in Screen..
3) Soft reboots happens multiple Times...
I know its a Beta release. I am not complaining . But answering ur question...
mmm273 said:
ok, only for compare - what antutu score ? With stock ( fresh flash) i have 21 000...
Click to expand...
Click to collapse
I'd like to see a screen of that score. Seems a bit too high. Sure you have the SP ?
You're using V4 ofcourse, my bad.
Bootloader
Just wondering if you are guys are using locked or unlocked bootloader? I'm locked with CWM and I'm wondering what the process would be of installing... (e.g. wiping /data...)
jakelooker said:
Just wondering if you are guys are using locked or unlocked bootloader? I'm locked with CWM and I'm wondering what the process would be of installing... (e.g. wiping /data...)
Click to expand...
Click to collapse
Hey, Make a backup, you need an unlocked bootloader for this. Then wipe all cache and data etc. then flash the rom on your phone
jakelooker said:
Just wondering if you are guys are using locked or unlocked bootloader? I'm locked with CWM and I'm wondering what the process would be of installing... (e.g. wiping /data...)
Click to expand...
Click to collapse
Well asfaik CM requires a custom kernel which can only be installed on a phone with unlocked bootloader. Hope ive helped.
Rajeev said:
Hi Bro @uberlaggydarwin
Yes i am saying truth only.
1) While Scrolling in settings Its flickering like waves. But its not coming after Click the " Disable Hardware Overlay" Function.
2) When i press the Reboot option its rebooting but its rebooting like something weird in Screen..
3) Soft reboots happens multiple Times...
I know its a Beta release. I am not complaining . But answering ur question...
Click to expand...
Click to collapse
LOG"S OR IT DIDN"T HAPPEN . I'm serious.
I'm downloading this release to test but I can't help much if you don't provide logs.
Are you sure its not auto-brightness being turned on as auto-brightness doesn't work very well in stock so the changes are probably more noticeable.
Reboots work perfectly fine for me..
On the recent test builds I haven't had a reboot issue but as you know the kernel is temporary so I'll redo it when 4.3 comes out....
WE NEED LOGS.