[Q] Specific game not working on new ROM - Atrix 4G Q&A, Help & Troubleshooting

Hello XDA Forum!
I'm a new member in the forum, recently iv'e discovered the inner geek in me and decided to explore the world of roms. (yes im a newbie lol)
I hope to contribute to the forum as much as i can.
Anyway, Here's the story:
I have a Motorola Atrix 4g of course and i'm using epinter's excellent cm 10.1 rom
The only problem i have is that my favorite game Leauge of Shadows isn't working. I had the game working on epinter's cm 10 rom based JB 4.1.2 with 2.6 kernel and the game works on other JB roms with 2.6 kernel. So i believe the problem is with the kernel. With the current kernel i have ( 3.1.10) the game start but crashes alot and touchscreen doesn't work.
So my question is, is there anyway to run this game? can i run a specific app in a 2.6 kernel will my device has 3.1.10?
I've tried to install diffrent kernel but failed to install for some reason.
Any help will be much appriciated!!

Hi! Welcome to the forums!
Short answer: Not yet.
Long answer: As you should know, anything with the 3.1 kernel is considered an (not so) early stage alpha. It isn't meant to be used as a daily driver, only as testing and development. Right now, the focus of the development is set into modem drops and audio issues, once all basic things are working, then they can focus on other things, like the issue you have.
Also, kernel is the main piece of software any device (computer, smartphone, etc) uses. on windows xp, the kernel is ntkernel.exe, on linux and android is vmlinuz.
So far the only solution is to install a rom that doesn't use the 3.1 kernel, such as cm10 (not 10.1), cm7 or early iterations of atrics

Thanks!
andresrivas said:
Hi! Welcome to the forums!
Short answer: Not yet.
Long answer: As you should know, anything with the 3.1 kernel is considered an (not so) early stage alpha. It isn't meant to be used as a daily driver, only as testing and development. Right now, the focus of the development is set into modem drops and audio issues, once all basic things are working, then they can focus on other things, like the issue you have.
Also, kernel is the main piece of software any device (computer, smartphone, etc) uses. on windows xp, the kernel is ntkernel.exe, on linux and android is vmlinuz.
So far the only solution is to install a rom that doesn't use the 3.1 kernel, such as cm10 (not 10.1), cm7 or early iterations of atrics
Click to expand...
Click to collapse
Thanks for the answer!

Related

[DEV][DEPRECATED][4.0]ICS 4.0.4 for the 4.0 (Build #3.5 up)

THIS THREAD IS DEPRECATED.
This project has move down, out of the alpha stage, to here:
http://forum.xda-developers.com/showthread.php?t=1950453
This thread is here for documentation purposes only! There are better builds at the new link, more detailed instructions, and support. Please direct your attention there! Thank you.
Warning! Flashing this may/will delete your /efs, which will causes major issues if you ever decide to return back to stock, so make sure you make a backup! If you don't know how, frankly you shouldn't flash this, as you need at least some experience just in case something goes wrong.
Team SuperNOva:
Oisis (helped us get over the final issue)
Zaclimon (first kernel dev, did a LOT of the preliminary work)
Neyodmium (helped us sort out that SGS sources that CAN be used for the 4.0, and helped pinpoint what needed to be replaced/fixed)
Me, hanthesolo (Rom dev, I will be providing updates, support, and other smaller things, so they can concentrate on the kernel, while I fix up the ROM)
The Back Story:
Firstly, excuse my cheesy biblical writing, I just have always wanted to write something in that format .
In the beginning (march 2012), there was hanthesolo. He saw the Galaxy Player forums, and all that he saw was good. This man started creating new work for the Gplayer forums, a and gained a small following. There was just one issue that concerned him: NO ICS!
In light of this, this man created a thread, to collect all ICS development, into one easy-to-read forum. Other began to follow him, zaclimon, Ijimaniac, and several others. Ideas flew fast and furious, but hope was waning quickly. A kernel would have to be created from scratch, a monumental task that had not been undertaken by any man so far.
All was quiet for awhile, and people began to slowly fade out, until only hanthesolo and zaclimon remained, slowly trading ideas and guesses over several weeks. Then a new disciple arrived: neyodmium. This korean (?) developer brought a different kind of kernel experience to the trio, and development began in earnest, with zaclimon and neyodmium trading work, while hanthesolo contributed where he could. One unsurmountable issue arose: this magnificient kernel, the likes of which had never lit up these forums before, would merely boot into recovery, not into Android.
Then Oisis came around, hearing our desperate cries for help. Like a moses, he guided his flock in the right direction, squashing issue after issue, until a monumental day arrived: August 13, 2012. On this day, ICS was finally created in Cyanogen's own image, and it was good.
Then increased development began, with hanthesolo squashing CM9 bugs, while zaclimon, neyodmium, and Oisis working feverishly on the kernel.
But an issue occurred, a wrench in the works. Thine enemy's name is GL, SuperNOva. GL would not cooperate, acting as a barrier between usable ICS, and frustrated efforts to fix it. But one day, the magical variable was flipped, and the builds booted! About this time there was a github mishap involving a bad I9000 push that stopped things for about a week, but that's another story.
What happens next? I dunno, but I will update this story when it happens .
NOTE: This does NOT represent anyone's political or religious standpoint, or the way anyone is viewed. It was created as a humorous way to explain our situation to users.
The fix list:
ROM:
Bluetooth (should be easy)
HW acceleration (easy, just neds to be implemented)
Camera (will take awhile)
Kernel:
HW acceleration (Oisis is working on it)
Drm manager (needs to be fixed before market can be used!)
US home button
Boot to recovery (very annoying when trying to flash builds)
Camera (?)
Changelog:
Build#1:
Initial release, basically everything is broken.
Build#2 changelog:
Finally fixed bootlooping that was plaguing our github
fixed ALL GL crashing and oddness
Fixed/improved sound (if it was broken)
Fixed Browser (slow, but usable)
Waiting on a new kernel to readd GL and/or HW acceleration.
FM radio! Just download the spirit FM app, you can find it for free on XDA
Build#3 changelog:
Fixed av codecs (videos should play just fine now, as well as youtube)
General code cleanup and optimizations
Build #3.5:
Performance improvements and some code cleanup.
Download links:
Build#1:
CM9: http://www.broken-arrow.pl/oisis/aokp/YPG1-CM9-OiSiS-build-02.zip
Kernel: http://zhshibenzhu.host22.com/tuchuang/cm9_kernel.tar
Build#2:
CM9: http://www.mediafire.com/download.php?lu33uubm6der2j9
Kernel: Flash the one above.
Build#3:
http://www.mediafire.com/download.php?96yk0e3y8cqzj1b
New kernel: http://forum.xda-developers.com/attachment.php?attachmentid=1298676&d=1346633739
Build #3.5: http://www.mediafire.com/download.php?oscyfde4w364dj6
Install instructions:
Special thanks to daniel644 for the video and his high praises of me .
If you get stuck in recovery, flash a GB kernel, it will boot into recovery, simply hit "reboot". When it bootloops, boot into download and flash the CM9 kernel.
Resources:
Manifest.xml (so you can just simple "repo sync" instead of git pulling every time we have a new commit):http://forum.xda-developers.com/attachment.php?attachmentid=1278615&d=1345762041
Wiki link (please help improve it!): http://forum.xda-developers.com/wiki/YP-G1
Github repo: https://github.com/TeamSupernovaSGP
NOTE: this is just the modded files. You need to full CM9 source before you can compile!
Contact us at: [email protected]
Please only emails us with valid questions or useful support!
port kernel 3.x from Galaxy S to SGP4.0 should be easy, coz hardware parts are almost the same, but SGP5.0 conpoments arent the same, the way for SGP5.0's 3.x kernel should be harder.
tdmcode actually has a booting CM9 build. I believe that wifi and sound work, but nothing else. His vendor tree and device tree are here:
https://github.com/tdm/android_vendor_samsung_ypg1/tree/ics-cm
https://github.com/tdm/android_device_samsung_ypg1/tree/ics-cm
He just never released it as it is still not very functional.
Maybe it would be easier to just take his source and try and fix the issues and make it fully working. Because getting an AOSP bringup to boot is most of the work; the rest should be easier to do.
Would it not be easier to port over a rom, as the hardware is the same? It would at least be more helpful, because if we could create a guide, we could port other roms over very quickly!
Sent From my Galaxy Player running StratusRom using XDA
klin1344 said:
tdmcode actually has a booting CM9 build. I believe that wifi and sound work, but nothing else. His vendor tree and device tree are here:
https://github.com/tdm/android_vendor_samsung_ypg1/tree/ics-cm
https://github.com/tdm/android_device_samsung_ypg1/tree/ics-cm
He just never released it as it is still not very functional.
Maybe it would be easier to just take his source and try and fix the issues and make it fully working. Because getting an AOSP bringup to boot is most of the work; the rest should be easier to do.
Click to expand...
Click to collapse
I built it and I will test to see if it works (I'll use the newest kernel from cm7)
I am going out on a limb here...could we use the cm7 kerbel to help port a workable ics kernel for a galaxy s port? Once thats done cooking up a working rom should be easy and quick.
Sent From my Galaxy Player running StratusRom using XDA
One thing
Ambitious project hanthesolo
one thing: could i suggest that the title of this thread should be Operation: ICS for Galaxy Player 4.0 or something?
Okay, I may rename it. ICS is far more feasible than you think. Once we get a working kernel running (which will be soon) we can port ics over from the galaxy s (which would be best, as once it boots most features would work). I hope by the time school starts up ics will be functional as a daily driver. I may not be able to help a ton, as most of this revolves around making a working kernel, but I will try to help where I can.
Sent From my Galaxy Player running StratusRom using XDA
I can't get it to boot. (stuck at samsung logo) I think it would be better to build it from source instead of porting over.
Its stuck at the samsung logo because the kernel probably didnt work. It has happened to me before, we need to compile an ics kernel. The galaxy s one almost works, we just need to find out what makes it fail to boot.
Sent From my Galaxy Player running StratusRom using XDA
We can use the BML/STL partition layout in waiting for yaffs2. We can use entrophy's device tree as base for it(we can ask for help from him too)
https://github.com/Entropy512/android_device_samsung_infuse4g
Thanks for looking into that zaclimon! I will pm him and see if he would be interested. I willxupdate the opxwoth info from various people/sies as I get it.
Sent From my Galaxy Player running StratusRom using XDA
Would a tablet kernel made from scratch to run ICS do anything or does it need to be more kosher with Samsung and their device tree?
rozelle25 said:
Would a tablet kernel made from scratch to run ICS do anything or does it need to be more kosher with Samsung and their device tree?
Click to expand...
Click to collapse
I dont quite understand what you mean. Can you elaborate please?
Sent From my Galaxy Player running StratusRom using XDA
Hey I've been looking at this situation too and science coming back after q long time in the Xperia play forum I decided I wanted to help I found this guide about compelling ics http://www.freeyourandroid.com/guide/compile-ics but 1 problem I need to find the device and vendor tree on github but I've never used githubn before so need some help with that so if I can help please let me know
minipot said:
Hey I've been looking at this situation too and science coming back after q long time in the Xperia play forum I decided I wanted to help I found this guide about compelling ics http://www.freeyourandroid.com/guide/compile-ics but 1 problem I need to find the device and vendor tree on github but I've never used githubn before so need some help with that so if I can help please let me know
Click to expand...
Click to collapse
If it was that easy, webwould have ics today on our devices. The reason its been so difficult is that we need to combine/port githubs to create a working kerbel, which is a lot harder than it sounds. Thanks for the link! I will put it in the op.
Sent From my Galaxy Player running StratusRom using XDA
Im guessing u mean we could make a rom using that but first we need a kernel that qill work with it
Yeah. Porting a rom is easy, but getting a working kernel is not. Once we get a working kernel we can port as many roms as we please.
Sent From my Galaxy Player running StratusRom using XDA
Well I don't think it is that hard if we base ourselves from other devices trees like entrophy's one. I think he removed RFS from his initramfs which leaves him only ext4. Then he used a script that would convert the partitions to ext4 when installing CM9. I think it is the same things than with the mmc partitions (I think this is a part of why the 5.0 got ICS sonner than 4.0)
EDIT: And I think it's better to build it from source the first time. (instead of porting for the case of CM9 for example.)
Yeah, I was just talking comparatively. Has anyone begun working on this yet? I have been researching a LOT (the best thing I can do to help right now), but since my knowledge is limited on kernels, i cant help with that riht now
Sent From my Galaxy Player running StratusRom using XDA

[Q] Kernels and Android Versions

I'm not understanding how kernels and ROMs connect. Can someone give me some extra insight?
[Hardware] <-- Unique to every phone
--
[Kernel] <--- Tells the OS how to talk to the hardware
--
[ROM] <--- Slightly confused. Is the OS in the Read only Memory, or has this term changed its "street" meaning?
I understand that most ROMs (e.g. CM7 and CM9) include both the kernel and the ROM, but can you flash these separately too?
I have a 1.5 year old thunderbolt that's rooted, and has CM7 which is based on gingerbread. I believe HTC has also released the kernel as open source, which is probably the reason I have CM7
Anyway, I guess what I'm looking for is an answer/guide/forum that explains why I can't install newer versions of android onto the already working/open source kernel I'm already running. Is it accurate to view the kernel as all the phone's drivers, or just the CPU driver? If that statement is true, why can't I load ICS or Jelly Bean onto my already existing set of drivers?
I'm thinking about starting a Wiki on this if 1) it doesn't already exist, and 2) I can wrap my brain around it enough to share with others!
Thanks to anyone with a response!
shadowrelic said:
I'm not understanding how kernels and ROMs connect. Can someone give me some extra insight?
[Hardware] <-- Unique to every phone
--
[Kernel] <--- Tells the OS how to talk to the hardware
--
[ROM] <--- Slightly confused. Is the OS in the Read only Memory, or has this term changed its "street" meaning?
I understand that most ROMs (e.g. CM7 and CM9) include both the kernel and the ROM, but can you flash these separately too?
I have a 1.5 year old thunderbolt that's rooted, and has CM7 which is based on gingerbread. I believe HTC has also released the kernel as open source, which is probably the reason I have CM7
Anyway, I guess what I'm looking for is an answer/guide/forum that explains why I can't install newer versions of android onto the already working/open source kernel I'm already running. Is it accurate to view the kernel as all the phone's drivers, or just the CPU driver? If that statement is true, why can't I load ICS or Jelly Bean onto my already existing set of drivers?
I'm thinking about starting a Wiki on this if 1) it doesn't already exist, and 2) I can wrap my brain around it enough to share with others!
Thanks to anyone with a response!
Click to expand...
Click to collapse
You are correct about the ROM, but ROMs also include the kernel (if it didn't, or no kernel was flashed separately, the device would not boot). Yes, other kernels can be flashed on your existing ROM, but it's not necessarily going to be compatible.
Sort of, but there's a lot more than that. See here and here. Later versions of Android will require newer drivers,etc. which the existing kernel won't provide (they'll be outdated). Back porting and additional coding is theoretically possible, but insanely difficult (many times). Even after this some things may still not work.
Thanks for the insight, I was able to get a lot deeper into this with those links. For anyone else wandering down a similar path, you might as well stop now! Here are a few links:
http://forum.xda-developers.com/showthread.php?t=1039217&page=2#17
http://www.cs.uwc.ac.za/~mmotlhabi/avmk.pdf
http://www.iteachandroid.com/2012/01/what-is-firmware-rom-and-firmware.html
So, if anyone else is still listening, I do have two more questions:
Do any phones have truly open source drivers? (a.k.a. higher probability of allowing old hardware to work with new android OS)
Is there any way to determine which phones will be supported by the custom-ROM community early on? I know the Nexus line doesn't have vendor modified code, is that the direction which would have the highest probability to stay at top of the Custom ROM curve without upgrading devices every year?
Thanks again for any insight! I hope I'm posting this in a Newb-Friendly forum!
shadowrelic said:
Thanks for the insight, I was able to get a lot deeper into this with those links. For anyone else wandering down a similar path, you might as well stop now! Here are a few links:
http://forum.xda-developers.com/showthread.php?t=1039217&page=2#17
http://www.cs.uwc.ac.za/~mmotlhabi/avmk.pdf
http://www.iteachandroid.com/2012/01/what-is-firmware-rom-and-firmware.html
So, if anyone else is still listening, I do have two more questions:
Do any phones have truly open source drivers? (a.k.a. higher probability of allowing old hardware to work with new android OS)
Is there any way to determine which phones will be supported by the custom-ROM community early on? I know the Nexus line doesn't have vendor modified code, is that the direction which would have the highest probability to stay at top of the Custom ROM curve without upgrading devices every year?
Thanks again for any insight! I hope I'm posting this in a Newb-Friendly forum!
Click to expand...
Click to collapse
For both your questions, the Nexus-line devices would be the way to go. They usually have everything working on new Android versions the soonest, and Google always releases their code, etc.
Hi
i can use linux kernel (zimage) to update android kernel if yes ,how ?
thnx

[Q] General question regarding kernels and android releases

Hi! This is maybe a general dev question, but I'd like to get an answer anyway:
what is exactly the link between an Android release and the kernel it works upon?
I noticed most recent releases use 3.0+ Linux kernels, and others (like the DSCs) use the Phoenix Universal Kernel, which is based on a 2.6.35... So I wonder: is ICS/JB in any way dependant on "newer" kernels?
I understand the answer must be closer to "no", since the pre-alpha build also uses a fork of the PUK, but the fact that it uses a *different version* makes me wonder how much work does it take to get a kernel ready for a newer release, and most importantly... why?
Thanks a lot! Total n00b here, but eager to know more.
Newer kernel not required at least for ICS.
All GB/ICS kernels are based on this kernel (and it's a Dell's lie about using same sources for 407 release as SoD was fixed there without switching timer source):
http://opensource.dell.com/releases/streak/4.05_and_4.07/
kibuuka successfully applied kgsl/genlock patch and it's the only thing actually needed for ICS.
List (a bit old) of changes in Phoenix kernel and later derivatives:
http://forum.xda-developers.com/showpost.php?p=25291276&postcount=3812

[Q] CM vs. Omni vs. AOKP/RR stability

Hi guys,
before I start: this is not supposed to be a "What's the best ROM?" thread.
I want to update my i9100 to a "stable" Kitkat ROM (if such a thing exists). The major ROMs seem to be CM11 (unofficial), Resurrection Remix and Omni ROM. I have followed the CM discussion for a long time and the Exynos SoC was always an issue to provide a stable ROM. I don't care that much about the ROMs individual features, but I DO want all basic hardware features to work (tethering, camera, etc.)*.
So, my questions:
- Do all these ROMs have the same hardware/drivers related (!) bugs and issues?
- What are the current issues (if any)?
- Can any one of these ROMs be used as a daily driver (i.e. everything working)?
Thanks
Ralf
Edit: Except for TVout obviously.
No.
As far as daily driver is concerned.
And yeah most likely all kk roms will have some bugs.
Sent from my GT-I9100 using Tapatalk 2
I'm on slimkat sabermod by fusionjack, 4.4.2. I'm using it as a daily driver with no problems. As far as exynos problems, correct, all custom ROMs which are not stock based experience the same kind of issues. However I haven't had any problems (reboots etc) since I've been on KK for a week or so.
As has been said many times on this forum.... Flash it yourself and see. What is acceptable to one (say me) is not acceptable for another (say corruptionfreeindia).
Sent from a galaxy far, far away
Can you elaborate on the Exynos related probems? What are they?

Seeking for a rather recent CM release that fully supports Bluetooth Phone Call !

palmbeach05 said:
CM dropped official support due to kernel stability issues. I remember we were discussing ROMs. 7.2 was, according to CM, the last stable version. Due to all the changes when everything became 4.0, the kernel became unstable on our device. Our devs have created a kernel that is stable enough for daily use, but not stable enough for an official CM. You do have CM9, 10, 10.1, 10.2, and 11 that are stable. CM12 needs work before being recommended for daily use.
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the information, glad to see that i can still get support for this device. :good:
I'm trying to get general information for the last 2 days, reading especially the Q&A and development sections in the forum . If i understood correct;
* There's a new kernel being developed named as [KERNEL] [3.1.10] as you mentioned in your post. This new kernel seems nearly perfect, it just has these 3 downsides regarding the given information on its own topic:
1) HDMI [post-poned] (Nvm, I don't need it)
2) Fingerprint ROM Libs+Framework [work in progress] (Nvm, I don't need it)
3) Flash [work in progress] (Camera flash? It would be nice, but still not mandatory for me)
So i thought i could try the newest unofficial CM releases based on this new kernel. I checked the most-used ones in the development section for CM11, CM10.1, CM10, CM9. But i learned a very disappointing thing in the posts. If it's true, although bluetooth is operable for data transfer, it is NOT working for voice, meaning that i won't be able to use it in my car. :crying:
Other negatives are not that important, but GSM calls over bluetooth is very necessary for me. Because it's a security issue, as most of all need to use our phones while driving! So i regrettably had to eliminate the CM Roms which use this new kernel for now!
I need a Rom that is stable enough and has a wide hardware support such as necessarily:
1) Calls over bluetooth
2) GPS
3) Wi-fi tethering (USB tethering is not important)
Plus; android version must be new enough to support some of the applications. I found out that i need at least CM10 (Android v4.1) for the applications that i need to install.
At the end i can summarize my choices as follows:
* CM7.2 based Roms: All of them seem very stable, but some of my applications doesn't work on Android 2.3, so negative.
* CM9 based Roms: New kernel or not, Android v4.0 is old for a few of my applications. So, negative.
* CM10 based Roms: "CM10 (JellyBean) for Atrix" from @epinter seems very appropriate for me. It doesn't use the new kernel and Android v4.1 is sufficient (recent enough) for my applications. POSITIVE
* CM10.1 based Roms: "CM 10.1(Android 4.2) for Atrix" from @epinter could be very good, but it uses the new kernel. So, negative.
* CM11 based Roms: "CM 11 ( Android 4.4.4 ) for Atrix (BigPart)" from @Zn7mkUKzN1r8aCIV would be perfect, but i think it also uses new kernel, as it's indicated that ".BT phone call" is NOT working. So, negative.
* CM12 based Roms: I saw the "Mokee For Atrix 4g (Android L 5.0.2) (preview)", but as you see, it's not an option for me yet. So, negative.
If i didn't misunderstood what i've read till now, the most appropriate Rom seems;
"CM10 (JellyBean) for Atrix, By epinter" for me.
Link: http://forum.xda-developers.com/showthread.php?t=1781970
I think it would be better for me to continue on its own Q&A thread, I don't want to ruin this CM7.2 thread anymore.
Please share your opinions, i really need your advises.
EDIT: Oopss, basic kernel on CM10 seems lacking HW acceleration. So, i can't play NFS Most Wanted, Dead Space, Max Payne etc. games properly, right? What about navigation apps like iGo, Sygic, etc?
EDIT: This post was originally in the "CM7 Q&A" section and moved here as a seperate thread. My aim is not to find the "Best Rom ever" etc., i just seek for a Rom that's similar to the current awesome CM7, which fits my needs. I think i could find the best title for this post.

Categories

Resources