7320 ROM - is there anybodywilling ... - Galaxy Tab 8.9 General

hello there,
I know not many people own model 7320.
There is no updates or new ROMs at all for it
Was wondering if there is some developer that is willing to port some other ROM (4.3) to our (my) device
I am willing to start some support actions for that.
I love my tablet but software is too old...
Suggestions welcome

strazicic said:
hello there,
I know not many people own model 7320.
There is no updates or new ROMs at all for it
Was wondering if there is some developer that is willing to port some other ROM (4.3) to our (my) device
I am willing to start some support actions for that.
I love my tablet but software is too old...
Suggestions welcome
Click to expand...
Click to collapse
No. Neither http://forum.xda-developers.com/member.php?u=3081699, nor http://forum.xda-developers.com/member.php?u=5019846 have this device. And there are no other developers with GT8.9.

DemonGloom said:
No. Neither http://forum.xda-developers.com/member.php?u=3081699, nor http://forum.xda-developers.com/member.php?u=5019846 have this device. And there are no other developers with GT8.9.
Click to expand...
Click to collapse
As you should remember, Arlic was the only dev of p7320 but unfortunately he disapeared suddenly...
Anyway, I am still satisfied on his rom:
http://forum.xda-developers.com/showthread.php?t=1923371
btw. there are some November's releases of stock roms at sammobile.
It is still 4.0.4 but I wonder if it comtain any improvements over previous builds?

Is your 7320 on Tegra or some diffrent SoC? I cant find reliable info...

pax0r said:
Is your 7320 on Tegra or some diffrent SoC? I cant find reliable info...
Click to expand...
Click to collapse
p7320 - SoC Qualcomm (2x1.5 Ghz, Adreno 220)
p7300/p7310 - Tegra 2

strazicic said:
hello there,
I know not many people own model 7320.
There is no updates or new ROMs at all for it
Was wondering if there is some developer that is willing to port some other ROM (4.3) to our (my) device
I am willing to start some support actions for that.
I love my tablet but software is too old...
Suggestions welcome
Click to expand...
Click to collapse
I have just made a new kernel, but it is based on ICS.
You can get it here:
Downloads:
https://sourceforge.net/projects/kernel-p7320t-ics/files/
Source:
https://github.com/CL0SeY/kernel_P7320T_ICS
The features so far are:
Interactive CPU governor available for selection (was left out of the stock kernel for some reason). If you want to enable this governer you will need to firstly get ROOT for the tablet, and then install some app to control it, e.g. Voltage Control. If you enable this, it should give you a more responsive tablet, compared to using the default ondemand governer.
Max CPU frequency "UNICPU" bumped to 1512MHz from 1242MHz. This is the maximum frequency that you will see the tablet sitting on at times. If you are concerned about battery usage you can tweak this the maximum frequency value down using using Voltage Control or other apps.
USB charging and notification, as per glitschi667 / pershoot's patch, which was previously in a honeycomb custom kernel: http://forum.xda-developers.com/showthread.php?t=1569122 . The tablet will show as charging when plugged into a PC with enough power, whereas previously you would see the red X over the battery icon.

Wow!
Do yoy think it will work with Arlic's ROM (I am still on)?
Does it actually change charging method or just change the visualisation of the status (i.e X replaced by powering)?
Many, many thanks !!!,
I hope it is just the beginning of your magic here...

janla said:
Wow!
Do yoy think it will work with Arlic's ROM (I am still on)?
Does it actually change charging method or just change the visualisation of the status (i.e X replaced by powering)?
Many, many thanks !!!,
I hope it is just the beginning of your magic here...
Click to expand...
Click to collapse
Not too sure if it will work with Arlic's ROM. You could give it a go at your own risk, if you were keen.
The USB charging is more than just a display thing, it should work the same as glitschi667 / pershoot's one. I didn't want to advertise the charging capabilities too much without trying it myself but I can report now that it seems to charge fine off my laptop.
I will probably try next flashing the AOKP test build from the i957 forum as people have reported that it works, to some extent. I shall report back.

CL0SeY said:
Not too sure if it will work with Arlic's ROM. You could give it a go at your own risk, if you were keen.
The USB charging is more than just a display thing, it should work the same as glitschi667 / pershoot's one. I didn't want to advertise the charging capabilities too much without trying it myself but I can report now that it seems to charge fine off my laptop.
I will probably try next flashing the AOKP test build from the i957 forum as people have reported that it works, to some extent. I shall report back.
Click to expand...
Click to collapse
I have a preliminary GT-P7320T AOKP 4.1.2 ROM working based off dan-htc-touch's http://forum.xda-developers.com/showthread.php?t=1899018
I had to change the mount point for /data inside the fstab.qcom file inside the boot.img. It has to be
/dev/block/mmcblk0p28
and NOT
/dev/block/mmcblk0p26
I will hopefully report back soon. If this turns out to be all the "migration" that we need to use ROMs from the SGH-i957, it's looking good. Beware though that while they have a few devs working on ROMs it isn't extremely active over there either (http://forum.xda-developers.com/galaxy-tab-8-9/i957-development)

CL0SeY said:
I have a preliminary GT-P7320T AOKP 4.1.2 ROM working based off dan-htc-touch's http://forum.xda-developers.com/showthread.php?t=1899018
I had to change the mount point for /data inside the fstab.qcom file inside the boot.img. It has to be
/dev/block/mmcblk0p28
and NOT
/dev/block/mmcblk0p26
I will hopefully report back soon. If this turns out to be all the "migration" that we need to use ROMs from the SGH-i957, it's looking good. Beware though that while they have a few devs working on ROMs it isn't extremely active over there either (http://forum.xda-developers.com/galaxy-tab-8-9/i957-development)
Click to expand...
Click to collapse
OK, so for the game people here that want to try this out... ensure you have a stock image from sammobile ready to plonk back on your device if you're unhappy with it...
Also once I get enough posts up I might be able to make a thread in the appropriate forum
ROM (flashable CM zip): aokp_p7320t_DannoRom_Nov-03-12.CL0SeY.20131124.zip (https://drive.google.com/file/d/0B48JIYNc4wvsT2txZS16WGV0MUE/edit?usp=sharing)
GAPPS required: http://goo.im/gapps/gapps-jb-20121011-signed.zip
Procedure:
(This has only been tested moving from a STOCK ICS ROM. Unsure if it will work for Arlic's ROM. If it all goes wrong try from a stock ICS ROM.)
Ensure you have a CWM recovery installed, see http://forum.xda-developers.com/showthread.php?t=1569122
* Copy the zips to your tablet
* Reboot into recovery
* WIPE data
* Install aokp_p7320t_DannoRom_Nov-03-12.CL0SeY.20131124.zip
* Install gapps-jb-20121011-signed.zip
* Reboot and enjoy!
Known working:
* Display
* 3G/4G/LTE
* Wifi
* Sound (headphones, speakers)
Known issues:
* Google play store seems to lose its network connection after a while. This seems to be a common problem amongst other ROMs.
* Plenty that we don't know about yet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

CL0SeY said:
OK, so for the game people here that want to try this out... ensure you have a stock image from sammobile ready to plonk back on your device if you're unhappy with it...
Also once I get enough posts up I might be able to make a thread in the appropriate forum
ROM (flashable CM zip): aokp_p7520t_DannoRom_Nov-03-12.CL0SeY.20131124.zip
Click to expand...
Click to collapse
Great work!
I am going to give it a try next weekend or so.
Need to be sure no reverting problems will be while downgdading,
Definitely you should start new tread.
There is a typo in the filename of the rom?
should be p7320 instead p7520.

janla said:
Great work!
I am going to give it a try next weekend or so.
Need to be sure no reverting problems will be while downgdading,
Click to expand...
Click to collapse
Do you mean about going back to stock after trying it out? I have tried it myself going back to the sammobile OTA image fine.
janla said:
There is a typo in the filename of the rom?
should be p7320 instead p7520.
Click to expand...
Click to collapse
Yes! Thanks for picking that up... I was making the ZIP in a bit of a hurry It's definitely a typo.
---------- Post added at 05:26 PM ---------- Previous post was at 05:19 PM ----------
CL0SeY said:
Yes! Thanks for picking that up... I was making the ZIP in a bit of a hurry It's definitely a typo.
Click to expand...
Click to collapse
And the file is now named correctly

I have also succeeded in booting this ROM (CM10/JB 4.1) by using the same minor modification, but haven't uploaded my version for p7320 yet:
http://forum.xda-developers.com/showthread.php?t=1867579
It seems to be a smoother build than the AOKP one. If anyone wants me to upload it please let me know.
Also, if techy people are interested, I can make up a short guide for making a P7320 ROM out of a SGH-i957 ROM. This might be better for the "long term evolution" (pun intended ) of the tablet. But let me know if there is demand for it.

CL0SeY said:
I have also succeeded in booting this ROM (CM10/JB 4.1) by using the same minor modification, but haven't uploaded my version for p7320 yet:
http://forum.xda-developers.com/showthread.php?t=1867579
It seems to be a smoother build than the AOKP one. If anyone wants me to upload it please let me know.
Also, if techy people are interested, I can make up a short guide for making a P7320 ROM out of a SGH-i957 ROM. This might be better for the "long term evolution" (pun intended ) of the tablet. But let me know if there is demand for it.
Click to expand...
Click to collapse
OK guys, here's a nice little nugget for the weekend.
I've followed the instructions for making a CM10 ROM for the i957 above, and simply changed the mount point and have it working on the P7320.
The ROM (cm-10-20131130-UNOFFICIAL-p7320.zip) should appear in this folder as soon: https://drive.google.com/folderview?id=0B48JIYNc4wvscVpIZkRKZWd4RmM&usp=sharing
I've tested wifi, 4g, and that is about it. Once again flash at your own risk yada yada yada...
MASSIVE thanks to @nrvate for the guide! I would like to see if we can do something potentially with the upgrade scripts to make them generic. between the p7320 and i957. I suspect this ROM will work fine on the i957 with the reverse fix (ie. make it use mm block 26 instead of 28).
Also I will make a proper thread for this work soon enough...

thanks a lot for participating CL0SeY
It is great that we are moving somewhere ...
I have wish to start working on cooking but building house and 2 little children are taking all of my time (with full right

Where do people think the p7320 dev stuff should go? The I957 is sui similar, but I think people will find it easier in the other development section?

CL0SeY said:
Where do people think the p7320 dev stuff should go? The I957 is sui similar, but I think people will find it easier in the other development section?
Click to expand...
Click to collapse
I think that the "Galaxy Tab 8.9 Android Development" is the right place.
Oh, btw... I installed the CM10 to my P7320 and currently testing everything...
Issues :
Camera does not work. Camera app starts, but there's no image.

_kankea said:
I think that the "Galaxy Tab 8.9 Android Development" is the right place.
Oh, btw... I installed the CM10 to my P7320 and currently testing everything...
Issues :
Camera does not work. Camera app starts, but there's no image.
Click to expand...
Click to collapse
Same here, thanks for giving it a go and the feedback . Also, the auto brightness seems to be very unpredictable, I think it's something wrong with the values coming back from the sensor.
I've been bashing my head against a wall trying to get us up to at least cm10.1 without too much luck so far. Compiling is quite a slow process even on an SSD, so it can take a while between fixing build errors.

_kankea said:
Issues :
Camera does not work. Camera app starts, but there's no image.
Click to expand...
Click to collapse
There is a patch for the camera in the i957 thread: http://forum.xda-developers.com/showpost.php?p=31382526&postcount=47
I've downloaded it and applied it to my p7320 and it works fine.
I will incorporate it into my next update.
Other things I've noticed:
. The boot animation sometimes displays, sometimes doesn't
. Applications that want to write to USB storage seem to fail

CL0SeY said:
There is a patch for the camera in the i957 thread: http://forum.xda-developers.com/showpost.php?p=31382526&postcount=47
I've downloaded it and applied it to my p7320 and it works fine.
I will incorporate it into my next update.
Other things I've noticed:
. The boot animation sometimes displays, sometimes doesn't
. Applications that want to write to USB storage seem to fail
Click to expand...
Click to collapse
Yeah, camera works now \o/
I read from the i957-thread that the boot animation problem is a known issue...
The vibration seems to be a bit powerless...
But still, I have waited for ages that anything newer than ICS appears for this device. Great job, CL0SeY! :good:
EDIT:
Mobile hotspot function (tethering) does not seem to work...

Related

[MOD] tabletUI on AOSP/CM10.1/CM10.2 - Auto-Patcher >>UPDATE: AOSP 4.3 supported!!<<

[MOD] tabletUI on AOSP/CM10.1/CM10.2 - Auto-Patcher >>UPDATE: AOSP 4.3 supported!!<<
tabletUI for ANY DEVICE running AOSP, CM10.1, or CM10.2​​​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Check out post 2 for way more screenshots!​
All you need is to get the latest version of the Auto-Patcher.(or ApG)
Linux/Mac: Check out mateorod's thread for instructions on getting the auto-patcher set up and how to use it.
Windows: Check Kobik77's post on ApG and download the latest version of ApG, which puts everything you need to make these patches together for you automatically!
Once you have that all set up just run your favourite AOSP, CM or SlimBean rom through the auto-patcher, patching for tabletUI. Auto-patcher will automatically detect your rom type and use the appropriate patches. It really could not be any easier!
(In ApG if you must set the rom type then use AOSP for Slim)
Make A Backup Before Trying Any Of These Mods! I will not be responsible for your data loss.
The Auto-Patcher will produce an update.zip and a restore.zip. I recommend moving both to your device before flashing.
Flash the produced update.zip in recovery and reboot.
Enjoy the tabletUI goodness!
If you do experience any issues, or your device bootloops, or you just want to go back to the way things were before applying the tabletUI mod, boot into recovery and flash the restore.zip. This will replace ALL of the original rom files and you should be able to boot up normally.
​
Confirmed Devices (Roms):
Nexus 7 - 2013 (AOSP/CM)
Nexus 10 (AOSP/CM)
Nexus 7 (CM)
Galaxy Tab 2 (AOSP/CM/SLIM)
Asus Transformer TF101 (CM)
Nook Color (CM)
Motorola Xoom (CM) - Thanks LQQKS!
Acer Iconia A500 (CM) - Thanks rsriram22!
Galaxy Grand Duos GT-I9082 (CM) - Thanks @karipari95! (who says setting dpi to 160 perfects the tablet look!)
If you have just patched a new device, not on this list let me know so I can add it!​Known Issues:
This mod is going away from what android has been moving toward for a few months so there are a few issues with some android features. I personally think that the gains outweigh the losses in this, but depending on your device usage YMMV.
Multi-User: If you use multiple users on your device then this mod is probably not going to work well for you. In tests it seems that any user will get the notifications for all users. They can't be clicked but they do come through and can be seen.
Encryption: I have had a report that enabling Security/Encrypt tablet in conjunction with tabletUI mod will lead to a boot loop.
Notifications: Most notifications will work fine, however certain ones will not be seen:
Storage related notifications may not be seen. For instance the popup to enable mass storage when you plug into your computer.
Persistent Alarm Notification will not be seen when you have the alarm set.
Preferences: Sometimes certain options in Settings (having to do with appearance) will either no longer be present, or will have no effect when changed.
Launcher/Apps: On devices with smaller screens and lower resolutions the default launcher may not look very good after applying tabletUI mods. I recommend using a custom launcher from the play store, like Nova/Holo, which let you customize appearances. Also some apps may appear a little odd, or be missing content. This only affects small, low-res screens and is minimal.(see Youtube: missing/squished "Like"/"Subscribe" buttons)
Bugs/Requests:
If you have to report a failed attempt at patching a rom please include as much detail as you can, including the log from auto-patcher (full log please, not copy/paste of terminal output) and the rom and device you are trying to patch for (link to thread/source appreciated)
Please do not report failures for roms other than those stated as working in this thread; currently AOSP, CM10.1, and SlimBean.
Please do not post requests for support for roms which are not currently supported.
Be aware that some roms which are called "AOSP/AOSP based" are actually heavily modified by their developer already and these patches may fail in that case.
If you need to report an issue with some function that worked on your device before flashing the tabletUI mod but isn't working after, a log of the failure can be very helpful in coming to a solution, and is appreciated. Please check the Known Issues above before reporting.
Thanks/Credits
mateorod & pastime1971 for the amazingly versatile Auto-Patcher!
kobik77 for ApG which really makes the Auto-Patcher accessible for everyone!
barrmulio for all his work on tabletUI!
All the happy, willing testers: brGabriel, 138, 19cam92, dlumberg, astro_75, rraaka, tuxafgmur, and anyone else I am forgetting! Without you...:crying:!
All the awesome, talented developers on XDA that bring us these great roms for our devices! Thanks to each and every one of you for helping make this community what it is!
All my fellow tabletUI fans out there, who don't want to accept an awkward user interface!
Anyone else who has slipped my mind at the moment, and anyone who has ever contributed anything to XDA you're great too!:highfive:
​
Screenshots:
Galaxy Tab 2 7.0: CM10.1 (for more see here)
Galaxy Tab 2 7.0: SlimBean
Galaxy Tab 2 10.1: CM10.1 (for more see here)
Nexus 10: CM10.1
Nexus 10: AOSP
Asus Transformer TF101: CM10.1
one more just in case
Thank you but still getting the same error with Team EOS4 rom (tf101)
http://codepad.org/S3qVlSss
i9apps said:
Thank you but still getting the same error with Team EOS4 rom (tf101)
http://codepad.org/S3qVlSss
Click to expand...
Click to collapse
That's because there aren't patches for Team EOS roms. Right now your choices are either AOSP, CM10.1, or Slim.
"Recent Apps" style?
Maybe I didn't get it right but after patching my CM 10.1 on my Nook Color the "Recent Apps" button still shows the phone style not the tablet one Recent Apps view!? Maybe this should be added to "Known Issues".
SGH-i200 said:
Maybe I didn't get it right but after patching my CM 10.1 on my Nook Color the "Recent Apps" button still shows the phone style not the tablet one Recent Apps view!? Maybe this should be added to "Known Issues".
Click to expand...
Click to collapse
Thank you for the report. I guess to be honest I don't really think of this as an "issue" but I guess that you are right. At best it is still a shortcoming in acheiving what you would expect as tabletUI. I will have to see if I can get it to look like in Honeycomb, where it was a column view, pushed to the left of the screen. That is the way that you mean, right?
@SGH-i200
I think that I got it all sorted out the way you would like. I will try to include this fix in the auto-patcher the next time I update the tabletUI patches. It does look better this way, thanks for the push!
Awesome work Caldair!
Well done. Thanks for helping us Slimbeaners keep our phones secure.
Do you know what the GsmServiceStateTracker.smali does?
I see this error when I am compiling the latest Slim 4.2.2 build 4 patch.
It still completes the patch, and the patch works with no problems. Some people on the Slim thread have reported problems with Google maps, but as I have maps & network location disabled, I can't say.
Oddly it wasn't there on build 2.5
Anyways, thanks again for all your help in making Slimbean a safe rom.
Didgesteve said:
Well done. Thanks for helping us Slimbeaners keep our phones secure.
Do you know what the GsmServiceStateTracker.smali does?
I see this error when I am compiling the latest Slim 4.2.2 build 4 patch.
It still completes the patch, and the patch works with no problems. Some people on the Slim thread have reported problems with Google maps, but as I have maps & network location disabled, I can't say.
Oddly it wasn't there on build 2.5
Anyways, thanks again for all your help in making Slimbean a safe rom.
Click to expand...
Click to collapse
Sorry, I don't know anything about that. I saw your post at the auto-patcher main thread as well and I think you have the wrong impression. This thread is meant to be for discussion of the tabletUI mod part of the auto-patcher. Your question would be better in the main thread, and trust me, those guys are way smarter than me anyway.
Updates were just pulled into auto-patcher. ApG users can try the newest patches right now, otherwise you could pull from Mateor/auto-patcher on github or wait for the next auto-patcher release.
Huge thanks to tuxafgmur for all the work he did on streamlining these patches!:good::good:
These changes help reduce the extra load that tabletUI seems to put on the gpu!
Also fixed the 'latest' symlink in the CM patch so you should be able to use multiple auto-patcher mods together with tabletUI (ie. pdroid)
And I changed the appearance of the recent apps panel so it is more similar to the old style tablet recent apps (similar to the pictures I posted a couple posts back), hope you like it!
hey mate,
i'm trying to patch this mod into my cm10.1 rom on Xoom MZ601 everest.
i've already seen that someone did it successfully on the Xoom wingray.
but when i try : it fails to extract the build prop
hopefully the attached AP log will tell you something
this is on the most recent version of APG
LQQKS said:
hey mate,
i'm trying to patch this mod into my cm10.1 rom on Xoom MZ601 everest.
i've already seen that someone did it successfully on the Xoom wingray.
but when i try : it fails to extract the build prop
hopefully the attached AP log will tell you something
this is on the most recent version of APG
Click to expand...
Click to collapse
From the look of your log I think there is something wrong with your ApG installation.
I have never used ApG, as I don't use windows, so unfortunately I can't really be very helpful with this issue. But the patcher really should be working for that rom.
Maybe you could try completely removing ApG and starting fresh, that may help. I hope!
OK I will try that when I get home
and I've found a patched version that I'm running but I'd like to do it myself as I update CM10.1 frequently
Thanks for the help
Edit: working now \o/ I had a bad download of the rom, everything else was sweet feels like a complete n00b
You can add Xoom MZ601 Everest to list of confirmed working devices (CM10.1) thanks heaps Caldair for the awesome mod \o/
Sent from my rooted Xoom MZ601
running Elemental CM10.1
using XDA Premium app \o/
LQQKS said:
OK I will try that when I get home
and I've found a patched version that I'm running but I'd like to do it myself as I update CM10.1 frequently
Thanks for the help
Edit: working now \o/ I had a bad download of the rom, everything else was sweet feels like a complete n00b
You can add Xoom MZ601 Everest to list of confirmed working devices (CM10.1) thanks heaps Caldair for the awesome mod \o/
Sent from my rooted Xoom MZ601
running Elemental CM10.1
using XDA Premium app \o/
Click to expand...
Click to collapse
Glad to hear it!
And don't worry we all fall victim to the simplest mistakes. They are never simple until you find the solution, and they are usually the most frustrating to solve!
Thanks for sharing your success:highfive: I will add the Xoom to confirmed devices!
@i9apps @rafal.k
For all you teamEOS users out there I have put together a test build of the Auto-Patcher that will patch your EOS roms for tabletUI!
I made test patches for Asus Transformer tf101. These zips are based on the build dated: 2013-05-05 from http://goo.im/devs/teameos/roms/eos4/nightlies/tf101 and must be used on that build and only on the tf101: The top 2 attachments are for the tf101.
I also made test patches for the Motorola Xoom Wingray model. These are based on the build dated 2013-05-04 from http://goo.im/devs/teameos/roms/eos4/nightlies/wingray and must be used on that build date and only on the Wingray: The bottom 2 attachments are for the wingray.
I don't have either of these devices to test and there is no EOS rom for the tablets that I do have so be warned:
These are completely UNTESTED! Be sure to download both the update and restore file and have them both on your device before flashing the update.zip in recovery. This way if you have issues like boot loops all you need to do is get back in recovery and flash the restore.zip to have all the original rom files back.
I hope to get some feedback on whether these patches work or not and then I can procede with getting EOS roms supported in the Auto-Patcher for TabletUI. Then EOS users with any device should be able to make these patches for any build!
I anxiously await your feedback:fingers-crossed:
Edit: Well I got my feedback... and it was not good:crying: To make matters worse I have since read in one of the EOS threads that bigrushdog is working on bringing tabletUI back into these roms anyway, so I am just going to leave this for now. You EOS users should have your tabletUI back before you know it anyway!
ATTACHMENTS REMOVED.
Caldair said:
@i9apps @rafal.k
For all you teamEOS users out there I have put together a test build of the Auto-Patcher that will patch your EOS roms for tabletUI!
I made test patches for Asus Transformer tf101. These zips are based on the build dated: 2013-05-05 from http://goo.im/devs/teameos/roms/eos4/nightlies/tf101 and must be used on that build and only on the tf101: The top 2 attachments are for the tf101.
I also made test patches for the Motorola Xoom Wingray model. These are based on the build dated 2013-05-04 from http://goo.im/devs/teameos/roms/eos4/nightlies/wingray and must be used on that build date and only on the Wingray: The bottom 2 attachments are for the wingray.
I don't have either of these devices to test and there is no EOS rom for the tablets that I do have so be warned:
These are completely UNTESTED! Be sure to download both the update and restore file and have them both on your device before flashing the update.zip in recovery. This way if you have issues like boot loops all you need to do is get back in recovery and flash the restore.zip to have all the original rom files back.
I hope to get some feedback on whether these patches work or not and then I can procede with getting EOS roms supported in the Auto-Patcher for TabletUI. Then EOS users with any device should be able to make these patches for any build!
I anxiously await your feedback:fingers-crossed:
Click to expand...
Click to collapse
I tried the Xoom version and as soon as it enters the OS I get a neverending "Unfortunately System UI has stopped"
I click OK and it immediately pops up again.
Let me know if there's something specific you'd like me to try that will help you debug.
Caldair said:
@i9apps @rafal.k
For all you teamEOS users out there I have put together a test build of the Auto-Patcher that will patch your EOS roms for tabletUI!
I made test patches for Asus Transformer tf101. These zips are based on the build dated: 2013-05-05 from http://goo.im/devs/teameos/roms/eos4/nightlies/tf101 and must be used on that build and only on the tf101: The top 2 attachments are for the tf101.
I also made test patches for the Motorola Xoom Wingray model. These are based on the build dated 2013-05-04 from http://goo.im/devs/teameos/roms/eos4/nightlies/wingray and must be used on that build date and only on the Wingray: The bottom 2 attachments are for the wingray.
I don't have either of these devices to test and there is no EOS rom for the tablets that I do have so be warned:
These are completely UNTESTED! Be sure to download both the update and restore file and have them both on your device before flashing the update.zip in recovery. This way if you have issues like boot loops all you need to do is get back in recovery and flash the restore.zip to have all the original rom files back.
I hope to get some feedback on whether these patches work or not and then I can procede with getting EOS roms supported in the Auto-Patcher for TabletUI. Then EOS users with any device should be able to make these patches for any build!
I anxiously await your feedback:fingers-crossed:
Click to expand...
Click to collapse
Tried with nightly 112 for TF101. Did not work. System UI kept crashing and I could not use the pad. Had to wipe system and reinstall without this.
drewski_1 said:
I tried the Xoom version and as soon as it enters the OS I get a neverending "Unfortunately System UI has stopped"
I click OK and it immediately pops up again.
Let me know if there's something specific you'd like me to try that will help you debug.
Click to expand...
Click to collapse
Gatak said:
Tried with nightly 112 for TF101. Did not work. System UI kept crashing and I could not use the pad. Had to wipe system and reinstall without this.
Click to expand...
Click to collapse
Thanks to you both for testing this! I am sorry that it failed so miserably and you had to wipe and reinstall.
For now I will take a closer look at the patches themselves and the sources. There is definitely more going on in EOS roms than other AOSP/based roms, especially in SystemUI.apk.
Gatak, I would have said your issue could have been caused by the fact that you tried to flash the update over a newer build than the modded files came from, but since drewski_1 had the same exact issue I think the patches are probably not right.
Drewski_1, I am assuming that you did flash the update on a wingray model and that you were running the corresponding build of the rom, dated 2013-05-04. If that is not the case, and you are also using a newer (or older) build, please let me know.
These patches can really screw up when used on different nightly (or weekly or whatever the build frequency is for EOS) builds than they were based on. Devs can change a lot in a week, and these patches contain important core files.
Thanks again to you both, I really want to get EOS working. I see how many downloads there are of these roms from goo.im, just for these 2 devices, so I know a lot of people would benefit from this.

[DEPRECATED]--[GUIDE][ROMS] List of ROMs for I537 using SafeStrap

ATTENTION: THIS INFORMATION IS DEPRECATED!
I am leaving the thread up for reference, but as I no longer have the device and haven't been keeping up on the development of the I537, many of these methods may not (and probably won't) apply any longer. Please search the subforums for recent information.
Disclaimer: If you post a successful ROM to the thread, I will gladly add it to the OP. However, I can't promise how quick I can do it. I am very busy with work. I will try to keep this thread as up-to-date as I possibly can.
Purpose: The point of this thread is to make a list of ROMs that have been confirmed to work on the SGH-I537 S4 Active using SafeStrap.
Feel free to ask any question you like pertaining to this topic. Noobs are welcome. Please do not flame other members.
Please provide feedback on what works or doesn't work! This community thrives when you share your experience.
Steps for flashing a ROM
1. Download a ROM file (must be 4.2.2 based with stock kernel)
2. Create ROM slot in SafeStrap
3. Flash the ROM and three update.zips: keys fix, camera patch, and modules fix (MF1, MF2, or MF3 depending on your stock firmware).
4. Wipe cache and dalvik.
5. Boot system
6. Report on how it works if you have problems and share any success.
Confirmed Working:
S4 Google Edition ROM
Goldeneye
SHOstock
MDOB
Graviton
Omega ROM I9505
WickedROM
Alpha - I had SuperSU problems, but flashed the latest SuperSU .zip here and now everything works great.
Hyperdrive - Make sure you flash the ATT compatability .zip in order to clear up the problem with SMS on LTE.
Will Not Work:
ANYTHING WITH CUSTOM KERNEL
_____________________________________
LINKS:
Hardware Key Patch
SafeStrap Dev Thread (modules fix zip in third post)
NEW:
I put together a "MasterPatch" for both MF1 and MF3, each which contains: respective modules, hardware keys fix, camera patch, and an edited gps.conf file which allows for a quicker GPS-fix in the U.S.
This is just to make things easier when flashing a new ROM built for the S4. Enjoy.
MF1 MasterPatch
MF3 MasterPatch
I posted this in another thread and thought it might be useful here.
You can more or less easily flash regular S4 ROMs onto our phones. Be aware that this has only been done in SafeStrap thus far. You could possibly make your phone unusable if you flash S4 ROMs as your only ROM without using SafeStrap.
To use a regular S4 ROM in SafeStrap:
Flash your desired regular S4 ROM into a new slot in SafeStrap. Currently you can only flash 4.2.2 TouchWiz based ROMs due to a kernel limitation with SafeStrap. I believe @Hashcode is still working on this and hopefully we will eventually be able to use any kernels with SafeStrap.
Without rebooting, flash the MOD file of your stock ROM. So if your stock ROM is MF1, then flash the MF1 MOD file. MF2....flash MF2 MOD file, and MF3...flash MF3 MOD file. The MOD files can be found here.
Again without rebooting, flash the camera fix that was put together by LeJay. The camera fix can be found here.
Finally flash the Hardware Key Fix that is attached in the first post.
Make your new ROM slot the active ROM slot and reboot your phone.
If any of this information is wrong please let me know and I will update this post so people don't brick phones. Please note that this has only been reported to work in SafeStrap so far, flashing regular S4 ROMs as your stock ROM could brick your device and has not been tested yet.
Just a quick update, I've confirmed that Hyperdrive, a ROM originally intended for Verizon works on the S4Active. See the picture below. Steps to get this working:
Download the latest version of Hyperdrive from here.
This is an Aroma installer, so as you work your way through the installer options choose the AT&T kernel, not the Verizon one.
After finishing the install, DO NOT REBOOT, flash your corresponding modules file (ex. MF3).
Flash LeJay's camera fix
Flash the keyboard fix in the first post.
Finally flash the AT&T Compatibility Pack on the Hyperdrive page so that your phone will work on the AT&T network. The default configuration for the phone has it set up to work with the Verizon network, so if you don't flash the AT&T Compatibility Pack you won't be able to get a signal.
The only thing I can't get to work correctly is the camera with the stock camera app, even with LeJay's fix. I downloaded Focal and I am able to take pictures, video, and panorama however when taking a panorama picture the display is rotated 90 degrees making. The camera is fully functional, it's just not perfect. EDIT: It sounds like the Focal issue has been resolved with the latest update to the app in the Play Store.
TL;DR Hyperdrive works out of the box on the S4 Active if you flash everything properly and in the correct order.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm curious to try Jedi ROM for s4 but I can't find a working link. Don't know if @ptmr3 knows it's not working.
GT-i9295(i537) running SafeStrap
Deadly Venom works same camera issues I used camera mx no 90 ° rotation https://play.google.com/store/apps/details?id=com.magix.camera_mx
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Others have posted that Goldeneye and SHOstock works. And of course the S4 Google Edition ROM works.
I wonder if this works vise versa to the S4?
MDOB confirmed working!
Mdob works, very nice slim version of stock with nice flashable add ons,when flashing progress bar will show nothing, just wait!
http://forum.xda-developers.com/showthread.php?t=2280556
I got Hyperdrive to work and I was excited but without being able to use aqua mode it defeated the purpose of having the S4A so I revert to Stock ROM. Really looking forward to the day that Aqua can be used on anything other than stock.
i537 Roms!
Can someone either post or show how these roms exactly work on installing them? So far I only got hyperdrive and google edition to work and still have not got GoldenEye,SHOstock or MDOB to work and I do not know if I may be doing something wrong but I don't understand I got others to work and not these ones that certain people say that work and I have the s4 active i537 model. Could someone PLEASE at least put a step by step with links for each Rom it'd be very appreciated as of right now its rough for me working a lot and trying to learn new stuff as I am a noob with some of this but I use to have the galaxy s3 but seems to be huge difference, THANK YOU!!
dealwitit187 said:
Can someone either post or show how these roms exactly work on installing them? So far I only got hyperdrive and google edition to work and still have not got GoldenEye,SHOstock or MDOB to work and I do not know if I may be doing something wrong but I don't understand I got others to work and not these ones that certain people say that work and I have the s4 active i537 model. Could someone PLEASE at least put a step by step with links for each Rom it'd be very appreciated as of right now its rough for me working a lot and trying to learn new stuff as I am a noob with some of this but I use to have the galaxy s3 but seems to be huge difference, THANK YOU!!
Click to expand...
Click to collapse
I've already provided these instructions in the second post of this thread. You shouldn't have to do anything different than you did for Hyperdrive of GPE, you may have just had bad downloads. Make sure you check the MD5 after you download to make sure you don't have a corrupted download.
Devo7v said:
I've already provided these instructions in the second post of this thread. You shouldn't have to do anything different than you did for Hyperdrive of GPE, you may have just had bad downloads. Make sure you check the MD5 after you download to make sure you don't have a corrupted download.
Click to expand...
Click to collapse
I figured it out, it was the size of the rom I made, I would like to know the sizes to make for roms that I could use all 4 slots if wanted but as of right now I am currently testing still but thank you so much for the reply!
dealwitit187 said:
I figured it out, it was the size of the rom I made, I would like to know the sizes to make for roms that I could use all 4 slots if wanted but as of right now I am currently testing still but thank you so much for the reply!
Click to expand...
Click to collapse
It would be nice if you could post the optimal slot sizes you end up with. There isn't much information in any of the SafeStrap threads on any of the S4's that say what sizes people are using.
If you feel up to it, I think it would be nice to say for example:
Code:
ROM: [URL="http://forum.xda-developers.com/showthread.php?t=2301724"]Hyperdrive[/URL]
System partition size: 2800 MB
Data partition size: 2500 MB
Cache partition size: 300 MB
Free space after booting slot: [B]XXXX[/B] MB
This way people would know how much space they have for apps, music, videos, etc. after they boot into their new slot.
Devo7v said:
It would be nice if you could post the optimal slot sizes you end up with. There isn't much information in any of the SafeStrap threads on any of the S4's that say what sizes people are using.
If you feel up to it, I think it would be nice to say for example:
Code:
ROM: [URL="http://forum.xda-developers.com/showthread.php?t=2301724"]Hyperdrive[/URL]
System partition size: 2800 MB
Data partition size: 2500 MB
Cache partition size: 300 MB
Free space after booting slot: [B]XXXX[/B] MB
This way people would know how much space they have for apps, music, videos, etc. after they boot into their new slot.
Click to expand...
Click to collapse
I completely understand right at the moment im in a rush to work but would like to test different sizes and inform people as well but I will say I tried every rom that is confirmed working besides Hyperdrive cause I had it working before but I will reply and update later tonight.. but I do believe this is what I was trying if its wrong I will correct it later as well but it was the lowest size you could do for system and data partition I will say..
*Safestrap*
system partition size - 1000
Data partition size - 1000
Cache partition size- 300
OP updated
This is awesome!!!! I thought my wifes att active was on deathrow. For the international roms like omega which kernel patch/module do you use? Im assuming mf3?
Brought to you by my Golden Eye powered ATT S4. Modified with Jkay mod, KT Kernel, and Xposed.
my-blue-snog-box said:
OP updated
Click to expand...
Click to collapse
It depends on what version your stock ROM is. If you go to about phone you can see what version of firmware you're on. You then flash the corresponding MOD file. Odds are if you accepted the latest AT&T update then you're on MF3.
Just tried the new AOSP 4.3 S4 rom here: http://forum.xda-developers.com/showthread.php?t=2348272 and it seems that the display doesn't show up on boot, all I can see is the notification light flashing different colors on boot and then a black screen and then reboot. So I never got into the OS itself. Still working on this to see if I can get it to work. I've flashed all of the patches required also. If it is ported for the S4 it should work with our patches right?
uvbeenzaned said:
Just tried the new AOSP 4.3 S4 rom here: http://forum.xda-developers.com/showthread.php?t=2348272 and it seems that the display doesn't show up on boot, all I can see is the notification light flashing different colors on boot and then a black screen and then reboot. So I never got into the OS itself. Still working on this to see if I can get it to work. I've flashed all of the patches required also. If it is ported for the S4 it should work with our patches right?
Click to expand...
Click to collapse
You're not going to be able to install that. It has a different kernel than the one we have on our phones. We can only install roms based off of TW or roms that use Samsungs stock kernels at the moment.
mutatismutandis said:
You're not going to be able to install that. It has a different kernel than the one we have on our phones. We can only install roms based off of TW or roms that use Samsungs stock kernels at the moment.
Click to expand...
Click to collapse
OK wasn't sure what kernel it ran from.
Sent from my Galaxy S4 Active.

[ROM] [4.2.2] Archos 80 Cobalt - CyanogenMod 10.1

CyanogenMod 10.1 working on the Archos 80 Cobalt!
This is oma7144's ROM, I've been able to get it running under a bit of guidace from oma and I thought I'd share it here if anyone else is interested.
The original thread is here - but this ROM is designed for Odys Genio tablet, which has basically the same specs as the 80 Cobalt. (RockChip 3066 chip)
As always, only flash if you know what you are doing, I am not responsible for anything you do or break.
New Version 1.3.4
Thanks danielo83 for putting this zip together
Oma CM10.1 v1.3.4
Battery problem fixed and ROM is now ready for daily use
- CWM 6.0.1.5 recovery
- System ext4
- Internal Storage 2,5 GB
- PhabletUI & Multiuser
- Device spoofed as Nexus
- Ethernet Support
- Init.d support
- USB-Hub enabled
- Gameloft compatible
- Gamepad (PS2, XBox, ...)
- Kernel modules (cifs, tun, lan, serial)
- latest hosts, su, su-binary, busybox
- MX Video-Player, Apollo & FX Sound
- Reboot Menue, CPU Tweaker, Pimp my Rom
- Dateimanager HD (Root)
- Trebuchet & Nova Launcher
Instructions
Before you do anything, download the file below and extract everything to your desktop, find 'Oma RK30 CM10.1 Format NAND.zip' and copy to your externalSD card
then unmount and remove the externalSD, this is very important because if you try to boot after flashing the rom, you will not have access to the internal SD - which means you can't flash files from CWM or do anything basically
Boot to bootloader
Turn off the tablet
Unplug from charger and USB
Hold the 'volume down' button and then hold the 'power button' to turn the device on and boot into bootloader, keep holding both until you see the boot screen
Connect USB and you will get "Unknown Device" message in windows
Install device drivers included in the zip below under x64 or x86 depending on your system - see gavroche's root thread if you are having trouble
Open up RKandroidTool.exe as administrator (located in RKDevelopTool_v1.35 folder)
- if you have trouble try different USB ports on your computer
You should see at the bottom of the RKAndroidTool "Found RK Android Loader Rock USB"
Click 'erase IDB' button - this will only take a few seconds
Now click 'Run' button, this will take a few minutes to install the ROM
Insert your external SD card
The device will boot into CWM, now choose install zip from sdcard (not internal), install Oma RK30 CM10.1 Format NAND.zip that you copied to your external SD earlier
Reboot, and enjoy CM10.1
--------------------------------------------------------
Downloads
http://www.mediafire.com/download/15wh4o4xwhec11o/OMA_4.2.2_CM10.1_Rom.zip
--------------------------------------------------------
What is working
Wifi
Camera
Display
Touchscreen
Battery info showing
...everything apart from mentioned below
Known Problems -
Scren flicker when rotating screen,
When battery is low the tablet wont wake up from sleep and the power button will only reboot it instead of waking it up
- Thanks to danielolsman
- To "fix" this you could install "no sleep" from the play store.
--------------------------------------------------------
If anyone is interested in helping get rid of these three problems please don't be shy.
I'm not a dev and I'm looking at fixing the bugs but don't really know where to start...
Credits
oma7144, gavroche
kage00,
Thanks for your effort!!! You're breathing new life into our tablets. We (I am sure there's a very big community alongwith me) who have been waiting for this.
I don't have my cobalt with me right now but will try and install at some point and feedback how it goes.
Are you also willing to work actively on issues and improvements. I am happy to help wherever I can. Perhaps, others will join in as well.
Thanks
Looking at the forum feedback from HUKD, the rom is not far from being a stable rom for day to day use. I see following general issues raised with this rom so far
1. Waking up issues after deep sleep in case when the battery is low
2. Rotation issues
3. Default language
4. Nexus port and therefore certain apps incompatibility
As mentioned earlier, I am happy to help wherever I can.
Thanks
Hey nikunj87,
Thanks for your support! I would love to be able to work on the issues with this rom but to be honest, I'm not a dev, not even close, and I wouldn't even know where to begin to start fixing the problems.
For the moment I'm looking at putting together a kernel from Archos' source and adding overclocking, I've never built a kernel before so it's a learning curve... don't hold your breath, haha!
I just thought I'd post this rom here to see if we could get some interest in the project and maybe get a dev's (or two's) attention to take a look at the problems, but for the moment it's just you and me who are interested in this..
I think the best we can do is wait for an update to this rom from Oma (the original dev), as you mentioned all the problems with this rom on the cobalt are problems that exist with the same rom on other devices. So maybe with a new update it will work a bit better.
Unless if we can get someone else who knows what they are doing to take a look at it...
kage00 said:
Hey nikunj87,
Thanks for your support! I would love to be able to work on the issues with this rom but to be honest, I'm not a dev, not even close, and I wouldn't even know where to begin to start fixing the problems.
For the moment I'm looking at putting together a kernel from Archos' source and adding overclocking, I've never built a kernel before so it's a learning curve... don't hold your breath, haha!
I just thought I'd post this rom here to see if we could get some interest in the project and maybe get a dev's (or two's) attention to take a look at the problems, but for the moment it's just you and me who are interested in this..
I think the best we can do is wait for an update to this rom from Oma (the original dev), as you mentioned all the problems with this rom on the cobalt are problems that exist with the same rom on other devices. So maybe with a new update it will work a bit better.
Unless if we can get someone else who knows what they are doing to take a look at it...
Click to expand...
Click to collapse
willing to lend a hand tho I am only new to this stuff as well!
I tried this ROM, it seems that OMA posted an AKKU Fix here
I will trie it soon....
There are some problems with the camera; its inverted. The provides fix did not solve the problem, does someone know how to fix it ?
Akku fix does not work
Sent from my Nexus 4 using xda app-developers app
Cool! looks like we've got some attention from the devs!
So there is a new version of this ROM over at this thread
edit ----> please take note, if anyone tests this ROM you will need to keep the same kernel from the existing package in OP and use that to flash with new ROM, Otherwise you risk having a bricked device
Aparently the battery problem exists, but netlars has a possible fix on this thread if anyone can test it that would be great. My tablet is off getting fixed, I had some problems with the touchscreen.
Also Oma was asking if anyone could test this too
Are these paths there?
/sys/devices/platform/rk30-battery/startget
/sys/class/rk30_battery/rk30_battery_start_timer_work
Click to expand...
Click to collapse
If anyone can test and reply here please, then I can tell him on the other thread.
Thanks
Battery problem is solved (see original thread)
CM10.1 is now ready for daily use.
(@Kage00: maybe its possible for you to make a new zip package with the new boot image found here?)
EDIT:
made a zip package myself : CrewRKTablets_RK30_Cobalt 80 by Oma_CM10.1_v1.3.4.zip
Thanks danielo83,
Nice one, I'll update the OP,
I got news back from Archos repair about my tablet / touchscreen problem. They decided to replace the whole unit, so I'm going to sell the brand new one and get a Nexus 7, which means I won't be able to play around with this ROM anymore becuase I won't have the tablet. I'm happy to still keep the thread open and you guys can tell me if there's anything to update in the OP
Thanks
edit----------
In the new version do you still have the screen flicker artifacts on rotate?
danielo83 said:
Battery problem is solved (see original thread)
CM10.1 is now ready for daily use.
(@Kage00: maybe its possible for you to make a new zip package with the new boot image found here?)
EDIT:
made a zip package myself : CrewRKTablets_RK30_Cobalt 80 by Oma_CM10.1_v1.3.4.zip
Click to expand...
Click to collapse
Not sure if anyone will see this but I own an unrooted/untouched Archos 80 Cobalt which I haven't used for months. Decided to dig it out for my son to play with but I can hardly fit any apps on it so looking in to alternative roms.
Came across this rom which I want to flash but I'm unsure on how to start. Do I have to root and flash CWM on to the tablet before doing anything in this thread or are the instructions in this thread all that I need to do in order to flash this rom on to an unaltered tablet?
Yes you will need to be rooted first before using this ROM, please follow this thread to get root and CWM on your tablet then you can flash this ROM with the instructions in the OP
Yeah the storage space is limited for some stupid reason on the stock ROMs, that shouldn't be a problem on this ROM, also if you find you dont like this ROM there is also another custom ROM here based on stock 4.0.4 firmware with better app storage space
the new version still has the rotate "problem".
Sent from my Nexus 4 using xda app-developers app
I just wanted to say as well, that Archos have released kernel sources (downloadable from their website) that are from May or June 2013 from memory. The last stock ROM built for this device was released in February 2013. Which means if anyone wants to try their hand at compiling the kernel from Archos source, it would be a newer kernel than what you are using now and it could possibly fix any left over problems with this ROM. I don't have any spare time to do it anymore, but if anyone was interested I'm sure you could find a walkthrough on XDA to tell you how to do it easily enough.
The kernel for this ROM at the moment is still the stock kernel from the stock 4.0.4 ROM, which is working, but maybe if a newer kernel was made from the sources it may work a lot better
app space and vold.fstab
Does anyone know if this ROM exists with 6gb of app space? I currently have the supersport ROM with 6gb app space and edited the vold.fstab to swap the internal and external sd cards. I’d like to do the same with this JB ROM.
How difficult would it be to edit the ROM to change the app space?
Does this ROM use the vold.fstab to set where the internal and external sd cards are mounted? (I think this has been changed in JB 4.3 but I’m not sure about 4.2.2)
Cheers, T
To be honest I'm not sure if it is possible, but you could ask the devs who made the ROM they would probably be able to tell you if it was possible or not. Have a look over at http://www.arctablet.com
You'd need to ask oma7144 or netlars
You could try to post in this thread and see what they say
kage00 said:
Yes you will need to be rooted first before using this ROM, please follow this thread to get root and CWM on your tablet then you can flash this ROM with the instructions in the OP
Yeah the storage space is limited for some stupid reason on the stock ROMs, that shouldn't be a problem on this ROM, also if you find you dont like this ROM there is also another custom ROM here based on stock 4.0.4 firmware with better app storage space
Click to expand...
Click to collapse
Can you please tell me why I'm getting this error when trying to follow the root instructions from?
http://forum.xda-developers.com/showthread.php?t=2066972
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm using Windows 8.1 64 bit
I'm doing this with USB debugging enabled and the device switched on as this is the only way I can get the 'ARCHOS' device to show in Device Manager under 'Other Devices.
If I put the tablet in to download mode (power + vol down) I get a dead Android symbol with red exclamation, is this normal? However when I insert USB cable in to the device at this point my computer doesn't bring up the 'ARCHOS' device in Device Manager...
All I get then is this:
I don't actually have this tablet anymore, but I remember mine being a bit strange when I first tried to root it too. It can be a bit temperamental... I remember reading someone saying somewhere about leaving the charger plugged in when trying to reboot into download or recovery mode, if that doesn't work try with the USB cable (or both) plugged in while you try.
I also remember with mine I had to direct windows to the specific driver folder extracted from the zip based on which drivers you need, eg, x86 or x64 etc.
You could also look at this thread http://www.freaktab.com/showthread.php?3244-Archos-80-Cobalt-900-supersport-rom where the might be more info on root.
I'm using windows 7 though, so I don't know exactly what differences there are with win 8.
If all else fails just keep searching and reading all/any forums you can find about rooting the thing, I'm sure you'll find that someone has had the same or similar problem
good luck
kage00 said:
I don't actually have this tablet anymore, but I remember mine being a bit strange when I first tried to root it too. It can be a bit temperamental... I remember reading someone saying somewhere about leaving the charger plugged in when trying to reboot into download or recovery mode, if that doesn't work try with the USB cable (or both) plugged in while you try.
I also remember with mine I had to direct windows to the specific driver folder extracted from the zip based on which drivers you need, eg, x86 or x64 etc.
You could also look at this thread http://www.freaktab.com/showthread.php?3244-Archos-80-Cobalt-900-supersport-rom where the might be more info on root.
I'm using windows 7 though, so I don't know exactly what differences there are with win 8.
If all else fails just keep searching and reading all/any forums you can find about rooting the thing, I'm sure you'll find that someone has had the same or similar problem
good luck
Click to expand...
Click to collapse
Hi do you have any idea how to get XBMC working with this rom? XBMC just goes back to home screen whenever i try launching it?
For xbmc you will need an older version of it. The one from August seemed to be the one to use for most people with the same issues on the HP slate 7 so am guessing it will sort your issue too. A quick search on Google should locate the archives for you
Sent from my ARCHOS 80G9 using Tapatalk

[KERNEL][4.4.2][V500] Gpe-ish kernel

So some kernel features through q&a
Does this kernel:
1. Play go fetch? No
2. Has this superduper ***No!
3. So this is like stock kernel but better? Yes, as is more up2date
4. Can it offer me better battery life? It might can yes
5. Can it offer me better performance too? Sure!
6. Can it play games that stock kernel cant? Performance wise they should run better
7. Can i quote this #1 post? No! you can't and you shouldn’t
8. Can i flash it on x,y,z rom? See next line:
For cm11 and compatibles
9.How i flash this? See next line:
As usual flash in recovery
Look at this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Source
Powered by loki flashing script.
Changelog for Rel4
Can you tell us what this Kernel does?
Gamma control?
Under volt?
....
Sent from my SM-N900W8 using Tapatalk
Its just a plain kernel simply updated, wip of course
Sent from my LG-P880 using Tapatalk
Didn't work for me on CM11 1/19, wiped cache and dalvik, flashed kernel then wiped dalvik and cache. Stuck on boot screen and cannot access recovery via power buttons.
Secure booting error
Cause: boot certification verify
You should be able to enter recovery as this only flashes the kernel.
Sent from my LG-P880 using Tapatalk
dont worry about the boot cert error, i already have loki-doki setup ( and a few useless kernel replacement tools) ported if need be/uploaded ( ill get it up after compiling pac), or @Demetris can lokify the boot.img if he wants
Demetris said:
Its just a plain kernel simply updated, wip of course
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
Newb question. If the kernel had no added features what is different from stock kernel
Sent from my LG-V500 using Tapatalk
Canadoc said:
Newb question. If the kernel had no added features what is different from stock kernel
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
to test and eventually port the V510 (GPe Version of the LG G Pad, and probably the better kernel to base on going to kk and beyond) kernel to the v500 so that the Gpe Rom can work fully, Demetris from what i have been see might not have the tablet or the V500 version, so he needs testers to get back at him whether it works or not.
EDIT: @ikenvape if you want to give it another shot flash the zip below, it automatically lokifies and reflashes the boot.img so that you can get passed the error, ill think about setting up a thread on this much later...
Warning though, do not flash it on anything else, as there are no checks whether its a V500 or another device and can brick any other non lokifiable device
Demetris said:
You should be able to enter recovery as this only flashes the kernel.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
Oh man what a ride. Yeah, couldnt get into recovery or reset, the boot error kept popping before i could hit the power button to start the operation. Used lg tools, procedure failed, then ran out of battery on the 2nd go. From there getting into download mode was touch and go. Finally got some juice for another run and was sucessfull according to the pc. The gpad was bootlooping the animation so then I retried manual reset but kept getting 'device needs to be charged more" by this time she was on charge for about an hour. Finally got manual reset to go through and voila. Lost root but not the pad.
Maybe it was a bad flash or d/l which i hope it was, but all in all, it was an entertaining night. Thanks for grabbing this and its definitely progress on the gpe road. :good:
---------- Post added at 03:00 AM ---------- Previous post was at 02:58 AM ----------
darkassain said:
to test and eventually port the V510 (GPe Version of the LG G Pad, and probably the better kernel to base on going to kk and beyond) kernel to the v500 so that the Gpe Rom can work fully, Demetris from what i have been see might not have the tablet or the V500 version, so he needs testers to get back at him whether it works or not.
EDIT: @ikenvape if you want to give it another shot flash the zip below, it automatically lokifies and reflashes the boot.img so that you can get passed the error, ill think about setting up a thread on this much later...
Warning though, do not flash it on anything else, as there are no checks whether its a V500 or another device and can brick any other non lokifiable device
Click to expand...
Click to collapse
Hey thanks man. Ill hold on to it for when i re-root in a bit.
no testers ?
I'am curious to know if it's working or not ( i can't test it for now since i have a week of exams... sure i will test at the end of the week)
Ok guys. i think you must be kidding me.
You scream and yell you want the Gpe Source code fully working on v500 and i see no reports here and only 3 downloads.
Didn’t i ask my self why bother but i do now.
This stays close to public until further notice.
I hope you are happy.
Edit Since the previous post am been getting a lot of pm's and interest on this seems healthy.
Downloads have increased and i know lokified script needs fixing as it doesn’t work now.
So ....
Lets continue the gpe kernel shall we?
Thread re-opened.
Thanks to all xda users for their reports and support on this, i hope for the best :fingers-crossed:
Demetris said:
Ok guys. i think you must be kidding me.
You scream and yell you want the Gpe Source code fully working on v500 and i see no reports here and only 3 downloads.
Didn’t i ask my self why bother but i do now.
This stays close to public until further notice.
I hope you are happy.
Edit Since the previous post am been getting a lot of pm's and interest on this seems healthy.
Downloads have increased and i know lokified script needs fixing as it doesn’t work now.
So ....
Lets continue the gpe kernel shall we?
Thread re-opened.
Thanks to all xda users for their reports and support on this, i hope for the best :fingers-crossed:
Click to expand...
Click to collapse
tried flashing the kernel in the first post with no luck, doesn't even flash so i can't even loki doki it
I'll fix it asap currently busy with slim
Sent from my LG-P880 using Tapatalk
Demetris said:
I'll fix it asap currently busy with slim
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
no rush man just letting you know
Demetris said:
Ok guys. i think you must be kidding me.
You scream and yell you want the Gpe Source code fully working on v500 and i see no reports here and only 3 downloads.
Didn’t i ask my self why bother but i do now.
This stays close to public until further notice.
I hope you are happy.
Edit Since the previous post am been getting a lot of pm's and interest on this seems healthy.
Downloads have increased and i know lokified script needs fixing as it doesn’t work now.
So ....
Lets continue the gpe kernel shall we?
Thread re-opened.
Thanks to all xda users for their reports and support on this, i hope for the best :fingers-crossed:
Click to expand...
Click to collapse
since i you closed this thread without being able to voice my thoughts, i honestly believe that you pulled the plug a little too early, not only are we a small bunch of users compared to nexus and other tablet makers counterparts, but its it feels like there was no marketing at all, just word of mouth and a few publications pushing reviews (which i still dont understand how only one review noticed the few screen issues most have noticed),
sorry for OT, back on topic since i have the device ill take a look at your zip and see if ill be able to fix it...
EDIT: Took a quick look at the script and it seems the loki tools and script arent in the zip, simple fix which im uploading now
EDIT2: @thoughtlesskyle try it now...
darkassain said:
since i you closed this thread without being able to voice my thoughts, i honestly believe that you pulled the plug a little too early, not only are we a small bunch of users compared to nexus and other tablet makers counterparts, but its it feels like there was no marketing at all, just word of mouth and a few publications pushing reviews (which i still dont understand how only one review noticed the few screen issues most have noticed),
sorry for OT, back on topic since i have the device ill take a look at your zip and see if ill be able to fix it...
EDIT: Took a quick look at the script and it seems the loki tools and script arent in the zip, simple fix which im uploading now
EDIT2: @thoughtlesskyle try it now...
Click to expand...
Click to collapse
still getting a binary error
thoughtlesskyle said:
still getting a binary error
Click to expand...
Click to collapse
whoops didnt upload the right edited one...
one last try
darkassain said:
whoops didnt upload the right edited one...
one last try
Click to expand...
Click to collapse
Giving it a go now, trying the Gpe Rom hopefully this fixes it (I got a feeling there is little chance)
Sent from my HTCONE using Tapatalk
thoughtlesskyle said:
Giving it a go now, trying the Gpe Rom hopefully this fixes it (I got a feeling there is little chance)
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
i believe some of ricardos patches need to be reverted before that, this is mainly a base to build off for @Demetris

[ROM] Community Note 7 Port, Stock, N930VVRS2APHE, De-odexed [5/14/18]

I have decided to release my Verizon Note 7 port ROM for the public so that those of you wanting the best software features available for your Note 4, can have a good ROM base to work with. This ROM is not 100% finished but it is working for the most part. Calls, texts, wifi, bluetooth, etc is all working as far as I know. The purpose of this ROM and this thread is to give the XDA Community a base ROM to work with. I want you all to work together to find and fix bugs and share your knowledge here in this thread so that you can all help get this rom across the finish line. I feel it's the least I can do for all of you who have shown your enthusiasm and support to me. So here it is. I will try to make this OP short and straight to the point.
***You MUST wipe all partitions on your phone AND wipe internal storage before flashing this ROM. So make backups as needed. There are data folders from previous ROM's that MUST be deleted from your internal storage AND your SD card. Make sure you delete the "Android" folder in both locations before flashing this ROM! Failure to do this will result in isues with the ROM. You also need to make a complete backup of any stock Note 4 ROM including the modem and EFS using the latest Note 4 firmware and stock Note 4 ROM which you can find here in the development forum. (kevintm78 has a stockish Note 4 ROM that will serve this purpose). Again, backup EVERYTHING using the backup feature in TWRP and include EFS.***
I'm not going to break down the necessary steps for unlocking your bootloader and flashing a custom recovery. I expect you all should know how to do this before attempting to flash ROM's anyway. This ROM is 100% stock including 99% of the original Verizon bloat apps. The ROM is based off of the Verizon Note 7 N930VVRS2APHE software as well as the Verizon Note 4 firmware, libs and modules as necessary. It includes FlashPoint V4 kernel by kevintm78. So expect a stock ROM experience and expect minor bugs that can be sorted out easy enough with libs, apk's and simple xml edits here and there. You'll need to search around here at XDA for information, tips and files that will help you fix bugs. Upon flashing this ROM you may not be able to receive text messages. If this happens you will need to flash the FlashPoint V3 kernel for Note 7 port ROM's. You can find the FlashPoint Note 4 kernels here at XDA. This was reported to fix that bug. Pay attention and download the correct kernel version for this port ROM. Other than that, you all will need to get together and start figuring out the minor bugs and share your findings here so others can make the necessary adjustments to the ROM.
The person who shows the most activity and interest as well as his/her contribution to this ROM will be made contributor so that he or she can edit this ROM thread, add fixes, etc. I will be watching this thread from time to time and can offer some assistance, advice and knowledge from time to time. You can PM me, but only if you can't find answers here in this thread or elsewhere on XDA.
Donations are not mandatory but are very much appreciated! I spent a LOT of time putting this ROM together for you all to enjoy. Use the donate link next to my avatar in any of my posts. Please share your feedback and bug solutions about the ROM so we can get the ROM updated as you guys find fixes. Post in this thread and above anything else, please keep this thread respectful and please don't be rude or hateful to others. Everyone has something to offer and this is why I want you all to have this ROM to work with on your free time. Have fun and share knowledge as I have done!
DOWNLOAD​
XDA:DevDB Information
Community Note 7 Port ROM, ROM for the Verizon Samsung Galaxy Note 4
Contributors
tx_dbs_tx
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: CQI2 or later
Based On: Stock Samsung Odin Package
Version Information
Status: Testing
Created 2018-05-14
Last Updated 2018-05-14
Reserved
Reserved
Thanks for making this available to all!:good:
For all those wondering, this is the same ROM from the previous thread.
https://forum.xda-developers.com/note-4-verizon/general/rom-coming-soon-t3746380
I don't have the skills yet to help with maintaining the ROM, but I can sure test it and provide feedback.
Thanks again for all who help on this:highfive:
I've installed this rom and played with it for a some time now.
Upon initial installation, the phone dialer would freeze after one use, requiring a reboot and text messaging would not work. Both of those issues where resolved with the OP suggestion of the kernel change. I used the v3.1 for port and root successfully.
I put in most of the apps I use and all seem to run fine. Admittedly, I really don't use anything exotic in the app department. Email, file explorer, maps, nova launcher, sports apps, trip advisor type stuff. All run great.
This rom really is very nice.
The real issue for me is VoLTE. While the settings suggest Advanced Calling features are activated, they in fact do not work. As most of you know, this is typical in custom roms. I spent 50-100 hours (no joke) trying to find a simple solution, as I do not possess developer skills, and came up dry. I really wanted to use this rom as my daily driver, but this is a deal breaker for me due to personal hearing issues. For this reason I am moving on to try other things on this phone, which is a spare/hobby unit.
I will keep a backup copy of this rom on my sd card and would be willing to test something out if someone needs a tester. Should someone indeed get VoLTE working on this rom, I would enthusiastically run it as my daily driver. Good luck.
I'm just going to grab a post here at the beginning of the thread so I can update it later on.
good job!!
you do very well. I hope to be able to use it soon. I think Note 8 is also a good idea
zaibuchan said:
you do very well. I hope to be able to use it soon. I think Note 8 is also a good idea
Click to expand...
Click to collapse
The Note 8 and S8 runs Android 7.0 Nougat. Without a Nougat compatible kernel, we can't port either of these softwares from the N8 or S8. The Note 4 was only updated to Android 6.0 Marshmallow. However there are some ported apps from these devices that can be used. This is what people need to test with this ROM.
After minor hiccup with 2 step varificarion due to texts not arriving (fix in OP), I am very excited about this new DD. Besides the obvious issue with fingerprint, I'm not seeing any major bugs. Other than perhaps a DPI issue with dialer (could be caused by battery saving) I'll update
Update1: GPS boked. Not sure if it's from something I did or if it's a bug. I will look at it again when I have time to test
On the kernel side I had to switch from MPdecision to MSMhotplug to have some of my cores go offline. I'll update
As for battery/wakelocks I'll update when I get some reliable data.
Thank you immensely to you and the rest of the devs still supporting this device. I'll be sending donations to all.
gserp4sox said:
I've installed this rom and played with it for a some time now.
Upon initial installation, the phone dialer would freeze after one use, requiring a reboot and text messaging would not work. Both of those issues where resolved with the OP suggestion of the kernel change. I used the v3.1 for port and root successfully.
I put in most of the apps I use and all seem to run fine. Admittedly, I really don't use anything exotic in the app department. Email, file explorer, maps, nova launcher, sports apps, trip advisor type stuff. All run great.
This rom really is very nice.
The real issue for me is VoLTE. While the settings suggest Advanced Calling features are activated, they in fact do not work. As most of you know, this is typical in custom roms. I spent 50-100 hours (no joke) trying to find a simple solution, as I do not possess developer skills, and came up dry. I really wanted to use this rom as my daily driver, but this is a deal breaker for me due to personal hearing issues. For this reason I am moving on to try other things on this phone, which is a spare/hobby unit.
I will keep a backup copy of this rom on my sd card and would be willing to test something out if someone needs a tester. Should someone indeed get VoLTE working on this rom, I would enthusiastically run it as my daily driver. Good luck.
Click to expand...
Click to collapse
Did you try the fix here?
https://forum.xda-developers.com/no...dvanced-calling-fix-hd-calling-video-t3524339
sam298 said:
Did you try the fix here?
https://forum.xda-developers.com/no...dvanced-calling-fix-hd-calling-video-t3524339
Click to expand...
Click to collapse
Yes. Didn't work.
i'm testing.
There are quite a lot of verizon apps (I do not like this)
When busy wifi hosport does not show up
still not announced sim card not from verizon
I have not checked much yet. thank you
1
1
Thanks so much for this great port rom, is the best ported rom for note 4 tested so far, my experience with rom bring about the ffg bug.
1. App sort (from A-Z) not stable.
2. occasionally suck battery on standby while no app running.
3. fingerprints error.
4 blur camera.
5. weather forecast doesnt automatically updated.
6. pop up dialog msg of "mobile data" whenever turn off data annoying.
7. screen brightness minor bug.
8. Reinstall photos error msg dialog.
everybody might not experience these but it could be look into before the next version is out.
tx_dbs_tx said:
I have decided to release my Verizon Note 7 port ROM for the public so that those of you wanting the best software features available for your Note 4, can have a good ROM base to work with. This ROM is not 100% finished but it is working for the most part. Calls, texts, wifi, bluetooth, etc is all working as far as I know. The purpose of this ROM and this thread is to give the XDA Community a base ROM to work with. I want you all to work together to find and fix bugs and share your knowledge here in this thread so that you can all help get this rom across the finish line. I feel it's the least I can do for all of you who have shown your enthusiasm and support to me. So here it is. I will try to make this OP short and straight to the point.
***You MUST wipe all partitions on your phone AND wipe internal storage before flashing this ROM. So make backups as needed. There are data folders from previous ROM's that MUST be deleted from your internal storage AND your SD card. Make sure you delete the "Android" folder in both locations before flashing this ROM! Failure to do this will result in isues with the ROM. You also need to make a complete backup of any stock Note 4 ROM including the modem and EFS using the latest Note 4 firmware and stock Note 4 ROM which you can find here in the development forum. (kevintm78 has a stockish Note 4 ROM that will serve this purpose). Again, backup EVERYTHING using the backup feature in TWRP and include EFS.***
I'm not going to break down the necessary steps for unlocking your bootloader and flashing a custom recovery. I expect you all should know how to do this before attempting to flash ROM's anyway. This ROM is 100% stock including 99% of the original Verizon bloat apps. The ROM is based off of the Verizon Note 7 N930VVRS2APHE software as well as the Verizon Note 4 firmware, libs and modules as necessary. It includes FlashPoint V4 kernel by kevintm78. So expect a stock ROM experience and expect minor bugs that can be sorted out easy enough with libs, apk's and simple xml edits here and there. You'll need to search around here at XDA for information, tips and files that will help you fix bugs. Upon flashing this ROM you may not be able to receive text messages. If this happens you will need to flash the FlashPoint V3 kernel for Note 7 port ROM's. You can find the FlashPoint Note 4 kernels here at XDA. This was reported to fix that bug. Pay attention and download the correct kernel version for this port ROM. Other than that, you all will need to get together and start figuring out the minor bugs and share your findings here so others can make the necessary adjustments to the ROM.
The person who shows the most activity and interest as well as his/her contribution to this ROM will be made contributor so that he or she can edit this ROM thread, add fixes, etc. I will be watching this thread from time to time and can offer some assistance, advice and knowledge from time to time. You can PM me, but only if you can't find answers here in this thread or elsewhere on XDA.
Donations are not mandatory but are very much appreciated! I spent a LOT of time putting this ROM together for you all to enjoy. Use the donate link next to my avatar in any of my posts. Please share your feedback and bug solutions about the ROM so we can get the ROM updated as you guys find fixes. Post in this thread and above anything else, please keep this thread respectful and please don't be rude or hateful to others. Everyone has something to offer and this is why I want you all to have this ROM to work with on your free time. Have fun and share knowledge as I have done!
DOWNLOAD​
XDA:DevDB Information
Community Note 7 Port ROM, ROM for the Verizon Samsung Galaxy Note 4
Contributors
tx_dbs_tx
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: CQI2 or later
Based On: Stock Samsung Odin Package
Version Information
Status: Testing
Created 2018-05-14
Last Updated 2018-05-14
Click to expand...
Click to collapse
This rom is really good only having problem with connecting to my Bluetooth controller it say Bluetooth share unfortunately stopped when I use a gamesir app any way to fix this?
aliurahmon said:
Thanks so much for this great port rom, is the best ported rom for note 4 tested so far, my experience with rom bring about the ffg bug.
1. App sort (from A-Z) not stable.
2. occasionally suck battery on standby while no app running.
3. fingerprints error.
4 blur camera.
5. weather forecast doesnt automatically updated.
6. pop up dialog msg of "mobile data" whenever turn off data annoying.
7. screen brightness minor bug.
8. Reinstall photos error msg dialog.
everybody might not experience these but it could be look into before the next version is out.
Click to expand...
Click to collapse
Do you know how to fix that
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Media Option in Bluetooth Missing
Thankyou for this rom. I have been using this for 3 days now and i have noticed that when connecting a bluetooth device that there is no option to connect bluetooth via media.. and i still can not get Netflix working after trying multiple apk. Can you give me some tips. thankyou
I fixed Bluetooth, gps, photo editor, slow motion editor. I need help fixing the Wi-Fi tethering. That's the last bug i have encountered encounter im going to post a link to the om tomorrow been trying to get Wi-Fi going. Need to recompile rom.
---------- Post added at 11:26 AM ---------- Previous post was at 11:23 AM ----------
No sleeeep
---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------
d1876j said:
This rom is really good only having problem with connecting to my Bluetooth controller it say Bluetooth share unfortunately stopped when I use a gamesir app any way to fix this?
Click to expand...
Click to collapse
To fix the Bluetooth grab the Bluetooth file from system/lib/hw from a Rom that works and place it using root explorer. In the same area and change permissions and reboot. Same with GPS it will fix.
d1876j said:
This rom is really good only having problem with connecting to my Bluetooth controller it say Bluetooth share unfortunately stopped when I use a gamesir app any way to fix this?
Click to expand...
Click to collapse
https://drive.google.com/file/d/1trThqjQWoEVNmoaAehU95AsVFOc7pRkr/view?usp=drivesdk
---------- Post added at 05:41 PM ---------- Previous post was at 05:41 PM ----------
https://drive.google.com/file/d/1trThqjQWoEVNmoaAehU95AsVFOc7pRkr/view?usp=drivesdk

Categories

Resources