Is there a near 100% working android rom for the sprint touch pro?
been looking through some pages but cant find anything solid.
Short answer: no.
Reason: The only Android version for the Touch Pro (RAPH 800) is the xdandroid branch of development. As far as I know, NAND support isn't being heavily researched yet as there are still a couple show stoppers before they move to that.
1. Camera
2. Accurate battery metering (wildly inaccurate currently)
This is the newest and feature-completed version for the 800 (Froyo):
http://forum.xda-developers.com/showthread.php?t=711692
This is the most feature complete Eclair version:
http://forum.ppcgeeks.com/showthread.php?t=104276
does the tp have to be unlocked to run off of SD?
if so, can it be unlocked without flashing of rom and keeping current wm6.1 intact?
answer: no
Code:
[COLOR="gray"]
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
[/COLOR]
Prerequisites for Installation
- Backup your existing ROM in case you want to go back
- Must have the 4.5.3 bootloaders loaded
- Must have TWRP access
Fresh Installation
- From your recovery perform a Factory Reset
- Flash the ROM File
- Flash SuperSU if you want root access
- Flash Open Gapps of your choice.
- Reboot and enjoy!
Downloads
*** Please do NOT create any mirrors ***
- lineage-11.0 for Amazon Fire HD6 and HD7 2014 Tablet
Source Code
- Kernel Source: Ariel stock kernel, build number update-kindle-20.4.5.5_user_455002120
XDA:DevDB Information
Lineage-11.0 Fire HD6&7, ROM for the Amazon Fire HD 6 and 7
Contributors
ggow
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.10.x
Based On: Cyanogenmod
Version Information
Status: Testing
Created 2015-12-13
Last Updated 2019-10-18
Release Notes / Changelog
14 Oct 2019
- Security patches up to and including February 2019
- Bluetooth works
17 Oct 2016
- Ported Google's October 2016 security patches.
18 Sep 2016
- Security Patches Up to and including September 2016
- Some OMX features fixed
- Youtube Fixed
- VLC now plays HD video
12 May 2016
- Security Patches Up to and including May 2016
- Updated CM-11 Code
11 Jan 2016
- Set DPI to 252
- Add launcher rotation setting to build.prop (enabled by default)
- Add lock screen rotation setting to build.prop (enabled by default)
- 01 January 2016 AOSP security patches included
- Updated CM-11 Code
13 Dec 2015
- Initial Release
Reserved
New Build is Up
- Dated 13 Dec 2015
- Initial Release
- Links are now up
I will be trying this out as soon as I can.
Just a quick question: why CM11 and not CM12+? Was it because of kernel limitations?
Regardless, thanks immensely for your time. Hopefully it works. Cheers mate
Remolten said:
I will be trying this out as soon as I can.
Just a quick question: why CM11 and CM12+? Was it because of kernel limitations?
Regardless, thanks immensely for your time. Hopefully it works. Cheers mate
Click to expand...
Click to collapse
- Yes you're right, went for CM-11 it's easier due to having a working recovery
- I thought about CM-12 but the risk is high of producing a bricked device
- If you flash a non-working 5.1.1 system and haven't got a recovery which you can reflash with then instant brick
ggow said:
- Yes you're right, went for CM-11 it's easier due to having a working recovery
- I thought about CM-12 but the risk is high of producing a bricked device
- If you flash a non-working 5.1.1 system and haven't got a recovery which you can reflash with then instant brick
Click to expand...
Click to collapse
Cool! Trying it out later today.
nice work,thanks:good:
Very awesome to see the first ROM. Great job!
Sent from my KFARWI using Tapatalk
Installed successfully! Thanks mate! Much faster than the Amazon Lollipop, and more storage free!
Worth noting that xposed does not work, as well as videos, camera, and bluetooth. Lots of issues with Google Now crashing as well. Seems pretty buggy atm, but definitely feels great—a speedy upgrade over the amazon stock.
Nice! I hope it becomes official. (If that's how it works )
BTW I can confirm that Stock GApps have enough space to install, compared to the stock Amazon system.
EDIT: REALIZED I SHOULD HAVE EDITED MY LAST POST INSTEAD
Remolten said:
Installed successfully! Thanks mate! Much faster than the Amazon Lollipop, and more storage free!
Worth noting that xposed does not work, as well as videos, camera, and bluetooth. Lots of issues with Google Now crashing as well. Seems pretty buggy atm, but definitely feels great—a speedy upgrade over the amazon stock.
Click to expand...
Click to collapse
- I'll fix xposed for the next release
- I'm preparing to take a run at the next release shortly
ggow said:
- I'll fix xposed for the next release
- I'm preparing to take a run at the next release shortly
Click to expand...
Click to collapse
Sounds good! Looking forward to testing it!
ggow said:
- I'll fix xposed for the next release
- I'm preparing to take a run at the next release shortly
Click to expand...
Click to collapse
Can't wait
Sent from my KFARWI using Tapatalk
Wow It's amazing I flash it in a Fire HD7 and change dpi to 213 and it's perfect!
I can try CM12 on a tablet that I have to return. Nothing happens if it bricks
Enviado desde mi SM-N910F mediante Tapatalk
ggow said:
- Yes you're right, went for CM-11 it's easier due to having a working recovery
- I thought about CM-12 but the risk is high of producing a bricked device
- If you flash a non-working 5.1.1 system and haven't got a recovery which you can reflash with then instant brick
Click to expand...
Click to collapse
ggow, you can flash cm12 with 4.5.3 bootloader and twrp and next flash 5.1.1 bootloader and Amazon stock recovery in case of brick you can flash a original rom by sideload the brick risk is null.
Sorry for my english
3 Days Testing Report
Firstly, i really appreciate for your work, ggow! That's the best first build what i'd ever tested, so smooth, didn't expected such a nice performance. Successfully installed SuperSU and GApps (pico). Picked up flash drive to OTG, worked perfectly, not worse then in Fire OS. With disabled lockscreen, my Fire wakes up and locks impressively fast. Made a proper wifi speedtests and very satisfied - speed is increased, compared to Fire OSes (4.x and 5.x) - from 43 mbps (max) to 51 mbps (max) with my cheap 741nd home router. All's ok with Spotify. As described, Youtube isn't working, Bluetooth service is crashing after boot. Tried few camera apps and it still cannot take photo. There is an areas, what you may look to focus on. Audio output is extremely low with headphones, tried different ones, from speaker volume is normal. Audio recording seems not working. In MXPlayer, HW video decoding isn't working. Also, there are rebooting problems - it performs not every time, rebooting to recovery isn't performs for me at all (Fire is just shuts down), interface rebooting is ok. I'm exited for the next builds. I think it's good that you develop CM11 Rom, because higher versions are not that good on low memory devices like this, and yes, 872 mb is not a big amount in 2015. Would be good to see newer versions in the future, but i'm still very happy with KitKat!
Firmware_Addicted said:
Firstly, i really appreciate for your work, ggow! That's the best first build what i'd ever tested, so smooth, didn't expected such a nice performance. Successfully installed SuperSU and GApps (pico). Picked up flash drive to OTG, worked perfectly, not worse then in Fire OS. With disabled lockscreen, my Fire wakes up and locks impressively fast. Made a proper wifi speedtests and very satisfied - speed is increased, compared to Fire OSes (4.x and 5.x) - from 43 mbps (max) to 51 mbps (max) with my cheap 741nd home router. All's ok with Spotify. As described, Youtube isn't working, Bluetooth service is crashing after boot. Tried few camera apps and it still cannot take photo. There is an areas, what you may look to focus on. Audio output is extremely low with headphones, tried different ones, from speaker volume is normal. Audio recording seems not working. In MXPlayer, HW video decoding isn't working. Also, there are rebooting problems - it performs not every time, rebooting to recovery isn't performs for me at all (Fire is just shuts down), interface rebooting is ok. I'm exited for the next builds. I think it's good that you develop CM11 Rom, because higher versions are not that good on low memory devices like this, and yes, 872 mb is not a big amount in 2015. Would be good to see newer versions in the future, but i'm still very happy with KitKat!
Click to expand...
Click to collapse
Just to let you know, even though the Youtube app doesn't work, the website does, and it works pretty well. (Using Chrome here)
Thank you for doing this. I actually use your Apollo ROMs for myself. FireOS is garbage, but I wasn't willing to destroy one of the kid's devices while I muddled around. This gives me hope!
My device
Brand: O+ (Not a popular brand) search their site type Oplususa.com since I still can't post outside links
Model: 8.17
OS: 4.4.2 KK
Cores: 6 (hexa)
Custom Recovery: TWRP 2.8.2.0
MediaTek6591
Rooted
I've just ported a custom rom called Mystic OS to my phone's stock rom even though the rom is made for a device running on mtk6592 I still take the risk to flash it on my device. Luckily it worked but has a lots of bugs like can't use wifi, bluetooth, can't detect sd card etc. But I fixed this bugs by reading on some forums, but the only problem that I can't solve is the resolution of my camera, my camera should be in 8 mp but in this custom rom I think it is about 2 mp, it is said in the source of this custom rom that it may affect camera and the only solution is to go back to the stock rom of my device, But I don't want to go back to my stock rom because it performs poorly compared to this rom that I flashed, I think there is a solution in this problem probably a simple fix on some scripts in the system files I just don't know, I tried flashing some camera resolution enhancements from this site but still can't fix the problem , Any help will be appreciated thanks in advance
Help me,please.
My Le Max 2 became not able to work Camera AutoFocus suddenly.
But it can take photos.
Focus became rigid.
I entered android secret code *#*#34971539#*#* few days ago.
I wanted to see Detailed camera information.
But nothing happend when I entered that secret code.
Is it affected this situation?Was Camera firmware broken?Or was camera hardware broken?
I asked this issue at indian Le forum.
There is one who have met same issue.He also entered that code and his camera also became not able to work Autofocus.
He said"I updated the ROM to the leaked 829 US version and camera is ok again"
After that, I also tryed to flash 829 US ROM with wipes system,data,cache,dalvic.
But nothing changed...
My camera dosen't work Autofocus yet.
If camera firmware was broken when I entered that code, are there any way to fix it?
Do you know Where the camera firmware is?
Is the camera firmware in any phone's partitions?
Sorry,I would like XDA users to help me...
chatmonchy said:
Help me,please.
My Le Max 2 became not able to work Camera AutoFocus suddenly.
But it can take photos.
Focus became rigid.
I entered android secret code *#*#34971539#*#* few days ago.
I wanted to see Detailed camera information.
But nothing happend when I entered that secret code.
Is it affected this situation?Was Camera firmware broken?Or was camera hardware broken?
I asked this issue at indian Le forum.
There is one who have met same issue.He also entered that code and his camera also became not able to work Autofocus.
He said"I updated the ROM to the leaked 829 US version and camera is ok again"
After that, I also tryed to flash 829 US ROM with wipes system,data,cache,dalvic.
But nothing changed...
My camera dosen't work Autofocus yet.
If camera firmware was broken when I entered that code, are there any way to fix it?
Do you know Where the camera firmware is?
Is the camera firmware in any phone's partitions?
Sorry,I would like XDA users to help me...
Click to expand...
Click to collapse
did you fix it?if yes,how?I have the same problem.
Code:
*#*#34971539#*#* - This code is used to get information about phone camera. It shows following 4 menus:
* Update camera firmware in image (Don't try this option)
* Update camera firmware in SD card
* Get camera firmware version in LeEco Le Max 2
* Get firmware update count
WARNING: Never use the first option otherwise your phone camera will stop working and you'll need to take LeEco Le Max 2 to service center to reinstall camera firmware.
As above, you probably need to have LeEco repair it.
flash stock eui 19s it will start working
I have a Samsung Galaxy A3 2016 (SM-A310F), and basically I need to configure the device so that it uses an OTG connected UVC webcam instead of its rear camera. In this application, it's not enough to simply get the webcam working - it needs to fully replace the rear camera (or front camera).
Several others have accomplished this with different android devices - unfortunately I can't provide links as a new user, but you can find them by googling 'android uvc nvcamera.conf'. These devices have support for UVC devices by default, so they simply modified the contents of the configuration file /etc/nvcamera.conf to assign the rear camera to use /dev/video0.
This is more complicated on a Samsung phone like the A3, because it lacks kernel UVC support by default and does not have an /etc/nvcamera.conf file. I've compiled a custom kernel for the SM-A310F with UVC support and that is working nicely, but I can't figure out how to set /dev/video0 as the rear camera device. I've tried adding an /etc/nvcamera.conf file but the system ignores it - the device assignments for front and rear cameras must be handled somewhere else, but I haven't figured out where.
Does anyone know where camera configuration files would be on a Samsung device? Am I on the right track here? I'm sure it would be much easier to use an AOSP or Cyanogenmod image but unfortunately they aren't available for the SM-A310F (yet).
Extra info:
Device: Samsung Galaxy A3 2016
Model No: SM-A310F
Android Version: 6.0.1
Kernel Version: 3.10.61 (custom built)
Device is rooted
TWRP installed
need advice too for this problem
usb camera as rear camera on all apps