Hey guys, my question is essentially what the title says. I find that in CM10 based roms, that whenever I use the stock cyanogen mod browser, it automatically goes into desktop mode (and is stuck there. The desktop mode checkbox, however, is unchecked.) I'm fairly sure it worked before I used the touch pad fix here - http://forum.xda-developers.com/showthread.php?t=1893343 - So I think it might be a framework/build.prop issue, but I'm not sure. I've been looking to fix this problem everywhere but haven't really been able to find a solution. Do you guys have any idea what the fix might be?
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
smokerman said:
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
Click to expand...
Click to collapse
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
fishvtt said:
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
Click to expand...
Click to collapse
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Hey, smokerman, would you know how to mess with .jar files. I kinda want to go exploring to see if I can do anything.
you have here a simple guide by @CriGiu
http://forum.xda-developers.com/showthread.php?t=2322231
could help you.:good:
fishvtt said:
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
Click to expand...
Click to collapse
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
Oh ok, I'll try testing that out.
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
All right, well that seems to do the trick. When I try to use the touchpad activator app, it gives me the "error 5 expected reciever of type android.view.ViewRoot, but got android.view.ViewRootImpl". But, Dead Trigger works perfectly how it's supposed to, and the stock browser is using the mobile version now. Just remember to make the necessary build.prop changes as outlined in Fahrenheit's guide.
Related
*** This thread is now outdated ***
Please follow this link for a much better solution - Also, be sure to hit the Thanks! button to show your support for DizzyDen's excellent work!
********************************************************************************
I have removed all the files from this post and I encourage everyone to migrate to DizzyDen's superior solution. If for some reason you are unable to use Dizzy's tool you can PM DizzyDen or myself (Martian21) and one of us should be able to get you want you need.
********************************************************************************
[Original Thread]
I have seen several threads regarding this topic and thought I'd try to consolidate as much as I can in one place.
Credit for the original IMEI work goes to mthe0ry His original thread is here.
Because the NOOK Color is not a phone it does not have an IMEI number. This is why some apps that check for an IMEI number do not work on the NOOK.
Thanks to the work of mthe0ry and now DizzyDen it is possible to modify the framework.jar file in order to create a fake IMEI number on the NOOK Color. Doing so will allow programs such as Swype Beta, the free version of the XDA app, HBO GO, and the Xfinity app to work on the NOOK Color.
Unfortunately you need to have a framework.jar file that matches the ROM you are running as changes to the framework between ROMs can (and probably will) cause problems.
[See DizzyDen's thread for the IMEI generator tool]
*** This is mostly obsolete now that Dizzy's tool handles replacing the framework.jar file and backs up your original file - but I will leave it here just in case it is still useful to someone. ***
Installation:
You will need a file manager with Root access such as Root Explorer.
Download the framework.jar file for your Rom.
Unzip the file and transfer the framework.jar file to your NOOK Color.
Navigate to /System/framework using Root Explorer.
Mount the /System/framework folder R/W.
Rename the original framework.jar to framework.jar.bak.
Using Root Explorer, copy the new framwork.jar file.
Paste the modified framework.jar into /System/framework.
Long press the newly copied framework.jar and select "Permissions".
Change the permissions to match framework.jar.bak [rw-r--r--].
Mount the /System/framework folder R/O.
I recommend you reboot your NOOK although resetting the launcher may be enough.
For those that used my original files or the ones from mthe0ry, the original IMEI used in those files is "12-34567-89012-45". If you wish to continue using this IMEI number [NOT RECOMMENDED] you can manually enter it into Dizzy's tool.
Martian21
Request pls
I know that nightly 78 was the last nightly that runs on .29 kernel all the new nightlys 80,82,83 and 84 need uboot 1.2 and .32 kernel. I have read that some people have been experiencing problems on these builts. Also being that .32 kernel is still label beta i would like to ask you if you could please make a framework for nightly 78. I have attached the framework file from my nightly 78. Thank you
Finally was able to reboot after copying framework82. Was able to sign in but have yet to play a movie. I get stuck in the spinning circle.
Sent from my Vision using XDA Premium App
MACLUIS1 said:
Finally was able to reboot after copying framework82. Was able to sign in but have yet to play a movie. I get stuck in the spinning circle.
Sent from my Vision using XDA Premium App
Click to expand...
Click to collapse
I did a total wipe, stock 1.2 install, then a second total wipe before n82. I then added the modded framework and HBO GO worked really well! But, after adding Dal's 5/13 OC, I then got the spinning circle problem you describe.
I tried re-flashing just n83 to fix it (without Dal's OC), and re-installing the modded framework, but the spinning circle problem remains.
I can't say for sure that the OC kernel broke it -- it could be one of a dozen apps I installed? -- but it's certainly the leading culprit in my case. The 5/13 OC kernel also appeared to break a few of my other apps as well (360 Live failed too, but started working again after I returned to vanilla n83).
I'm going to start the entire process over again tonight to try and narrow down the problem...
I have the 5/13 OC installed but HBO GO is now working on my Nook. Just need to uninstall and reinstall HBO GO. Worked like a charm for me.
Sent from my Vision using XDA Premium App
MACLUIS1 said:
I have the 5/13 OC installed but HBO GO is now working on my Nook. Just need to uninstall and reinstall HBO GO. Worked like a charm for me.
Sent from my Vision using XDA Premium App
Click to expand...
Click to collapse
Didn't work for me -- still stuck on spinning circle after intro clip plays.
I used TiBu to wipe data, uninstall, then install app. Did you reboot in between, or take any other steps?
martian21 said:
I am using the same IMEI of "12-34567-89012-45" that mthe0ry used.
Click to expand...
Click to collapse
So every one gets the same IMEI?
We are going to fix this in CM soon. Please don't break every other program that uses IMEI to identify a UNIQUE device! I suggestion that no-one uses this. You are really playing with fire here.
nemith said:
So every one gets the same IMEI?
We are going to fix this in CM soon. Please don't break every other program that uses IMEI to identify a UNIQUE device! I suggestion that no-one uses this. You are really playing with fire here.
Click to expand...
Click to collapse
I do appreciate your warning (and, as always, all your hard work), but Dal came out and stated plainly that an IMEI solution would not get added to cm7 builds, so the rest of us took his word for it and had to solve the problem some other way.
Now, if you're saying that the solution WILL be built into one of the next few nightlies -- with unique IMEI's -- then that's fantastic!!
However, without it, there's currently no other way to run HBO GO, Swype, etc -- unless we compile our own framework.jar... which isn't an option for some of us noobs.
Has work already begun on a better solution?
paleh0rse said:
I do appreciate your warning (and, as always, all your hard work), but Dal came out and stated plainly that an IMEI solution would not get added to cm7 builds, so the rest of us took his word for it and had to solve the problem some other way.
Now, if you're saying that the solution WILL be built into one of the next few nightlies -- with unique IMEI's -- then that's fantastic!!
However, without it, there's currently no other way to run HBO GO, Swype, etc -- unless we compile our own framework.jar... which isn't an option for some of us noobs.
Has work already begun on a better solution?
Click to expand...
Click to collapse
I meant the static IMEI hack as presented in this thread. This hack will not be added to CM7.
We are working on a real solution as we speak.
dalingrin said:
I meant the static IMEI hack as presented in this thread. This hack will not be added to CM7.
We are working on a real solution as we speak.
Click to expand...
Click to collapse
You're a good man, thank you!
dalingrin said:
I meant the static IMEI hack as presented in this thread. This hack will not be added to CM7.
We are working on a real solution as we speak.
Click to expand...
Click to collapse
This is great news!!!
I will cease and desist as soon as it it completed. Obviously the best thing would be for people to follow mthe0ry's instructions and do this themselves (it's really not that hard) using their own unique IMEI number. That said I'm happy to continue the "hack" method for those who don't wish to do it themselves.
Yes, having multiple devices with the same IMEI could become problematic but so far it's worked for the apps people want. I do appreciate the warning as I probably wasn't as clear about the "hack" nature of this in the OP as I should have been.
Martian21
jzibit17 said:
I know that nightly 78 was the last nightly that runs on .29 kernel all the new nightlys 80,82,83 and 84 need uboot 1.2 and .32 kernel. I have read that some people have been experiencing problems on these builts. Also being that .32 kernel is still label beta i would like to ask you if you could please make a framework for nightly 78. I have attached the framework file from my nightly 78. Thank you
Click to expand...
Click to collapse
Attached:
enjoy
slide it
please disregard below. in reading the thread better I can see it's not for swype at all but for setting the nook up with an IMEI.
I don't mean to be rude, but why not just use slide-it? I'm cognisant of the simplicity of swype as I use it daily on my Galaxy S, but slide-it is nearly as good and works without fault on the nook (rooted stock and CM7) without any mods.
smiley1960 said:
please disregard below. in reading the thread better I can see it's not for swype at all but for setting the nook up with an IMEI.
I don't mean to be rude, but why not just use slide-it? I'm cognisant of the simplicity of swype as I use it daily on my Galaxy S, but slide-it is nearly as good and works without fault on the nook (rooted stock and CM7) without any mods.
Click to expand...
Click to collapse
Many of us use this hack for HBO GO, not just Swype...
First zip file is for which Rom?
Sent from my NookColor using Tapatalk
RASTAVIPER said:
First zip file is for which Rom?
Click to expand...
Click to collapse
Opps - Typo. It is for CM7 Stable 7.03
I added a note to the first post. I'll try to fix the file name when I get home tonight. I'm sure there will be 1 or two more nightly builds as well.
paleh0rse said:
Many of us use this hack for HBO GO, not just Swype...
Click to expand...
Click to collapse
It's also needed for a number of Gameloft titles.
Rodney
Concerns about unique devices make me wonder... I have a broken HTC Kaiser sitting on a shelf above my desk. It will never again be a functional device, but yet it has it's own unique IMEI.
Does the IMEI alone tell apps anything about what sort of device belongs to the number? If not, then it seems that I could use the IMEI from that Kaiser or the broken G1 I have.
It doesn't seem like these apps know anything about the device from the IMEI alone, given that people have been implementing this fix with no repercussions. That means apps probably don't check any hypothetical IMEI-device info against what's recorded in the build.prop, so this seems like a safe, workable solution for those of us with defective devices on our shelves.
Is there a way to make this work on a ManualNootered nook with 1.2, or does it only work if you have a custom rom.
Thanks
integrate in CM7
could you not ask the maintainers of CyanogenMod to integrate this in the future nightlies?
they would probably welcome the added functionality
Hi.
Atm i am developing a bit, but i try to find the best kitchen for the SGS2. I mean programs to edit APKs, deodex, sign, align etc...
I am using "dsixda's kitchen" atm, working good, but there are some problems.
When deodexing the newest ICS (4.0.3 LPB) samsung keyboard gets force closes after flashing. Also WIFI isnt connecting.
Moreover i am flashing CF-Root, but e.g. Titanium backup isnt working.
Maybe its because of this kitchen, i dont really know... so there is the question to you: what do you use to deodex etc or what do you know? i used something from "sicopat" in the past, but i think thats only for gingerbread.
Thank you for answering,
greetz, Cloud2F
Cloud2F said:
Hi.
Atm i am developing a bit, but i try to find the best kitchen for the SGS2. I mean programs to edit APKs, deodex, sign, align etc...
I am using "dsixda's kitchen" atm, working good, but there are some problems.
When deodexing the newest ICS (4.0.3 LPB) samsung keyboard gets force closes after flashing. Also WIFI isnt connecting.
Moreover i am flashing CF-Root, but e.g. Titanium backup isnt working.
Maybe its because of this kitchen, i dont really know... so there is the question to you: what do you use to deodex etc or what do you know? i used something from "sicopat" in the past, but i think thats only for gingerbread.
Thank you for answering,
greetz, Cloud2F
Click to expand...
Click to collapse
The keyboard ICS issue was fixed a month ago in the kitchen.
dsixda said:
The keyboard ICS issue was fixed a month ago in the kitchen.
Click to expand...
Click to collapse
so you mean i am using an old version of your kitchen? thx for the answer
// i am using 0.188, so its the newest version... trying all different types of rom now, zipaligned, nonzipapligned, newer kernel etc....
WANTED: Users to port SGS roms to the 4.0. You will need to know how to complete a full restore if something goes wrong, but that's it. I cannot go through the forums searching for good SGS roms, as I have several threads to manage, and a rom to work on. The steps are easy for you though, and if you port a rom I will add it in the OP.
First of all, I want to say that I take NO credit on any of these roms. All I did was port them over and add speed tweaks, or added ones that users have ported. If the rom creators or mods have any issue whatsoever with this thread, I will happily take it down, even though I think it would be a large contribution to the 4.0 community. I will continue to update this forum with info as I go along.
I, after a fortunate afternoon of boredom, have managed to successfully begin porting I9000 roms to our devices! Fortunately, they are similar enough that it boots without any modifications. I will put up here any ports that I make, and any that the users create. Note that these WILL NOT BE UPDATED! These are one-time ports, to be used and improved upon by the community. Anything that is broken now will stay broken, unless a user decides to fix/update it, then I will include it in the OP.
What *should* work in all ported roms:
wifi
GPS
home buttons
everything else
What will probably *not* work on ported roms:
Bluetooth
Camera
backlight on buttons
Ported roms:
~GamerzRom odexed V11-~
Link to original thread: http://forum.xda-developers.com/showthread.php?t=1656081
Added:
V6 supercharger, and build.prop tweaks from it.
init.d tweaks from my rom
ext4 filesystem
Advanced mount options
Auto zipalign and Database optimize
Removed apps that do not work on our Player (such as the Dialer)
Download:http://www.mediafire.com/download.php?ctuu2w295w2xlk6
~Saurom~
Original thread:http://forum.xda-developers.com/showthread.php?t=1388342
Ported download link:http://www.mediafire.com/download.php?csua40hkg1r3m86
~JellyBeanRom~
Original thread: http://forum.xda-developers.com/showthread.php?t=1260709&highlight=gb
Ported download link:http://www.mediafire.com/download.php?mgec81f3ifck221
~Ario Rom (ported by ChaosChris)~
Ported thread link : http://forum.xda-developers.com/showthread.php?p=29950015#post29950015
Original thread: http://forum.xda-developers.com/showthread.php?t=1536558
To use these Roms:
You MUST use a Gplayer kernel! GT-I9000 kernels will not boot!
A full wipe may be necessary with some roms if you encounter issues.
Converting (for porters)
Steps:
1. Download wanted rom (must be GB)
2.Move the zip to the internal sdcard
3.Reboot into recovery
4.Flash zip, then boot into download mode
5.Flash a SGP kernel
6. apply my mod pack to the rom, by either copying/pasting the system directory over the SGS rom's system directory, or by pushing it via adb, (eg. adb push /path/to/modpack /system).
7. Profit!
NOTE: after applying this, porters may want to remove non-working packages such as the dialer and mms, as they may cause issues with the end result if they are kept in. Do not delete phone.apk though!! This is required for the camera and some other things, and breaks stuff on certain roms. You have been warned.
NOTE: If you use this modpack, please give me credit, and link back to this thread so that more people can use it. Also, you should probably link back to the ported rom's thread as well, to avoid "ripping off" those devs.
Modpack:
Changelog
V1-
Preliminary release
Fixes wifi and GPS
Includes v6 supercharger and init.d tweaks
V2-
fixed vold.fstab so sdcard is mounted properly.
Download:
ModpackV1:
http://www.mediafire.com/download.php?diaq6im4i18ktf7
NOTE:Note that this is preliminary. It fixes everything listed, and attempts to fix some broken things. Your mileage may vary. This is not a cwm flashable zip! you much extract and adb push this over the existing system directory. This is mainly intended for porters, so users apply at your own risk. This will work, but is a very early release.
Modpack V2 (thanks to ChaosChris):
https://docs.google.com/open?id=0B9OVlH2Pl76DZk5Pa3lJVXlrYzA
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
iJimaniac said:
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
Click to expand...
Click to collapse
Yeah, it says that because it includes semaphore's kernel, which raises the max rom to 380, which we could do on our kernel's, but apparently that breaks a lot of stuff if you go much further then 350 (according to klin).
is the wifi fixed in your port or do we have to do your fix after flashing?
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
check over in the operation: ics for the 4.0 thread I believe they are already attemping to use the cm7 kernel to boot a cm9.
daniel644 said:
is the wifi fixed in your port or do we have to do your fix after flashing?
Click to expand...
Click to collapse
Yeah, it is fixed before you flash. Once I manage to iron out a few more bugs, I will probably release a "conversion pack" that fixes all the issues. I already have one that fixes wifi and gps, but bluetooth and camera have me stumped, and I do not want to replace the entire hw/lib folder, because some of these roms have lib optimizations, but I may have to.
Sent from my GT-I9000 using xda app-developers app
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that zaclimon has tried it, and he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable. I also believe that he said the issues may have been rom based, so here it goes, and wish me luck.
Sent from my GT-I9000 using xda app-developers app
hanthesolo said:
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that daniel has tried it, abd he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
zaclimon said:
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
Click to expand...
Click to collapse
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course . A lot farther out there, but maybe I can use a SGP5.0 kernel to get it booting. A LOT less likely, but hey, i'm experimenting .
EDIT: I cannot try ICS, since I need to reboot into recovery a second time, and I cannot do that, as I have the intl bootloader on my US device, and it would require it to be booting first.
hanthesolo said:
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course .
Click to expand...
Click to collapse
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
zaclimon said:
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
Click to expand...
Click to collapse
Well, thet camera shows a preview, but fails when a pic is taken, for some reason. Bluetooth does turn on, but is not seen by any other devices, and cannot scan for others either. I did do a little tweaking with Gamerz, so it will be even faster than it was already, which is pretty blazing! I have 2 more that I can put up (I have a preliminary package that I just adb push over the system files that works for now). I have also gotten the camera apk onto my rom, and it works really well! It doesn't take 5 MP pics, or record 720p video (which may be because I am using Terrasilent, which reduces the amount of Vram the system can have), but tap to autofocus and everything else works pretty well. I have a sneaking suspicion that the camera is soft limited, not hard-limited.
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
zaclimon said:
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
Click to expand...
Click to collapse
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
hanthesolo said:
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
Click to expand...
Click to collapse
Here's the vold.fstab if you need it
Okay, it seems that the zip hosed my partitions (converted them to yaffs2 and mtd), so I am going to perform a full restore, and just keep porting GB roms. As soon as you can get the usb gadget driver working, zaclimon, I guess I can keep working on it, but for now I will just keep to GB.
Two more roms up! I will probably not port any other unless I see an especially good one, but I will put up my mod pack tomorrow.
has anyone found out if the ported roms enable tv out or has someone found out if tv out support is in the i9000 kernal?
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
iJimaniac said:
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
Click to expand...
Click to collapse
what hardware does the galaxy s i9000 have that allows for tv out? I thought the galaxy s i9000 and the galaxy player 4.0 had the same gpu?
Hi, researching for a family member here, so sort of new to the Aria forums (what's left of them).
Basically GPS is never locking on. This is new since the upgrade to 7.2 from 7.1 stable. From what I have read it at least WAS a known problem in the RCs, and i saw this thread with some flashable zips for other gps libraries. Does that sound like a solution, or does anyone have any other ideas?
Which zip would you go for first? I had said try the reverted cm one, but would it be better to just use stock?
Thanks for your help!
I'd suggest the stock libs first. If that doesn't work out try the reverted.
drumist said:
I'd suggest the stock libs first. If that doesn't work out try the reverted.
Click to expand...
Click to collapse
Thanks, worked with the reverted ones just fine.
i've fixed it with the free gps status , just change filtering option and change it back if you want , and it will lock fast
Hi, this is the first PORTED ROM I release, and also the first P.A.C. ROM for the HOX+, I tryed to build from source for about 2 weeks and keept fixing errors, making needed files to just get new errors and new needed files not found and in the end I tryed to build CM just to see if I can even build that, and it worked, so I realised PACman was a bit over my powers and gave up and deleted the source, but after a bit KaptKeefmenneke sent me his PACman 22.1.1 and I sterted porting newer versions over it with great success, so here I am posting this rom after geting permisions from both KaptKeefmenneke and [vertigo] to post it.
This rom is for the INTERNATIONAL ONE X+
This rom was ported from the NEXUS4 over an unreleased P.A.C. 22.1.1 for the HOX+
I will update the rom as long as I can, and fix as many bugs as I can with my limited development knoledge.
This rom also has an OPD (OpenPDroid) patch that can be flashed after flashing the rom.
I hope you will enjoy it as much as I do.
Not working:
-no vibration when touching the touch buttons-did all that came into my mind but still can't make the vibrations work, even did the framework-res.apk edit that should enable it and no luck, if anyone has any Ideea I'd like to hear it.
-headsets not recognised, looking to find a fix but I am kinda blind at this part because I don't know what files contain things related to headset.
-same things as in all other aosp roms
-you tell me
Bugs:
-same things as in all other aosp roms
-OS is allways in black mode, the PAC in Black toggle doesen't do anything.
-you tell me
NOTE: for bugs that need it, post logs, I did not include the Sharelogs and Performance Tool apk's so you will have to download them, sorry, also even if I am not too much of a developer I can mostly read logs, also post if you find any fixes for any bugs, don't expect me to be able to fix all the bugs that may appear, remember I am preety new in the development thing and my knoledge is limited (verry limited as far as I understand) and my time is also limited due to school.
Working:
-mostly everything as far as I can see
I would not recommend using this rom with Xposed Framework even if it is great just because of the same reason it is not really working ok on AOKP (it will take longer for the SystemUI to load)
Downloads:
Rom: http://www.mediafire.com/download/mg8sdj47cs5fq9k/enrc2b_PAC_JB_4.2.2-v23.0.0.zip
Gapps: http://goo.im/gapps/gapps-jb-20130301-signed.zip
Kernel: Use CM10.1 kernel, DO NOT use the included kernel as many things will not work with it (wifi, bluetooth, etc)
OpenPDroid patch: http://www.mediafire.com/download/1..._4.2.2-v23.0.0-openpdroid-20130612-update.zip (No dark mode in Messages app, will try to fix, but don't think I can till I will manage to build from source) for the moment I would say just use XPrivacy if you can live with the SystemUI startup delay added by XPosed.
Thanks to...
ParanoidAndroid Team
CyanogenMod Team
AOKP Team
P.A.C. Team
Maxwen and Lloir for theyr great work on this device
[vertigo] for making the NEXUS4 rom (here:http://forum.xda-developers.com/showthread.php?t=21468790)
KaptKeefmenneke for making the P.A.C. 22.1.1 rom for enrc2b
FFU5y for OpenPDroid
mateorod for the Auto-Patcher
Reserved for changelog
Reserved also just in case.
I've removed some posts about permissions. Feel free to continue via PM and CC me if need be
Sorry if I missed it, but which version of the HOX+ will this work on?
For my purposes, does it work with AT&T version?
Arvoreen said:
Sorry if I missed it, but which version of the HOX+ will this work on?
For my purposes, does it work with AT&T version?
Click to expand...
Click to collapse
Nope, this is also for the international variant
Sent from my HTC One X+ using xda premium
aardappel12 said:
Nope, this is also for the international variant
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
I was afraid you would say that....
I might be wrong but shouldn't this be under the original android development section.
Nice work btw
Sent from my HTC One X+ using Tapatalk 2
flipside101 said:
I might be wrong but shouldn't this be under the original android development section.
Nice work btw
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Nope, due to the fact that it is not built from source
Headphone/Earphone jack doesn't work. Music just plays on the phone speaker.
And is multi user supposed to work? I can't seem to setup a second user.
KiGWa said:
Headphone/Earphone jack doesn't work. Music just plays on the phone speaker.
And is multi user supposed to work? I can't seem to setup a second user.
Click to expand...
Click to collapse
Will have a look as soon a I reupload the rom, thanks for reporting.
Just so people are aware, pacman can and does have HUGE issues with some apps on the market.
Could someone that has this installed tell me if they have any problems with the signal (not getting signal at all), cause a friend had it when he flashed it to his X+ and I also did have the problems after wiping data, then fixed the problem as my friend told me to and then wiped data again and set up the device and did this process again and again lots of times and I only got that once, but at the first wipe data I had my data from the 22.1.1 pacman rom, if anyone else has this problem I will post a how to fix it in the OP, I am not sure if it is related to the rom or not, that is why I am not adding the bug and fix to the OP, for me it happened only once, and my friend has lots of apps installed so it may have been caused by an app for him, test if you have this problem and tell me please.
Ranomez said:
Could someone that has this installed tell me if they have any problems with the signal (not getting signal at all), cause a friend had it when he flashed it to his X+ and I also did have the problems after wiping data, then fixed the problem as my friend told me to and then wiped data again and set up the device and did this process again and again lots of times and I only got that once, but at the first wipe data I had my data from the 22.1.1 pacman rom, if anyone else has this problem I will post a how to fix it in the OP, I am not sure if it is related to the rom or not, that is why I am not adding the bug and fix to the OP, for me it happened only once, and my friend has lots of apps installed so it may have been caused by an app for him, test if you have this problem and tell me please.
Click to expand...
Click to collapse
I did not have any issue with signals on both wifi and mobile network. Though, before i adb pushed the rom/gapps zip, I did a full wipe of the system, data and caches. The phone was like totally empty before i install this ROM.
KiGWa said:
I did not have any issue with signals on both wifi and mobile network. Though, before i adb pushed the rom/gapps zip, I did a full wipe of the system, data and caches. The phone was like totally empty before i install this ROM.
Click to expand...
Click to collapse
Ok, thank you, also could you tell me if it is just me or even if the PAC in black toggle is off the os is still in the black ui?
Ranomez said:
Ok, thank you, also could you tell me if it is just me or even if the PAC in black toggle is off the os is still in the black ui?
Click to expand...
Click to collapse
yup, os ui is black even toggle is off.
Ranomez said:
Could someone that has this installed tell me if they have any problems with the signal (not getting signal at all), cause a friend had it when he flashed it to his X+ and I also did have the problems after wiping data, then fixed the problem as my friend told me to and then wiped data again and set up the device and did this process again and again lots of times and I only got that once, but at the first wipe data I had my data from the 22.1.1 pacman rom, if anyone else has this problem I will post a how to fix it in the OP, I am not sure if it is related to the rom or not, that is why I am not adding the bug and fix to the OP, for me it happened only once, and my friend has lots of apps installed so it may have been caused by an app for him, test if you have this problem and tell me please.
Click to expand...
Click to collapse
got no data signal,too.please post your solution.had same issue while trying to port pa2.5x (from N4,too),but never explored why.
thnksAlot,alex
maerdance said:
got no data signal,too.please post your solution.had same issue while trying to port pa2.5x (from N4,too),but never explored why.
thnksAlot,alex
Click to expand...
Click to collapse
Go to settings->More->Mobile Networks, wait for it to load, click automatically connect around 3 times, it will give you an error, but in 1 min you should be connected and allmostly sure that it should not happen again.
EDIT: Found a real solution, will upload a fixed rom when I get home in 5 and a half hours, at school now and getting ready for a exam.
EDIT2: found the solution and updated apktool to decompile framework, apply fix and recompile and get errors at recompiling......is there a special apktool for pacman or something?
->Ranomez:Go to settings->More->Mobile Networks, wait for it to load, click automatically connect around 3 times, it will give you an error, but in 1 min you should be connected and allmostly sure that it should not happen again.
chaos leads to a new order. how did you find out this kind of weird(individual?)
input/output behavier.
I suppose we found a proof of that android should be labelled alive : )
will 'apply' later. thank you for your afford in this rom in general.
greets, alex
maerdance said:
->Ranomez:Go to settings->More->Mobile Networks, wait for it to load, click automatically connect around 3 times, it will give you an error, but in 1 min you should be connected and allmostly sure that it should not happen again.
chaos leads to a new order. how did you find out this kind of weird(individual?)
input/output behavier.
I suppose we found a proof of that android should be labelled alive : )
will 'apply' later. thank you for your afford in this rom in general.
greets, alex
Click to expand...
Click to collapse
I may be sleepy or something wrong with me cause I just woke up and I can't remember half of yesterday but I don't understand anything of what you sayd.
Also for anyone that wants to help me can you please try to apply the fix at the bottom of the OP in this thread http://forum.xda-developers.com/showthread.php?t=1908008 to the framework in my rom, cause for me it doesen't work, I can not recompile the framework even if I don't change anything, so I decompile it and try to recompile and fail, also I get some errors at the decompilation part also, but it seems to decompile.....
EDIT: anyone having a problem that when you talk with someone the other person hears himself, cause dad told me that today, but no one else told me till now?